mtzet

5 ms·

1.
by mtzet 2mo ago
The main point is to use zswap over swap plus zram. The sd card usecase definitely doesnt want swap to disk, compressed or otherwise, so zram or no swap are the options.
2.
by mtzet 1y ago
A normal desktop with non-soldered components is more repairable, cheaper and can also run on stock Linux? The only selling point is the form factor and a massive amount of GPU memory, but a dGPU offers more raw compute.
3.
by mtzet 2y ago
I don’t get this take. Is it so hard to understand that a computer operates on a giant array of bytes? I think the hard thing to understand is that C’s pointer syntax is backwards (usage follows declaration is weird). I also think understan
4.
by mtzet 2y ago
So let's focus on the case where I'm setting up a bunch of bare-metal hosts as servers. What's the value proposition of using FreeBSD over Debian/Ubuntu if we're not counting familarity? Either experience will be CL
5.
by mtzet 2y ago
> special case where all memory can be easily handled in arenas That seems to be an unfair bar to set. If _most_ objects are easily allocated by an arena, then that still removes most of the need for GC. I like Jai's thesis that the
6.
by mtzet 3y ago
Most software in the industry is slow because it's doing a lot of stuff that it shouldn't. Often times additional "optimization" layers adds caching, but makes getting to the root of the issue harder. The biggest win is
7.
by mtzet 3y ago
Processors doing out-of-order execution doesn't change the semantics of the code. That's very different from the example where gcc just throws away the assignment. The idea that he just needs to accommodate the compiler people is
8.
by mtzet 3y ago
> I’m not a go developer. How does go document how a function can fail? There's no magic to it. Errors are values, so it's a part of the function signature that there's an error code to check. In C++ any function can throw
9.
by mtzet 3y ago
I'm not arguying that go has modern tech, but rather that it has modern sensibilities. This means not trying to force 90s style OOP, preferring static linking for easier deployment, including a build system and package manager with the
10.
by mtzet 3y ago
I agree that go and rust have different areas, but that was less clear when they were getting started. Back then go was trying to figure out what it meant by 'systems programming language' and rust had a similar threading model. A
11.
by mtzet 3y ago
Thanks!
12.
by mtzet 3y ago
> as best as I understand it, because of the content of JeanHeyd's blog post on reflection in Rust. I'm having trouble finding it. Can anyone link this post?
13.
by mtzet 3y ago
Off the charts? Compared to completely at will maybe. You generally have to pay 3 months severance + 1 month per 3 years of employment for a maximum of 6 months severance after 9 years of employment. That's it.
14.
by mtzet 3y ago
As someone who knows nothing at all about the success of PayPal, can you elaborate on why? I'm also curious about his role in the success of Tesla and SpaceX. I personally find those to be two of the most interesting startups in a long
15.
by mtzet 4y ago
I agree. Emacs out-of-the-box is terrible, but my Doom Emacs config is all 50 lines of code. For that I get: - IDE-like features via LSP - The best git porcelain out there: magit. Even when I'm not using emacs, I come back to magit for
16.
by mtzet 4y ago
On the other hand, I've found that a lot of the caching that happens organically from each component building up it's own state of the world can lead to poor performance of its own. You often end up reading single values from rand
17.
by mtzet 4y ago
I agree about being pragmatic and doing what the business needs are at the moment! But that's also why I argue for having less process up front and creating it as needed. The master branch exists solely for the aesthetic reason of havi
18.
by mtzet 4y ago
Gitflow merges everything to a linear 'master' branch, from which releases are tagged. That means you can't create new 1.x releases after 2.0 has been tagged. In TBD you'd have most new development happening on trunk, bu
19.
by mtzet 4y ago
To me the argument makes more sense in reverse: Gitflow solves a problem few teams actually have. Throwing away a working (simpler) process of having a single trunk when there's no real benefit doesn't seem like a great idea. It s
20.
by mtzet 4y ago
> IOW, if I build a system with yocto for an embedded system, which is also a very useful candidate for a read-only system image installation, I cannot use this feature for this use-case because ... I agree that this is precisely a nice
21.
by mtzet 4y ago
> Systemd has this problem How does systemd have a problem? Systemd doesn't care about having a read-only rootfs at all, except that it supports it and now ships a little tool that's useful if you happen to use them. Fedora and
22.
by mtzet 5y ago
Theoretically, Wayland has proper support for fractional scaling, and this just works. In practice however, this only works for wayland-native applications and all applications running through XWayland will be rendered small and scaled up,
23.
by mtzet 5y ago
Chesterton's Fence is a valid point, but I dislike how the article celebrates it. Doing the archeology required to figure out why things are the way they are is oftentimes much more expensive than building it was in the first place. Th
24.
by mtzet 5y ago
I can highly recommend the interview with Jason Gregory of Naughty Dog from Handmadecon 2016. He gives a lot of insight into the reality of working with the scheme-based format in recent-ish times. https://guide.handmadehero.org&
25.
by mtzet 5y ago
The article expands upon this point in great detail. To wit: > Flutter's HttpServer that crashed on iOS if the user briefly switched to another app and then back to mine. The author is seemingly capable of writing a solution to the
26.
by mtzet 5y ago
That's a bit misleading though. The problem with header files is that they tend to get (textually) included in lots of compilation units, and hence rebuilt a lot of times. I did an experiment on a codebase at work where turning on unit
27.
by mtzet 5y ago
Bootstrapping GNU userland is a major pain point, and it's great to see GNU Guix taking it so seriously. There's even a section of their manual dedicated to it [1]. This is important, even if you don't intend to run GNU Guix
28.
by mtzet 5y ago
That's a feature, no?
29.
by mtzet 5y ago
In my experience the important libraries I need to interact with are C libraries, not C++ libraries. Of course certain niches have very important C++ libraries, but I don't think the C++ library story in general is that great. Care to
30.
by mtzet 5y ago
> One nice thing that sqlite being dynamicly typed allows for, is having a key-value table for storing singleton objects, like project config (as opposed to having a well defined table with a single row). If you need to store singleton o

More ›