That headline's as psyoppy as "schizophrenia".

I three MUDs in one as a channel mode for my IRCD the other month: https://github.com/float64co/psyrcd/blob/master/plugins/mud....

Both of these things. The timbres can be explained through evolutionary biology. The same brain centers used for processing movement in 3d space also start firing up to start predicting where any given piece of music will go.

An interesting note has a fundamental and harmonics and allows analogies to be drawn in RF engineering and quantum mechanics: https://www.google.com/search?q=any+good+parallels+between+i...

law.py — A Distributed Legislature: https://gist.githubusercontent.com/float64co/deb887691f13dee...

In the past couple of months I've

Built a Cythonized Icecast2 implementation I've wanted for years: https://github.com/lukeb42/cycast

Built a p2p Kanban board that fits in a single .html file and uses only the Python stdlib for LAN discovery https://github.com/lukeb42/kanban_p2p

Developed a p2p legislature that scales from a small team of 3 users to countries of tens of millions of people: https://gist.githubusercontent.com/LukeB42/deb887691f13dee9c...

Developed a small SPA framework inspired by React, Ractive-Load and hn.js: https://lukeb42.github.io/vertex-manual.html

Updated a news archival service for Python 3.x: https://github.com/lukeb42/harvest

Made a scriptable IRC client inspired by irssi and mIRC: https://github.com/lukeb42/scroll

and worked on a couple of my company's products.

Had to fix hardware detection myself only to find engine.generate()'s not implemented and yields "".

Maybe the author could get a large param model to help him get this done though.

Happy to help if needed. The project is already tested and benchmarked with several models and everything is working as expected. If you run into any specific issues, feel free to open an issue or PR.

Would you prefer to see ESM or neither?

ES6 modules. Tooling can take care of generating UMD from that as a single source of truth and since it’s the language standard for years now it’s the best supported format in the ecosystem. At this point UMD/CommonJS/etc are historical artifacts only useful to legacy codebases and by now they’ve all adopted whatever ESM->legacy compilation pipeline they need.

Thanks for this. I stopped writing JS for awhile just as ES6 was coming around the corner / coming into use. This will be in 0.0.2.

React components might eventually be removed in favor of making the templating system as fast and as elegant as possible but for the time being they provide flexibility.

You can read https://lukeb42.github.io/vertex-interop.html for more info.

9kb (minifier+brotli)

We could remove 3kb by removing the router but that's not gonna happen. You're more than welcome to minify+brotli it yourself if you use vertex.js in production.

Beauty /is/ in the eye of the beholder. The rationale /here/ is that the more text in a page the more code you'll fit in your head the more you'll get done, the more confidence you'll have and again the more you'll achieve.

OP has a valid point. On my Mac, it's unreadable without zooming in. I immediately left the page.

Thanks for the valuable feedback. I've added a mediaquery for your use case. This should be more legible now: https://lukeb42.github.io/vertex-manual.html

Send me a screenshot via https://catbox.moe if it's unreadable and I'll get this done and dusted before leaving the thread. Thanks.

Zero code is in your head if you can't read it.

The predominant monitor in existence is your average 24" 1080p monitor, sat at, on average, 32" away from the head. The average person has worse than 20/20 vision.

You must test your website in such conditions and make sure it is readable, and also make sure it meets at minimum WCAG A, but preferably the whole way to AAA if possible.

Thank you but the predominant monitor's probably a smartphone. The average professional is probably using a 4k monitor at the moment.

Everything in the free documentation I've provided you out of my own time and money that you're referring to exists in relation to the other elements in that page, so to get the experience you're after simply ctrl+scroll and change the CSS zoom level like the riot at parties that you could be or catch up with circa 2013-2014 and invest in a 4k display please.

"Zoom in" or "buy a different monitor" is not an appropriate response to people bringing up the plethora of objective & subjective a11y issues on the page.

If you really don't care about providing an accessible experience, try this: no one will use the tool if they can't read the docs. With my monitor and eyesight, it's entirely illegible.

read the rest of the author's responses here. Everything comes across as very defensive and "take it or leave it". OK, you're the one trying to get me to adopt yet another SPA framework in 2026 so I guess I'll leave it.

Presumably you've posted it here because you would like others to either view it or consume it, neither of which are possible on (at least my) fairly common Galaxy S23 phone. Of course it's your decision how you want to serve the experience; we're just saying that right now your page is a fairly poor experience compared to the average website.

>> is that the more text in a page the more code you'll fit in your head the more you'll get done

I don't know in what world that makes any sense. Or why someone would want to "fit code" in their head...