zamalek

I've been using it exclusively for a few years now, but I'd still say: it depends. e.g. we've yet to see an actual photoshop replacement in OSS (Krita seems to be on a good trajectory now that they've pivoted to a broader scope). First stop is checking whether you have viable replacements for things that you use.

Ubuntu is going to strong-arm you into Snaps, the snap-ectomy is nontrivial, and they have a habit of reappearing. Some people don't have a problem with Snaps - so non-issue if you don't care. Otherwise I'd go with a downstream distro that removes them: pop os, mint, or even upstream (Debian).

XFS is an extremely mature file system if you don't need anything fancy, and you're probably less likely to lose data compared to $proprietary. The other major ones (ext4 and btrfs) are probably just as good, but XFS honestly does stand out in terms of maturity and simplicity.

A common trap is trusting the installer with partitioning. My last Ubuntu installation ran out of space on EFI. 5gb is overkill, but given how abundant disk space is, who cares. Separating / and /home is a good idea for rescue/reinstalling but without btrfs subvolumes (Ubuntu uses btrfs subvolumes by default) it becomes a bit challenging to figure out how to dice things up: e.g. docker containers are stored in /var, so they can deplete your system drive space. Last time I didn't use btrfs, 200gb for / never caused issues for me.

Oh, and Windows has a habit of removing other boot loaders from its drive. If you dual boot, use a different disk for the entire installation.

That's really the extent of the gotchas I'd give to a person literate enough to install an OS. I would slightly urge towards immutable (Silverblue), but Ubuntu is just fine.

> The index is 214 MB! That's almost half the size of the entire table. So the analysts are happy, but you? Not so much...

This is part of a broader choice: write amplification. You'd want to, of course, have the most precise index possible - but no matter how you cut it, you are incurring extra I/O for writes - one for the tuple, one per index. How you index things is heavily influenced by the mix of reads and writes, and this is why we have data warehouses/read replicas in the first place: it allows us to avoid write amplification in the write path, while having fast filtered reads (that are slightly delayed).

If you're dealing with <ridiculous number of users>, there is a good chance that you don't want to be putting BI/OLAP indices on your OLTP database. You probably don't have enough users to worry about this - but - if you ever find that your writes are becoming an issue this is something to consider.

It's the name of their AT&T MVNO.

I started mid last year and haven't run into any problems. Haven't needed to switch off of Dark Star yet.

I was previously on Google Fi, and MVNO roaming is bloody fantastic - I always had reception.

Games that have problems with the previous approach might have hitches or stalls, though it could manifest in many ways.

Edit: I am running a kernel with it on, as well as Proton-CachyOS which has it opt-in. I have yet to see it make an improvement of any kind. Maybe it might help on lower-spec hardware such as the Deck.

If the old wisdom is correct then there is no issue in regurgitating it in a format suitable for a modern audience. We departed from it for a very long time, especially in regards to fat and processed foods. America has been been on a sharp decline in diet-related health.

The deeper problem is that you can feed a family with a few bucks at a fast food joint. Eating correctly costs money, money that Americans don't have.

So it's ads masquerading as cookie consent?

I think someone around here said: LLMs are good at increasing entropy, experienced developers become good at reducing it. Those follow up prompts sounded additive, which is exactly where the problem lies. Yes, you might have tests but, no, that doesn't mean that your code base is approachable.

Corrective votes will follow, if warranted.

Piracy isn't only a matter of money, it can also be convenience or outright accessibility (no way to purchase the item legally).

When I was forced to use a Mac at work I found that Nix was also just a better (mostly faster) package manager than brew. Even if you're not on the immutable bandwagon it's very worthwhile.

As a bonus I was able to achieve some semblance of uniformity across Mac and my Linux desktop with home-manager.

At the end of the day these developers are almost entirely volunteers. Codebases that are a mess, ie X11, are not enjoyable to work on and therefore convincing people to use their discretionary time on it is more difficult. If there wasn't Wayland the current set of developers on Wayland might not have been doing DE work at all.

Attracting new contributors is an existential problem in OSS.

BAR is definitely one of the stars of OSS game dev.

Yeah, as far as I understand it, that politics is: Sinofsky entrenched NIH on every team that he touched.

Right, the very thing that works against AC on Linux also works for it. There are multiple layers (don't forget Wine/Proton) to inject a cheat, but those same layers could also be exploited to detect cheats (especially adding fingerprints over time and issuing massive ban-waves).

And then you have BasicallyHomeless on YouTube who is stimulating nerves and using actuators to "cheat." With the likes of the RP2040, even something like an aim-correcting mouse becomes completely cheap and trivial. There is a sweet-spot for AC and I feel like kernel-level might be a bit too far.

> You can put some work into windows

That's exactly my point.

There's an ever growing list of things to do in order to fix Windows, and that list is likely longer than Linux. This whole "your time is free" argument hinges on Windows not having exactly the same issue, or worse.

You aren't comparing Linux to anything here.

Windows has recently been a complete shitshow - so even if Linux hasn't gotten any better (it has) it is now likely better than fiddling around with unfucking Windows, and Windows doing things like deleting all your files.

Its going to be a decade, the slow erosion of Window's market share, and we might already be in it.

FUSE will provide Dropbox in a more integrated way than Windows (eg. terminal) and a cursory Google revealed some projects for Dropbox that do the JIT download you are after - they are old, but I wager still work just fine (an inactive project can just mean that it's complete).

> Groq makes innovative AI accelerator chips that are significantly faster than Nvidia's.

Yeah I'm disappointed by this, this is clearly to move them out of the market. Still, that leaves a vacuum for someone else to fill. I was extremely impressed by Groq last I messed about with it, the inference speed was bonkers.

Consider using a user-space buffer instead, syscalls are slow so bonus points for limiting them are on the table. If you want to avoid resizing an array have a look at the vectored io syscalls (readv etc.).

Unfortunately grok doesn't even meet that bar anymore. There was the very recent incident where it claimed Musk was the best at everything, so xAI are clearly not beyond baking in intentional bias/clutching pearls.

https://techcrunch.com/2025/11/20/grok-says-elon-musk-is-bet...

> Is traveling less really that much to ask?

I'm currently on dating apps and the amount of people who define their personalities by their travel habits is staggering.

> Anybody who thought the simple action of rewriting things in Rust would eliminate all bugs was hopelessly naive

All bugs is typically a strawman typically only used by detractors. The correct claim is: safe Rust eliminates certain classes of bugs. I'd wager the design of std eliminates more (e.g. the different string types), but that doesn't really apply to the kernel.

Github runners are slow. We're using WarpBuild and they are still cheaper per-minute, even with all the changes Github has made. Then there's the fact that the machines are faster, so we are using fewer minutes.

There are multiple competitors in this space. If you are (or were) paying for Github runners for any reason, you really shouldn't be.

C# is already memory safe. This isn't the reason why some people chose Rust over C#.

Would any of these soft forks survive without Mozilla working on Firefox?

I love the bare-bones landing page, many products have landed me as a customer due to that.

Do you have IMAP import? And CardDAV/CalDAV? Edit: also wildcards?

Firefox Mobile, Android: can't access property "enable", c is null

> But I found that the 20-30 minute stops every 2h really improve how I feel after a day or two of driving.

I honestly started considering this a feature. I am a huge believer in "productive friction" - where some things are intentionally made annoying or hard so that humans avoid them - and this is a really good example.