ilyak

"most things become popular for very good reasons" Sure. But those reasons are gone. Long gone. So please, wrap it out already.

"that is what a web server does" Did. Most PHP apps don't use /some-article.php and /another-article.php with relevant PHP files under those names, that would be bizzare. There surely is A routing FRAMEWORK those days.

"One PHP file per page is also not true" ...if you're using A FRAMEWORK.

"There is also no 'default templating', I can pipe to, or make PHP calls from the command line" So what? There's still default templating outside <? ?> And that's what you use unless you've got A FRAMEWORK.

Do you see a pattern here? The pattern is that you didn't read my comment, you used regexes instead. Sadly.

We are tired of you being loudly tired of Desktop Linux, FAVO you.

It would never work without frameworks:

The PHP's default templating (stick code into templates) sucks (unusable for anything serious).

PHP's default routing (/foo/bar.php, lookup the file) sucks (you really really want one entry point for your web app.

PHP's default code layout (one PHP file per page) sucks too.

Idiomatic PHP is unusable! So you'd NEED a framework. Maybe homebrewn one. And if you're going for a framework, why not start with Django or Rails?

Every large-scale project in PHP contains an ad-hoc implementation of at least half of Django.

But it still has 1000+ functions in the default namespace?

And every file still starts with <? And if one of them doesn't, then your web app would fail epically because you were gzipping your output into your output stream (one and only one), and this extra space in one of files ruined your gzip.

To be fair, it's wonderful that complex PHP apps ever work. It's a complete surprise to me, I'd say they run-by-accident.

I'd go ugly early by saying that so did Hitler.

Well. Ruby?

However I'd say he's directly responsible for the misery the most PHP development now is.

If he actually spent time reading about languages and designing his own, he would throw in function namespacing and function naming conventions and a good built-in abstraction for database access (with a strong bias against SQL injections and towards placeholders/variable binding from the day one), PHP would come out an okayish language and not an universal hate target.

There are some other blunders that he could just not make. And I'm not even dreaming about template system that makes sense now.

He didn't! Who the hell could do that if he wasn't going.

Why not? I mean, rhino has methodNotFound-like thing, so you certainly can.

"Also you forgot to write that" Okay. You want to argue with yourself not with me, to the point when you start rewriting my claims. So, you go and argue with yourself.

You can easily pass an object into Javascript:

context.put(“rubyObject”, MyRubyClass.new)

Whether you would be able to call methods on it depends on whether the Snarl author did some (trivial) code magic or not, but it's certainly doable too.

Still I have no idea why would you want javascript in ruby in the first place.

There's JSLint, you can surely build it in.

And it would have syntax colouring which basic lagged in.

Sorry, but for programming language, popularity is everything. It's a social phenomenon, it grows superlinearly with number of users.

And languages become popular and unpopular for a reason.

For common lisp, those reasons are:

It's ancient.

Parties interested in it can't agree on anything so its development is stalled.

It claims to have a huge library which is tiny by 2009 standards, and doesn't have vital things like network i/o or unicode. Yes, implementations support those proprietarely, yet noone cares, because it's not in standard libs.

It has problems with reflection, which is doubly awful for a lisp.

CLOS is interesting, but for most uses smalltalkingly simple OO would be much more desirable.

Tool support is neliglible.

Nope it isn't.

I've heard about CL, know a few things about it, and it's a failure nontheless.

Its problem isn't the unpopularity between Blub programmers; its problem is its unpopularity even between geeks. Even language geeks!

Teach children to draw on a canvas in javascript.

You can easily make a page with a javascript editor and immediate evaluation if you wish, and simplified api.

I'd say that, in the world of politics, yes.

China is the only major state left who is claiming to be communist; therefore, China now defines "communist".

Clojure is two years old and already has more useful software being written in than CL.

CL is a failure, admit it.

"...the lack of trained and skilled workers as opposed to the surging numbers of graduates has led to the emergence of an abnormal trend where graduates are paid the same or even less than migrant laborers."

Everybody wants to talk and earn, nobody wants to actually work.

Do you see a problem here?

It's different in that, being common lisp, it's actually useless. Might be fun to tinker, tho, with its CLOS and stuff.

JBoss's "tattletale" program does just that for a few years already.

Maybe it doesn't draw pretty drawings, but otherwise it's oldnews.

...and newer Windows default on the local (i.e. cyrillic) layout.

Some clueless linux distros even install cyrillic layout as the only one; which is completely unusable of course.

Small languages may be interesting but we just don't have enough humans to speak them all, as humans don't want to study small languages unless they happen to be hobbysts or acquire that language as children.

Why would anyone want to live in a small town in the middle of nowhere?

Even worse, in rural area.

Makes no sense to me.

Why not? Serving pages fully off cache.

How many hits per second is slashdot effect? We could count.

I think slashdot effect mostly happens because database (mysql, generally) locks down, and we're removing that bottleneck by going into file-based storage and in-memory caching.

"Five years is a factor of ten in Moore's Law, meaning that computers will be capable of far more by that time than they are today."

Remember PCs five years ago?

Exactly, not much changed except for multicore, and it's still underused. I'd not expect an average PC in five years to be anything unusual.

Mobile devices, on other hand, have a lot of way to grow. Maybe we'd see phones with HD screens and 1GB RAM in five years, and those would run whatever you'd wish.

This statements makes no sense to me either.

I'm not going to learn chinese; you neither, for most values of you. So we'd still have our web for a small group of maybe one billion english-speaking (FSVO) users. Maybe there would be more content in Chinese, but we will never know because we won't bother to read it unless they translate, to ENGLISH.

In Java, you usually do not invent the wheel but rather take an existing open-source jar.

Even those of them that aren't very good, sadly. But most are.

...while reducing perfomance...

XSLT makes for a nice templating engine.

"Provides integration with Hibernate" == "Would be a huge pain in the ass".

Otherwise, I'd still either pick JRuby on Rails or go ugly early with idiomatic java.