4 ms·
I can't believe Javascrip is really that awful that anyone would rather go through all this trouble, rather than just write JS.. Maybe it has more to do with p
by gizzlon 14y ago
I can't believe Javascrip is really that awful that anyone would rather go through all this trouble, rather than just write JS..
Maybe it has more to do with people being to reliant on IDE's, which he, kind of, admits to anyway..
I can't believe that any IDE is that great that anyone would rather go through all this trouble, rather than just use something else..
- yawgmoth 14y agoI think in this case, it isn't about being dependent on Visual Studio, but C#.
- hkarthik 14y agoThe two go hand in hand. Aside from a very small cross section of Mono users, most C# users are very dependent on Visual Studio.
- georgemcbay 14y agoIMO JavaScript is that awful, but I still don't understand why you wouldn't just use Go or C# or whatever natively on the backend. There are lightweight frameworks similar in concept to node for virtually every language out there. I understand why people write JavaScript translators for the browser -- there you're (unfortunately) stuck with JavaScript there is no other option. I also understand why people who do like JavaScript use node. Even though I'm not a fan of JavaScript, there is certainly some benefit to keeping a project all in one language. But if you're the type of person that wants to avoid JavaScript in the first place, why start off in a situation where you already have an overly complicated language-to-language transpiler situation on the backend?