this post was submitted on 22 Jan 2024
15 points (89.5% liked)
General Programming Discussion
8810 readers
14 users here now
A general programming discussion community.
Rules:
- Be civil.
- Please start discussions that spark conversation
Other communities
Systems
Functional Programming
Also related
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's not what the article is saying though. It's arguing that the memory model that imperative languages assume is not actually how modern chips work. What we end up with effectively is a VM on the chip that pretends to be a really fast PDP-11 style architecture. Writing assembly against this VM still has the same problem. Interestingly, the way modern chips are designed actually fits better with functional style that doesn't rely on global state.
i got there at the end
I'm not familiar enough with how Habit and Ante represent memory allocation to say, but part of the problem right now is that there's already a VM baked into the chip to provide the PDP-11 style emulation on top of it. Ideally, we'd want chips that expose their native behavior, and then craft languages to take advantage of it. Similarly to what we're seeing happening with graphics chips.
I imagine it would be the same dynamic, and you could have an emulation layer on the chip with its own instruction set for legacy code while providing direct access to the native instruction set.