3 ms·
> And I'm a C# guy, I wouldn't want to use anything else, it's Java done right. It has colored functions. Every async function is turned by the compiler into a
by shock 6y ago
> And I'm a C# guy, I wouldn't want to use anything else, it's Java done right.
It has colored functions. Every async function is turned by the compiler into a class with an embedded FSM. Async is viral in C#, so much so that even main() had to be made async. So, no, it's not Java done right.
- BuckRogers 6y agoJava done wrong? I've always been a Java/C# person, that's the general programming abstraction layer I've spent most of my education and career in and prefer it. I greatly prefer C# (and all that comes with it) over Java. But if C# didn't exist, I would probably prefer Java over all other alternatives. The only reason I'd fall onto Javascript upon C#'s disappearance would be because most of my experience is in web, but definitely not due to the ecosystem or language. So from a language/ecosystem perspective, Java is my 2nd choice, I never hated Java, it's popular for good reasons.
- shock 6y agoI like C# a lot (internal classes, yield, etc.) except for their async implementation. I believe Java's Project Loom will prove to be the superior solution.
- BuckRogers 6y agoI'd likely agree with you, mostly on the grounds that by default being late and learning from earlier implementations always helps.