The current licensing by Nvidia makes that impossible... It takes two to tango.

How in the world this was moderated insightful is beyond me - mod parent down, its wrong.

Apparently not me (They don't allow gay people to donate - even if I am HIV-)

If by 250k you mean 80k, then sure..

-rw-r--r-- 1 xxxxx staff 85260 Apr 30 10:28 jquery-1.5.1.min.js

If you're building any sort of complicated website these days, you will use alot of jQuery.. Do you really want to go write a custom ajax handler? why bother..

Plus, using jQuery allows you to leverage tons of other pre-written libraries which were all written on top of jQuery and will avoid alot of cross-browser bugs and repeated code..

echo + html tags is a huge fail...

Riight..

Because looking at code littered with var e = document.getElementById('stuff'); is just so much more elegant and non-shit-looking than $('#stuff')..

Why do organizations target specific versions of browsers - I really don't understand why its so hard for people to write cross-browser web applications - I do it every day at my job..

It's not like anyone will want to buy that franken-ui anyways...

Huh? WebBrick is really only meant for development use.. You can hook any web server up to rails easily. For apache, just gem install passenger...

It sounds more like you're used to what you're used to and don't want to change. Meanwhile thoose "overexcited college grads" don't want to be weighed down by the 20 years of trash thats part of the PHP code base... I'm a PHP dev now, and was a rails dev for 5 years - I'll take ruby/rails any day.

Rails is very easy to deploy..

1. 1. gem install passenger
2. 2. Point the apache vhost to the public directory.
3. 3. Restart apache..

There ya go, fine tune passenger to your hearts content...

I've spent alot of time writing code in Ruby/Rails... I've now been a PHP dev for 2 years and have used alot of what I learned in rails and applied it to PHP..

I don't see why you'd prefer php language constructs over Ruby - they are more tedious in every way right down to having to write "array" in front of every array.. (thank heavens they finally changed the latest version)

@array.map! {|x| x**2 } is much easier to read/understand than using the equivlent array_map function in php.. (Or for that matter using foreach or classic index-based for loop)

PHP's biggest problem - to me - is the lack of a FastCGI-style environment where code is already running and requests are just fed to the running daemon.. For this reason, its always going to be slower than other languages.... APC is an attempt to do this but its not very mature yet and still requires byte code to be interpreted on each request. Facebook wrote a PHP->C++ translator and that should say alot about the state of the language...

IE9+ is pretty much standards compliant out of the box and requires little to no effort to support over chrome, FF, etc...

IE8 got us about half way there..

IE7 uses the broken box model and, ergo, a pain in the ass..

Atleast in the consumer preview, there is no way to disable metro, there is no start menu to fallback to..

IE7 still uses the broken box model... IE8+ is pretty easy.. IE9+ pretty much just works...