glicol VS vite

I've worked on Ambient Engine and now on the Bevy engine. I totally agree with these points, very valuable. I only make some comments from my professional (audio) perspective:

We need the highlight author's affirmation of cli. Rust's tui (ratatui) is great. I used it to make Glicol-cli [1]. If you are a Linux user, you are welcome to test the music production of the code.

Speaking of game audio, I actually think rust is perfect for audio. I have also continued to develop Glicol recently, and my recent goal (starting tomorrow) is the bevy_glicol plug-in. I want to solve bevy's audio problem on the browser.

All in all, even though I've had my share of pain with ecs, I still think rust is very valuable for game and app development, maybe not multiplayer AAA, maybe practical apps.

[1] https://github.com/glicol/glicol-cli

[2] https://github.com/chaosprint/glicol

Nice! Great project website styling and demo.

I had a WebGPU scope demo using vanila JS here, but it's not connected to AudioContext at all.

https://stackblitz.com/edit/vitejs-vite-cuc9vs

Still, I had to use the old WebGL solution for https://glicol.org since the WebGPU support seems to be pretty slow at the moment.

Suno is great and I already shared its potential back in v2. I have always believed that the essence of digital music is "organized numbers". I think what needs to be thought about is how to use AI in this process. If you look at the results (numbers) generated, then we are indeed very close. But there is another future I believe: I hope AI can compose music with me, like copilot. This is why I keep working on

https://glicol.org/

and the destination is:

https://github.com/chaosprint/RaveForce

Also want to hear your feedback.

Interesting!

Similar note-based expression can be found on TidalCycles/Strudel. although it's not valid MIDI format anymore, you can use notation like c4, f3, and make them as "pattern". Samples are also supported in the same manner:

https://strudel.cc/

And in my project Glicol, I use only numbers in the seq node. So 60 means middle C. Underscore means rest.

https://glicol.org/

I also applied with Glicol (https://glicol.org/) and got rejected, which is totally understandable. I am basically working this project on my own with almost zero extra funding.

I am currently working on a new website. The old stack is Vite, Svelte and Windi CSS (discontinued unfortunately). So this time maybe Astro + Solid + Tailwind.

And I am also trying to rewrite the whole Rust backend if possible, so there is quite some work to be done.

Let me know on GH or Discord if you are interested.

It's a good chance to try Rust, WASM, DSP, etc.

This is a really informative and inspiring article.

It hasn’t been 6 months (not 6 years) since I quit my full-time job as a Rust developer to start my own business.

As time goes by, I can feel the pressure of mortgage and car loans, and I can also feel the care and pressure of my family.

My original plan was to make an interface for Glicol (https://glicol.org), and to develop relevant hardware with firmware written in rust for school education.

I sent some cold emails to VCs, but most of them got no reply.

I also sent an email to the Norwegian Museum of Science and Technology, offering to perform for children for free, but they didn’t reply for two months. I shamelessly sent it again, and someone finally replied with a rejection.

Only one VC talked to me and thought that I should convince and validate a partner first, and he suggested that I go to an incubator.

Very good advice.

Later I learned that even Norwegian education startups skipped Norway and focused directly on the US market.

People from the incubator also told me that it is impossible for Norwegian schools to accept new things independently.

This is very enlightening to me because most of Glicol's visitors are indeed from the US. And it took me so long to discover this fact.

But if I don’t start, I’ll never get past those six months.

I picked up LOGO when I was 6 and leant Pascal and C later.

I didn't program for a few years because I wasn't interested in competitions. So I think interest is the most important, otherwise it will be easy to get lost and give up.

Later, I became very interested in programming, mainly because I came into contact with music technology.

I think since your child is interested in game development, it is a good choice to start step by step. For example, starting with threejs. I also recommend learning Rust and Bevy so you learn the underlying layers and ECS.

Last but not least, although it's not related to games dev but I sincerely invite you and your son to try Glicol (https://glicol.org), the project that I am developing.

I quite my job as well to work on

https://glicol.org

I have a lot of feelings, but I don't have a blog so far. But one of my feelings is that universities should alloc some of their funding to many of these open source projects and open source community should be better managed rather than donation. My plan is to start my own company and work on hardware .

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/

Without any adding any dependencies you can connect react props to raw css at runtime with nothing but css variables (aka "custom properties"). If you add CSS modules on top you don't have to worry about affecting the global scope so components created in this way can be truly modular and transferrable. I use this with vite.

Little confused as to why it has vite in it‘s name, it seems unrelated to https://vitejs.dev/

it says in their docs that they recommend Vite https://vitejs.dev/

it goes like this.

1. you create a repo folder, you cd into it.

2. you create a client template using vite which can be plain typescript, or uses frameworks such as react or vue, at https://vitejs.dev/guide/

3. you cd in that client directory, you npm install, then you npm run dev, it should show you that it works at localhost:5173

4. you follow the instructions on your url, you do npm install @web3modal/wagmi @wagmi/core @wagmi/connectors viem

5. you follow the further instructions.

> It seems like this is for npm or yarn to pull from a remote repository maintained by @wagmi for instance. But then what?

you install the wagmi modules, then you import them in your js code, those code can run upon being loaded or upon user actions such as button clicks

> Do I just symlink to the node_modules directory somehow? Use browserify? Or these days I'd use webpack or whatever the cool kids are using these days?

no need for those. browserify is old school way of transpiling commonjs modules into browser-compatible modules. webpack is similar. vite replaces both webpack and browserify. vite also uses esbuild and swc under the hood which replaces babel.

> I totally get how node package management works ... for NODE. But all these client-side JS projects these days have docs that are clearly for the client-side but the ES2015 module examples they show seem to leave out all instructions for how to actually get the files there, as if it's obvious.

pretty much similar actually. except on client-side, you have src and dist folders. when you run "npm run build" vite will compile the src dir into dist dir. the outputs are the static files that you can serve with any http server such as npx serve, or caddy, or anything really.

> What gives? And finally, what exactly does "browserify" do these days, since I think Node supports both ES modules and and CJS modules? I also see sometimes UMD universal modules

vite supports both ecmascript modules and commonjs modules. but these days you'll just want to stick with ecmascript which makes your code consistently use import and export syntax, and you get the extra benefit of it working well with your vscode intellisense.

> In short, I'm a bit confused how to use package management properly with browsers in 2024: https://modern-web.dev/guides/going-buildless/es-modules/

if people want plain js there is unpkg.com and esm.sh way, but the vite route is the best for you as it's recommended and tested by the providers of your modules.

> And finally, if you answer this, can you spare a word about typescript? Do we still need to use Babel and Webpack together to transpile it to JS, and minify and tree-shake, or what?

I recommend typescript, as it gives you better type-safety and better intellisense, but it really depends. If you're new to it, it can slow you down at first. But as your project grows you'll eventually see the value of it. In vite there are options to scaffold your project in pure js or ts.