••
That's not exactly true when you look at the history of how fascism works. Actually, capitulation is futile, as there is no bottom to what the autocrat will demand. If you give in, all it shows is you are an easy mark. Resistance is the only winning move. Timothy Snyder put out a great book about this called "On Freedom", which explains most of the power an autocrat has is given freely by people who anticipate what he would want and just offer it without being asked, precisely because they have a notion that resistance is futile. Tech leaders were right there at the inauguration, they didn't even try! So the role these tech guys played early on was teaching Trump the extend of his power. If you look at how Trump handled schools and law firms, you see an excellent case of capitulation vs. resistance and how that played out. Take the situation with Columbia compared to Harvard. With Columbia, they capitulated to Trump illegally withheld $400m and agreed to all sorts of demands, only to be met with more demands. Harvard faced similar pressure, but decided to fight it and won in court. In the law world, Trump made demands to several high-profile law firms. Paul Weiss, Skadden, and Kirkland & Ellis all capitulated to the demands, other firms saw these law firms capitulate and just offered up settlements themselves. 11 law firms entered into agreements with the administration, and they didn't even have to ask all of them! Meanwhile, every firm that challenged demands made by the Trump admin, including Perkins Coie and Jenner & Block, won in court. Tech giants didn't capitulate to the Trump administration because they felt they had no other choice, they did it because they felt it would be best for their bottom line. They have no principles, no backbone, and are opportunists who will say anything if a dollar is on the line.
•••••••••••••••••••••••••••••••••••••
I have worked on the code of legacy applications like MasterTracks Pro, Studio Vison and SAW and my opinion would be that you need to start from the ground up with collaboration as the guiding light. The existing applications have workflows and data models that are very monolithic and tied into the concept of a single user, using a single application with application logic and workflows implemented in code. That code sometime exposes functionality through scripting dictionaries or plugin APIs, but the this is backward in my opinion. Other commenters have stated what a pain it is to just get two environments in sync. A complex production will have tons of plugins, various MIDI and audio interfaces, differing outboard gear and other variables that make life hard when sharing files. You also have asset management issues; where are the audio stems, vocal tracks, library resources, etc. stored and how are they shared. If you want to collaborate in real-time, then there is another layer of technical challenges. I have been working on a system that is influenced from my earlier experience building audio tools for earlier generations of sequencers and DAWs, rendering pipelines for Dreamworks and configuration management systems for Amazon. I feel you really need a system that uses a DSL and all operations are defined at that level. There shouldn't be anything you can do in the user interface that isn't available at the DSL level. You can then think about techniques used in Docker, k8s, etc. to define and deploy both the environment and the interpretation of the DSL in the user interface.
•••••••••••••••••••••••••••••••••••
hi HN, im luis. 10+ years in software and security, homelabbing for about 5 "netflix and spotify" is how it feels to use, not what it does under the hood. holyarrs doesnt play anything. you browse your shows, movies and music like a streaming app (top 10s, new & popular, coming soon), tap what you want, and it sends it to your downloader and files it into jellyfin or plex. those still do the playing before this, my server needed 6 apps for that: sonarr for shows, radarr for movies, lidarr for music, bazarr for subtitles, prowlarr for indexers and overseerr for requests. 6 setups, 6 databases, and nobody in my house but me could use any of them - the image is 15 MB. the 6 apps it replaces are 718 MB together - one go binary, svelte UI, sqlite. the image has no OS and no shell - runs on amd64, arm64 and armv7 - works with qbittorrent, sabnzbd, plex, jellyfin, emby - imports your sonarr/radarr setup, and speaks their api so seerr can keep talking to it - no api keys to set up. posters and search come from a metadata server i run and pay for - free, AGPL-3.0 how it got built: claude code wrote most of the go and svelte. i wrote the specs, reviewed everything and tested it on my own server. what it got wrong: it never noticed cost. the app got heavier build after build until i started measuring every single one. thats the only reason its still 15 MB why you might want to wait: its young, 1.0.7 shipped today and im fixing reports as they come in. music is still being built out, and a few features are held back until theyre fully tested (plex watchlists, trakt lists, subtitle sites) why i built it: my family wanted netflix and i had 6 apps nobody but me could use im in the comments, tell me what breaks
••••••••••••••••••••••••••••••••••••••••••••••••••••
 Top