|
|
|
|
|
by stevendgarcia
172 days ago
|
|
That’s an interesting comparison. I agree J aligns philosophically (values over references), and you're right that it feels more optimized for pure mathematical work rather than managing long-lived, mutable state in concurrent services. What I’m exploring is whether a model like this can provide similar benefits in CRUD-heavy systems without needing GC or manual memory management. If you’ve seen J used effectively in that space, I’d love to hear more about it. |
|
It may be not efficient at all for using rich types and structs because stack language is the earliest approach whose pros are coming from ability to make the single-pass compiler. If your requirements do not fit in single-pass approach, then you are going to have a really hard time of guessing what and when is needed to be recycled.