HNHacker News
TopNewBestAskShowJobs

lawik

3,352 karma · joined December 6, 2016

https://underjord.io, lars@underjord.io https://twitter.com/lawik @lawik@fosstodon.org

Podcasting on beamrad.io and regprog.com

submissionscomments
lawik··on Buildroot
That's the general wisdom I've seen.

I work on the Nerves project which does Elixir on top of Buildroot and there we use fwup (https://github.com/fwup-home/fwup) which does a very nice job of a lot of this. Including signing, hashing and more.

This is a real example of a config: https://github.com/nerves-project/nerves_system_rpi4/blob/ma...

lawik··on To Nerves from Elixir
The years help. As they do everywhere. Competitive job market all around right now.

Taking the question at face value, I don't know your intent, and not as a bitter commentary on the experience of trying to find a job with tech one likes:

I know people that did embedded C++ that got recruited into doing Elixir on a Nerves project.

I know lots of people who have just switched their web work in Ruby or Python to Elixir. Either by finding the job or doing the work for getting the tech adoption OK:ed at current employer.

Most Elixir devs I know did not have prior Erlang experience. But most did have prior dev experience. The BEAM ecosystems solve problems you mostly encounter with some experience.

I have also seen and onboarded several junior folks into the ecosystem and jobs as their first professional thing.

Connecting and collaborating with people who could vouch for you when the opportunity comes is a good starting point. But there are many paths.

(edit: fix a spelling)

lawik··on To Nerves from Elixir
I (author) have been dealing with the ReTerminal DM from Seeed Studio which in spite of being industrial is a fairly fun device:

https://elixirforum.com/t/bringing-up-cool-hardware-with-ner...

I have also done a bunch Nerves stuff on that blog as well as my YouTube. Some of it cool.

I know the Nerves Meetup recently posted a video covering a rotary telephone using Nerves: https://youtu.be/U4hetzVpjmo?si=Wc7QZ1SG0TPyjnaJ

lawik··on To Nerves from Elixir
Mini Phoenix? What? And I run the full Phoenix web framework on Nerves. This comment does not make sense to me, as the author. Sorry.
lawik··on To Nerves from Elixir
Bwaha! It is kinda jacked up but it was late. Might fix later.
lawik··on To Nerves from Elixir
It was never intended to. The BEAM is not a good fit for that environment. I find it a bit bewildering that people are disappointed about that but I think it comes from having had the difference between microcontroller and embedded linux device clear to me from the early Pi and Arduino days.

You can look at AtomVM for a way to run Erlang and Elixir on an MCU. It just isn't Nerves. Nerves is a Linux :)

lawik··on Typing lists and tuples in Elixir
Heck, I script with Elixir like it was Python.
lawik··on Google Meet rolls out multi-device adaptive audio merging
Unless you need legible screen dharing of a code editor in my experience. Zoom is awful in many ways but blows Meet out of the water for our needs.
lawik··on Install Asdf: One Runtime Manager to Rule All Dev Environments
I work in about 5-10 versions of Elixir depending on a similar number of specific Erlang versions. At any given time. Also 2-3 NodeJS versions.

It is quite helpful. Also incredibly practical when chevking whether Library X will work on an older version.

I do open source and consulting for clients. I deal with a lot of projects, my own and other's.

lawik··on Why Elixir (2014)
As others have commented it can do all this. What it doesn't do is automatically balance/place GenServers and processes across your cluster. This is up to you. The ways in which you distribute work across a cluster is full of trade-offs.

Need raft concensus? Paxos? Something else? Want to place work with consistent hashing? Want to hydrate/dehydrate with persistence vs memory only?

Those are all important decisions and the languages do not force you to one option.

lawik··on Fundamentals of Object Storage in Elixir
If I knew what was up with us swedes I'd be consulting on that instead.
lawik··on Fundamentals of Object Storage in Elixir
There are a bunch of things that are kind of quick and dirty about these snippets. I think I mentioned that in the post, that these are not best practices. But not quite so ill as compile-time in this case :)
lawik··on Redis adopts dual source-available licensing
So the technical founders of both Redis and Hashicorp managed to step down before their respective businesses take on a shitstorm by steering away from FOSS. Unless I have my timelines wrong.

I wonder if they knew that was coming and disagreed. Or knew it was coming and didn't want to take the hit to their reputation. Agree or not with the move, there is a reputation hit. Or was it them leaving that enabled the change to be pushed through?

This is entirely speculation and just something I noticed with Hashi and now see repeat with Redis.

lawik··on Unpacking Elixir: Phoenix
A lot of things conspire towards productivity.

The dev tools (build, deps, project generation) are not necessarily better than everything else but they are very good.

The paradigm of Erlang that Elixir builds on is outstanding for building reliable, efficient services. It makes trade-offs for that. Trade-offs that mostly don't have downside for your average web app.

Things that begin to get complex in many ecosystems. Low latency "live" functionality and lots of concurrency are trivial and supported from the ground up.

