DEV Community


Discussion on: The Dark Side Of The Magic

bootcode profile image
Robin Palotai

I agree that you have to dig deep to be successful, but see the point in other's argument that Javascript is not necessary more magical than others.

For example, eventually under JS there's the JIT engine (like V8). Once I had to debug into the V8 internals to see why some code got the slow path. It's magical to the extent that it is rarely encountered.

Similarly, while Haskell on the surface is a smooth language, the compiler internals and the runtime of GHC is pretty complicated (rewrite rules, blackholing..). These are magical in the same way, that they rarely dealt with directly.

The common thing is, once you hit the "magic barrier", unless you have the willpower to dig deep, you are stuck and have to rely on others to fix your problem. Which is fine sometimes. Other times too costy.

Does that sound good?

codemouse92 profile image
Jason C. McDonald Author

I think it sounds reasonable. Again, I'm not actually picking on Javascript in and of itself. I've simply noticed that an apparently significant reason it's "trendy" is because it abstracts away so much at the elementary level, perhaps more than most languages.

The problem isn't that some JS devs are apathetic because JS, but that many apathetic devs use JS because apathy.

Javascript can be used responsibly, and I certainly don't know much about its deeper principles. Thanks for the insight from the other side of the "magic barrier" on that language.

I think your point about the magic barrier is pretty much what I'm saying.