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.
That's all fine if you stay stateless. Once a well-meaning developer introduces local application state into your web app or adds a feature that locks your database, your web server is no longer "embarrassingly parallelizable". This doesn't even start to handle issues you get when you use a single-threaded langugage that cannot handle multitasking well. Sidekiq makes money purely because Ruby is single threaded, and its thread will lock if you give it a task that takes too long.
The microservices movement seems to be a misguided reaction to these self-imposed issues where instead of handling proper task management on a process level or with async/concurrency, functionality is split between servers, codebases and infrastructure. This problem was solved with Erlang decades ago with the actor model and supervision, and newer BEAM languages like Elixir and LFE are a pleasure to work in.
You even have this model and concurrency ported to JVM with Akka, C++ with CAF. Granted, the Actor model and the field of concurrency as a whole is solving the problem of enforcing statelessness in a way such that tasks can be efficiently distributed multiple cores, and that no single task locks up your machine for too long.
Depends on what you want out of a computer. If you want a general purpose (as in write programs and run them) Plan 9 is a pretty self-contained operating system and software system if you are confident in your C and C++ abilities. I've also heard that BSD is pretty well documented internally, so if you know that system, you should be ok.
Alternatively a fun retro setup could be an apple II or a windows 98 box with Encarta disks.
As a specific distro that is directly focused on what you specified, Endless OS seems to have the Encyclopedia and other preinstalled apps for online use you were talking about.
Sometimes the vim key-bindings are incomplete, or wrong. I moved from intellij to vim with language server plugin because the times where the keybindings did something that I didn't expect, or were not supported leaving me hunting through dropdowns were a pain in the ass.
The other thing to consider is if you are really comfortable in a language, sometimes the lag you get from editing fast in an IDE outweighs the feature set you get from it. Vim is always buttery smooth for me, even in large files and with a bunch of plugins. I can't say the same for other editors.
Finally, having vim from within a terminal means that I can CTRL+Z to all my cli apps to manage the project I'm working in. That combined with backgrounding live-reload for web development, or jumping into a REPL make for a rewarding flow-state between building, executing commands and editing that I've only heard about from Emacs users. As much as it is on topic with the rest of the conversation here, I tried emacs and spacemacs and doommacs a few times, and have never been able to enjoy it as much as jumping between vim and zsh.
It could have been an internal document that was published a few years after written. This could be due to a indecision on whether or not to publish the work. This document could also be originally for internal use to educate new hires.
Building Javascript-based frontends are already compiling to static assets, which Netlify could already host. JAMstack is about having the javascript front-end call APIs on the backend. This is about creating an environment for all the back-end functions to be in one place, possibly with the front-end deployment. Not sure how it is going to be implemented though.
Definitely a framework to play with. Currently using Actix-web https://github.com/actix/actix-web and Tower Web seems like a more ergonomic web framework that still has async. Not sure that it can beat actix-web in speed and throughput though.
Seems expensive. Everybody I know that would spend $3-5 on a cup of coffee would spend it at a store, and people who want convenience would make large-batch cold brew, or use a k-cup. I'm not sure that consumers would go for the price of a store, but the convenience of a k-cup, for what could be done at home for cheap as batch-cold brew.
I've also seen cold brew cans at the grocery store for the $1-3 range, so I'm not sure what they are trying to do at that price point either. Hopefully after the kickstarter funds their supply chain, they can get to a better price point.
It looks like it prevents you from posting to twitter while injecting a fake tweet into the DOM of the client's browser. After 10 seconds it actually posts the tweet unless the client is revising the content of the tweet.
Its in the web browser using WebRTC, and with end-to-end encryption. It's free and good quality, and you can play lunar lander while you are waiting for the other party to join.
Make a CRUD app for an outside hobby. CRUD is trivial, but CRUD for a specific niche with good design is a good business. Look at your hobbies, and see if you would enjoy a X for X hobby.
It helps to have a product that works without a critical mass of users, but that can be solved with social media campaigns.
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.