2 ms·
The Symbolics systems are very nice but very niche. They only really work when you can ship a product with a complete supporting stack, down to the hardware. Y
by TheOtherHobbes 9y ago
The Symbolics systems are very nice but very niche. They only really work when you can ship a product with a complete supporting stack, down to the hardware.
You couldn't build an equivalent for web or app development, because the technology doesn't support an equivalent approach.
You certainly couldn't sell them to the public and leave them open, because they're too easy to break. You might have been able to sell a commoditised application layer with commoditised hardware to the public, but that would have required an extra few zeroes on the end of R&D and marketing costs.
You could argue that web technology should have started with an open approach like this. But there would have been consequences, not least of which in browser design, which would have gone from being a fairly trivial parser/renderer to a complete VM running on non-optimal consumer hardware, and the fact that without commoditisation, development systems would have cost five or even six figures.
The benefits might have taken a while to become obvious.
It's possible that functional VM web technology would have made the web work better after the initial take-up issues, and we'd have something sleek and elegant instead of the awful glued-together patchwork of mediocre hack technologies we have today. But it's also possible the adoption costs would have strangled the web at birth.
We'll never know, but IMO it's an interesting question.
This kind of competition is something that I'd really like to see being analysed in academic CS. It would be useful if the tradeoffs were understood theoretically instead of just being historical curiosities.