The Typelevel stack and Scala Native

[armanbilge]

Thank you for the reply!

@jrudolph

So, providing proper threading (+memory model) support, really would be an important milestone for scala-native.

I absolutely 100% agree. My concern is that properly supporting multithreading is an enormous amount of work for a project that is currently very under-resourced, and furthermore that work distracts from less ambitious improvements that will do more to improve adoption today. To quote you from the old thread:

@jrudolph

Ultimately, the only way (for anything) to survive is find its (probably temporary) niche. The statement at the top about why Scala Native is relevant and what is missing and will be done is too fuzzy to be useful. You could say this is a classic project management problem. If you want such a project to succeed you will first have to admit there’s an insurmountable amount of work ahead of you, and then you will need to have a very specific idea how to arrive incrementally at something useful as quickly as possible.

Essentially, I am trying very hard to help carve out that temporary niche. We now have a platform, and I think the ball is in Scala Native’s court again to catch up with UX improvements (such as incremental linking and line-numbered exceptions) as well as performance (early benchmarks of http4s Native show that it’s not atrocious, but there’s still work to be done to match the top Node.js frameworks). This will help make Scala Native a real production choice, not for every use-case as you point out, but at least for some.

Of course, this is predicated on the assumption that Virtus Lab and Scala Center want to see more adoption before they will allocate more resources for the project.