I successfully use Claude Code in a large complex codebase. It's Clojure, perhaps that helps (Clojure is very concise, expressive and hence token-dense).
Perhaps it's harder to "do Closure wrong" than it is to do JavaScript or Python or whatever other extremely flexible multi-paradigm high-level language
Having spent 3 years of my career working with Clojure, I think it actually gives you even more rope to shoot yourself with than Python/JS.
E.g. macros exist in Clojure but not Python/JS, and I've definitely been plenty stumped by seeing them in the codebase. They tend to be used in very "clever" patterns.
On the other hand, I'm a bit surprised Claude can tackle a complex Clojure codebase. It's been a while since I attempted using an LLM for Clojure, but at the time it failed completely (I think because there is relatively little training data compared to other mainstream languages). I'll have to check that out myself
> EV have much higher emissions of micro plastics and pfas (or variations thereof) due to increased tier degradation
I find those claims highly suspect: I own an EV and haven't had to change the tires more often than I did on a gasoline-powered car. My EV bought in 2021 still runs on original tires and they're fine (although I do change from winter to summer tires, so that's 2 sets technically).
I suspect black PR, and there is always a grain of truth in black PR: emissions are indeed likely to be higher. Probably not "much higher" and probably not in a way that really matters.
Just because a tire lasts as long doesn't mean it isn't wearing in different ways. EV specific tires are a lot different than their ICE counterparts.
This isn't "black PR". It's comparing apples and oranges. But throw non-EV tires on one and you'll definitely chew those tires up much more quickly [0][1][2][3].
The class of the Ioniq 5 isn't lighter than it's ICE competitors. It may be lighter than a larger SUV, but the tire changes drastically as the GVWR increases.
An Ioniq 5 can weigh over 1000lbs more than a Honda CR-V, for example (depending on trim & battery).
Sigh. After Apple suddenly discontinued Aperture, which left users like me with huge complex photo archives hanging, I will never trust any professional software tool from Apple again. It is a disaster that I still haven't fully recovered from.
I've learned my lesson — all my archives will now be maintained by me, in file structures, with metadata in text files.
And yes, I agree with the article, Aperture was a really good piece of software, with many design decisions that seemed controversial, but were driven by many hours spent with professional photographers, looking at their workflows and listening to them. The result was very good.
I've been having the same thought. Just move back to a file structure which is what I was doing from 1995 until 2007 before migrating to iPhoto.
The metadata in Apple Photos doesn't fully sync to iOS over a cable now. Did Apple intentionally make offline sync not work to force everyone on to iCloud? Also, even the local search inside of Apple Photos doesn't work correctly either. I thought it was hilarious when they tried add "AI" to this shitshow. Apple literally can't even make a local tag search.
Isn't it possible to put all the metadata in EXIF tags? People keep telling me to use Immich, but IDK.
I might be wrong, but I thought the situation in Kraków improved significantly several years ago due to the efforts of local administration, so much that we were jealous here in Warsaw. Has it worsened again since then?
Incidentally, radio buttons are a (sadly) forgotten art and are neglected in modern browsers. There are many issues with them, which is why people reimplement them on their own.
That's programmer incompetence. Unfortunately pervasive, especially with devices like parking meters, EV chargers, and similar, where the feedback loop (angry customer) is long (angry customers resulting in revenue decrease) or non-existent.
It's a nice theory, but many of those terrible parking ticket machines predate smartphones, so it might be the case for machines built now, but it's really hard to imagine that that was the original intention
I work in an adjacent industry, and trust me when I say that a lot of older equipment companies just did not care much about the experience of using the equipment. It's much more important to tick all of the boxes in the back end accounting system than to have a high quality experience on the kiosk.
After Apple suddenly discontinued Aperture, which left users like me with huge complex photo archives hanging, I will never trust any professional software tool from Apple again. It is a disaster that I still haven't fully recovered from.
I've learned my lesson — all my archives will now be maintained by me, in file structures, with metadata in text files.
Learned that lesson too. Then got into Lightroom. Now getting out of that by exporting stuff slowly. Moving to files on disk and edits in Darktable now. No "library".
Please don’t take this as me saying you were wrong to ever trust Apple, however the best way to organise any data is usually just files on a disk.
That’s becoming a recurring theme for me and even some of my corporate clients now. Confluence, for example, is out the window for secure documentation around sensitive environments and Word Docs in One Drive are back in. It’s surprisingly refreshing and gets the job done way better.
From what I recall, aperture did use files-on-a-disk, maintaining original photos read-only and letting everything else be operations on those originals.
Agree with all of this, apart from possibly OneDrive but that's for another post.
Not Apple-specific really that point for sure anyway. Personally I don't think we should ever ever trust any vendor to control our data or act as a proxy for access to it. If it's not on a physical disk in your hands, in a format which is documented and can be opened by more than one application, then you're one step away from being screwed. There are so many tangible risks we love to sweep under the rug from geopolitics, commercial stability, security, bugs to unexpected side effects. And I've seen some real horror stories on all of those fronts.
At the same time I managed to embed myself thoroughly in it and I'm 3 months in to undoing the mess. It's VERY hard to get back to files on disk. No moving away from that is probably the best option I suspect a lot of us never took.
Hardest stuff to get out of is iCloud/Apple and Adobe.
It's all true, but if you think organizing photo archives is easy, boy have I got news for you.
Metadata, versions, version groupings, projects, albums, there is lots of structure that most people don't realize exists.
Think every picture has an EXIF date and that's the date when it was taken? Think again. Scanning date is not the same as picture date.
Actually, even if you think of a date, you probably imagine the usual ISO8601 2026-01-14T17:37:46Z date — how about when we only know a year? This is something Aperture didn't do either, but when dealing with photo archives what you want is arbitrary precision date intervals. E.g. 1900-1902 for example.
Anyway. Just pointing out that even though "just files on disk" is the right approach, managing those files and their metadata is far from obvious.
reply