3 ms·

Is it async. with one thread per "work"? If so you are in trouble. I tried to see if you can abstract async. into a sync model but you need the callback and wak

by bullen 10y ago

Is it async. with one thread per "work"? If so you are in trouble. I tried to see if you can abstract async. into a sync model but you need the callback and wakeup syntax which is a dealbreaker. Google is not async the way you need async to work for it to make sense for IO-wait. What this discussion should lead to is for you to read the code and learn how async. can work. Not just to blindly follow the majority. Maybe if you like to have someone explain things; go to school, but don't take a student loan. But you are right there are a million things I'm missing to communicate, because of time and frankly I forget how it all works, intuition is very important for progress, if you had to explain everything all the time nothing would get made.

icebraining 10y ago
Is it async. with one thread per "work"? If so you are in trouble. I tried to see if you can abstract async. into a sync model but you need the callback and wakeup syntax which is a dealbreaker. No, you don't need any callback syntax. You can use CSP or Actors, and there are probably other models. See Go, Limbo, Erlang, Akka, and a bunch of other languages and frameworks.
- bullen 10y ago
  Ok, tell you right now, this abstraction is overengineered (akka). My Async.java class replaces the whole framework in 750 lines of Java: http://root.rupy.se/code http://root.rupy.se/code Erlang is not a good language because it can't share memory across threads. As for Go, it doesn't have real threads that can share memory either, you can't hot-deploy it and coding non-VM languages should only be done if you need the performance (3D engine). Don't know anything about Limbo except that it probably is crummy as hell and probably suffer from the same "no real threads" syndrome. The reason you don't need callbacks is because these language ARE "callback" languages. Just like Javascript. There are only two families of real usable programming languages: native: C (C++, Rust, etc.) and VM: Java (C#, F#, etc.).

by bullen 10y ago

icebraining 10y ago

Is it async. with one thread per "work"? If so you are in trouble. I tried to see if you can abstract async. into a sync model but you need the callback and wakeup syntax which is a dealbreaker. No, you don't need any callback syntax. You can use CSP or Actors, and there are probably other models. See Go, Limbo, Erlang, Akka, and a bunch of other languages and frameworks.

bullen 10y ago
Ok, tell you right now, this abstraction is overengineered (akka). My Async.java class replaces the whole framework in 750 lines of Java: http://root.rupy.se/code http://root.rupy.se/code Erlang is not a good language because it can't share memory across threads. As for Go, it doesn't have real threads that can share memory either, you can't hot-deploy it and coding non-VM languages should only be done if you need the performance (3D engine). Don't know anything about Limbo except that it probably is crummy as hell and probably suffer from the same "no real threads" syndrome. The reason you don't need callbacks is because these language ARE "callback" languages. Just like Javascript. There are only two families of real usable programming languages: native: C (C++, Rust, etc.) and VM: Java (C#, F#, etc.).