I don’t come from a JS background, and JS makes me very angry every time I use it. But it’s unavoidable if you want to build something on the web. I tried to pick up React a few years ago for a project, saw the JSX, and put it right back down. At the time, Vue’s emphasis on HTML templates was comforting and approachable, since I like HTML and its simplicity and visual structure. So I tried Vue, and found it was easy to go from toy examples to real, working projects with no major gotchas.
I recently spent some time learning Vue 3, and I’m a little less enamored. The composition API is nice for not requiring deeply nested code inside a giant object literal. But having my code littered with .value is ugly and a source of endless bugs. (You also don’t always need .value, such as when referencing a Pinia store. Ugh.) I looked into the pending “Reactivity Transform”, but it too introduces weird surprises and seems like its issues may be unsolvable.
Bottom line: I hope and pray for the day WASM allows Python to get a decent footing in the browser environment.
I recently spent some time learning Vue 3, and I’m a little less enamored. The composition API is nice for not requiring deeply nested code inside a giant object literal. But having my code littered with .value is ugly and a source of endless bugs. (You also don’t always need .value, such as when referencing a Pinia store. Ugh.) I looked into the pending “Reactivity Transform”, but it too introduces weird surprises and seems like its issues may be unsolvable.
Bottom line: I hope and pray for the day WASM allows Python to get a decent footing in the browser environment.