|
As the last few paragraphs of the cited article suggest, I think that "the JavaScript / framework world as we now know it" is about to be taken-over by transpilers ... and by languages like Apple's Swift. The unquestioned dominance of " 'JavaScript, Of Course(TM),' driving millions of lines of other people's source code," is finally about to be questioned. And I think that it will lose the interrogation.
Frameworks became very interesting, at least for a while, when the aptly-named PhoneGap promised that "mobile application development," far from being a strange new world, was actually just another form of web-site. These have ballooned into things like Ionic, which still let you write a mobile app in JavaScript if you don't mind the 120,000-or-so lines of accompanying Java and/or Objective-C which is required to actually make the magic work. And in the end ... 60 to 100 megabytes later ... it's still "just JavaScript." In terms of the tool that you use to write your part of the source-code, you haven't gained a damned thing. You're still making the same mistakes and discovering them at runtime.
Transpilers, like Haxe and OpenFL, allow you to write your source code in a language that is far more sophisticated, and to compile your code to multiple native platforms. (As well as a JavaScript target.) These tools have long ago passed the "curiosity" stage.
Languages like Apple's Swift are just as exciting, now that Apple has open-sourced the project, which is based on LLVM compiler-construction technology that is already open.
Although nothing will displace the billions of lines of JavaScript (and frameworks) that are now in stable, revenue-producing service ... nor should there be, anytime soon ... I clearly foresee that both the way in which developers operate, and the fundamental nature of the applications they produce for any platform(s), is changing. People aren't going to continue writing as they now do.
|
