Comments by "Okie" (@okie9025) on "JavaScript in 100 Seconds" video.

@multiarray2320 its a joke bro jfc
14
C took years to perfect yet nobody uses it now 🤷‍♂️
4
Not true. a === c // false b === c // false a === b // false
4
cynics make terrible programmers
2
wasm can only make things worse because its harder to make bad code in JS compared to something like C or Rust
2
@igorswies5913 that doesn't prevent you from making bugs, and besides most rust code contains unsafe code because some features from C aren't ported yet
2
@igorswies5913 that's exactly why javascript doesn't need replacing, making the same program in rust instead of js won't make it magically more safe or secure
2
@igorswies5913 Rust's documentation is likely dozens of times larger than JS's, yet reading the ecmascript docs even once properly will make you avoid any of these "weird problems" when writing JS
2
@igorswies5913 you can make the same mistake in rust if you call unwrap when you dont want to or declare the wrong number type
2
@igorswies5913 avoiding unwrap is like avoiding the "throw" keyword in JS, which can be fine depending on what philosophy you follow, but nothing will make you completely immune to bugs, which can and will occur no matter what you do
2
@igorswies5913 which is why replacing JS is completely unnecessary as you have dozens of ways to reduce the likelihood of bugs occuring which are mature and popular
2
[] === 0 // false [] !== 0 // true [] === [] // false What confuses you about the strict equality operator? It's really not that hard
2
@M9625Rahul === was added years after ==. Its the same case with var. If you use any of these deprecated features then you probably wont get any support because you arent supposed to use them. They are only there for backwards compatibility reasons and nothing else.
2
cope
2
JS would be nothing without node
2
java, python, c# etc. are also garbage collected
2