Ehm, still those benchmarks filesystems are optimized for. Please try blogbench in order to make filesystem really hurt like they would do for a file server.
GPL. So BSD coders will have to rewrite it from scratch.
This is better than nothing, but worse than good documentation and worse than a BSD driver (that could be merged to BSD and GPL licensed operating systems).
Before someone nitpicks: ZeroMQ is not really a messages broker, messages are directly sent to the recipient without passing through any broker and this is what makes ZeroMQ different and fast. But the end result is that you get the same features as a messages broker, just faster and easier.
ZeroMQ is still under development though. But it really needs more exposure.
PHP ? Real OO? Thanks for the great joke. How can I add methods to Number? Ehm you know, the class used for numbers... In order to write 3.times() for instance... ah, it doesn't exist? Ok, so how can add methods to strings? Impossible, strings aren't objects either?
Stop kidding.
Why do PHP programmers use classes for? Just to avoid collisions between two functions with the same name when files are included. Really... very few PHP code instanciates more than one object per class.
Introduction of namespaces might limit this.
But there's something else that PHP miss: a "static" keyword.
Guess how very large source code like OS kernels or demos have been built in C or assembler, without namespaces, without classes, without symbols like \, but without coders constantly fighting about names collisions?
The reason is file-local symbols, ie. the static keyword in C (and local symbols in assembler). Only export (ie. make non-static) what you need to use in other files. As a bonus, it helps the compiler in order to optimize the code.
If the programmer needs to refactor its code because of stupid restrictions of a language, the language just sucks as it makes the programmer waste time.
Please try to make coroutines with PHP 5.2. Oh you can't? It's impossible without being horrible kludged, complex and slow? Oh, of course, without anything like GOTO or setjmp/jmplong. So keep refactoring your code, and think that your code would already be running if you had GOTO.
GOTO is what your CPU is actually doing 80% of the time. You can pump up your ego by imagining that using a language without something explicitely called "GOTO" makes your code "up with the time". But what you actually do is nothing but GOTOs, just written in a different manner.
Ironically, the VM that PHP uses is completely GOTO-based (well, you can pick several methods at compile-time, but GOTO is what a lot of distributions chose because performance is often better than CALL and it's very stable nowadays).
Oh and even JAVA has GOTO and relies a lot on it. The compiler hides an explicit thing called "GOTO", but what you get after compilation is full of GOTO. And it's actually why apps can actually do something.
Laughing at "GOTO" is ignorance, or just blind trolling because you read somewhere that BASIC had a "GOTO" keyword. I guess in a few years your children will laugh at those horrible "$", "$this", "->", ":" and "\" symbols, that would remind them the old time of a language called PHP. Though you are proud of them now.
Using temporary variables like "$should_exit", dummy loops just to "break" at the right place, or named loops to work around "break" that would only exit the first loop is nothing but writing "GOTO" in an obfuscated and inefficient way. "GOTO" is not synonym for "spaghetti code" (the famous keyword always used by people blindly repeating that GOTO is bad).
Nowadays, anyone who wants to discover a new operating system wants to try a live CD first.
Although there were other live OpenBSD CDs (like OliveBSD), yet another one, especially based upon something original like Enlightenment, is a great thing.
OpenBSD is often described as a server-only (or network-stuff-only) operating system. Actually, it can also be a decent desktop OS.
I'm using OpenBSD on my primary workstation for 7 years and I'm quite happy with it. The only thing I *really* miss, especially as a web developper, is the lack of Flash support (except crappy support with Opera). nspluginwrapper + linux emulation is still as stable as nitroglycerine.
You don't need to seek 10000 times for the same element. You can look it up *once* and store it. Avoiding useless DOM traversal is the basic of javascript optimization.
If your visual effects depends on traversing 10000 times the DOM in order to always find the same node, something is seriously broken in your code, not in the framework.
Also songratulations to everybody who has worked on Prototype!
I have used Prototype extensively and it is easy to learn and easy to handle. In fact, I had been using JavaScript for quite a while before Prototype, but after I started using Prototype, read some source, wrote a few plugins, etc. (even some patches, including performance related ones), I feel my understanding of the weird and advanced things in JavaScript is also much much better - and it didn't require any hard work or thinking:)
In comparison, before Prototype I used Dojo, which still gives me a headache just to think about. This is now some time ago though, so I will not bash Dojo as it's quite likely my specific problems with it have long been solved. However, Dojo never 'invited' me to become better at JavaScript myself.
All in all, Prototype is a great tool, it makes JavaScript fun again, and it makes me feel sorry I'm hardly doing any webdevving anymore (imagine that!)
jQuery is a great tool, too. It all depends on the application you are working on.
It would be a very stupid reason to pick a framework over another one.
Your link shows results from a benchmark. What does that benchmark? It just benches the speed of selectors.
It tries tons of times to fetch DOM nodes from a fixed definition like "a A in a P in a DIV".
If your application heavily depends on the framework's ability to fetch 10000 times the same element the same way, there's something really wrong with it.
I can't understand how Javascript frameworks can be compared using such a benchmark.
Moreover the Selectors API is coming to browsers, so this is going less and less significant. Prototype 1.6.0.3 (released today) supports it, every other frameworks will soon do.
The real difference between frameworks in the time you need to build the app you need with them.
When it comes to playing with the DOM and building visual components, jQuery is great.
When it comes to working with data structures, Prototype fits like a glove, way much than jQuery.
Slashdot Mirror
Ehm, still those benchmarks filesystems are optimized for. Please try blogbench in order to make filesystem really hurt like they would do for a file server.
Too bad that they used an old version of Prototype. Version 1.6.0.2 didn't support querySelectorAll(), that Safari has for a long time.
GPL. So BSD coders will have to rewrite it from scratch.
This is better than nothing, but worse than good documentation and worse than a BSD driver (that could be merged to BSD and GPL licensed operating systems).
Come on. Your production system costs $10,000 a minute if a service is down, and you have NO REDUNDANCY?
You can't turn off a single server without bringing down a critical service that costs $10,000 a minute?
$10,000 a minute a no HA? Flicking a switch? Is it how you manage HA on a system that costs $10,000 a minute?
The issue is not the OS you are using, really.
softraid is enabled by default, no need to recompile anything. So is SMP, just use the default GENERIC.MP kernel.
A PHP extension for the Skein hash is now available.
You can download it from:
http://download.pureftpd.org/php-skein-hash/
Yes, I also run Vista and it never cra
Before someone nitpicks: ZeroMQ is not really a messages broker, messages are directly sent to the recipient without passing through any broker and this is what makes ZeroMQ different and fast. But the end result is that you get the same features as a messages broker, just faster and easier.
ZeroMQ is still under development though. But it really needs more exposure.
If you are looking for a very fast messages broker, have a look at the ZeroMQ project : http://www.zeromq.com/
Although it looks not a lot of people have heard about it, and although AMQP is still on the todo-list, it's free, open-source and it works damn well.
Regardless of the API and protocol, messages brokers are very helpful to build horizontally scalable applications.
Let me know when PHP has threads.
PHP ? Real OO? Thanks for the great joke.
How can I add methods to Number? Ehm you know, the class used for numbers... In order to write 3.times() for instance... ah, it doesn't exist? Ok, so how can add methods to strings? Impossible, strings aren't objects either?
Stop kidding.
Why do PHP programmers use classes for? Just to avoid collisions between two functions with the same name when files are included. Really... very few PHP code instanciates more than one object per class.
Introduction of namespaces might limit this.
But there's something else that PHP miss: a "static" keyword.
Guess how very large source code like OS kernels or demos have been built in C or assembler, without namespaces, without classes, without symbols like \, but without coders constantly fighting about names collisions?
The reason is file-local symbols, ie. the static keyword in C (and local symbols in assembler). Only export (ie. make non-static) what you need to use in other files. As a bonus, it helps the compiler in order to optimize the code.
If the programmer needs to refactor its code because of stupid restrictions of a language, the language just sucks as it makes the programmer waste time.
Please try to make coroutines with PHP 5.2. Oh you can't? It's impossible without being horrible kludged, complex and slow? Oh, of course, without anything like GOTO or setjmp/jmplong.
So keep refactoring your code, and think that your code would already be running if you had GOTO.
GOTO is what your CPU is actually doing 80% of the time.
You can pump up your ego by imagining that using a language without something explicitely called "GOTO" makes your code "up with the time". But what you actually do is nothing but GOTOs, just written in a different manner.
Ironically, the VM that PHP uses is completely GOTO-based (well, you can pick several methods at compile-time, but GOTO is what a lot of distributions chose because performance is often better than CALL and it's very stable nowadays).
Oh and even JAVA has GOTO and relies a lot on it. The compiler hides an explicit thing called "GOTO", but what you get after compilation is full of GOTO. And it's actually why apps can actually do something.
Laughing at "GOTO" is ignorance, or just blind trolling because you read somewhere that BASIC had a "GOTO" keyword. I guess in a few years your children will laugh at those horrible "$", "$this", "->", ":" and "\" symbols, that would remind them the old time of a language called PHP. Though you are proud of them now.
Using temporary variables like "$should_exit", dummy loops just to "break" at the right place, or named loops to work around "break" that would only exit the first loop is nothing but writing "GOTO" in an obfuscated and inefficient way. "GOTO" is not synonym for "spaghetti code" (the famous keyword always used by people blindly repeating that GOTO is bad).
Oh and grep for "goto" in your Linux kernel or in any BSD operating system. Wow, tons of them. Really. But I guess this is just because these source codes are shits written by people who can barely write GW-BASIC, and of course none of these operating systems actually work. Glad you are there to help. Teach them how to code, tell them that their code is so passé.
Or shut up.
PHP source code is already cluttered with symbols like ->, : and $ (and those horrible $this-> everywhere...) and now \ ...
Really, PHP code is ugly. Why does PHP need this, while Ruby is way more elegant without missing any feature?
Why are you describing ZFS as the only option, are you working for Sun?
Real-time remove replication and distributed storage are real alternative to RAID 5 or 6.
No need to use Solaris. There's a ton of very efficient tools to do that on Linux, like the excellent Zumastor project.
Even before Subversion 1.5, the svnmerge.py tool just did this.
This is why HAMMER is the holy grail of filesystems.
Oh, and it's BSD-licensed.
Nowadays, anyone who wants to discover a new operating system wants to try a live CD first.
Although there were other live OpenBSD CDs (like OliveBSD), yet another one, especially based upon something original like Enlightenment, is a great thing.
OpenBSD is often described as a server-only (or network-stuff-only) operating system. Actually, it can also be a decent desktop OS.
I'm using OpenBSD on my primary workstation for 7 years and I'm quite happy with it. The only thing I *really* miss, especially as a web developper, is the lack of Flash support (except crappy support with Opera). nspluginwrapper + linux emulation is still as stable as nitroglycerine.
The same thing can apply to any browser-side storage : localStorage, globalStorage, userData, Google Gears and HTML5 database storage.
Purging those is not as easy as with cookies.
But they also have a lot of legitimate uses.
And Prototype is so much better than jQuery.
You don't need to seek 10000 times for the same element. You can look it up *once* and store it. Avoiding useless DOM traversal is the basic of javascript optimization.
If your visual effects depends on traversing 10000 times the DOM in order to always find the same node, something is seriously broken in your code, not in the framework.
It doesn't play well with badly written Javascript that blindly use "for ... in ..." (not loops) in order to iterates over Objects and Arrays.
Have a look at why it's bad: http://www.prototypejs.org/api/array
Prototype doesn't do anything wrong here.
But Prototype can play very well with any other library and with badly written code, using Protosafe : http://code.google.com/p/protosafe/
Also songratulations to everybody who has worked on Prototype!
I have used Prototype extensively and it is easy to learn and easy to handle. In fact, I had been using JavaScript for quite a while before Prototype, but after I started using Prototype, read some source, wrote a few plugins, etc. (even some patches, including performance related ones), I feel my understanding of the weird and advanced things in JavaScript is also much much better - and it didn't require any hard work or thinking :)
In comparison, before Prototype I used Dojo, which still gives me a headache just to think about. This is now some time ago though, so I will not bash Dojo as it's quite likely my specific problems with it have long been solved. However, Dojo never 'invited' me to become better at JavaScript myself.
All in all, Prototype is a great tool, it makes JavaScript fun again, and it makes me feel sorry I'm hardly doing any webdevving anymore (imagine that!)
jQuery is a great tool, too. It all depends on the application you are working on.
It would be a very stupid reason to pick a framework over another one.
Your link shows results from a benchmark. What does that benchmark? It just benches the speed of selectors.
It tries tons of times to fetch DOM nodes from a fixed definition like "a A in a P in a DIV".
If your application heavily depends on the framework's ability to fetch 10000 times the same element the same way, there's something really wrong with it.
I can't understand how Javascript frameworks can be compared using such a benchmark.
Moreover the Selectors API is coming to browsers, so this is going less and less significant. Prototype 1.6.0.3 (released today) supports it, every other frameworks will soon do.
The real difference between frameworks in the time you need to build the app you need with them.
When it comes to playing with the DOM and building visual components, jQuery is great.
When it comes to working with data structures, Prototype fits like a glove, way much than jQuery.
Try Syllabe : http://web.syllable.org/pages/index.html
It boots almost instantaneously.