That's unfortunate, perhaps your particular macbook is having a hardware problem?
As a point of comparison, I daily two ARM macs (work M4 14 + personal M3 14), and I get far better battery life than that (at least 8 hours of "normal" active use on both). Also, antidotally, the legion of engineers at my office with macs are not seeing battery life issues either.
That said, I have yet to encounter anyone who is in love with macOS Tahoe and it's version of Liquid Glass.
The current issue is iOS 26.1’s wallpaper renderer crashes in a tight loop if the default wallpaper isn’t installed. It isn’t under Xcode.
I have macos crash reporting turned off, but crashreport pins the CPU for a few minutes on each ios wallpaper renderer crash. I always have the iOS simulator open, so two hours battery, max.
I killed crashreport and it spun the cpu on some other thing.
In macos 25, there’s no throttle for mds (spotlight), and running builds at a normal developer pace produces about 10x more indexing churn than the Apple silicon can handle.
To those not familiar with LA or the USA, here’s a cultural time capsule from 2Pac circa 1996:
“ It's the, City of Angels and constant danger
South Central L.A., can't get no stranger
Full of drama like a soap opera, on the curb
Watchin' the ghetto bird helicopters, I observe”
Well the danger part has decreased a lot. It peaked at almost 100 per 10k people in the 90s, and now it's closer to 25. Still very high, but a lot of progress.
Remember the movie Minority Report? Where a central plot point was the main character being tracked (by their retina in that case), and how to defeat the tracking? Vibes.
Illegal immigration is a crime. So is jay walking and software piracy and murder. There’s a lot of nuance to be had here in how big of a deal it is and how people who do the deed are treated.
It’s always felt weird though that it’s become taboo to call it a crime, but maybe that’s just me.
The issue is that it is illegal AND a nontrivial part of the electorate wants it enforced.
The “let’s all step back and consider my side’s view of this” isn’t really relevant after our side loses elections. If the will of the people is to start enforcing jay-walking, for better or worse, we’re going to see a lot of jay-walking enforcement.
The vast majority of undocumented immigrants arrived legally and are visa overstays, which is NOT a criminal violation but rather a civil violation.
For most of America's history it wasn't even illegal to enter the US without prior authorization. The law that made it a crime to enter the US without authorization (8 U.S.C. § 1325) was specifically created in the 20's to restrict immigration by race. And the violent enforcement of this law has really only ramped up in the last few decades.
It is very strange to see many people in the US (and in this thread) accept the current enforcement framework as simply a set of static rules that just happen to be here, and not a relatively recent phenomenon that was enacted and enforced for a project of racial prejudice.
I think it's more that something being a crime doesn't make it immoral, and something being a crime doesn't mean it should continue to be.
I do not think most illegal immigration should be considered a crime. That's my position. Moralizing about it by saying "well these people are CRIMINALS" because they crossed an imaginary line on a map is odious to me.
I guess I don’t have a huge association with calling someone a CRIMINAL as a big deal. Like I speed on the highway every day, I’m a criminal too. I don’t really feel like I’m doing anything wrong if I drive safe and there’s no traffic near me. If I got a ticket though I did the deed and so be it. It’s not some black and white, “you’re a criminal so you’re evil” thing for me at all. The punishment should fit the crime.
It’s kind of a fun time capsule, there’s this unspoken question of “is there any truth to all that commie propaganda?” constantly floating in the background (the book was written by an American professor at the height of the Cold War).
That said, still think it has a lot of great insights.
Imagine you can get 20 rolls of toilet paper at Costco for $20. Or one roll at your corner store for $5.
However, you need a car to get to Costco, which you don't have, so now you're looking at riding the bus there. But you just worked two back-to-back 8 hour shits, and you're a zombie so that's not happening. Besides, $20 is a stretch, you really might need that $15 to cover a few meals until your next paycheck if you can't get enough hours this month.
So, you have to pay $5 for what should be a $1 roll of TP.
Now imagine that for everything - food, rent, everything.
To quote a song, "having money is not everything, not having it is"
This kind of inspires me. I have an i5-1340p NUC I’m not using for anything at the moment, I wonder if I could press it into service as a sort of “dry run” for this type of experience
I often explicitly discuss roles. Who is responsible for a feature (must be exactly one person). Who will have input (without veto power), who will have input (with veto power), who is the “decider” if the responsible person gets vetoed and they don’t agree. Setting up all of this early (and keeping the veto list as small as possible) makes collab a million times easier.
We’re stuck with big endian forever because of network byte order. There will probably always be a niche market for BE CPUs for things that do lots of packet processing in software.
Anything which is a bitstream on a slow processor BE has the advantage of being simpeler, see in order processing, anything else it does not matter due to caches and the non issue of adding a few more fets here and there depending on your preferred format and arriving format.
(though for debugging hex encoded data I still prefer BE but that is just a personal preference.)
From first hand experience, swapping the endianness is a non-issue in network processing performance-wise (it is headache-wise though). When processing packets in software, the cost is dominated by the following:
- memory bandwidth limits: for each packet, you do pkt NIC -> RAM, headers RAM -> cache, process, cache -> RAM, pkt RAM -> NIC. Oh and that's assuming you're only looking at headers for e.g. routing; performing DPI will have the whole packet do RAM -> cache.
- branch predictor limits: if you have enough mixed traffic, the branch predictor will be basically useless. Even performing RPS will not save you if you have enough streams
So yeah, endianness is a non-issue processing-wise. So more so that one of the most expensive operations (checksumming) can be done on a LE CPU without swapping the byte order.
Even assuming this does have a measurable performance effect for the kind of processors you run Linux on (as opposed to something like a Cortex-M), you only need to have load-big-endian and store-big-endian instructions.
I’d recommend this classic for a read: https://graphicdesign.stackexchange.com/questions/15142/whic...
Tl;dr dark text on a light background is usually easiest to read. Note in dark mode, you often see font bolded to compensate for the readability drop.
Almost ever major website dosent use dark backgrounds for text for a reason.
I personally like a dark mode UI (menu bars, dock, and so on), so it’s less distracting, but light mode for content.
reply