Oh, i haven't really talked about zerolith on this thread, so i'll give you a basic idea.
Zerolith attempts, at every possible angle, to make programming faster, easier, and more powerful... while helping the programmer help find bugs and identify fat parts of the code the entire way.
It includes an onscreen debug bar and profiler, both which were heavily designed for readability and relevance. The debugger is optimized to the hilt so that having it by your side doesn't bring any downsides.
Here's the template library in action. It works kind of like a win32 GUI api and way less like traditional templating systems in PHP.
Notice the lack of instantiation? i'm using static classes, and static variables are serving as the 'memory' of the ZLT class.
The code on the left is what's used to generate what's on the right.
The code can define all parameters of the look and feel of what's being created, even though the syntax is very short.
Here's another example. This is a simple mailing list unsubscribe script. In the database read, we allow a little unsafe SQL only because we've sanitized the string before starting, but in the db::writeRow() function, we're taking an associative array and writing it with an automatically generated parameterized query, which is SQL injection safe. Of course, you can also do parameterized reads too, but the syntax is much longer and might resemble a painful to work with database library you remember, lol.
The best thing about the framework is that it doesn't care how you do things. It doesn't impose a structure or way to use it. It attempts to act as a global function library, so we can toss the need for instantiation, dependency injection, and other fun things that make writing object oriented code kind of a nightmare.
What do you think of the idea of working with it?
Zerolith attempts, at every possible angle, to make programming faster, easier, and more powerful... while helping the programmer help find bugs and identify fat parts of the code the entire way.
It includes an onscreen debug bar and profiler, both which were heavily designed for readability and relevance. The debugger is optimized to the hilt so that having it by your side doesn't bring any downsides.
Here's the template library in action. It works kind of like a win32 GUI api and way less like traditional templating systems in PHP.
Notice the lack of instantiation? i'm using static classes, and static variables are serving as the 'memory' of the ZLT class.
The code on the left is what's used to generate what's on the right.
The code can define all parameters of the look and feel of what's being created, even though the syntax is very short.
Here's another example. This is a simple mailing list unsubscribe script. In the database read, we allow a little unsafe SQL only because we've sanitized the string before starting, but in the db::writeRow() function, we're taking an associative array and writing it with an automatically generated parameterized query, which is SQL injection safe. Of course, you can also do parameterized reads too, but the syntax is much longer and might resemble a painful to work with database library you remember, lol.
The best thing about the framework is that it doesn't care how you do things. It doesn't impose a structure or way to use it. It attempts to act as a global function library, so we can toss the need for instantiation, dependency injection, and other fun things that make writing object oriented code kind of a nightmare.
What do you think of the idea of working with it?
