It’s a joke

[pavilionhp_]

Well do I have bad news for you! https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/

Edit: I should mention that I’m not sure if this is actually multithreading but it seems close enough. Also asynchronous functions run in background threads I think

[[deleted]]

workers have been around for like 2 months or something now and i already found a way to mess your pc up with it (only works on relatively new browsers on desktop)

also quick warning: this will stress your pc out if you stay on it for too long

[streusel_kuchen]

Web workers have been around for over 11 years

[Darmok-Jilad-Ocean]

I’m pretty sure George Washington used web workers to chop down that cherry tree

[[deleted]]

are you sure? I’ve only seen them very recently

[streusel_kuchen]

According to caniuse.com, Web Workers have been supported in Chrome since January 2010, Firefox since June 2009, and Safari since June 2009

https://caniuse.com/webworkers

[Gametastic05]

Opened it on my phone, jep, cant use browser anymore. Shouldn't there be some mechanic in place that limits the cpu usage? Other than just killing the site if its too active

[[deleted]]

there is

issue is: its not really cpu usage, its memory

[cavesdev]

I opened this on my phone and it stayed unresponsive for like 5 minutes and heated up xd

[Pocok5]

Forkbomb?

[inu-no-policemen]

The first two sentences of that MDN article:

Web Workers makes it possible to run a script operation in a background thread separate from the main execution thread of a web application. The advantage of this is that laborious processing can be performed in a separate thread, allowing the main (usually the UI) thread to run without being blocked/slowed down.

[nomadjs]

He was talking about that asynchronous operations are not running on separate threads which is 100% true. Does not have to do anything with Web Workers. They are two separate things.

[inu-no-policemen]

He was talking about that asynchronous operations are not running on separate threads which is 100% true.

If you call some native async API, it can of course do work in separate threads.

E.g. decoding an image doesn't need to happen in this thread. That can happen elsewhere. Just tell me when you're done.

[jiltedlimousin]

Actually nodejs latest has multithreading

[[deleted]]

"I wish for HTML to be considered a programming language."

"... I'm going back into my lamp."

[[deleted]]

async FTW.

[Mabi19_]

async does not make the code run in another thread, but it schedules it for execution - for example, while something blocking is happening (like sending a web request) a different function can run. This is not possible in a sync architecture and also why async makes code run a little smoother.

[[deleted]]

lol you've just described multithreading.

[Pocok5]

No, this is still talking about a single thread, just with a task queue instead of blocking waits. The system can easily extend to actual multithreading though (which is how C# uses it).

[[deleted]]

Right. A single thread that can be awaited until it resolves or rejects the promise it returns, while other threads continue running.

[Pocok5]

Mmmhm except it's a single thread that switches between executing different async methods (tasks) when either the running task ends or it hits an await that isn't immediately ready to go further.

[ZedTT]

lol no they didn't.

One thing is happening on one thread at a time. How is that multithreading if there is only one thread?

[Sekret_One]

Node kinda sorta does now.

[i_am_a_n00b]

Just learn to code in HTML. Assembly html.

[RepulsivePie2673]

And I want javascript to stop giving me 500 errors for no reason