I guess what's unusual is that the scope includes inbox access.
IMO it's probably a bad idea to have an LLM/agent managing your email inbox. Even if it's readonly and the LLM behaves perfectly, supply chain attacks have an especially large blast radius (even more so if it's your work email).
He didn't flop. He's had a number of high-status bespoke projects, including the coronation logo for King Charles and a redesign of Christie's (auction house) podium.
He's not doing commoditised consumer design any more. He has enough money now, so he no longer needs to.
I agree his post-Jobs years at Apple were somewhere between mediocre and hopeless (gradients...) and not many people seem to miss him.
Although to be fair, he wasn't responsible for Liquid Glass, which has set the bar for design failure at Apple to new depths.
FFmpeg doesn't disallow commercialization. Or to put it another way, the authors of FFmpeg specifically allowed commercialization. As long as you follow the LGPL you're free to commercialize your app that uses FFmeg
Fair, it actually started out in JS, moved to Deno, then Zig and ended in Rust.
If I ever find the time I'd like to back port what I have now, up the chain.
It is supposed to be a RDF replacement so it will eventually have to happen, but it's hard work to make everything extremely idiomatically integrated into the host language.
A somewhat little know part is a "pre-biased transistor": this is a bipolar transistors with built-in resistors, and will often work as a drop-in replacement for a logic-level MOSFET (like 2n7000), but is an order of magnitude cheaper.
JOINS make these kinds of queries get slower as the number of hops gets larger. And property databases have the big advantage of not having to mutilate their query results to fit into a flat table. A path query returns a path object of connected nodes. Property graphs are superior for applications with deep, variable-length connections, such as social networks, recommendation engines, fraud detection, and IT network mapping.
I have been a GrapheneOS user for several years, and I choose to dedicate my time supporting the project. Supporting an open source project is not 'astroturfing'.
Seems to me like there's also a divide between observational laws (e.g. Hyrum's Law just says "this seems to be true") and prescriptive laws (e.g. Knuth's Law, which is really a statement about how you ought to behave)
There have already been several attempts to procedurally generate Where’s Waldo? style images since the early Stable Diffusion days, including experiments that used a YOLO filter on each face and then processed them with ADetailer.
It's a difficult test for genai to pass. As I mentioned in a different thread, it requires a holistic understanding (in that there can only be one Waldo Highlander style), while also holding up to scrutiny when you examine any individual, ordinary figure.
It's evolving, and I'm using transducers more over time, but I still regularly am in situations where a simple map or mapv is all I need.
Lazy sequences can be a good fit for a lot of use cases. For example, I have some scenarios where I'm selecting from a web page DOM and most of the time I only want the first match but sometimes I want them all - laziness is great there. Or walking directories in a certain order, and the number of items they contains varies, so I don't know how many I'll need to walk but I know it's usually a small fraction of the total. Laziness is great there.
This can still work with transducers - you can either pass a lazy thing in as the coll to an eager transducing context (maybe with a "take n" along the way) or use the "sequence" transducing context which is lazy.
I tend to reach for transducers in places in my code where I'm combining multiple collection transformations, usually with literal map/filter/take/whatever right there in the code. Easy wins.
Recently I've started building more functions that return either transducers or eductions (depending on whether I want to "set" / couple in the base collection, which is what eduction is good for) so I can compose disparate functions at different points in the code and combine them efficiently. I did this in the context of a web pipeline, where I was chaining a request through different functions to come up with a response. Passing an eduction along, I could just nest it inside other eductions when I wanted to add transducers, then realize the whole thing at the end with an into and render.
Mentally it took me some time to wrap my head around transducers and when and how to use them, so I'm still figuring it out, but I could see myself ending up using them for most things. Rich Hickey, who created clojure, has said if he had thought of them near the beginning he'd have built the whole language around them. But I don't worry about it too much, I mostly just want to get sh-t done and I use them when I can see the opportunity to do so.
Well, it is change, but that doesn't mean it's not destruction. While the world has experienced mass die-offs before, the hallmark of the planet's current situation is distinguished by its unprecedented speed and the fact that it is being driven by a single species' behavior rather than geological cycles or cosmic externalities.
To repeat myself in another comment: I have tried to really focus on and take comfort in the idea "deep time", and the sincere belief that for as much destruction as we create, there will be more and different beauty in the far, far future. Yet where the Louvre to burn, how much comfort would it be to me that over the next 1000 years other artists will create yet more great works? In the same way, how long will it take the earth to return to such complexity and diversity of life? Many, many millenia.
I don't think I've ever /resumed a Claude Code session even once. What do people use that for? The way I use it is to make a change, maybe document the change, and then I'm done. New session.
There's a very interesting fallacy at play here. It's true that Ukraine is doing absolutely amazing and ingenious things on a shoestring budget across all military domains. It's also true that the armed forces of other world powers have a lot to learn from them, especially when it comes to drone warfare.
The fallacy comes in when blindly transferring these lessons to other wars and other armies.
In a perfect world with unlimited production and budgets, Ukraine would love to use Patriot or SAMP/T to shoot down every slow moving drone. In the real world, they make do with what they have, because the alternative is defeat and annihilation.
Ukraine is using propeller trainer planes to shoot down Russian drones because they have them and they can be quickly modified for the mission. That doesn't mean that an air force starting with a clean slate would prefer to use a cheap propeller plane in an anti-drone role. Instead, given enough time and budget, they'd probably prefer to build a custom-designed, more expensive and more capable solution, which still lands in a better spot on the shot exchange curve than Patriot vs Shahed. Think interceptor drone (which are usually several times more expensive and capable than their targets, but that's air defense) or 21st century gun systems.
Ukraine is a post Soviet state with a huge stockpile, engaged in a drawn out attritional defensive conflict where neither side has claimed air superiority. They have no choice but to be efficient, and to make everything they have go as far as they can. From an economic point of view, the USA can afford to be less efficient when fighting into Iran.
For the USA, shot exchange as an economic problem is mostly theoretical. The real problem is supply exhaustion. It doesn't matter if the air defense interceptors cost $10,000 or $10,000,000 if the total stockpile and yearly production capacity of them is only enough to fight for 3 months.
No, but my point is this argument isn't really consistently applied. The excuse about a law made specifically to apply against people that can't vote is quite popular and accepted. The cockfighting law was cheered by most the mainland US, while Puerto Rico desperately fought against it, though they weren't able to get cert in SCOTUS to challenge it.
I wish that Opera Omnia, also by Stephen Lavelle, got more attention. It is mind-blowing exploration of the idea of propaganda and revisionist history, which somehow also manages to be engaging and fun, with an incredibly unique core mechanic.
IMO it's probably a bad idea to have an LLM/agent managing your email inbox. Even if it's readonly and the LLM behaves perfectly, supply chain attacks have an especially large blast radius (even more so if it's your work email).