849 karma · joined November 23, 2015
I built something similar to manage sysex messages and patch libraries for my digitech guitar modeling workstation with webmidi: https://v0.app/templates/digitech-gnx3000-sysex-tool-GC5LzXA...
My favorite part of this so far has been spanning a range of parameters in seconds that would have taken a much longer time with gdigi and a completely unrealistic amount of time with the built-in knobs.
I own that FPGA now in a way I didn't before.
Teamwork Graph exposes all the people working on stealth products with code names right alongside their other work anyway.
There are many people working to extend NeXT, Openstep and even Rhapsody. Not to mention emulation projects and deep dives into XNU source, early Darwin source and shoehorning kernels and libraries into various places.
The Epson NX was purpose-built to run NeXTStep, for example, and bringing support for machines like that and the Canon object.station into 86box is a pet project of mine.
Join us https://www.nextcomputers.org/forums/index.php?topic=5286.ms...
This is a brutalist gew-gah.
The value built on that stability was probably worth acquiring, and it’s infra will decay.
And a new system prompt stanza was fledged.
"No, there is ... at home."
"At home..."
In five? Everybody but me.
Ever try make a product using Google Glass?
My hunch is that torsion, flex and their effect on the capillary structures are at play, but I haven't been able to step away from CS myself.
Being comfortable with the default level of trust is one thing. Command of the code is another.
By running the generated code at all, you've found some acceptable level of trust and comfort.
Scaling that comfort and trust seems to be the obvious move.