4 ms·
This whole language of the future concept is just mistaken. The era of being able to choose a language, for most operations, is over. That's because the future
by JulianMorrison 12y ago
This whole language of the future concept is just mistaken. The era of being able to choose a language, for most operations, is over. That's because the future will be (already somewhat is) the disappearance of PCs, the minimization of overt gadgets, and the rise of ubiquitous, invisible, small, smart, with no user serviceable parts. And in most cases with no option on programming languages. Embedded? You'll probably have a choice of C, C++ and maybe Rust. Android? Java. Apple? ObjC. You don't like the tools? Suck it up, there's too much momentum to re-invent the wheel even if you think square is a terrible shape. They already laid the roads in inverted catenaries.
- pjmlp 12y agoThis is nothing new. I learned more than 20 years ago that it is less pain to just use the languages that are part of the OS vendor SDK than spending development time writing yet another FFI wrapper. This is how C got where it is now, as the language got adopted by OS vendors outside the UNIX world.
- mpweiher 12y agoThis is one of the great lessons from Objective-C, IMHO: layering additional functionality in such a way as to be completely compatible with the platform ABI. There are other compromises you make as a result, but that one feature is a huge win. (And yes, Objective-Smalltalk tries to extend that lesson of connectivity to other areas).