Ask HN: Besides Go, what languages are muti-threading "in background"?

#1

Post by stanlogin » Thu, Mar 28, 2024, 6:21 AM UTC

I mean, no need to write "async/await".

Re: Ask HN: Besides Go, what languages are muti-threading "in background"?

#2

Post by stop50 » Thu, Mar 28, 2024, 6:25 AM UTC

I think the tokio library does this for rust

Re: Ask HN: Besides Go, what languages are muti-threading "in background"?

#3

Post by mrudolph22 » Thu, Mar 28, 2024, 6:48 AM UTC

Java 21+ (virtual threads).

Re: Ask HN: Besides Go, what languages are muti-threading "in background"?

#4

Post by viraptor » Thu, Mar 28, 2024, 8:01 AM UTC

I think you're mixing up async execution and multithreading. They're quite different concepts, although you can offload an awaited work on another thread.

Almost any language supports spawning a new thread.

Re: Ask HN: Besides Go, what languages are muti-threading "in background"?

#5

Post by stanlogin » Thu, Mar 28, 2024, 8:04 AM UTC

viraptor wrote: post #4

I think you're mixing up async execution and multithreading. They're quite different concepts, although you can offload an awaited work on another thread. Almost any language supports spawning a new thread.

"in background"

Re: Ask HN: Besides Go, what languages are muti-threading "in background"?

#6

Post by viraptor » Thu, Mar 28, 2024, 10:10 AM UTC

stanlogin wrote: post #5

viraptor wrote: post #4

I think you're mixing up async execution and multithreading. They're quite different concepts, although you can offload an awaited work on another thread. Almost any language supports spawning a new thread.

"in background"

What does that mean?

Re: Ask HN: Besides Go, what languages are muti-threading "in background"?

#7

Post by stanlogin » Fri, Mar 29, 2024, 8:39 AM UTC

viraptor wrote: post #6

stanlogin wrote: post #5

Earlier quoted context omitted.

"in background"

What does that mean?

I don't think its difficult to understand. Look at the other two answers.

Re: Ask HN: Besides Go, what languages are muti-threading "in background"?

#8

Post by viraptor » Fri, Mar 29, 2024, 8:12 PM UTC

stanlogin wrote: post #7

viraptor wrote: post #6

Earlier quoted context omitted.

What does that mean?

I don't think its difficult to understand. Look at the other two answers.

No, it really is. I've got experience with multiple languages / multithreading approaches and could argue it means 3 different things. I don't know what others think the question is about.

Re: Ask HN: Besides Go, what languages are muti-threading "in background"?

#9

Post by stanlogin » Sat, Mar 30, 2024, 2:06 AM UTC

viraptor wrote: post #8

stanlogin wrote: post #7

Earlier quoted context omitted.

I don't think its difficult to understand. Look at the other two answers.

No, it really is. I've got experience with multiple languages / multithreading approaches and could argue it means 3 different things. I don't know what others think the question is about.

OK. It's difficult to you.

Re: Ask HN: Besides Go, what languages are muti-threading "in background"?

#10

Post by pjmlp » Sat, Mar 30, 2024, 2:00 PM UTC

mrudolph22 wrote: post #3

Java 21+ (virtual threads).

Java already did it in the past, that is why we have the notion of green threads versus red threads.

What virtual threads bring to the table is that now they are both officially supported, with APIs for both cases, while previously it was an implementation detail of each JVM how threading was actually done.