A modern programming language that makes developers happier.

kotlinlang

Has the possibility of concurrent mode been discussed? React has started implementing it, and it looks interesting

<https://reactjs.org/docs/concurrent-mode-intro.html>

&gt; Imagine we’re navigating between two screens in an app. Sometimes, we might not have enough code and data loaded to show a “good enough” loading state to the user on the new screen. Transitioning to an empty screen or a large spinner can be a jarring experience. However, it’s also common that the necessary code and data doesn’t take too long to fetch. Wouldn’t it be nicer if React could stay on the old screen for a little longer, and “skip” the “bad loading state” before showing the new screen?

Making the solution to that problem above trivial to implement could greatly improve UX

totally agree, it’s kind of sad that decades later and all the phases of technological solutions, a case like that is presented as currently insoluble.. you would think this would be an ideal problem for a declarative ui, especially one that also is using a language with a suspend keyword..

Yes, we are wanting to support concurrency.  The primary reason we are currently single-threaded is just that it was the most pragmatic first step.

will concurrent mode slated to be a likely “post 1.0” feature then?

I'd like it to be pre-1.0, but there are a lot of competing priorities, so TBD.