I can't help but sigh exhaustedly. There was a moment in time angular was the thing. And then x. And another. And React.
The problem each of them tried to solve, and continue to try to solve is purely lexical in the end. It's about writing things differently. Creating abstractions (terms) beyond what the underlying language/platform allows you to do.
And this is not a bad thing. The solution really is to create your own language so you can express the problem you are solving in the terms of the problem and not the underlying language/platform/hardware.
And then I sigh again... aah but if only Common Lisp and it's macros were the underlying platform.
> The solution really is to create your own language so you can express the problem you are solving in the terms of the problem and not the underlying language/platform/hardware.
That's what Elm is about. I've talked about it in another thread, so I won't repeat myself here.
I had heard of it, but never checked until you mentioned it in this context. It seems that Elm is an entirely new language written atop JS (or maybe not, and targets JS?). A DSL.
DSLs also usually are an incomplete solution. Unless they themselves allow adhoc language creation using the DSL as a base. Common Lisp with its macros allows writing DSLs quite off-handedly as you program. You grow your program and language together as you get deeper into your problem.
The problem each of them tried to solve, and continue to try to solve is purely lexical in the end. It's about writing things differently. Creating abstractions (terms) beyond what the underlying language/platform allows you to do.
And this is not a bad thing. The solution really is to create your own language so you can express the problem you are solving in the terms of the problem and not the underlying language/platform/hardware.
And then I sigh again... aah but if only Common Lisp and it's macros were the underlying platform.