> declarative languages have almost no bugs"
Is this even a declaritave language? Doesn't look like it to me at a glance.
Is this even a declaritave language? Doesn't look like it to me at a glance.
But the nicest feature, invisible in the syntax because it is a property of the runtime under the hood, is that when you change your mutable state, any layout that used those variables is automatically scheduled for refresh. You thus declare what is on the screen, and how it is arrange, and the system knows what to do. In this sense it more like SQL, where you give it a goal, and don't specify the ordering of how to achieve the task.
There are also mini-solvers built into the language for the common tasks of solving for rectangles and points, which are quite handy.
Please take it for a spin, you might like it!
1) Changes are triggered through regular mutation, not special API calls
2) Reactive dependencies are automatically determined
The combination of these two traits is somewhat unique, and is offered by MobX and (apparently) Beads.
If the main facilities for writing logic in the language are procedural, than i'd call that a procedural language.