I think at this point the brand reputation and software quality are a big selling point.
If you're trying to build a couple of units of some embedded thing where you need to toggle some GPIOs or serial devices in response to requests over the network, but don't have the expertise or resources to do it with a microcontroller, a Pi is a great option - you know you'll have software support, and you know that the vendor will be making the exact thing you bought for 5-10y.
For hobbyist stuff at home, I agree, though. A mini PC is probably better for homelab stuff, and an RP2350 or ESP32 is probably better for anything embedded or battery powered that you want to do.
Development speed is also one of the forgotten axes. I mentioned upthread a system I built that was done in less than a day. There's no microcontroller solution I know of that would have let me deliver it that fast.
I've been playing with Circuit Python (variant of Micro Python, etc.), and it seems quite great actually. For small projects it's far simpler to use than C/C++, although if you're using some peripheral that isn't just toggling pins or simple serial commands you need a library (module). But then in that case you'd probably want a library in C as well. Definitely recommend it :) (it works on ESP32 boards as well as similar recent microcontrollers)
I like CircuitPython: shipped at least one freelance project using it. However, MicroPython seems to have support over a broader range of platforms. Haven't decided which one to stick with just yet.
You do know those are trivially bypassed with a signal processor, right? If physical access is outside your threat model, that's OK, but it makes (for example) the forced Win11 upgrade for DRM^H^H^H boot integrity enforcement seem ridiculous.
Yeah, fair enough. "Compliance" is probably the phrasing I should've used, rather than "security".
I've been curious for a while about the overall taxonomy of security, especially for embedded platforms. It seems like the only hope is defense in depth, given the power glitching attacks and the like that you can find demonstrated.
Specific to the Raspberry Pi, I believe I even saw a thread at some point where one of their firmware engineers was making the case that secure boot on the Pi 5 was equivalent to a TPM in almost any reasonable threat model, since, in either case, you were out of luck if an attacker had physical access and was willing to put in enough effort.
Normal secure boot does not use the TPM. Secure boot is the proactive process of ensuring only allowed code loads and executes.
The TPM is used for measured boot, the post process to understand what actually was booted and if the right set of things were booted then to allow unlocking of specific items like keys.
Both are important but they are not the same thing.
I wouldn't be against better labeling, but I've found that I don't have to worry about it too much, day to day.
USB-C has allowed me to grab one decent two-port charging brick, two solid 6ft cables, and charge just about everything I own just by keeping those in my backpack. If I think I'll need to move any data fast, etc., I just throw my one good USB4 cable in my bag, too.
I will admit, though, that I've had some crappy situations at work where it turned out my flaky monitor setup was due to the stupid work-provided docks coming with cables that only supported 10Gbps. Better labeling would've solved those ones.
Hah same exact setup one brick two ports and it charges everything even my laptop! I've been eyeing some of the ones with built in batteries, but I get a lot of mileage of one brick in the bag.
The steam deck forced me to finally pay attention to the usb-c ecosystem and I can only imagine how some non tech people might get with mysteriously bad or slow charging.
I find it crazy that Apple went back to magsafe in the m4 (maybe earlier but that's the machine I have at work). But at least you can still charge over usb-c.
I can't get myself to do the battery-built-in-to-charger thing. I've always treated portable power banks as semi-disposable since they do eventually get worse and fail, and it feels icky to me to tie ~immortal charging gear to something that will die.
I did have the same feeling about flashlights for camping/hiking with lithium batteries, though, until someone walked me through just how much better they are than lugging around AAs.
Where I live these days, it's 50/50 heat included in rent versus not, and I have to remind my friends that literally all of the buildings they rent in are 50+ years old.
And if your landlord is balking at including heat in rent, there's a decent chance it's because your bill will be outrageous because there's zero insulation, and as a tenant there's little you can do to fix that.
I was curious to see the "Innovative DICOM Medical Imaging" section. I wouldn't have thought that Apple would be interested in niche applications like viewing radiology imaging, but I guess they're probably interested in any cost-insensitive market for these since they're so expensive.
At a local hospital the radiologists have been all Mac for a long long time. They refused to give it up and resisted all attempts to get them to switch. So it doesn’t surprise me at all.
Yeah, in my first job I was an Apple technician for a company that supplied DICOM solutions to radiologist, both in hospitals and standalone.
I thought it was weird they spent so much money on Apple hardware when most of what we sold was servers that would be hidden anyway.
But they do like OsiriX; once a solution is established in those fields, they stick with it, very conservative professions obviously...
Interesting, I would've guessed that they would've forcibly been on Windows since time immemorial.
Entirely unsurprised that someone would refuse to give up their workflow, though! I've rarely found a user with specific needs who wants to change literally anything else about their system, since what they have works for them.
It's probably an easy win for them. It also might have been a good target when they were ideating on specs. Having these pro certifications gives the devices a halo of premium quality.
Regular consumers probably don't buy these displays in bulk, when you can get very nice displays for less than half the price that are 98% the same on specs.
So targeting checkbox-compliance for places like hospital systems is probably an easy win to generating / keeping some long term contracts.
> you can get very nice displays for less than half the price that are 98% the same on specs.
Can you recommend any displays with PPI and brightness equivalent to the studio display, with 120Hz+ refresh rates? I was waiting for this announcement to buy a studio display because I thought they might bring 120Hz to the base model, but $3300 is a lot to spend on a single display. I have an original studio display and a high refresh rate 4K OLED monitor, and they are both compromises unfortunately.
I don't think you can get a DICOM-certified display at 5K and 27" for half the price. Probably like $1k less but that's it - and if you're a radiologist making $300k+ you're not going to want to cheap out on a display.
If you're a radiologist making $300k+ you're going to want to use certified displays so that you don't get sued for using non-approved devices for diagnostic use, and that's going to cost you maybe $6k for a 21" monitor.
Seems to be the expected relatively small refresh, mostly just adding the M5?
The language towards the end of the press release implies to me that they're targeting last-gen Intel MacBook Air users thinking about upgrades more than anyone with an M2/3/4 MacBook.
Echoing a sibling comment, lots of landlords require it now, and the basic packages that insurers offer you as a bundle with auto or other forms of insurance are pretty decent, depending on state.
Typically seems like $100-200 per year for coverage that would handle the loss of most of one's possessions, provided you don't get screwed by "well, you don't have the receipt" or "we only cover water ingress, not floods or leaks".
> But iNaturalist data is often not considered high quality enough to be publishable by itself (wide brush statement) in my field of plant conservation.
As someone who recently started using iNaturalist, I've been curious about this. I think it's an awesome platform and really cool that people can share what they find, etc, but I noticed that people would pile on with species-level IDs on pictures that were obviously ambiguous between different species known to exist in the vicinity.
I of course want as much data as possible to be available to science, but it piqued my interest about whether a negative feedback loop of misidentifications to future identification models could form.
I think GP might’ve been referring to the part of Jeff’s post that references GPS, which I think may be a slight misunderstanding of the NIST email (saying “people using NIST + GPS for time transfer failed over to other sites” rather than “GPS failed over to another site”).
The GPS satellite clocks are steered to the US Naval Observatory’s UTC as opposed to NIST’s, and GPS fails over to the USNO’s Alternate Master Clock [0] in Colorado.
I find this stuff really interesting, so if anyone's curious, here's a few more tidbits:
GPS system time is currently 18s ahead of UTC since it doesn't take UTC's leap seconds into account [0]
This (old) paper from USNO [1] goes into more detail about how GPS time is related to USNO's realization of UTC, as well as talking a bit about how TAI is determined (in hindsight! - by collecting data from clocks around the world and then processing it).
Raspberry Pi seems to have been on a tear of good stuff this year. Lots of activity on both the hardware accessory and software side. I've been following their secure boot provisioning work in particular.
Conveniently for me, they keep releasing things right as I start to have an interest in using that thing.
If you're trying to build a couple of units of some embedded thing where you need to toggle some GPIOs or serial devices in response to requests over the network, but don't have the expertise or resources to do it with a microcontroller, a Pi is a great option - you know you'll have software support, and you know that the vendor will be making the exact thing you bought for 5-10y.
For hobbyist stuff at home, I agree, though. A mini PC is probably better for homelab stuff, and an RP2350 or ESP32 is probably better for anything embedded or battery powered that you want to do.
reply