Autre

The interesting thing here is: why do big companies don't need to keep their talents? Does bureaucracy compensate for lack of talent? And vice versa? Does this also mean that you can innovate without talent?

I was deliberately excluding the constructor situation. I should have made that clearer in my previous comment. I think the way out of the constructor mess is not to require them at all.

I do think the Object.getPrototypeOf approach is feasible for methods.

Yeah, it gets really hairy, really quickly.

Beyond the need for calling the constructor (which I'm currently viewing it as an unnecessary hidrance [objects are already initialized]), Object.getPrototypeOf may provide a way out - but maybe not the way you intended. Have you considered it?

Maybe I overlooked, but is there support for "super.method()" or something along those lines?

Yeah, but would you be willing to read and develop, say Cassandra, in ed? I, for one, wouldn't. One more thing: would you be able to?

  If you've made changes to your profile, you may force a refresh by pointing your browser to hackerhub.org/r/yourid.

Are arbitrary rss feeds recognized?

[edit:] Seems like rss, not atom feeds, are recognized.

Readability is just one click away http://www.readability.com/

Also: have a look at https://github.com/manuel/schampignon (an interpreter for a Kernel-like language)

Practically you need some desicion making control structure (cond, if) and an emulation of read/write tape (arrays)

The same philosophy is applied in the Seaside framework for Smalltalk. See for example [1].

[1] http://onsmalltalk.com/page-templates-and-seaside

Well, I have to argue that it's not the same pattern. I think the problem is that you still like to believe that js has classes, which it doesn't: js has got objects only. That it also has constructor is an (admitted?) historical mistake. Just think of all the weird crap that goes on to make `new func()' work and produce a new object.

What is no mistake is the refreshing change of view you get when you start embracing objects and prototypal inheritance. See for example the traits library[1, 2].

[3]: Is a cursory introduction to Self, with another points example :)

[4] Contains an example of my own (heavily inspired by Self and Io). I have stitched together various internet sources to come up with `clone', an operator assisting in differential inheritance.

[1] http://traitsjs.org/

[2] http://code.google.com/p/es-lab/source/browse/trunk/src/trai...

[3] http://www.cs.aau.dk/~bt/DAT5E08/MarkusKrogh1.pdf

[4] https://gist.github.com/997910

I don't see how Object.create goes against the grain of the lang. On the contrary, `new' was bolt on to make js look like classical oo languages. I have found, in toy and exploratory projects at least, that using variations on Object.create [1] is a nice, strong pattern, that really gets the best out of js. It certainly feels more natural than class based oo. Though, take it with a grain of salt, since I'm unable for now to provide an example backing my thesis :)

[1] https://developer.mozilla.org/en/Differential_inheritance_in...

Is there a reason you are not targeting ECMA5 (with the exclusions you mentioned)?

Just tried the following:

  for (var i = 0; i < 10; i += 1)
    eval("function function_" + i + "() { print('i am ' + i); }");

  for (i = 0; i < 10; i += 1)
    this['function_' + i]();

Well, i'm not sure about that. Aren't we expected to be professionals and act like ones on any given job? Should we just eschew Knuth and express ourselves? Don't think so.

OTOH, it seems like something is clearly wrong here since, we are having a tough time being professional and working with the current crop of languages, tools, technologies, etc and in the same time, fully expressing our vision while enjoining our work.

It's my understanding that JSqueak was (is?) just a toy. OTOH, redline aims to be a full blown implementation of smalltalk that integrates with the jvm like jruby, scala, clojure, etc do. As you can see from the github repo, it's still pretty much a work in progress (plus a learning tutorial for interpreters/compilers).

Heading for JavaWars?

Though I'm glad for this desicion, I can't help but wonder: what's in it for oracle? The puny 5% of desktops running mac os?

It's from one of the great ones by raganwald: http://blo.gr/352

You cannot really suggest a vi replacement that runs on non-UNIX. Sorry, I'd like to try it out.

Seems there's at least some direction the new java owners want to head at.

I find instructive and intuitive the usage of common UNIX commands for the api.

For a minute there, I was actually scared.

It keeps hitting me as a contradiction these two suggestions, namely: a) that you have to understand design to be a good hacker; and b) that planning is overrated.

How can you get to a good design without some plan? Could someone shed some light?

Yeah, it definitely feels like a coup or something. It's so lame.

Would you claim, from a programmer's point of view and also from a user's, that Apple is usually doing the Right Thing?

A priority queue [http://en.wikipedia.org/wiki/Priority_queue] seems to be the way to go with this.

That's what pg have been saying all along.

A brief explanation can be found here http://pv0.info/2k/v.