Apple generally provides 6-8 years of OS support for hardware. My 6.5 year old 2019 Macbook Pro works fine with macOS 26; macOS 27 will drop support in September 2026; macOS 28 will drop Rosetta Intel support. macOS 26 get updates thru September 2028 at which point all Intel mac hardware will be >8 years old.
I would argue that Steam and Homebrew users are relatively niche portions of the userbase, and that they would be more likely to own newer systems.
Neither statistic comes from a sample group that's more representative of the average user, who is mostly browsing the web and using a handful of undemanding applications, and is therefore less motivated to upgrade for performance reasons.
Maybe for Steam, but my gut instinct is that Homebrew would be the opposite: it would be disproportionately popular among devs who pride themselves on keeping hardware for many years longer than most people. "Yeah, this 2015 MBP isn't great for gaming anymore, but it's fine for running vim!" is absolutely the kind of thing I hear frequently.
I bought an Intel MBP towards the end. No regrets, I had valid reasons.
But the MacOS support at this point is pretty atrocious. I mean, it technically runs, but the OS is clearly designed in a way that ruins performance on this hardware. It’ll run Vim, sure, for 2 hours on battery, hot as hell. At this point, Intel Macs are only fine for running Linux.
There's actually two Engineering Emmy Awards. There's also the 'Primetime Engineering Emmy Awards' given by the ATAS (Academy of Television Arts and Sciences) while 'Technology and Engineering Emmy Awards' are given by NATAS (National Academy of Television Arts and Sciences), not confusing at all.
Very few units sold. Distribution was poor, most were GSM only and only a couple supported 850mhz. I had the E70-2 and later E61i but I never meant anyone else with one.
Yep, I presume that’s primarily what the article author meant. To Americans Nokia mostly means "feature phones" whereas in Europe Nokia smartphones were, if not ubiquitous, commonplace enough around 2007 (remember that Nokia had been making smartphones for a decade by then). The N series in particular were targeted at consumers.
1. You can specify your terminal font via terminal.font_family in zed settings.json
2. Not sure.
3. For most languages, the default is to use prettier for formatting. You can disable `format_on_save` globally, per-language and per project depending on your needs. If you ever need to save without triggering format ("workspace: save without formatting").
Prettier is /opinionated/ -- and its default is `singleQuote` = false which can be quite jarring if unexpected. Prettier will look for and respect various configuration files (.prettierrc, .editorconfig, via package.json, etc) so projects can set their own defaults (e.g. `singleQuote = true`). Zed can also be configured to further override prettier config zed settings, but I usually find that's more trouble than it's worth.
If you have another formatter you prefer (a language server or an external cli that will format files piped to stdin) you can easily have zed use those instead. Note, you can always manually reformat with `editor: format` and leave `format_on_save` off by default if that's more your code style.
Thank you for the excellent and informative reply. Will try it out
It would be nice for prettier to throw a user warning before making a ton of changes on save for the first time, and also let them know where they can configure it
Very similar to the Beepberry. Exciting to see someone else building into that form factor. Also love to fun to see the Nokia BL-5C battery (originally introduced in the Nokia 3650 in 2003) still alive and kicking 20years later.
That appears to have been renamed to the Beepy, and the product page now has the repurposed Blackberry keyboard blurred out. Did whoever owns the corpse of Blackberry go after them for trademark infringement?
This was the question I was going to ask! I've recently been diving into Lua 5.x internals and have been extremely impressed with Lua's register-based bytecode implementation. Lua has a stable byte code interface between patch releases (5.4.0 -> 5.4.1, etc) but not between major/minor revisions (5.3 -> 5.4). SQLite on the other hand does not consider this a public interface at all!
> "Remember: The VDBE opcodes are not part of the interface definition for SQLite. The number of opcodes and their names and meanings change from one release of SQLite to the next."
https://www.sqlite.org/opcode.html#the_opcodes
For anyone interested in understanding how a register-based VM operates I highly recommend:
I also like their Automated License Plate Reader (ALPR) record retention period (3 minutes):
> Records of number plates read by each LPR shall not be recorded or transmitted anywhere and shall be purged from the system within 3 minutes of their capture in such a manner that they are destroyed and are not recoverable, unless an alarm resulted in an arrest, a citation, or protective custody, or identified a vehicle that was the subject of a missing person or wanted broadcast [...]
This seems absolutely reasonable. Keep the data about people who have committed or you can reasonably suspect might be committing a crime, get rid of the identifiable information for law-abiding citizens and maybe keep the aggregated metadata.
> to see how far it gets before killing itself (on a VM or easily re-flashed machine of course).
I did this, but with dd -- it completed. Was very anti-climatic. I was hoping it would crash or at least disconnect me, but the kernel, sshd and bash were still in memory and happily returned me to a prompt where I couldn't really do anything.
Homebrew 30d says 27% Intel
My gut says 20-25% is a reasonable ballpark.
Apple generally provides 6-8 years of OS support for hardware. My 6.5 year old 2019 Macbook Pro works fine with macOS 26; macOS 27 will drop support in September 2026; macOS 28 will drop Rosetta Intel support. macOS 26 get updates thru September 2028 at which point all Intel mac hardware will be >8 years old.
[1]: https://store.steampowered.com/hwsurvey/processormfg/
[2]: https://formulae.brew.sh/analytics/homebrew-os-arch-ci/30d/