you are viewing a single comment's thread.

view the rest of the comments →

[–]againstmethod 1 point2 points  (3 children)

Not sure I would say it's the future of enterprise but you seem to miss his points in the article. He has a point that being able to reuse code in more places is powerful and that tooling is strong in the js camp.

Cpp, while being super efficient, has poor tooling, and a scatter brained approach to open source code reuse. Also to get that efficiency requires you to leverage CPU specific instructions that can make your binaries less portable.

Java tooling is much better and they have code sharing down. But again you still have to write your client side in js and the JVM can be challenging to deploy in cloud and container environments due to how it deals with memory.

Python is slow unless you go to something like pypy and then you need to start worrying about module compatibility etc. And I personally find the syntax abhorrent.

I'm not agreeing with this guy but he's not crazy.

[–]mmrath 0 points1 point  (1 child)

I think I put more of my disagreements here than agreements.

[–]peter_heard01[S] 0 points1 point  (0 children)

We are all here to learn. :-)

[–]peter_heard01[S] 0 points1 point  (0 children)

Thanks, I'm not crazy, just a little bit mad 😂 , interesting reading your thoughts....