mid-kid

42 ms·

271.
by mid-kid 3y ago
Because ROM/flash/eeprom chip sizes are advertised as bits. It was clearer in a time where the definition of "byte" wasn't always exactly 8, and it stuck. The size of a cartridge was never advertised to users, so it
272.
by mid-kid 3y ago
I know this, I mentioned this as "setting up a binrepo" in my comment, as I think the binrepo approach makes more sense (esp. with regards to easy updates). It's just an unwieldy amount of extra overhead, disk space, and time
273.
by mid-kid 3y ago
compared to the average power draw of activities like gaming? probably not a significant amount.
274.
by mid-kid 3y ago
For me this is great news for less powerful devices I use that I don't feel like setting up a binrepo for (especially when it involves cross-compilation), but still want to reuse my portage config and custom ebuilds for.
275.
by mid-kid 3y ago
I've been looking into QOwnNotes as a "simpler" replacement for Zim[1]. Unfortunately, it isn't really trivial to convert a notebook that I've tended to for a decade, and from first impressions, it lacks the WYSIWYG
276.
by mid-kid 3y ago
We need more non-serious projects like this, but with actually remotely useful stuff.
277.
by mid-kid 3y ago
> You will be prompted for a password, and ultimately able to do it; but no setuid binary is involved. Polkit/pkexec is setuid.
278.
by mid-kid 3y ago
This is why I stick to layouts with separate keys for " and the dead-key ¨ Plenty of european layouts with qwerty and the necessary dead keys, that work on every OS.
279.
by mid-kid 3y ago
I just think they're neat.
280.
by mid-kid 3y ago
People seem concerned about bloatware. I'm concerned about backdoors like this easily being misused.
281.
by mid-kid 3y ago
In my opinion, there's a huge difference between working for personal interests (what you call "reducing entropy"), and working for the sake of money, causing it to dictate your activities. Even if you do the same "work&
282.
by mid-kid 3y ago
No matter how shortsighted this comment is, I get the sentiment. I'll eternally miss cool x11 gimmicks that could be added to any desktop like compiz, xpenguins, xsnow and xneko
283.
by mid-kid 3y ago
She was building on the B+ in the later example of the blog.
284.
by mid-kid 3y ago
asdfmovie is from, like, 2010
285.
by mid-kid 3y ago
There's no worse way to be right than being technically right. Most of these points are essentially the state of the art of desktop operating systems, or pure speculation, and the fact that they aren't perfect or widely used yet
286.
by mid-kid 3y ago
I think having a standard way to specify exact program dependencies (not package names, but e.g. pkgconfig files, command binaries, deps for specific languages, etc, so they can be translated back to the package name for each distro), as we
287.
by mid-kid 3y ago
How come the cookie popup blocking is only for Germany?
288.
by mid-kid 3y ago
I voted it down because numbers don't really mean anything. Top-level comments that directly disagree with the article always do good if they don't get drowned out by another comment doing the same, especially when it's a con
289.
by mid-kid 3y ago
Thanks, I mistyped it.
290.
by mid-kid 3y ago
It's less a workaround around bad dependency management, and more about the fact that it's simply easier to reason about a smaller set of dependencies regardless of the ecosystem . This includes both vetting, ensuring version com
291.
by mid-kid 3y ago
If you're smart about it you're not gonna have a very deep or wide dependency tree for your own deps. If you need more than maybe two of your own deps, maybe you need to reconsider how you structure your libraries, or you can join
292.
by mid-kid 3y ago
As a distro contributor, I don't share these views at all. Yes, it's sometimes a bit of a pain when some application needs an older, incompatible library, but in 99% of the cases, the fallout is minor, or there's some compati
293.
by mid-kid 3y ago
If you do this, remember to provide an option to factor it out. Meson (mesonbuild.org) makes this completely trivial and pitfall-free, and you should use it if you can't get away with just installing your libraries locally.
294.
by mid-kid 3y ago
When you make a new library for C/C++, you generally just install it locally at first (pkg-config and PKG_CONFIG_PATH make this trivial). It doesn't (need to) get packaged by a distribution until a program using it is packaged. Yo
295.
by mid-kid 3y ago
It solves most supply chain attacks. Distro maintainers are users, not developers. They put the needs of a user first, and their work is reviewed during submission. If one of them goes rogue, the damage is usually caught before reaching t
296.
by mid-kid 3y ago
It works in the C world because everyone is super fixated on library compatibility, and the programs are expected to be rebuilt by the distribution when necessary. When an API is broken, this entails a new major version and installing bot
297.
by mid-kid 3y ago
This. As long as any client can connect to it without attestation, things like NewPipe will remain working. I don't understand this fearmongering sometimes.
298.
by mid-kid 3y ago
I consider the linux-man-pages project (usually simply "man-pages" in most linux distributions) to be the single best reference manual for UNIX C programming. It has extensive descriptions, examples, warns about libc/platform
299.
by mid-kid 3y ago
The source of the manpages on die.net is always questionable to me. I've found they're often out of date or for questionable versions of software. https://manpages.debian.org/ has all the relevant man pages and is
300.
by mid-kid 3y ago
Apple is a particularly bad example of this kind of churn. They have an iron grip on the entire ecosystem and can get away with it, but you have to wonder at what cost.

More ›