4 ms·
I know this is a joke, but this seems to be one of those "the truth is stranger than fiction" things. No, they did not implement manual memory management in Jav
by gfodor 17y ago
I know this is a joke, but this seems to be one of those "the truth is stranger than fiction" things. No, they did not implement manual memory management in Javascript. But yes, they did in fact re-implement the Mac development ecosystem entirely in the browser.
Extremely powerful or extremely insane, I still can't decide. One things for sure, I certainly don't think it was necessary to go to the lengths they have to implement applications for the web well.
- gfodor 17y agoOne more thing to note, is that at the core of what 280North has done (with a Herculean effort) is traded something close to lisp for something close to Smalltalk.
- spooneybarger 17y ago/Smalltalk/Objective C/
- paulbaumgart 17y agoYou're both right. http://en.wikipedia.org/wiki/Objective-c#History http://en.wikipedia.org/wiki/Objective-c#History
- spooneybarger 17y agoSyntax is a tiny portion of Smalltalk. Smalltalk is all about the tools. Objective-J has no tools. Smalltalk without the environment and the tools isnt Smalltalk. Thus, my Objective C not Smalltalk comment.
- paulbaumgart 17y agoWhat tools in particular do you mean? Maybe Objective-J could have similar tools.
- paulbaumgart 17y agoAs a strict superset of JavaScript, Objective-J actually lets you have both.
- gfodor 17y agoYes but we all know that, as is the case in Objective-C, your primary mode of modeling problems becomes message passing and OOP. In Objective-C's case you drop to C for performance, I have a hard time believing that you'd drop to Javascript in Objective-J to eek out more performance. (If that's the case, truly we live in interesting times.)
- tlrobinson 17y agoThat was true for Objective-C, but JavaScript has closures, which can be used seamlessly in Objective-J. Of course now Objective-C also has closures/"blocks" too.
- paulbaumgart 17y agoI'm not going to claim to be an expert here, but I think the relationship is a little different between Objective-J and JavaScript than between Objective-C and C. The features of Objective-C pretty much across the board make operations simpler than they are in C. JavaScript already makes a lot of things pretty much as simple as it gets, and in some ways makes it too easy to accidentally do something wrong. So, Objective-J actually serves to impose a bit of structure on your code (and could even impose strict+static typing). That's basically how I've used it: Objective-J classes define the larger-scale architectural components of a project, but for smaller collections of data that are somehow related, especially for short-lived collections of data, I usually drop down to JavaScript and use the convenient hashes and arrays. Performance-wise, some operations will be faster in JavaScript than Objective-J, because things like message passing have an extra function call. I haven't found it to be a particularly noticeable difference, but admittedly I haven't been writing a lot of performance-critical code, so others might have better insights on that subject.
- pkulak 17y agoIf I'm going to write in a Javascript-using language, it's going to be Coffee Script. That's like Ruby and Python had a baby. A lovely, wonderful baby.