91–100 of 144 posts
Earlier quoted context omitted.
> Flutter exists too, and supports iOS and Android in addition to the desktop OSes. The dev time is pretty fast too imo. Flutter is a joke on the web, and it consumes as much as Electron, sometimes worse, on a desktop.
You got sources to back this up, or is this just you're opinion?
JS 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 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.
Earlier quoted context omitted.
To be fair there were a couple of disasters, such as [object Array] and undefined. Feels like the world is hanging on a single thread by now.
Protip: never even mention undefined in your codebase. Erase it from your vernacular. If you ever need to pass or return nothing, you use null.
undefined camp:
- out of bounds array index access [1,2,3][42]
- non existent object key access {}.foo
- array.find(...) no result
- ...
null camp:
- document.querySelector(...) no result
- regex.match(...) no result
- ...
Earlier quoted context omitted.
To be fair there were a couple of disasters, such as [object Array] and undefined. Feels like the world is hanging on a single thread by now.
Protip: never even mention undefined in your codebase. Erase it from your vernacular. If you ever need to pass or return nothing, you use null.
Surprised no one mentioned this is the guy who brought us this masterpiece. If you haven’t seen it, drop everything and watch it, best 5 minutes of your day guaranteed. https://www.destroyallsoftware.com/talks/wat
Incidentally it’s also a great introduction to thinking as a functional programmer if you are used to imperative logic with state spread all over the place.
Surprised no one mentioned this is the guy who brought us this masterpiece. If you haven’t seen it, drop everything and watch it, best 5 minutes of your day guaranteed. https://www.destroyallsoftware.com/talks/wat
Earlier 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
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?
Earlier quoted context omitted.
Darts an amazing language too.
It is basically a revamped Java. Google lost the opportunity to actually make it take off, had they replaced the Java stack with Dart, instead of staying in the Java world and adopt Kotlin. However the Android team was never a great supporter from Dart in first place, hence why you won't find anything Dart on https://developer.android.com .
Earlier quoted context omitted.
Protip: never even mention undefined in your codebase. Erase it from your vernacular. If you ever need to pass or return nothing, you use null.
You can't get rid of undefined. You can't ban null either. They're both used in the core language all over the place: undefined camp: - out of bounds array index access [1,2,3][42] - non existent object key access {}.foo - array.find(...) no result - ... null camp: - document.querySelector(...) no result - regex.match(...) no result - ...
Could the language have done without both null and undefined? Definitely. But it's here and here to stay.
Though, it's not the only language with two nulls. Julia has nothing and missing, though their semantics are more well defined and with different behaviors than in JavaScript.