I'm not into Ruby but I see people hesitate similarly about my preferred lang and mostly think they should just take that leap.
3,352 karma · joined December 6, 2016
Podcasting on beamrad.io and regprog.com
I'm not into Ruby but I see people hesitate similarly about my preferred lang and mostly think they should just take that leap.
The issue isn't where the servers are. The issue is what parties can compell them to hand over information. As far as I've read on it at least. And if there is US ownership you have US courts that can demand information they aren't legally allowed to hand over according to EU law.
Less need for an API-layer and related contracts.
You can still use Tailwind CSS. Works quite nicely.
Much appreciated.
It builds firmware for Pis and other IoT on top of a thin Buildroot Linux layer, starts the Erlang VM and then that's practically your OS for building your device. Plenty of escape hatches for special needs.
I've done a bunch of streams recently with clustering Pi devices using Nerves, especially fun on local network with mDNS. They are on my blog: https://underjord.io/blog.html
Feel free to reach out if you have questions about Nerves. I'm an enthusiast of it, contributing mostly by using it for fun in public. Also write the newsletter so I'm fairly up to date :)
A lot of devs find Elixir more approachable/familiar than Erlang so it might help in your case there as well.
The Nerves project is perhaps a more pragmatic approach that is in production use that I really like which uses a fairly light Linux to get the VM up and running: https://www.nerves-project.org/
With Nerves you mostly write Elixir or Erlang to build your device functionality.
Used it in this thing: https://github.com/lawik/calendar_gadget
The Erlang application/service should not be crashing. A crash happens in a process in a tree of supervisors and each supervisor can have strategies to recover if its child supervisor/process fails.
Supervision in Erlang/BEAM is not just microservice infrastructure with restarts. It handles many types of failures knside the application and only if all mitigations repeatedly fail would we crash all the way up to the trunk of the tree and crash the application. If that happens the Erlang heart should be starting it back up or otherwise invoking some last-ditch mitigation. Or if you run Erlang in a container, that's when you'd have your infrastructural stuff restart it.
Supervision in Erlang is much more granular and not about restarting the entire service.
I think this gives a good view of Erlang resiliency: https://youtu.be/JvBT4XBdoUE
https://underjord.io/the-mac-is-losing-me.html
In the end I use them all. The point is mostly that they are all disappointing. I haven't recently suffered additional annoyances from Apple, so this post speaks to recent frustrations.
edit: In addition, I don't feel like I need to address every actor in my rants. I would never get past LinkedIn.
I apologize if it felt misleading. That was unintentional. I don't believe I can edit it.
This is very much a rant. Hope you find your numbers elsewhere :)
If they could just stop with the egregious overstepping I'd be pretty okay with using Win for gaming, accounting and a few other things. I'll likely have Win around for the foreseeable future, not just me in the household :)
I appreciate the update on Linux gaming though, haven't really looked in a long time.
Haven't had a gap in clients for a year and a half of straight Elixir work. Have more opportunities than I can feasibly execute on.
Finding the right companies and connections is a bit of luck and a bit of networking of course. But most of the companies I've worked with are not well known in the community. There's plenty of usage in the wild.
I gather you got my meaning but chose to make your point. But just in case.
We don't have that solved in Elixir, I've helped a few find their way into employment and am working with a few on client work right now.
But companies just need to get into the habit of working with less experienced devs. Not specifically an Elixir problem from what I've seen but we certainly have it.
It might be slightly worse due to many early adopters of Elixir being fairly experienced so the pool of devs has tended to be intermediate/senior. This is changing and I expect companies will, eventually, adapt.
The demand for devs all around is going up what I hear. So competition should return with a vengeance.
Personally I'm not that keen on type-heavy programming. Do you have good examples of this mix from Typescript, I'd be curious to see what that can be like.
Jose has really thread a needle with Elixir I feel.
Rails has a strong reputation for productivity, it doesn't have the strongest reputation for long-term maintainability (though it can certainly be maintained). Or that's what I hear from the ex-Ruby devs in Elixir. I came via Python and I'd say the same of Django.
Phoenix is ludicrously quick to get from zero to realtime UI and interesting backend work such as polling, consuming updates, sharing state, collaboration.
Having done a bunch of Python I wouldn't discount Django but I would pick Phoenix almost every time at this point. The initial burst of Django doesn't seem like a long-term upside and Elixir/BEAM/Phoenix has a lot of long-term upside in my eyes.
If remote is an option there's really no shortage of people looking for experienced devs from what I've seen. Feel free to reach out if you want some options.
So after realizing both IKEA Markus and a gaming chair were just murder on my back I ended up getting one as I was improving my office.
Works great. High thin back that suit me as a tall person, good support but shoulders can move back. Armrests removed I can get close to the desk.
Very happy with it.