Comments by "" (@diadetediotedio6918) on "" video.

@ People need to know that there's no such thing as a silver bullet in computer science, virtual threads have their own sets of drawbacks compared to async-await, and async-await has it's own sets of drawbacks compared to using native threads. Async await is not automatically worse than virtual threads, it's more explicit and it works well enough for the majority of the cases, it's also only dependent on the compiler being able to implement it (and thus can run anywhere the runtime already runs without special modifications).
3
00:25 Has introduced? When? Can I use it right now in my project as a stable thing?
2
Why do you need to resort to fallacies to solidify your point? You know there are many codebases written in C# (or languages even less verbose than it) that are multi-million line, you did not asked for the opinion of all those codebase devs to see if this is true. You also made a leap of logic by scalling from "unless you are the only one working on your own project" to "work on a multi-million line project with other 100 devs", those things are not equiparable, it's pretty easy to see how things could be drastically different if the project scope was different or the number of devs was smaller (or even higher) than yours, and you don't have the data to back up your claims.
2
@ It only took 10 years, HAH. And it is still unusable in android, meanwhile Kotlin has coroutines (inspired by async-await) that work on any environment.
1
@ That's the thing, it's not automatically the superior approach. What are the drawbacks you recognize on this with a GC compared to async/await? This is the minimum I expect when someone says something like this.
1
@ Kotlin, however, is used everywhere, and it's heavily used in android. Meanwhile the Java solution still does not run on android.
1
@RealViPdude Bullshit.
1
@danielbennett5726 It's extremely easy to do so, there are things like Avalonia and Uno that makes this very simple.
1