Comments by "xybersurfer" (@xybersurfer) on "Why Null?" video.

  1. nothing is stopping you from writing code that can't compile, in a compiled language
    1
  2.  @AndrewTSq  from your description, it looks like you use JavaScript as pseudo code, as in without running it (or hitting compile). i figured you could do the same with a compiled language. whether you see a type mismatch immediately depends on the editor you use. it sounds like you are doing more in JavaScript, than you say
    1
  3. him being a nice guy does nothing for me
    1
  4.  @lancemarchetti8673  which other languages do you know?
    1
  5.  @lancemarchetti8673  oh. big props for doing that on your spare time. i also thought that my first language was beautiful, but that changed a lot as i got exposed to others (like functional programming). they all have their problems. but a lot of the concepts carry over from one language to another, so don't let that stop you from learning js
    1
  6. ​ @darkenlightmage  i have also used those languages myself, excluding Rust, but including some others, and also non-trivially (except Python and Java). the problem with JS is that it's dynamically typed and has many design mistakes, and that everyone is pretty much required to use it on the web. TS helps but it doesn't go far enough to fix JS in my opinion (and some things just can't be fixed). out of your list, C# has given me the least headaches (i like F# even more). mainly because of good tools like Visual Studio (not Visual Studio Code) and everything built into the .NET Framework and .NET Core "libraries"
    1
  7. ​ @darkenlightmage  the strength of dynamic typing like in JavaScript i would say, is that you don't have to sometimes jump through hoops for the compiler, when the designers of for example C# didn't consider something. but i think this is rare enough, and the benefits of static typing are still a greater time saver. what do you consider to be the strengths of dynamic typing? TypeScript tries to bolt on static typing, to fix JavaScript, but it does not go far enough in my opinion (because of having to be backwards compatible). there are also frequently issues in obtaining the right TS type definitions for the right version of existing JS libraries. this problem would not have existed if JS required types to begin with (Python seems to have similar issues with type hints). the "this" keyword is another mistake in JS. you can avoid it for yourself, but because using "this" is a mainstream practice, libraries expect you to use it. you basically can't fix the damage that has been done to the ecosystem by yourself. Visual Studio constantly crashing seems like a rare problem, that i don't share. what i have encountered is that it seems to get slower with each version, but not enough for me to use a less suitable tool like VS Code for .NET development (which sounds insane to me). i suggest reporting the Visual Studio constantly crashing issue, to Microsoft if you still encounter it, so that it gets fixed.
    1
  8. it's similar to Null, Nothing, Missing, Empty in VB6/VBA. it just causes problems
    1