threlte VS Svelte

Thanks! Threlte is "just" offering a declarative way to express Three.js. If you know how the `` component and its props and event handlers work, you can use the Three.js documentation for everything else.

Apart from that with Threlte I personally practice documentation-driven-development, so ecosystem packages are exhaustively documented. If you're missing something, let us know via an issue[1] or on Discord[2].

Accessibility is a topic we didn't care enough yet to be perfectly honest. Accessibility doesn't stop at screen readers though, it's about contrast, size, colors, motion, reachability, and so much more that we cannot provide and are a consumer topic. Naturally WebGL apps suffer from being practically invisible to screenreaders. There are workarounds[3] but essentially this has to be solved by consumers of Threlte (devs) and hopefully by browser vendors at some point in the future.

[1] https://github.com/threlte/threlte/issues

[2] http://chat.threlte.xyz

[3] https://github.com/pmndrs/react-three-a11y

more specifically it's using the svelte wrapper of three.js called Threlte: https://threlte.xyz/

Three.js is great when there is a layer between me and it's API. Been playing with https://threlte.xyz/ and really enjoying it.

Maybe try https://threlte.xyz/

Now this is a very high level overview and a lot of really important stuff is missing. Things like event propagation, pointermissed events, different event targets, a super clean syntax and more is all implemented in Threlte 6's interactivity plugin. Check out the code here.

GPT-4 is a fantastic tool for coding, really looking forward to using it with the latest Svelte docs. Perhaps consider adding the documentation for Threlte?

) with complex functionality, since the app needed a graphics pipeline and I wanted to write one up myself. The next page I made did not need a pipeline, so I opted to use Threlte (a Svelte version of react-three-fiber) to make the code simpler to write and easier to maintain. If a scene you want to create has a lot of different meshes, materials, animations, etc. you might be best off using Blender to get it looking perfect. You can export from Blender as .gltf files which can be imported into Three. If you want a more specialized solution, I'd need to know your use case a little better. How are you building the scenes?

Svelte and specifically, SvelteKit is an open source web framework that makes developing web applications easier.

the technical decision how Svelte should treat self-closing html elements was hindered by Prettier:

Svelte

React has introduced measures like batching state updates, background concurrent rendering and memoization to tackle this. My opinion is that the best way to solve the problem is by improving their reactivity model. The app needs to be able to track the code that should be re-run on updating a given state variable and specifically update the UI corresponding to this update. Tools like solid.js and svelte work in this manner. It also eliminates the need for a virtual DOM and diffing.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Svelte is a powerful web framework that offers a fresh approach to building web applications. Its simplicity, reactivity model, and built-in features make it an excellent choice for developers looking to create efficient and maintainable applications. By following this guide, you should now have a good understanding of how to get started with Svelte and build your first components, routes, and transitions. You can read more about svelte on the official Svelte website.