For a MVP, it's hard to beat Phoenix Framework channels and Liveview, and if you want to completely decouple the UI from the backend with something like a native app, or separate webapp, it's absurdly easy to just add the resources to a route that goes through the :api pipeline instead of the :browser.
Once you are ready to outgrow a single machine deployment, the BEAM clusters so well in a way that works the same on your dev machine. Also if you want to get really complicated multi-service design, Umbrella apps are leagues better than docker-compose setups that I have had on dev machines that make a 16G Macbook pro instantly put everything into swap.
Half of the reason that I enjoy using GNOME, KDE, and other distros is that I can theme the entire system for a relatively consistent experience. I enjoy having system apps all be the same configurable color theme and even design language with flat themes and material themes becoming popular.
Layouts might be a bit much, but themes are a key part of the user experience.
I think the bigger issue are that devices are trying to handle many things at once, and badly. I stick with projectors (which keep getting more affordable) which just handles video, and an audio system which just handles audio. No smart tv bs, and I just use a fire stick/chromecast/laptop to handle the content.
I'm more than happy with my setup, except that I usually want to wait until after sunset to watch shows or movies. It's probably better for my own free time to not spend a day watching tv anyways.
That's pretty cool. I remember using a rocksmith cable into my laptop running Bias FX as a last minute replacement for my amp when it died the day before a gig. Good to see that there is a product that fills in the niche for USB-C.
My biggest question for this product is the sample rate, and at what output the input clips. This would be fine for most passive guitars, but active EMGS or a Piezo system could definitely clip or distort the input if you don't roll off some volume.
For a MVP, it's hard to beat Phoenix Framework channels and Liveview, and if you want to completely decouple the UI from the backend with something like a native app, or separate webapp, it's absurdly easy to just add the resources to a route that goes through the :api pipeline instead of the :browser.
Once you are ready to outgrow a single machine deployment, the BEAM clusters so well in a way that works the same on your dev machine. Also if you want to get really complicated multi-service design, Umbrella apps are leagues better than docker-compose setups that I have had on dev machines that make a 16G Macbook pro instantly put everything into swap.