It is a high level dynamic language. Think abstraction-level Python or Ruby. But it has these very different trade-offs.

Docs are good. Ecosystem is not as frantic as JS.

Phoenix LiveView is particularly in service of delivering things quickly. Follows a very 80/20 approach. High abstraction level. Covers most needs. Not shy about making trade-offs to avoid complexity. Much like Erlang originally.

lawik··on Unpacking Elixir: Phoenix
Shortly before, during and after. Market has been kind of bad recently (not just Elixir). My sense is that things are improving again but might not be at the learn-on-the-job level yet.
lawik··on Managing mutable data in Elixir with Rust
Probably not ideal since Polars builds on Apache Arrow and that tends to want to treat the structure as immutable if I recall correctly.
lawik··on OPML is underrated
The audio file is hosted on any HTTP server. That is very open web. Except on Spotify which is closed and arguably not actually a podcasting service.
lawik··on When "letting it crash" is not enough
Bit of a cliffhanger style ad. But well set up for the pitch as I know the whole Erlang deal and that part was covered well.

I stopped reading somewhere in the presentation of flawless. Ran out of care for the moment. Might revisit it though. Sounds interesting.

lawik··on Vision Pro teardown part 2: What’s the display resolution?
The brick/battery charges via USB-C from what I have seen. Casey Neistat ran that into a battery pack for extended use. I think that makes them plenty compliant.

I asusme the custom connector on the head unit is better fit for purpose (comfort, not getting snagged) than USB-C would be.

lawik··on Browsers Are Weird
Worth mentioning is the new browser engine in town.

Ladybird https://ladybird.dev/

Ladybird and Serenity OS are both weirdly heartwarming projects. If you want to catch up on it I think the Changelog podcast was a good starter.

lawik··on WARC'in the Crawler
If you are working a lot with those parquet files it might be worth looking at Apache Arrow which is an in-memory/wire format for working with columnar data. It has a lot of good support for parquet from what I gather and is really focused on allowing efficient wrangling of data. Zero-copy and all that.

Note: no affiliation, just in a deep rabbit hole on data

lawik··on Fly Postgres, Managed by Supabase
Mostly better from the client project where we run them. Haven't had as many disruptions since shifting from their nomad offering to machines.

I have some reservations about machines but none of them have been actual problems yet :)

lawik··on Mitchell reflects as he departs HashiCorp
It was forked. The OpenTofu variant seems to have backing. Used it yesterday.
lawik··on Gemini AI
Just making REST calls against the predict endpoint is simple enough. Finding the right example document in the documentation was a mess. Didn't get a correct generated client for Elixir from the client generators. But this curl example got me there with minimal problems. Aside from the plentiful problems of auth and access on GCP.

https://cloud.google.com/vertex-ai/docs/generative-ai/text/t...

You might need to do the song and dance of generating short-lived tokens. It is a whole thing. But the API endpoint itself has worked fine for what I needed. Eventually.

OpenAI was much easier of course. So much easier.

lawik··on Botlib: C Telegram bot framework
By comparison I am currently doing some work with Google Chat of all things. If your bot is in a Space (channel/grouo) it only gets webhooks when someone @-mentions it. Which is really not ideal if you are trying to have an assistant bot participate organically in the convo..

I poked around with doing a Slack bot recently and the hoops for an app were many and confusing. Not Google credentials level but more than I cared for.

lawik··on Botlib: C Telegram bot framework
That they offer long polling as one option for fetching updates makes it incredibly friendly for local development and one-offs.

I have had so much fun integrating with Telegram from Elixir. There is a lib (not in hex unfortunately) that makes it all quite straightforward.

I even gave a remote talk about it with an interactive demo: https://youtu.be/DFGHaER6_j4?si=sooEsiyVTmfXPqNs

Telegram is a mile simpler to get going with than the others.

lawik··on Validating Data in Elixir: Using Ecto and NimbleOptions
The in-editor tooling definitely has rough edges. I've done a lot of Elixir and the ElixirLS stuff falls over a lot for me. There is a new effort with NextLS that seems very promising.
lawik··on Elixir and Phoenix can do it all
I hear this a lot. I get that it is helpful. But I know people run large projects without it in Elixir and seem to do fine. Discord and remote.com seem likely to be fairly massive. Last I spoke to Remote they did 70 releases a day and no type static typing.

I know from Elm that it does change how things feel. I could see an upside. But coming from a dynamic life I can't quite grok considering it a requirement.

lawik··on Elixir and Phoenix can do it all
I have found learning materials to be plentiful. I came from Python which I guess looks sikilar enough to Ruby. But of course what paths you hit can vary wildly.
lawik··on Things I like about Gleam's Syntax
This talk: https://codebeameurope.com/talks/etylizer-set-theoretic-type...

No clue if it will get into Erlang since I don't think it started from inside Erlang/OTP. But from conversations the team seem open to an effort like this.

← PreviousPage 3 of 14Next →