5 ms·
Refreshing that it's built using the vue framework vs the typical react.
by westoque 1y ago
Refreshing that it's built using the vue framework vs the typical react.
- treyp 1y agoThe bulk of it is WebGL. Vue is doing very little here. Since it's a single static page rendering to canvas, it really doesn't need a framework like Vue or React.
- wetpaws 1y ago[dead]
- mattlondon 1y agoWhy does it even need anything here other than vanilla JavaScript? I don't see the need for a SPA framework.
- IshKebab 1y agoWhy? React is much better than Vue in my experience. Vue 2 was so bad we ended up painfully porting an entire election app to react at a previous job.
- h4ch1 1y agosvelte's better than both : ^ ) (someone continue this with framework x) but seriously, I'm very interested to hear your gripes with Vue that were solved by react, since the latter feels much worse DX-wise than both Vue or Svelte, notwithstanding worse performance as well.
- DonHopkins 1y agoSvelte's MUCH better than both : ^ ) (You didn't say framework x had to be a different framework than Svelte! x)
- brazukadev 1y agoLit-html is better than all frameworks :)
- IshKebab 1y agoVue 2 had really bad support for static typing. It's improved in Vue 3 but still not as good as React. TSX is especially good. But the main issue is the automatic reactivity. It's difficult to reason about and leads to spaghetti code. We also had occasional issues where people would put objects in properties that had some tenuous link to a database object or something, and Vue recursively infects the entire object with getters and setters to make the reactivity work. Sometimes we didn't even notice but it makes everything way slower. I haven't tried Svelte so I'll take your word for it! Also this was 3 years ago so I may have misremembered some details. No nitpicking!
- PaulHoule 1y agoI was using React at work and looking at the Vue manual which at first looked good to me because Vue has first-class lists, it fit my model of web applications better. Than I saw three.js and other things were people used React to render things that weren’t ordinary web apps and I realized I could draw anything I could imagine with React but not with Vue. I like the idea of svelte but for apps that are small enough that svelte has a bundle size advantage the bundle size difference isn’t decisive (users won’t usually notice or care) and if your app is huge enough that the bundle size is a problem you have problems bigger than your choice of framework.
- phatskat 1y agoI helped port a Vue 2 project to Vue 3, and then I worked on a Vue 3 project we’ve slowly been rewriting in a greenfield Nuxt 3 project. Vue 2 and the options API were just difficult in all senses - even Vue3 with Options feels bad. I really enjoy 3 with the composition API, and I have always had a difficult time reasoning about React personally. While I will continue to probably promote Vue where it makes sense, I’m honestly more inclined towards learning Svelte, HTMX, and other less arduous frameworks.
- chrismorgan 1y agoIn practice, it’s been written as plain JS with a tiny bit of gratuitous Vue and SCSS bolted on (see even how Vue’s onMounted and onBeforeUnmount are fed callbacks that just run the actual initOGL and destroy functions). It would have been easier and shorter to write without Vue and SCSS than with them! What’s currently spread across index.html, src/styles.scss, src/main.js and src/App.vue would have worked better all in index.html, or if you really wanted to, you could still split the CSS and JS into files src/styles.css and src/main.js.
- qoez 1y agoSurprised this is using any vue/react framework. I expected just a plain webgl+shader without libraries codebase.