Comments by "Vitaly L" (@vitalyl1327) on "You Probably Shouldn't Watch This" video.
-
15
-
10
-
5
-
@Andrumen01 even if you always stick to the first implementation of the language and ignore all the others, there is still no reason to divide languages into "compiled" and "interpreted". Not to mention that the line between compiled and interpreted is very blurry. The said Python is compiling into a bytecode first, then executes this bytecode. Modern C compilers compile into some kind of IR (GIMPLE, LLVM IR, etc.), and then either further lower that IR to a target machine code, or not - it can be executed as is. Is there a significant difference? Nope.
What's really different between C and Python is how dynamic they are. C is almost fully static, while Python have far too many dynamic features - dynamic dispatch for everything, dynamic virtual tables, magic method, hash maps all over the place, all that stuff. You can compile Python into native code all you want, it'll still be slow and clumsy due to this level of dynamism. And you can stuff your C code with tons of run-time dynamic lookups and such, and your code will be slow and clumsy as if it's written in Python.
The more reasonable axis to divide languages into reasonable groups is static vs. dynamic, manual vs. managed, statically typed vs. dynamically typed (it's a different axis from static vs. dynamic in general), strongly typed vs. weakly typed. And then there are many meaningful sub-divisions - eager vs. lazy, statement-based vs. expression-based, purely imperative vs. can-be-functional vs. functional-first, and so on.
As for the web, I simply decline to touch it. Web UIs are ugly, user experience is very disappointing, and the whole stack of standards and technologies is over-engineered and extremely clumsy. There are much better ways, so I'll stick to them and wait until the web fad is finally over.
2
-
1
-
1