Hacker News new | ask | show | jobs
by kikimora 262 days ago
The only problem I see with this approach is lack of standard data structures allocated in native memory. In GC memory you have collections and strings. In native memory you would have to create such data structures yourself. Plus figure out interoperability between the two.
1 comments

You've hit on the exact problem. The friction of interoperability is the real wall.

Now, imagine if that friction disappeared. Imagine 90% of your codebase is safe, using traditional collections and strings, while only the critical 10% uses high-performance, native data types. What if moving between these two worlds was a natural, compiler-guaranteed feature, not a manual, error-prone task? How amazing would that be?

This vision of seamless coexistence is the core of my proposal. I've detailed it in a new, more focused post and would love for you to take a look.

https://news.ycombinator.com/item?id=45477324