I worked with the author of Fil-C at Apple while on the Safari team, and he's easily one of the brightest folks I've had the pleasure of knowing. Fil-C looks extremely cool.
Yes, the US Mint sells all of the coins in the American Innovation set to the public. Previous years’ coins can still be bought if they are not sold out.
Not an American but I wouldn't mind having some of these. Actually, coin collecting is a pretty neat hobby, especially for commemorative coins which depict a story like these. I wouldn't go in it for their possible future financial value though.
Before I left Apple ~10y ago, it was pretty common to drop linked-on-or-after hacks into AppKit and UIKit to keep popular software chugging along. Assuming they're still doing that sort of thing, this was either missed or deemed not high-enough priority to add such a check (or maybe one was added, and the only reason this issue has been noticed is because Electron and Electron apps are now being built against the macOS 26 SDK).
Visual Studio used to be as bad as modern Xcode, if not worse. Having used VS2022 a bunch for the last handful of years, I’m pleasantly surprised. Apple could take a page out of Microsoft’s book here.
They've literally never had a country. Went from Roman to various foreign Islamic states (plus a crusader kingdom and the Mongols briefly) to Ottoman to British to part of Egypt (Gaza) and Jordan (West Bank) to current situation.
Either way, it's weird that leftists will say every culture deserves their own land/country except Europeans...
You act like Palestine wasn't its own state before mass migration of Israeli settlers. Israelies have been expelling Palestinians and annexing their territory since about 1948.
So, do answer your extremely naive question, yes Palestinians deserve their own country. Preferably the territory they've occupied longer than the Israelies.
This exact same phenomenon bit me at a previous job. We hired a couple of really smooth-talking grifters, and it took a tremendous amount of time to get rid of them. Vibes matter.
The problem with this sort of hiring over time (we hired grifetrs because vibes) is that you never get to compare your vibe failure rate with those who had bad vibes but would have been better hires.
If you go with vibes too much you only ever accumulate data saying that vibes matter.
This is one of the things that I’ve tried really hard to impress upon engineers new and old while working on various projects, and IMO it applies to just about every layer of the stack; ultimately everything flows up into the UX.
This vibe was pervasive at Apple and could be taken more or less for granted, but elsewhere it’s all over the place.
And, like, sure, there are projects and industries where this doesn’t matter. But giving a shit and feeling it can be a major differentiator.
We've been using mise since it was called rtx at $DAYJOB, and it's caused many a headache (mostly around upgrades/backcompat/etc.). We use it both on dev machines and in CI. In spite of that, it’s decent at what it does, and I wouldn’t soon replace it with individual version managers, given that we have similar needs.
However…more than once we've seen language runtimes that used to be available exclusively via plug-ins be migrated to be internal to mise, which broke everyone's setups in strange and hilarious ways, and caused countless hours of debugging.
Less bad overall than using individual runtime version managers for sure. But the next time mise costs us a bunch of hours fixing multiple engineers' setups, I intend to find another solution, even if that means writing my own. It’s burned us nearly one too many times.
Do you have any examples what tends to break? We used pyenv/rbenv/sdkman etc. individually, then moved to asdf and now arrived at mise. Not using yet for CI just developer stuff and so far didn't have issues. But this is quite recent for us, so didn't have to deal with upgrade issues yet.
We manage mise itself via homebrew. Sometimes when upgrading mise itself, it doesn’t seem to handle being upgraded gracefully, and loses track of installed runtimes even if we manually kick it in our upgrade scripts. Restarting the shell entirely seems to be the only way to fix it.
That, and with Ruby, Node, and at least one other language/tool IIRC, when support for those things moved internal, we had to make a bunch of changes to our scripts to handle that change with effectively no warning. That involved checking to see if the third-party plug-in was installed, uninstalling it if so, and then installing the language based on the built-in support. In the meantime, the error messages encountered were not super helpful in understanding what was going on.
I’m hopeful that these types of issues are behind us now that most of the things we care about are internal, but still, it’s been pretty annoying.
