wrend VS vite

It’s also callable from JavaScript if you don’t want to have to deal with the Rust toolchain. Checkout this directory if you want to see some copyable examples, including raw html and javascript, which is about the lowest barrier to entry you can get I think: https://github.com/austintheriot/wrend/tree/master/examples

Major props for https://github.com/austintheriot/wrend/tree/master/examples -- having real examples integrated with different build systems really lowers the barrier to start playing around

Hi all! Wrend is a wrapper library around raw WebGL2 code. Its goal is to make working with WebGL/WebGL2 more convenient when writing Rust and/or JavaScript/TypeScript code in the browser. Because of a JavaScript-compatible wrapper API around the raw Rust code, wrend is callable from both Rust AND JavaScript, and it includes a strongly typed TypeScript API. Similarly, it is available for download from both crates.io and npm. I initially started this library out of frustration. I love to do creative coding, but I found myself dedicating more and more time and energy to refactoring bad infrastructure rather than working on new creative projects, so I decided to channel that misspent energy instead into a structured library that would give me the unified organization I was looking for and that I could also share with others. Some highlights: wrend provides safe and easy abstraction over requestAnimationFrame calls, making continuous animations as simple as calling start_animating and then holding the returned handle in memory. Stopping is also as easy as dropping the returned renderer handle and/or calling stop_animating. (When working with JavaScript, it’s as simple as calling free() on the the renderer. Taking canvas screenshots is built in, and so is direct recording of the canvas—something invaluable when doing creative coding and sharing the results. Why WebGL and and not WebGPU? While I’m aware that WebGPU is up-and-coming, and I’m very excited for it, and while it is even possible to write right now in Rust, I’m a web developer first and foremost, and I like to share my creations with lots of people. As soon as WebGPU support is stable in mainstream browsers, I will happily redirect my energies :) Wrend is very work in progress, and it’s actually my first Rust library in general, but I decided it was finally time to share what I’m working on with the world. Code: https://github.com/austintheriot/wrend Live Demo Site: https://austintheriot.github.io/wrend/

Demo: https://austintheriot.github.io/wrend/ray-tracer Code: https://github.com/austintheriot/wrend/tree/master/demos/ray_tracer

I think initially I used their autogenerated templates and other's templates as well, but lately, in my own personal projects, I've started rolling my own Webpack config (v5) with WasmPlugPlugin, which seems to work decently well most of the time. Here's one of my recent frontend crates that is fairly standalone and can be copied if you want a starter template that has been recently updated and has a good chance of compiling / working correctly for you with minimal dependencies: https://github.com/austintheriot/wrend/tree/master/examples/vanilla_rs

Code: https://github.com/austintheriot/wrend/tree/master/demos/game_of_life Demo: https://austintheriot.github.io/wrend/game-of-life

As of this writing, initializing a Hattip project requires some manual commands. However, keep in mind that a zero-config development environment based on Vite is in the works.

import { defineConfig } from 'vite' import react from '@vitejs/plugin-react' // https://vitejs.dev/config/ export default defineConfig({ plugins: [react()], server: { port: 4200, } })

For the frontend of "I Disappear," I leverage the automated build & deploy system provided by Netlify, which seamlessly integrates with Vite. This setup ensures that every deployment is optimized for performance, utilizing Vite’s modern build tools to enhance speed and efficiency.

Given our team's collective proficiency within the React ecosystem, we decided to leverage this expertise for our project. Initially, we contemplated utilizing Next.js; however, due to the limited practical experience with this technology among key engineers and the pressing timeline to develop the first prototype, we opted for a Single Page Application(SPA) approach. For bundling, we selected Vite, primarily due to its super fast build times, simplicity of configuration, and potential for a nearly seamless transition to server-side rendering.

We are continuing to add new project templates for various types of projects, and we've recently created one for the infamous combination of React with Vite tooling.

Vite focuses on providing an extremely fast development server and workflow speed in web development. It uses its own ES module imports during development, speeding up the startup time.

Vite and Next.js are both top 5 modern development framework right now. They are both great depending on your use case so we’ll discuss 4 areas: Architecture, main features, developer experience and production readiness. After learning about these we’ll have a better idea of which one is best for your project.

import { defineConfig } from 'vite' import react from '@vitejs/plugin-react-swc' import path from 'path' // https://vitejs.dev/config/ export default defineConfig({ plugins: [react()], server: { port: 3000 }, css: { devSourcemap: true }, resolve: { alias: { '~': path.resolve(__dirname, './src') } } })

I am currently utilizing Vite:

Homepage: https://vitejs.dev/