If you hate Javascript so much just use Webassembly and write everything in C++.
Your code will probably take 10x longer to debug and write.
But hey, now all your segfaults will be exceptional!

The market demands JavaScript, so if people want to get paid and also retain a decent chance of finding a job, they have to follow the market.

I don't hate JavaScript. I hate all the fuckos that use typescript and literally don't even use anything that typescript does.

Hey, that's vanilla JavaScript with extra steps!

Top it off, I fucking hate typescript because it's just another leash from Microsoft.

@sariel

How is TypeScript a leash of Microsoft?

Webassembly? It will be like Flash and Silverlight 5 years from now. Yep, 5 years, not even 10. It will be gone.

@yehaaw TS is MS's attempt to make JS lile C#

@jasongodev nah, I think it will stay as it is exceptionally interesting for unity devs (on unity you can compile to web assembly)

@sariel @jasongodev

Jesus fucking retarded christ poop, I know that. I was asking why is it A LEASH? WHY DID YOU USE THIS SPECIFIC WORDING?

REEEEEEE

@sariel It is open sourced. So how is it a fucking leash, slave?

@yehaaw I sense great anger in you. Im somewhat of an oracle you see

@Hazarth Amen

@yehaaw what does Microsoft do with all their defunct products?

They stop support, all downloads go missing, and the community rages until the next big MS nipple comes along to suckle.

What happens to everyone that is forced to continue using it? They get fucked.

It's a tale as old as Microsoft, and it will never change.

@sariel Might be true, but then again, who’s stopping someone from forking the source and building the community around it to support the project? Also, TS is way to big IMO for Microsoft to abandon it.

@sariel It's a tale as old as closed-source software, not an MS speciality.

Typescript, however, isn't closed source.

I hate JavaScript and I think that Typescript aka The try to unfuck the most fucked language ever is the best proof why I hate JavaScript.

MS will never be one of the good guys, that's for sure.

But lately, they're realizing that they will dig their own graves if they don't start being more tolerant.

Guess with the latest try of forcing Edge on the users they'll get one more painful reminder that this doesn't work (Edge / Bing search for alternative browsers).

@yehaaw @lbfalvy we'll see how many cease and desist letters go out when someone forks it and successfully begins a replacement.

There's more than one way to kill an open source protect.

The only way, and I mean THE ONLY WAY, we should ever trust Microsoft is if they open source the Windows kernel.

They fought open source for almost 30 years, they don't deserve trust until they show they trust the open source community with their precious.

Fuck those corporate cucks.

@yehaaw also, it's not about the size of community. It's what that community can provide to Microsoft.

I'll say it again and again, a multi-billion dollar company doesn't support shit unless it's profitable in some way.

Y'all know this was a joke right?

The punchline:

"now all your segfaults will be exceptional"

Watching the battle of JS vs TS has been entertaining though. One of the reasons I like coming to devrant.

Webassembly might actually be the only way to run your legacy C/C++ code without having to fear the RCEs it probably contains...

Javashit is here to stay. If not through TS, maybe dart will carry on.

Webassembly isn’t really a think to work directly, but I bet that it will be a good format to distribute your program. (See krustlet and other projects that uses webassembly as their entrypoints)

@sariel I disagree, we should never trust Microsoft no matter how much stuff they open source, because they're a profit-oriented company with no other motivation than to make as much money as possible.
Which is why I only depend on massively popular open-source tools like VSCode and Typescript which will carry on whether MS supports them or not.

Performance would be mediocre at best since WASM doesn’t have direct access to DOM so each update would take a quite expensive JS interop, at its current state WASM isn’t meant as a way to write entire applications with it

@DEVil666 If your JS does nothing but pass data from wasm to the api and back then the bottleneck is the DOM, not the JS part.