←back to thread

Fiber Concurrency

(honeyryderchuck.gitlab.io)
43 points amalinovic | 8 comments | | HN request time: 0.201s | source | bottom
1. fiskfiskfisk ◴[] No.45136264[source]
I have no idea if this is for a specific language, a framework, a plugin system .. or what. And I'm not able to say anything useful from the page or from the title of the post.

It'd be helpful to at least set the premise for those of us on the outside.

replies(4): >>45136277 #>>45136315 #>>45136806 #>>45138630 #
2. jaggederest ◴[] No.45136277[source]
It's Ruby, if that's helpful.
3. protocolture ◴[] No.45136315[source]
I am kind of awaiting some news about more breakthroughs in DWDM technology and clicked through thinking this might be related. All I could tell immediately was that it was code of some description. I really detest when higher level stuff steals terminology from lower level protocols. I feel like they could have found a better term than fiber.
replies(1): >>45136398 #
4. lock1 ◴[] No.45136398[source]
To be fair, "fiber" is a pretty well known term in the context of concurrency. The post author did not make it up.
replies(1): >>45137536 #
5. amelius ◴[] No.45136806[source]
In cases like this it helps to navigate to the homepage of the website. With one click on the header link, you find out that this is about Ruby and some http server.
6. Daneel_ ◴[] No.45137536{3}[source]
What an awful choice of terminology though - it’s almost designed to be confusing to anyone outside the space.
replies(1): >>45138842 #
7. ActionHank ◴[] No.45138630[source]
Glad I'm not the only one
8. lock1 ◴[] No.45138842{4}[source]
Maybe, but "thread" is a widely accepted term even though it's closely related to "fiber" both in concurrency (coop/preempt multitask) and general day-to-day sense (textile).