1,902 karma · joined October 4, 2014
https://stosb.com
https://www.etebase.com
https://www.etesync.com
https://github.com/tasn
https://mastodon.social/@tasn
https://twitter.com/TomHacohen
Contact: at tom @ any of the domains above.
Putting it here in case anyone is curious: https://github.com/tasn/scadjs
* Svix starts from $0/month which many companies (including very large ones) use, including in production.
* Svix doesn't have a $250/month tier, and you can go to prod with the $0 tier. Not sure where that came from.
* Svix is open source (open core) so you can run on your own infra, and there's no vendor lock-in.
1. The way Unix works, a directory is a file, so if you can write in a directory you'll also be able to move directories around (and thus break the structure you mentioned completely).
2. Doesn't make sense for multi-user. Yes, I understand most people have their own computers, but (1) why design it in a way that breaks multi-user unnecessarily? (2) there are a lot of utility users, and having them get access to user files because of the way this is structured is silly.
3. `grep -r` is going to be a pain in the ass when searching your own files, because it'll also search all the other system subdirectories too.
I mean, I do see crawler and bot traffic, but nothing that warrants taking action.
You can boot the pixel 10 with mainline Linux Kernel!
Oh, but the patches to support that haven't landed in the kernel yet.
Oh, and you also need a custom bootloader that hasn't been released yet.
And btw, it doesn't boot a fully functional system, just a basic uart interface.
Still cool, but not what I expected from the headline.
Posting this from my lineage phone.
As for the hacker's manifesto: we are now old. Teenage rebellion content doesn't resonate as much. I reread it after watching Hackers and agree it's not as great as I remembered. Though I also reread it multiple times as a teenager. It really resonated back then, and I'm forever grateful for it.
I think that's why we're seeing a lot of what you're describing. E.g. with Rust you end up writing mostly functional code with a bit of imperative mixed in.
Additional, most software is not pure (human input, disk, network, etc), so a pure first approach ends up being weird for many people.
At least based on my experience.
I've been using Vim/Neovim for 20 years, but still can't get enough of which-key[1] which I only installed ~6 months ago.
Note: I've used Azure and it sucks. :)
At least that's why I wrote that original comment.
Also, I had no idea it was added because of constant time crypto that was shared after I wrote my top level comment.
I guess there's also callgrind that may be useful for Gophers.
I guess maybe the failure is not the addition of it (as it's useful for people writing the bindings), but rather how happy everyone on the thread is (which means it's more useful than it should be due to a failure with the ecosystem).
Don't get me wrong, I love Valgrind, and have been using it extensively in my past life as a C developer. Though the fact that Go needs Valgrind feels like a failure of the language or the ecosystem. I've been doing Rust for ~6 years now, and haven't had to reach for Valgrind even once (I think a team member may have use it once).
I realize that's probably because of cgo, and maybe it's in-fact a step forward, but I can help but feel like it is a step backwards.
Just to clarify: I'm in favor of Cloudflare donating to Ladybird, and I'm in favor of them building it! I just don't think that's the solution to combating Chrome dominance.
Also, whoever takes your old residence is probably not malicious (they just want the house because they want a house), but whoever takes your email address is much more likely to be malicious (as the acquisition cost is low and it scales).
Ref: https://chatgpt.com/s/t_689a00f83f7c8191b70d07912a092f86
Somehow relatedly, I still remember the first time I heard about profile-guided optimization which is essentially the same but for all of your code at once (well, same idea, not sure it's aggressive enough to reach the same result as the anecdote you shared).