Nowadays, I just get old laptops with broken screens and take the mainboard out. They are dirt cheap, often even have 16GB of RAM, you can just dump pretty much any linux on them and they are usually way faster than Pis.
The boards are of course bigger, which I guess will be a non-starter for many. They'll also require active cooling unless you downclock them considerably. They often also require more power, although many mainboards can be configured down two a few watts of power consumption, depending on what peripherals and speed you need.
Yeah, it's more work than just getting a Pi, but given the current prices, it makes sense for me.
The goal of raspberry pi's was to have a standard GPIO connected to a moderately powerful and cheap computer for educational purposes. Then it slowly evolved into many use cases because of it's vast community and standardization and availability, not to mention the large number of boards that connect to it. The standardization did erode a little but it still maintains that reputation because of the community and availability and now because its turned into a big brand. Many industrial projects depend on it.
If you use the raspberry pi for homeservers or general compute (which I did/do sometimes) then the value proposition is quite poor regardless of pre AI prices unless you have very strict power requirements (in which case it probably fits the above use case already). The comparison with NUCs or mini PCs or laptop boards feels like it's a wrong comparison.
The chips used in PIs are repurposed Broadcom SOCs that have inferior bus speeds compared to a general purpose processor from intel or amd, even few generations old. For any general purpose computing these chips will always be slower. its like comparing apples and oranges. I never really understood why people did that.
Yeah, I don't disagree, but I would argue the Raspberry was always an applorange, and that's exactly what made it popular (together with the cheap price in the beginning, which made it basically an impulse buy). It brought people into microcontroller/embedded systems territory without having to actually deal with all of the stuff that made this so daunting. As you said, it is basically a normal Linux PC, just that it runs Arm and has GPIO.
People who are really into electronics/embedded systems will use a proper microcontroller nowadays anyway, these have gotten so powerful and easy to use that there's really no reason for a Pi anymore. And on the other side, people who want a little server, a pi-hole, tailscale or octoprint or whatever, can just use an old used laptop/miniPC or similar. Since the Pi has gotten so expensive, I see basically no reason to get one anymore.
Microcontroller prototyping kits have been very convenient for some time. I could say the same about cheap <$10 ESP32 kits (e.g. M5 Atom Lite) - for development I can do one-click push of updated code over wifi, pushing or pulling logs over the network is trivial, etc.
I'd say the Pi is for all kinds of situations where you do need more power than that, but for trivial usecases I don't really see a major convenience advantage, IMHO the ecosystems have comparable convenience, except that if you've gotten used to one, then the other will need some new learning.
Central Computers -> 404
MicroCenter -> endless loop
PiShop -> sold out
Sparkfun -> sold out
CanaKit -> ? seems to only be a product listing ?
AdaFruit -> sold out
Vilros -> sold out
Are you sure the device you linked to is actually supported? It's not listed on the PostmarketOS device page. Even devices that are typically don't have good driver support.
I would argue that even if you need "a cheap SBC with GPIOs", at this point you'd be better served by connecting a tiny $5 microcontroller-powered board with a USB PHY + its own GPIO headers, to any cheap "computer" (i.e. a GPIO-less SBC, or an old laptop, or a phone like in the article, etc.) over USB; where the MCU board essentially serves the host a "GPIO gadget."
You can make such a dongle yourself from ~any MCU dev board, but there are also productized "USB GPIO breakout" adapter boards, e.g. the Adafruit MCP2221A.
The "Pi as an SBC with GPIOs" case now only makes sense if you really, really require the Pi's compactness and/or monolithic-ness (as might be the case for e.g. ruggedized embedded systems like robots.)
I always thought the value-prop of a Pi was the monolithic nature. If you needed GPIO and Linux, you didn't have to glue two things together to make a solution, you could just buy one device that met the requirements.
> The goal of raspberry pi's was to have a standard GPIO connected to a moderately powerful and cheap computer for educational purposes.
At first it was a blessing that the Raspberry Pi gained popularity as a general purpose computer, not just for education and embedded applications. The additional demand and popularity brought more money and development attention to the ecosystem.
At some point, which I could never really put my finger on, this general purpose computer popularity grew so large that the embedded systems and educational aspects of Raspberry Pi seemed almost forgotten by the mainstream users. At a local in-person meetup group it was a running theme for people to brag about how many Raspberry Pis they owned for different purposes and to boast about using them for applications where they didn’t really fit. In person I’ve heard more about Raspberry Pi NAS systems (where people are always disappointed with the performance and the price of forcing a Pi into this role) or Raspberry Pi Kubernetes clusters (which mostly sat idle and could have been replaced by a single PC with more RAM).
This reached such a critical mass that it almost seemed like the mainstream discussion forgot the original purpose of the Pi and thought it was literally just another computer, but small. Most people who tried to use it for this purpose were left slightly frustrated by how it didn’t perform like they wanted a computer to perform.
So now every discussion about Raspberry Pi attracts comments about how nobody should buy a Pi when you can buy a NUC or laptop or some other used piece of hardware and it’s so much “better”. This is the right advice for a lot of people who wanted a powerful general computer but bought a Pi instead, but it’s also furthering the misunderstanding of what the Pi is for.
The real advice is that everyone should be shopping for the right tool for the job. There are a lot of cool applications for the Pi where a NUC or old laptop or phone doesn’t make sense because you actually need the compact size, the low-level I/O, or some other feature. However anyone who can put a NUC or laptop side by side with a Raspberry Pi and consider them both viable options for their project probably shouldn’t have been looking at a single board computer to begin with.
There is a parallel situation happening with the “just buy an ESP32” arguments. If an ESP32 solves your problem, you also probably shouldn’t have been in the market for a Raspberry Pi.
> There is a parallel situation happening with the “just buy an ESP32” arguments. If an ESP32 solves your problem, you also probably shouldn’t have been in the market for a Raspberry Pi.
I have mixed feelings on that.
For the longest time it was safe to say "just buy a Raspberry Pi" because they were cheap enough and powerful enough. If memory serves me correctly, the base board cost roughly the same as an Arduino Uno and offered considerably more. (Of course, there were cheaper Uno clones, but those depended upon support offered by official Arduino software development tools.)
While there are some projects which would only be possible with something like the Uno, there were far more projects that would only be possible with something like the Pi. So if you wanted to give generic go-to advice to a novice, the Pi it was.
The right advice is to use the right tool for the job, but that is something that a novice (or fly-by-night forum posters) aren't prepared to handle.
Of course, things change. There are more inexpensive microcontroller development boards and the microcontrollers themselves are much more powerful. While that doesn't negate the benefits of a Linux SBC, it does raise questions now that those SBCs are considerably more expensive.
As an owner of a few Raspberry Pis V2, a V3 and a V4 - of which only half ever done anything useful - I think this discussion is missing one key property that drove the popularity with hobbyists: it could do both the embedded stuff and normal "small Linux PC" stuff, and this didn't just mean you could bridge the two worlds and enter them from the side you're more comfortable in - more importantly, it meant you didn't have to decide it at purchase time.
N=1, but I vividly remember that the reason I could justify spending money on another Pi was that even if I didn't find time to tinker with one of my pet ideas for an embedded device project, I could always use it as a server for something.
> The comparison with NUCs or mini PCs or laptop boards feels like it's a wrong comparison.
For many (maybe even most) people they do the same thing. Some just want a HTPC, basic desktop, or small server, no GPIO needed. Raspberry Pis were definitely cheaper early on because you could actually buy boards at or near MSRP, but over time the price rose and mini PCs became cheaper.
or maybe the mini pcs started becoming available at all. I think these were a concept since core 2 duo and first gen i3 era. before then the chips were too much wattage for a mini pc. and the first generation mini pcs were also costly for enterprises to adopt in bulk. its only after 4th and 6th gen intel that these were adopted in large quantities in enterprises and once they dumped those in the used market they became comparable in pricing and somewhat in power to a rpi.
Used powerful PCs have always been available for dirt cheap on eBay even when the first pi was launched. just that mini pcs are a more recent thing.
Had a couple NUCs but I loved the Gigabyte Brix. They're over 10 years old at this point and I still have them doing things like running my local Unifi network software, etc.
Well, the earlier Mini-PCs were a good bit more anemic, that's why adoption was slow; I had one or two earlier ones; both were AMD Bobcat cores; one was a 'not quite finished' thing where I took a dreamcast and put a small board in it (Where did that go, anyway?) and the other was a small, almost router-sized box. And both of those were, well... good for most of what I wanted (i.e. 8/16 bit console emulation and basic media/browsing) but definitely constrained. (As a side rant, I still wish AMD didn't kneecap non-console Jaguar parts, that single channel limit always struck me as a 'we don't want to show how much we fucked up with bulldozer' sort of thing...)
As far as mini-pcs... The first Intel NUC was a Sandy bridge, i.e. Gen2, FWIW. And we did have the 'Mac Mini' as far back as 2005, buuuuut that wasn't cheap because Apple.
I think SSDs were another big part of mini-PCs though; it's easy to forget for granted the risks of having a hard drive in a poor thermal environment, as well as the general size constraints one imposes. [0]
[0] - Surrrre, you could use a 2.5 inch HDD instead, but 2.5 inch HDDs almost always were slower than a 3.5 inch HDD (excluding the VelociRaptor, but that would only be more demanding as far as thermal...)
I use a pi (4th? generation) to run homeassistant, calendar sync target and a few other random small services on. It's great. It works, it doesn't make noise, it's small, it plugs into USB-C, the power brick is small, too. The SSD I'm storing everything on because I had a few failed SD cards has a larger footprint than the rest of the computer. What not to like? Nothing I run on it requires faster CPU, and the small footprint is worth something to me.
Sure, if you have a big house with a dedicated server room/hobby space, you might as well have a NUC/old laptop/whatever.
A Pi with enough RAM to be useful is now more expensive than a far more capable NUC. And the Pi isn't powerful enough for things like Jellyfin transcoding and comfortably running game servers. ARM also limits uses cases, especially gaming. So no, it's not great.
I had Home Assistant on an RPi 4, and the best thing I ever did to it was moving it to a real computer.
Home Assistant is rather memory-hungry (especially if you use many docker containers, which you probably do if you if you want or Z-Wave or Matter or Apps, etc). And it hammers the storage subsystem due to rather abusive use of SQLite.
And RPi < 5 does not have a good storage story, and even v5’s isn’t great.
(I have nothing against SQLite. I do have something against the way the Home Assistant’s “Recorder” uses it. Recorder is, to put it politely, not a design I would have agree with.)
The GPIO in Pi is almost useless. Nobody runs servos off of those. Pis are mostly used as just Linux PCs with USB ports that reliably power itself on.
IMO, the problem with the Pi GPIO is that it's a collection of GPIO pins and low pin count buses for controlling peripherals, rather than a singular bus. The fact that it runs Linux without an RTOS monitor program or a sidecar of sorts adds to the problem.
> The GPIO in Pi is almost useless. Nobody runs servos off of those.
Good enough for some things, but yeah not great for motor control.
In a lot of ways the old TI BeagleBone Black board was a better-than-Pi alternative for the hybrid setup of having a full OS, but with reliable GPIO, since you could run Linux on it but then drive the GPIO pins off the two real-time PRUs.
Of course, like most non-Pi alternatives and in typical TI fashion, poor software support sunk it.
Much like the goal of the PS3 was to have a powerful gaming console that also let you run Linux. The market quickly deals with any hardware that is cheaper than its value.
For me the value prop is a low-power device that can be passively cooled but has a full Linux and tcp/ip stack, at a price point where I don’t care if I accidentally wreck it.
Fantastic for one-off projects.
Nowadays they require cooling fans and cost absurd amounts considering the performance so there seems little point.
Most of my one off projects these days are now on microcontrollers.
The Lenovo “Tiny” line of ultra small form factor PCs is effectively laptop hardware in a proper case, with ethernet and no battery to deal with. There’s a steady supply of used ones at good prices from enterprise IT liquidators. I’ve had one on my desk as a home server for years.
In a better world we'd all have one in our homes, storing all our personal data and documents. The cloud would only be used for storing encrypted backups.
Many small businesses, kindergartens etc. could also have all their digital needs served this way.
Yes they would sometimes break down, but with the right setup, the fix would be a matter of booting a replacement from the right thumbdrive.
With unattended-upgrades enabled and nothing open to the internet (I run Tailscale to be able to access it when I’m out of the house) I don’t worry too much about mine.
If you use something like Fedora CoreOS, the system keeps itself and all container images updated. And because system upgrades are also just a new immutable image, very little can go wrong.
I have a Nextcloud server running on it and the maintenance is negligible.
During the recent PHP-vulnerability I simply turned it off. The next day I booted it, and it automatically installed the new Nextcloud image with the vulnerability fixed.
Makes me wonder if I could have it check for CVEs and automatically shut down vulnerable containers until updated images are out.
I was just thinking last night about setting up an agent that would daily check in and do a full maintenance scan on a server or a home lab box. Check for operating system upgrades. Schedule them if needed to move from LTS to LTS. Check for CVEs against daemons you know you're running. Stuff like that. I've used agents and harnesses to set up machines before and do system administration tasks, but it feels like you could sort of set it up in a loop and just let it go forever.
I was treasurer of the kindergarten parents' association when my daughter was in that age. It’s a small org with 10-12 employees, 30-40 customers (children) twice as many stakeholders (parents, relatives) constrained budgets and strict regulations, eg also a privacy officer. We had a static website, everything with PII, so, basically everything, was on a laptop with encrypted backups. Everything was managed with an Excel Sheet and an accounting software. Payroll was handled by a tax advisor. We cloud have used cloud services but too expensive, too many compliance headaches, and too constrained. I think an agent with local inference on a Mac would be a good investment, today.
My first child's kindergarten used Facebook to share photos. You could opt-out and then - if they remembered - they'd leave your child out of the photos. Everything is an upgrade over that I suppose.
After pi’s got expensive I started picking up refurbished Dell micros and Lenovo tinys cheap and haven’t looked back. They are also perfect for the 10” mini rack[0].
Same. I have two Dell SFF 3070s and some MSI micro units in a rack - planning on getting some more for my Proxmox cluster. ServeTheHome has a great resource for the compute nodes [0] and GeekPi makes some awesome 10" racks [1]
Shoutouts as well for the USFF HP Elitedesk and Prodesks. They are amazing. I even got one with a Ryzen CPU that had a dedicated GPU option - that GPU part was on eBay brand new for $60 and replaced the hard drive bracket. Not on par with a desktop GPU but way better than integrated graphics, for things like Minecraft in my case. I use a second one, this one Intel with 32GB of RAM, as my home server. (Jellyfin, Home Assistant, Tailscale, miscellaneous stuff).
I also have one and use it as a home server. They’re insanely capable (I’m constantly running a lot of resource heavy things on it), and it cost a lot less than a pi even though the specs of mine are way better
A few years back I finally got tired of the quirks with ArchlinuxARM (some things only worked with the forked kernel, some only worked with mainline) and replaced all my persistent RPi usage with refurbished Lenovo mini PCs from Amazon. Even with Amazon’s markup it wasn’t that much more than a beefy Pi4 plus case and adapters.
This let me standardize on amd64 and simplified a bunch of my deploy code.
The wattage on labels on PSUs are just safe max power draw, above which the supply has the right to shut itself down. It's not 1:1 representative of idle draw.
There are adapters which take a USB-C connector on one side and offer a barrel connector on the other one. They're available in many sizes for a few €$¥£. Saves you a brick assuming you already have the required USB-PD adapter.
They're not an insurmountable problem but they are a major irritant with cable management (when there is a large brick in the middle of the cable) and space / placement. Like if you want a small device high on a bookshelf, the power brick supply is a bigger pain than a long USB cable.
I bought an HP thin-client PC for a few bucks that was basically just an HP Stream system board without battery, keyboard, or display. Delightfully, frustratingly rinky-dink but it seems to run Linux and OpenBSD well.
I've yet to find a laptop mainboard that doesn't work without a battery. As I've written below, I'm getting extremely boring old office laptops with integrated graphics. Usually phones also work fine without a battery. However, I'm not touching phones because I will not fiddle with locked bootloaders and "the Android situation". Running plain Linux is a hard requirement for me.
If only Frameworks were “extremely boring old office laptops” with costs reflecting that, instead of very interesting and desirable hardware for which people will pay a slightly lower than Apple premium.
Yeah, I really just want a refreshed early 2010s Thinkpad with a wide-open BIOS. The modern Chinese mainboards you can get for old Thinkpad chassis are very cool but the prices aren't so cool.
I have a ThinkPad x230 (3rd gen i7) which makes an incredible Windows XP nostalgia device. It’s basically the newest hardware that exists with full XP drivers (other than USB3 which I don’t need) so it’s massively OP, which was the point of that project. Basically, “what if I had access to insanely futuristic hardware in 2002.”
Obviously I wouldn’t sacrifice that hardware but it might be cool to try that on yet another laptop. (Hey, I don’t have a laptop collecting problem!)
It's not cheap but it is a very interesting project nonetheless IMO (I may be biased though, I love seeing people retrofitting older devices with modern internals)
Have you guys had any experience or luck adapting Framework motherboards to run on Thinkpads? I’ve thought of doing this side project several times for my old Thinkpad x201.
I'm just looking at an old Dell laptop refusing to boot without manual intervention because it looses its time setting since I removed its main battery. If I can fix that it'll become a very capable server for my home setup. Not sure it'll work though, as the bios can't be configured to ignore the time reset.
All old office laptops I had so far still had the good old CMOS/RTC battery... So if indeed the RTC is solely powered by the main battery, I would guess there's at least a backup capacitor somewhere so that it survives at least a short disconnect? If you can find that one, you can probably connect power there, but that's just me guessing...
Yes, good video, and it covers one of the most important bits: how do you turn that thing on. :-) (EDIT: holy crap he's delaminating a whole old Apple iMac display from the glass, I did this once with a phone(!) screen and I swore I'd never do this again... doing this with a whole iMac screen is hours and hours of absolutely painful work, it looks way too easy in this video...)
My home server is a first-generation Framework 13 laptop that I put into an enclosure that they sell on their website. I sold the battery and the case on their forum. It works great!
How do you power them? Via the battery? I was thinking about turning my old mbp into a build machine, but i am a bit concerned with running it via the battery 24/7
I feel like The Internet has this urban myth that says keeping a charged battery plugged in all the time will eventually cause it to explode and burn your house down, guaranteed.
I get that keeping a battery at 100% charge is not great for it in terms of longevity (ability to hold a charge). And it's obvious that heating the battery up by running the laptop at full tilt inside a backpack or something will turn it into a spicy pillow.
But I struggle to imagine the failure mode that reliably shows up when keeping the laptop powered on 24x7 that is never a problem for 8-16 hours of continuous use while plugged in (a very typical work day for my laptops).
I used a MacBook Pro as a server for years. It was fine for its purpose, however the battery did swell and need replacing. It may have damaged the trackpad, and like the other comment mentioned, idk what would have happened if I had left it swelling for a couple more years. Probably not a battery fire? But the $230 or so that a massively more powerful HP USFF that I replaced it with was worth it, even versus a 0.1% chance it would burn my house down and possibly kill my whole family in the process.
I ended up repairing the Mac, replacing the battery, and installing Chrome OS on it. (chrome sucks though, someday I’ll get it back out and switch to real Linux)
> I feel like The Internet has this urban myth that says keeping a charged battery plugged in all the time will eventually cause it to explode and burn your house down, guaranteed.
I had a MacBook Pro where the laptop worked but the battery became swollen so much that it distorted the case. If I wasn't there to notice it, it would probably burst at some point and Lithium is very flammable.
It's probably rare and overblown, but it can happen.
you're lucky you're running into models that don't panic in some way without a battery.
for example some alienware and XPS models rely on the battery for amperage capacitance when their big onboard GPUs get busy; allows them to run cooler/less-wattage/smaller wall-warts but it also makes for a platform that'll crash when it hits a high GPU usage without a decent way to make up the amps.
'spose you could use a bigger power supply if you get bios/uefi to play nice. hard proposition sometimes with Dell products.
Well, of course I'm not getting old gaming/pro laptops with dedicated gpus, they would consume far too much power, require extensive cooling, and these are way too expensive anyway, even when broken. I usually get old, boring office laptops (lenovo/dell) from bulk resellers, with integrated graphics who are sufficiently used/broken so they are dirt cheap. As long as they still turn on, the mainboard is usually fine (I've yet to get a broken one).
You can just limit maximum charge (using something like aldente), then replace the battery every 4 years if you need extra peace of mind.
Batteries degrade much faster when fully cycled repeatedly, and even then just about any laptop battery can easily make it 6+ years with low-to-zero risk of failure.
Most old PC laptops have external batteries you can detach by pulling out on a springloaded tab. Even MacBooks are possible to run without the battery, but it requires some NVRAM trickery IIRC.
Some older MacBook and MacBook Pro models reduce processor speed and GPU performance roughly by half when running without a battery, to avoid shutting down if the computer needs more power than the AC adapter can provide.
Apple documented the behavior in a support note. I’m not sure if the Apple Silicon models do the throttling as well. I guess the situation doesn't come up as often since the batteries are no longer user-removable.
I’ve got a 2017 MacBook Pro with a dead screen, dead keyboard & trackpad and no battery sitting behind my sofa, closed in a vertical stand and running macOS as a test server. Open Core Legacy Patcher will allow you to boot without the CPU slow down: https://dortania.github.io/OpenCore-Legacy-Patcher/
I have the same device, did you just remove the battery after installing opencore? last I tried, I got omarchy running on it but now it just boots to the startup disk always. Not sure what's wrong.
The thin clients that I've seen were all Linux/unix based machines. A Windows box sounds like a fat client to me and I'd be concerned about security updates and how locked down they are.
They're marketed as "thin" clients for whatever definition of it, probably for ease of management. What matters to surplus seekers is that they are great as Pi substitutes.
How do you configure them after pulling out the mainboard ? For example if you need to ssh into them, how does it work, if it is not configured correctly before removing the display ?
Factor in power usage, thermals (esp if they're sharing a living space with you), and time. This is where the modern CPUs on 2nm process nodes really start to pull ahead, especially when you can S3 sleep them or use IPMI type BMCs on stuff like real workstation-class systems and servers. Even an M6 Mac Mini can do a ton of work these days, and single-core speeds on those especially when you look at perf/watt are insane.
You can put it in a custom case. Releasing the space constraints enforced by a laptop design means you can easily have a better cooling arrangement so experience less thermal throttling if you ask it to perform longer compute-heavy tasks.
If you are building custom cases for laptop boards, just buy an old tiny PC at that point. They are like $50-100 on eBay if you don't need killer specs. Unless you're just doing it for the love of the game or happen to have a lot of laptop boards sitting around you can sell, it's not worth it.
If you already have a laptop with a board you can extract, and a 3D printer you can make a custom case with for a couple of quid, you'd rather reuse parts of the old laptop than let it go to waste, and you'd enjoy the whole project, why instead spend $50-100 and have to deal with the [censored]s on eBay?
> Unless you're just doing it for the love of the game
Isn't that way a lot of people do the home-lab thing and related projects what would need the Pi these ideas are talking about replacing? It is why I do it [or used to be before working in tech for decades killed a lot of the enjoyment I had for playing with tech].
> or happen to have a lot of laptop boards sitting around you can sell
You are the first in this thread to bring up what any of this is worth on a larger scale, selling the results. Everyone else is talking about putting together one simple computer or jumped-up microcontroller for a task of their own, and maybe more later for other projects. Some of us find this sort of thing fun, and in the shit world we are all living in right now having a bit of fun and achieving something [sort of] practical out of it, can be priceless.
Well, this is about replacing a Pi, so I guess people want a raw board. Indeed, if you just want to run a pi-hole, take any old laptop and just wedge it someplace...
Wanted to add that LLMs have become incredibly good at reverse engineering such devices, even when they don't have postmarketOS (now "Nura") or upstream kernel support yet. Been able to merge kernel changes and backport driver support to upstream kernels pretty easily by just giving them access to UART. They'll just go ahead and figure out all the partitioning and firmware quirks by themselves, and e.g. OpenWRT instructions seem to be well documented in the wiki so they'll understand the process on how to get there almost completely by themselves.
For my malware home lab, I decided to just reuse old phones and routers that nobody wanted anymore (quite literally got them from the trash bins). Now they're running an ARMv8 kernel as the host kernel and the rest is emulated or containerized, depending on the use case.
Works like a charm for most tasks I throw at it, and many old cheap Android phones have at least quad or octa cores in them, making them pretty awesome for podman/docker usage, too.
The only thing you have to look out for is to remove the battery, and that you use a separate power circuit with a step down converter to power it. But other than that, old smartphones have become amazing for selfhosting stuff now.
> It doesn't even pass a sniff test, if you know even the first thing about running.
And yet, it seems you do not know that the gap between men and women shrinks the longer the distances get? Also, as you are saying yourself: this is about distributions, not necessarily about the top 0.1% of the world. The article makes the claim that on average, women would perform better in ultra-endurance events, supporting their thesis that women actually did the hunting back then. You might disagree with this, but the article is more nuanced, and reducing it to the rage-bait comment above does not do it justice at all.
> And yet, it seems you do not know that the gap between men and women shrinks the longer the distances get?
So what? The gap exists. Saying that it diminishes with distance is interesting, certainly, but it's a far cry from evidence that the gender gap is due to something other than biology.
> The article makes the claim that on average, women would perform better in ultra-endurance events, supporting their thesis that women actually did the hunting back then.
This is sophistry. In reality, even on average, men are faster than women.
This is the paragraph. "As an example" here implies that they are talking about sports in general, not just endurance events.
Inequity between male and female athletes is a result not of inherent biological differences between the sexes but of biases in how they are treated in sports. As an example, some endurance-running events allow the use of professional runners called pacesetters to help competitors perform their best...
> Mounting evidence from exercise science indicates that women are physiologically better suited than men to endurance efforts such as running marathons. This advantage bears on questions about hunting because a prominent hypothesis contends that early humans are thought to have pursued prey on foot over long distances until the animals were exhausted. Furthermore, the fossil and archaeological records, as well as ethnographic studies of modern-day hunter-gatherers, indicate that women have a long history of hunting game.
Emphasis mine.
> Overall, females are metabolically better suited for endurance activities, whereas males excel at short, powerful burst-type activities. You can think of it as marathoners (females) versus powerlifters (males). Much of this difference seems to be driven by the powers of the hormone estrogen.
There are some pretty wild claims but overall, a fairly interesting article. I think they've just exaggerated an otherwise interesting point - that gender differences in hunting are not explained by differences in long-distance running aptitude (which are very small).
The examples of extant hunting techniques they themselves cited are not related to (ultra) long distance running anyway, so the connection between hunting and running is tenuous.
Jasmin Paris has won a fair number of extremely difficult ultras in mixed company, for example. Really long ultras are not an exclusively male domain. The marathon is if anything too short.
(Have a read about persistence hunting).
The article’s point is that the assumption that “men evolved to hunt” is unsupported by the evidence and therefore implicitly sexist. This is a defensible position.
Persistence hunting is speculative as a guiding force in evolution. It is a very rare practice amongst modern hunter/gatherer and there's no archaeological evidence that it was common enough historically to be important.
Compare this to game drives/trapping which are both mentioned in this article and have significant archaeological and anthropological evidence.
> You totally are. This is about ultra-endurance events.
No, it isn't. It's about sports, using ultra-endurance as an example. This is one of the cases where the example is the exception.
IOW, the quote uses an outlier to make claims about the distribution. This is, of course, from the same institution that claims using the word "normal" to describe a distribution is some sort of "-ist" (racist, sexist, whatever).
I went and read it and it doesn't seem to matter to me that it's about ultra-endurance events? Of course differences in stride length and endurance physiology will matter for run performance.
The full paragraph:
>Inequity between male and female athletes is a result not of inherent biological differences between the sexes but of biases in how they are treated in sports. As an example, some endurance-running events allow the use of professional runners called pacesetters to help competitors perform their best. Men are not permitted to act as pacesetters in many women's events because of the belief that they will make the women "artificially faster," as though women were not actually doing the running themselves.
To me both cultural and physiological differences are likely in play. I am not even sure how you could effectively seperate culture from physiology here (hard to do a randomised controlled trial on stride length - I guess Mendelian Randomisation regression might work?). Anyone confidently asserting only one or neither of these is at play is probably not stating that from a position of logic.
The claim that is being made in the article is that only cultural differences are relevant. Saying the relative effects of cultural and biological differences are hard to know would not be a very controversial statement.
Yes, which is why I am happy to state it having not read that deeply into the evidence either way. I would argue that stating "Inequity between male and female athletes is a result not of inherent biological differences" is a very strong statement that the scientific consensus has many counter-factuals available to disprove.
Would be interesting for x86-based tablets/convertibles, like for instance an old Lenovo X1. I tried using these with Linux with various different distributions, including PostmarketOS, and it was not a good experience.
> I don't understand why it took LineageOS so long to update to AOSP 17, while GrapheneOS managed to update to 17 in just 3 days.
Here's a hint: GrapheneOS has paid developers working on it full-time, while LineageOS is done by people in their spare time. Also, GrapheneOS has a collaboration with Motorola and through that gets for instance early access to security patches, and probably other things as well. And lastly, LineageOS supports roughly 10x the number of devices. It's significantly easier if you restrict yourself to Pixels.
Also, GrapheneOS has a collaboration with Motorola and through that gets for instance early access to security patches, and probably other things as well.
Just for clarification (your points are very valid): the GrapheneOS developers have stated on several occasions that they getting embargoed patches from another OEM than Motorola.
GrapheneOS doesn't receive early access to security patches via Motorola. We receive those through a different partner. We were already doing security preview releases prior to Motorola giving us access to their repositories which don't contain those.
LineageOS code can update pretty fast, but the problem is they want to do refactors, and also that bringing up a hundred outdated devices is difficult.
I was secretly hoping they'd stop supporting the Pixel 4a so I would have a reason to get a new phone, but no, still there in the list of supported devices. So I guess I'll just keep using that thing another year... Anyway: big thanks to the Lineage maintainers, keeping so many phones from landfill!
If you need a reason, the modem and the baseband firmware have several unpatched vulnerabilities on that model, which is not something that an Android update can resolve.
Based on the amount of modem CVEs posted in the monthly Android security bulletins, I think it's safe to assume that if you are no longer getting updates then there are unpatched vulnerabilities in them.
Based on the artificial delays Google introduces into the Android patching process, on the general crappiness of mobile firmware and the sleaziness of major mobile chipset vendors, I think it's safe to assume that even if you are supposedly getting updates, there are unpatched zero-day vulnerabilities in them. Usually under ongoing attack, at least by professional phone cracking software vendors and secret services.
>Based on the artificial delays Google introduces into the Android patching process, on the general crappiness of mobile firmware and the sleaziness of major mobile chipset vendors, I think it's safe to assume that even if you are supposedly getting updates, there are unpatched zero-day vulnerabilities in them.
Maybe if you include third party android OEMs like samsung, but google pixels are as up to date as you can get.
Pixels running GrapheneOS sure, but stock Pixels lag months behind patches that exist but not yet shipped. Check any bulletin and it links to git commits to months ago.
>Check any bulletin and it links to git commits to months ago.
Is there any evidence that the git commits weren't in the ROMs from months ago? The monthly ASB corresponds to when the bugs are publicly disclosed, not when they made it into ROMs.
Pixels only ship a tiny subset of the security preview patches early. Samsung ships a subset for their flagship devices too and it's likely larger than Pixels. Samsung lists these patches in their bulletins and you can retroactively figure out which were future Android Security Bulletin patches. Go through the vulnerabilities for September 2026 or October 2026 and search for them in Samsung's bulletin.
The only way to get the full set of security preview patches is through GrapheneOS. It's strange Google doesn't ship more for the Pixel OS but that's the way it is right now. It takes them around 4 weeks to make a release and even longer when including the time for adding changes to it so there's a long delay built into the process. They should fix it but are clearly not prioritizing it without media pressure that's not happening. They do a lot better than other OEMs but that's much different from doing a good job.
Android Security Bulletins don't list the vast majority of firmware, driver, HAL and especially Linux kernel vulnerabilities. Those list a large subset of the High and Critical severity Android Open Source Project (AOSP) vulnerabilities backported to older releases along with a tiny portion of non-AOSP vulnerabilities. AOSP vulnerabilities below High and Critical severity aren't backported so those aren't listed. Non-AOSP vulnerabilities for Pixels are covered in the Pixel Update Bulletins with many of those being vulnerabilities in components used by other devices. Each OEM is supposed to make their own equivalent to the Pixel Update Bulletins, but they aren't required to provide those updates to claim the latest patch level.
It has remotely exploitable vulnerabilities in the firmware, Linux kernel, kernel drivers, userspace drivers and HALs. Those don't require installing anything on your device to exploit. There are publicly available proof of concept exploits for a bunch of these vulnerabilities.
I too have a 4a that is still ticking thanks to Lineage!
The only problem I've discovered is that group texts sometimes don't work (I can't see others' replies or worst case I don't receive the group text at all). Not sure if anyone else has run into this, seems like it could be related to RCS and unlocked bootloader not playing nice.
I have stock Android on a Pixel 10 and RCS group texts don't work here either. Some people just can't be added to the group and some people just don't receive the texts.
I flashed my 10 with Graphene as soon as it was supported and RCS was a bit of a challange as well. Both because of the recipient's device/settings as well as my own privacy settings.
I have yet to find a banking app that refuses to work on LineageOS. The only problem is if you root your phone, in which case you'll have to use Magisk to hide root from those apps, which also works fine so far.
Revolut is notrious in this regard. If memory serves, they explicitly check the build string for LineageOS and block the app if it matches. The workaround at the time was to build the ROM yourself with a new build name string.
> Revolut is notrious in this regard. If memory serves, they explicitly check the build string for LineageOS and block the app if it matches. The workaround at the time was to build the ROM yourself with a new build name string.
What possesses companies to do things like this? A customer running a current version of LineageOS is going to have better security than running the out of date Android version that came with the phone. An attacker who wants root on something that will run the bank app doesn't have to use a different OS, they can just use any of this month's CVEs to root the "approved" version. Even requiring the latest patches -- which would exclude entirely too many actual customers' phones -- wouldn't stop attackers from controlling their own devices, because they could root the device before installing the patch and then install the patch for the vulnerability they used to get root on the device where they already have it.
And attackers who are going to modify the system to carry out an attack inherently have some kind of software development capacity, so measures like this have no effect on them and all they actually do is interfere with the ability of honest normies to replace their out of date OS with a version that is less likely to be compromised by attackers.
Are they just taking kickbacks from Google or something?
I suspect that especially banks have paranoid lawyers that probably don't understand the situation entirely, and perhaps because of that, mandate that all means have to be used to prevent non-official builds from being used, so that they cannot be sued (for some reason) if "something" goes wrong. Though I don't know if they are consistent and also apply the same reasoning to phones that don't have active security updates any more.
I feel like "the lawyers told us to do something stupid for no legitimate reason" is just one part of a bureaucracy trying to blame another part for the fact that the bureaucracy itself is doing something stupid for no legitimate reason.
This is objectively not true because there are companies, even banks, where this level of stupidity has not prevailed. In turn this implies that the others are doing something which is different but possible, and the scoundrel companies could be doing that too.
Even if the something is no more than engaging less fatuous attorneys.
You seem to be assuming that there is actually a law requiring them to do this. If you believe this to be the case, please identify it so it can be targeted for repeal.
Whereas if there isn't, the obvious alternative is that the other banks have lawyers who don't erroneously advise their client that they're required to do something they're not.
> there are companies, even banks, where this level of stupidity has not prevailed
Yes, because that particular set of lawyers haven’t said it has to be blocked. Doesn’t mean my statement that lawyers have final say is “objectively not true”.
Good to know. I'm using N26 and they work just fine in Graphene OS. What I do is I create a private space for the apps needing play services, which I keep locked most of the time. This acts as a separate profile and when locked, the apps including play services are completely off. My main profile uses only open source apps and no play services.
I actually called N26 (I'm a Metal customer with my own phone support) and asked will they support Graphene OS or no, and they said to me they will and gave me instructions what to keep in mind when installing the app.
I applied to open an N26 account, and after completing all the necessary documentation they then told me I had to install their app to activate the account. Forget it.
Instead I opened an account with Wise, and have never once been forced to use their app. One occasion where some ID verification process pushed me towards the app online, I spoke with support and everything was sorted without it. Wise.com, just need a web browser and a phone number, zero phone app dependency.
Insurance against collapse of the bank. FDIC doesn't insure against fraud because you expanded your trust relationship across multiple third parties with credentials to access your account.
This is the problem: it was a cat and mouse game always. I managed even strong integrity with keybox stuff and so on. Yes it is possible. But if you really need to do send money or e. g. want to pay with NFC, it gets rather stressful. Yes, I got everything working (Note 10 pro on LOS 23), but never longer than a few month.
I just decided to completely stop paying with NFC. I always carry a few cards with me and Wero is already working in a few spots, which requires just your banking app and a working camera.
I don't even have Google Wallet installed anymore.
Not everywhere, unfortunately. There are places in the world where only accepting digital payments is the norm and they won’t serve you if you pay in physical cash.
And the problem is people stopped paying cash, thus the facility was largely withdrawn. I don’t know what the answer is, but my gut says if cash remains legal tender, businesses should be obliged to accept it as a form of payment.
Otherwise, vote with your wallet wherever possible and prefer those businesses that do accept cash.
And even if they theoretically can serve you, one generally doesn't want to be 'that guy'.
I'm glad the option is still there in most places, but it's clear most people don't actually care for cash (neither do I for that matter, other than as a backup solution).
And I’m in Austria. Plenty of businesses still ONLY accept cash. And not just small rural concerns. Had lunch in the city yesterday and the restaurant only accepted cash payment.
In Berlin they started following the EU law and you can quite often pay with a card. Even in places like biergartens. Still having cash when going to a Kneipe, although last time they also accepted cards which was a bit weird...
There are alternatives to Google Pay in Europe which work on GrapheneOS and it's likely most of those work on a production (user) build of LineageOS with a locked bootloader too. Only a few are specifically permitting GrapheneOS, and those would also be willing to explicitly permit a subset of LineageOS devices too. They'd need to start keeping a bit more of the standard security model and features intact which wouldn't be a large change. They'd mostly just need to make full production builds and start officially supporting locking. Having the privacy and security improvements done by GrapheneOS is in no way a requirement for compatibility with those financial apps.
This really is really a great development. I really just hope that will be true for the new European Digital Identity Wallet as well and we see adoption across multiple industries.
The state for me personally is that my joint bank account with my wife uses a play integrity protected banking app (changing your own a accounts to a better bank is one thing). Also beyond banks things now require proprietary 'secure' TAN apps like my insurance broker. The issue is that for me every a new problem like this popped up and to find solutions take time over and over. Even thing that work now may stop working the next minute because there is no real effort of fintech and its management to keep compatible with niche devices. It is mostly either coincidence or the effort of tech savvy individuals at those companies.
We only can hope that a large group of people including regulators get sanctioned or mandated not to use any US tech even privately so they see little offer is left even inside Europe that is truly sovereign.
I gave up for now (after about 10 years exclusive on LineageOS ). I actually bought a pixel to have Graphene as a way out of vendor ROMs again, but I still don't have the energy to switch (alone reregistration all those TAN apps takes ages often involving waiting weeks for stupi snail mail activation letters)
In Germany that would be market places like eBay or Amazon (i.e. non-originally replacement parts). Original ones go for around 45 EUR (iFixit). But I guess you wouldn't care too much about original parts at that age.
I bet sprinkle beside the bath is ok, but toilet plop is not ( I have seen the second one, I suggest grabbing it without any delay, better grab it working because you have to grab it anyways)
I replaced battery in mine for like 90 EUR and several months in dropped it and broke the screen. Would still use it instead of 9a, love how light and compact the phone was. At least now I have a spare phone to root and do stuff with that I couldn't on my main one.
What happened there, ... After official support by Google for the 4a stopped, I remember checking LOS out, and found that it wasn't supported there either. Did I hallucinate that, or did LOS resume support afterwards? Or maybe I'm mixing up LOS and graphene
I was secretly hoping I didn't misread and Linaro wiki would be up again, I really wish we could just install mainline linux on those Android phones...
I second this. I've been using Lineage on older, second-hand OnePlus phones for about a decade now, currently a OnePlus 8T. You can pick them up pretty cheaply from eBay, and they're solid devices, often in near-new condition. Pair them with Lineage, and you're golden.
That might be coming to an end, though, if OnePlus no longer allows bootloader unlocking.
I flashed my 4XL today (from the no longer supported Graphene). It's nice to be able to keep a 7 year old device runnin, when most people bin theirs after 3-4 years.
They patched CVE-2026-43499 even for out of support kernels[1] so that's something. The bigger problem is CVEs in proprietary components (drivers, blobs, firmware).
That's very misleading since the vast majority of serious Linux kernel vulnerabilities aren't patched for these end-of-life devices. That vulnerability patched due to media coverage based on their policy to do so. It's no more severe than many of the unpatched ones.
It's very misleading since the vast majority of serious Linux kernel vulnerabilities aren't patched for these end-of-life devices. That vulnerability patched due to media coverage based on their policy to do so. It's no more severe than many of the unpatched ones.
The vast majority of kernel vulnerabilities aren't backported to end-of-life devices. Special cases are made for certain vulnerabilities with a lot of media coverage. Firmware, kernel drivers, userspace drivers and HALs on end-of-life devices go without patches in general.
Notably, this is still cutting out the middleman and bypassing the extra review that that entails. It's fine as long as you trust everybody involved in publishing the repo, which is probably fine here, but a thing to keep in mind.
I am sure he is quite happy to have people disagree with him on HN. He usually wears it as a badge of pride. We might even have a follow-up in a couple of days about how these techy weirdos lost the plot.
The boards are of course bigger, which I guess will be a non-starter for many. They'll also require active cooling unless you downclock them considerably. They often also require more power, although many mainboards can be configured down two a few watts of power consumption, depending on what peripherals and speed you need.
Yeah, it's more work than just getting a Pi, but given the current prices, it makes sense for me.
reply