8 ms·

> a simple but working example

by snissn 7y ago

amelius 7y ago
Yeah, of course, but how would you work this type of code into something that can be used in production? The goal should be to have a green thread library that you can just use without thinking about registers or assembly.
- heyzooos 7y ago
  > I’m not trying to make a perfect implementation here. I’m cutting corners to get down to the essence and fit it into what was originally intended to be an article but expanded into a small book. lol
- arnarbi 7y ago
  > how would you work this type of code into something that can be used in production? You wouldn't. There are production-ready solutions to this in many languages. > The goal should be to have a green thread library that you can just use without thinking about registers or assembly. The goal here is very explicitly to explain a concept by example, which is largely incompatible with what you say the goal should be. I think the author did a very good job.
  - amelius 7y ago
    > I think the author did a very good job. I wasn't questioning that!
- masklinn 7y ago
  > Yeah, of course, but how would you work this type of code into something that can be used in production? Why would you? > The goal should be to have a green thread library that you can just use without thinking about registers or assembly. No it should not. That's a completely separate (and mostly incompatible) goal than TFA's, which is educational.
- mamcx 7y ago
  Going for "toy" code to production ready is hard. Also, rust already have several options for concurrency/parallelism that are more idiomatic. The only reason I see is to have a coroutine library for build a language, yet I have wonder if I put a facade of Actix actors or similar for this case...
  - nwallin 7y ago
    > Going for "toy" code to production ready is hard. Too true. I recently implemented a feature, and I had a standalone working version 90% complete in a day or two. Getting the thing solid, tested, and integrated took the better part of a month. Part of that, I think, is our education model. Every project I ever had in school was started from scratch, I worked on it for a short period of time, turned it in, and never looked at it again. I got really good at that. I can write a toy version of a hard problem in a very short period of time. But I'm terrible at integrating those things into a larger whole, and I know for a fact I'm not alone in this. I think it's a huge problem that corporations think that a CS degree is job training and won't hire you if you haven't done it, but colleges think it's about abstract concepts and research and don't teach engineering principles.

> a simple but working example

by snissn 7y ago

> a simple but working example

Yeah, of course, but how would you work this type of code into something that can be used in production? The goal should be to have a green thread library that you can just use without thinking about registers or assembly.

heyzooos 7y ago
> I’m not trying to make a perfect implementation here. I’m cutting corners to get down to the essence and fit it into what was originally intended to be an article but expanded into a small book. lol
arnarbi 7y ago
> how would you work this type of code into something that can be used in production? You wouldn't. There are production-ready solutions to this in many languages. > The goal should be to have a green thread library that you can just use without thinking about registers or assembly. The goal here is very explicitly to explain a concept by example, which is largely incompatible with what you say the goal should be. I think the author did a very good job.
- amelius 7y ago
  > I think the author did a very good job. I wasn't questioning that!
masklinn 7y ago
> Yeah, of course, but how would you work this type of code into something that can be used in production? Why would you? > The goal should be to have a green thread library that you can just use without thinking about registers or assembly. No it should not. That's a completely separate (and mostly incompatible) goal than TFA's, which is educational.
mamcx 7y ago
Going for "toy" code to production ready is hard. Also, rust already have several options for concurrency/parallelism that are more idiomatic. The only reason I see is to have a coroutine library for build a language, yet I have wonder if I put a facade of Actix actors or similar for this case...
- nwallin 7y ago
  > Going for "toy" code to production ready is hard. Too true. I recently implemented a feature, and I had a standalone working version 90% complete in a day or two. Getting the thing solid, tested, and integrated took the better part of a month. Part of that, I think, is our education model. Every project I ever had in school was started from scratch, I worked on it for a short period of time, turned it in, and never looked at it again. I got really good at that. I can write a toy version of a hard problem in a very short period of time. But I'm terrible at integrating those things into a larger whole, and I know for a fact I'm not alone in this. I think it's a huge problem that corporations think that a CS degree is job training and won't hire you if you haven't done it, but colleges think it's about abstract concepts and research and don't teach engineering principles.