3,352 karma · joined December 6, 2016
Podcasting on beamrad.io and regprog.com
Maybe you could build an in-memory video stream for each user and just serve it slowly but then they would likely need to press play or you rely on autoplay and I've no idea how well that would play with buffering behaviour.
This solution maps quite closely to the idea that MJPEG is intended for "live" video. And also I find it adorable that it is just an img tag.
I don't think you can do anything particularly nasty even with CSS variable programming which can apparently be used for interactive games (https://github.com/propjockey/css-sweeper). As I looked into things writing for this post I couldn't come up with a non-JS way to transition much significant data into CSS.
Just like JS-based analytics I don't think most users would object heavily to someone trying to differentiate them from non-interactive bot traffic to get an idea of whether they have any real readers or just bots. But I'm absolutely certain that there are people who will not concede any analysis of the visitor's agent capabilities and behavior as legitimate. The browser sets one boundary, general public another, privacy advocates another.
I personally try to err on the side of minimal analytics. But the default idea for people creating sites tends to be that Google Analytics is "fine" and something more privacy-oriented like Plausible or Fathom are the good/ethical option. I'm not sold on that though I'm glad that there are options that are less bad. I doubt most businesses won't throw analytics out entirely but they might be willing to pick something with a better ethics profile.
I'm not sure I find Ecto and Phoenix as central to Elixirs value proposition in general. I'm looking a lot at Nerves (IoT) and Membrane (media serving). Having a strong web framework simplifies things and Phoenix is good there. But there are a lot of things to like about Elixir/Erlang/BEAM.
Nerves stacks the BEAM on top of a small Buildroot Linux setup. The general rule I hear from the Nerves team is "if it runs Linux, it can run Nerves" which is mostly true.
I was considering whether Nerves could run on something like the ZSA Moonlander keyboard and then we run into a limitation of the BEAM apparently. Frank Hunleth of Nerves said the BEAM requires a device with an MMU. This is above my paygrade so I'll take his word for it ;)
Site seemed slightly entertaining, baby is awake, I'm not currently amused ;)
Nerves is good for hobbyists that want a better workflow and more serious and reliable setup. But it focuses on solving for production devices of you compare it to Raspbian.
I am disappointed because I expected more openness from the new direction of Microsoft than this indicates. In most of the places I've heard of LiveShare and Remote it is discussed in the context of the larger open source efforts of Microsoft. And it really isn't part of that. Specifically on things like open source-focused podcasts and such. That's how I've come across it. I think the distinction of what parts are proprietary and what parts are open will pass most developers by while they happily think they are working with open source tools.
This is indeed about two plugins not being open source, as well as the marketplace for extensions which is dominated by open source work also being limited to Visual Studio-products only. I find this disappointing and it makes me more skeptical than I was previously.
I think Microsoft can afford and would benefit from going further in an open direction with this. Its fine to not believe the same.
They have chosen to subscribe, you can contact them. You don't know your RSS subscriber count. It is a more highly engaged group, easier to build a relationship with.
And the number of people using RSS compared to using email who would consider a newsletter subscription is tiny.
Getting someone who is really skilled can of course be beneficial but it certainly has the problems of retention, things like providing interesting challenges, high compensation. Not all businesses have deeply interesting technical problems. That's fine. There is plenty of use for the wide parts of the bell curve fpr both businesses and developers.
I'm invested in Elixir and there are some interesting, different trade-offs being made there for highly interactive things with Phoenix LiveView. And there is the Lumen compiler to potentially in the future not need JS as one could write Elixir to get WASM for the interactivity needed.
My bet is still mostly on server side rendering and static as much as possible. Current JS does have the JAMstack ideas that I find a healthier direction.
China and other oppressive regimes tend to be where the marketing gets in conflict with the law and China has a lot of leverage on any major electronics manufacturer.
Still a capitalist business so ideology or ethics don't really factor into it.
I think it is correct that Apple could benefit in amrketing from having no ad systems on their platforms. Not convinced it would be net positive for them though.
I think it's hard for people to appreciate thw other side of these argumenta without having lives through some consequences. I firmly believe in automation and testing. I believe tests must be pragmatic to not be overbearing. I mostly believe in code review for teaching. The research covered in the book Accelerate (subtitle something something devops) made a strong case against code review and change control for most software development.
So yeah, your standards sound reasonable, if maybe a bit much for my taste in some aspects but I know lots of shops that wouldn't be anywhere near. And this is a skillset and know-how you can provide. Hope that's a useful perspective.
This gives you folder packaged with everything you need to run the application on the architecture you compiled it on. Very straight forward.
If you want to set it up to be a systemd service I guess it would be like any other binary command for systemd. I usually run things under something like Supervisor (http://supervisord.org/)