Seth "Twylo" Morabito @twylo@mastodon.sdf.org

This is a really good discussion on licensing. I'll be honest, in the past I've chosen MIT just because I was lazy and didn't care what anyone did with my software. But maybe I need to adjust that attitude.

I started working on a Rust WebAssembly project about a year ago and more or less put it aside because the tool chains were so miserable and painful to work with. I picked it up again a few weeks ago and things are really night and day better.

`wasm-bindgen` and `wasm-pack` have made this process so much easier. I can just publish my WebAssembly as an npm module and be done with it. Way easy.

The default license I choose when creating a new project is the MIT license. But I wonder, am I doing a disservice to the open source community? Should I use GPL for new projects? Or do you find GPL to be too restrictive?

I worry about these things.

Apparently I am supposed to have strong opinions about trending topics, but honestly I just can’t muster strong opinions about them.

If you tweak the colors of the Open Genera X11 window just right, you can approximate the sickly blue glow of a real Symbolics console.

Looking for fellow hackers, tinkerers, retrocomputer enthusiasts, electronics people, linguists, book artists, calligraphers, and general nerds to follow.

TOOT AT ME.

I should really use this thing more often. In an ideal world, I'd kick Twitter to the curb and never speak of it again. I've become less and less enthused about its direction and leadership as time has gone on.

My first toot! Toot toot!