interpreted languages carry a lot more context than compiled ones. Sandboxed compiled languages don’t have the context baggage, but come with other parts of the brain dead.
I don't think Javascript is still interpreted though?
The Birth and Death of JavaScript (2014)
61–70 of 144 posts
Re: The Birth and Death of JavaScript (2014)
#62Earlier quoted context omitted.
The syntax? I got 99 problems with js, but syntax ain't one of them. It's just C-style syntax, no?
C syntax was never that great. It's basically mnemonic PDP-11 assembler with a few added data structures. js is mutant C with dementia - hacked together over over a fortnight, full of inconsistencies and weird corners. console.log(1 + "2"); // "12" console.log(1 - "2"); // -1 console.log(NaN === NaN); // false console.log(+0 === -0); // true const obj = {}; console.log(obj.foo); // undefined, not an error
Re: The Birth and Death of JavaScript (2014)
#63Earlier quoted context omitted.
The syntax? I got 99 problems with js, but syntax ain't one of them. It's just C-style syntax, no?
C syntax was never that great. It's basically mnemonic PDP-11 assembler with a few added data structures. js is mutant C with dementia - hacked together over over a fortnight, full of inconsistencies and weird corners. console.log(1 + "2"); // "12" console.log(1 - "2"); // -1 console.log(NaN === NaN); // false console.log(+0 === -0); // true const obj = {}; console.log(obj.foo); // undefined, not an error
Re: The Birth and Death of JavaScript (2014)
#64JS became a compilation target (and it really did), and back then in the video it was asm.js (that's been deprecated, hasn't it?), but then WebAssembly came along... Seeing it actually being implemented and running natively, it seems his prediction was accurate. I mainly use TypeScript myself, and now with Electron, web technologies are wrapped into desktop apps, so web syntax has even entered computer programs. Peop…
But why make an app when websites is enough? And I don't need to run n web browsers for that.
Re: The Birth and Death of JavaScript (2014)
#65I love(?) that he absolutely predicted a global disaster between 2020-2025, he just got the wrong type. Which is very JavaScript.
He was pretty close to being NaN% correct.
Feels like the world is hanging on a single thread by now.
Re: The Birth and Death of JavaScript (2014)
#66Earlier quoted context omitted.
> but it's also the fastest way to support Mac, Windows, and Linux all at once. Flutter exists too, and supports iOS and Android in addition to the desktop OSes. The dev time is pretty fast too imo. That said, idk how the performance compares to Electron or Native apps. As a small team, optimizing for "actually getting the thing shipped" is so much better than optimizing for speed anyway.
Flutter is great, still the fastest way to make cross platform mobile apps and you get desktop and web support essentially for free. Performance is very fast as it's all natively AOT compiled machine code without any web views like Electron.
Re: The Birth and Death of JavaScript (2014)
#67Earlier quoted context omitted.
Flutter is great, still the fastest way to make cross platform mobile apps and you get desktop and web support essentially for free. Performance is very fast as it's all natively AOT compiled machine code without any web views like Electron.
On desktop does flutter have native access to the machine it's running on? Can it talk to printers for example?
Re: The Birth and Death of JavaScript (2014)
#68webOS and Firefox OS was at least 20 years ahead of its time.
Re: The Birth and Death of JavaScript (2014)
#69Re: The Birth and Death of JavaScript (2014)
#70Almost everything happened according to the script. Now we are just waiting for another OS fully based on browser technology or WASM OS. webOS and Firefox OS was at least 20 years ahead of its time.
Just asking out of curiosity.
Also, the screenshots I've seen of webOS makes me long for a revival... not only on smart TVs