3 ms·
[Javascript] is good enough in exactly the way that MS-DOS was good enough. That's unfair. It's also, to judge by the rest of the post, a snap judgment with mo
by gruseom 18y ago
[Javascript] is good enough in exactly the way that MS-DOS was good enough.
That's unfair. It's also, to judge by the rest of the post, a snap judgment with more than a little bitterness in it. ("It is good enough that you can deploy hordes of programmers to produce crappy software that sort of works. And that is good enough for making money.")
My project does things with JS that I would never have thought possible. It has not let us down. The regularity and dynamicness of its core are reminiscent of Smalltalk and Lisp. There are annoyances, of course. But the one the OP places the greatest emphasis on - that all hash keys are strings - only caused us trouble once, and in that case we found a simple workaround. I'm curious: have other people here experienced that limitation of JS as a fundamental obstacle?
Given that the OP holds out Java, ActionScript, and that let's-turn-JS-into-Java thing as examples of how it ought to be done, I'm reminded again of how grateful I am that we have something as flexible as JS for making programs that run in a web browser. It's not what I would have chosen, but it's a hell of a lot closer than anyone could have expected, given the rest of computing history. We got lucky.
Edit: Oh, and they - the arbiters of programming correctness and staticness - can't do a thing about it. It's already taken over the world.
- tlrobinson 18y agoBut the one the OP places the greatest emphasis on - that all hash keys are strings - only caused us trouble once, and in that case we found a simple workaround. I'm curious: have other people here experienced that limitation of JS as a fundamental obstacle? Yes, any time you want to use a non-primitive type (strings, numbers, etc) as a key to hash map. But we solved it in Objective-J by automatically giving each Objective-J object a unique "hash" value. (of course you could do something similar in plain JavaScript, but you'd have to implement it yourself)
- gruseom 18y agoAh, I get you. We haven't needed that yet.
- maxwell 18y agoThis is one of those features that I've read Lua has and JS doesn't that sounds really good in theory. But I haven't ever run into a situation where I've wanted an index other than a number or string. It's probably just a blub paradox though; I'm curious, in what situations are other values particularly useful as keys?
- LogicHoleFlaw 18y agoIn Lua I've done stuff like maps of functions to tables of functions for permuting different methods of computation... kinda wacky but it does what I need.
- boucher 18y agoAny time you ever need to map an object to another object, you need this functionality. Without a memory address, object's don't have any other unique values associated with them. It's actually a pretty fundamental problem. Of course, like most things wrong with javascript, you can fix it if you work for it. Objective-J fixes all the things we had problems with, and this is one of them. A lot of things in Cappuccino would not be possible without the hashing feature Tom mentioned. As a hash table, JavaScript objects are pretty awful. You can't get a count of objects unless you literally count all the keys. And you can't iterate over the keys if anyone else has added anything to the Object prototype. Cappuccino has a proper hash table, CPDictionary, which solves both of those problems. There's a lot of other data structures that address some of the author's listed concerns.