Bose Quietcomfort (i have the 2nd gen ultra now but I've owned other models too) live up to their name for comfort. Very lightweight and the earcups are large enough that they don't pinch. They may not have the best ANC or featureset, but I enjoy mine immensely
I saw Current Reader (no affiliation) posted on the web a couple days ago. It seems like a nice way to keep up to date with many hundreds of feeds by giving them different priorities, where for example a low priority feed may disappear from view quicker than a higher priority one. https://apps.apple.com/us/app/current-reader/id6758530974
I used to use Reeder pretty religiously but as websites started to lock down their feeds and charge subscriptions, it became less useful over time. As readership declines, publishers are rightly concerned to protect their remaining revenue by charging subscriptions. I would love for a new protocol to exist which could compensate providers appropriately and allow for consumer choice in reading with whatever app
The framing (and name) of this company (subsidiary?) is a bit unfortunate. If this had been built as a natural extension to the Raycast API, with the advertised benefit of being able to create desktop applications, I think it would go over a lot better than presenting it as a different product altogether that dilutes the main offering
As Godot is still very simple from the UX perspective, I'd prefer a set of tools to fully replicate the flash workflow instead of a dedicated app. Why reinvent the wheel? Stuff like keyframe animation editor etc is already there anyway and the engine is powerful enough. Just missing some tools, which could be easily added via the asset store.
Are integration vendors like Pipedream in trouble now that every company is pushing out MCP servers and CLIs to ride the AI craze? After the Twitter and Reddit API troubles of prior years, I can't imagine any company would willingly bring down the walls of their gardens and give easy access to precious user data. I'm waiting for the rug pull
I tried all of Codex, OpenCode, Claude Code and Cursor these past few weeks. It was surprising to me that all of them have slightly different conventions for where to put skills, how to format MCP servers (how environment variables need to be specified etc), what the AGENTS/CLAUDE file needs to be called, what plugins/marketplaces are...it's a big mess for anyone trying to have a portable config in their dotfiles that can universally apply to any current and future agent.
It also showed me the difference between expectation and reality...even though these are billion dollar companies, they still haven't figured out how to make lag-free TUIs, non-Electron apps, or even respect XDG_CONFIG. The focus is definitely more on speed and stuffing these tools full of new discoveries and features right now
There's a bit of psychology around models vs. harnesses as well. You can't shake off the feeling that maybe Claude would perform better in its native harness compared to VSCode/OpenCode. Especially because they've got so many hidden skills (like the recently introduced /batch), that seem baked into the binary?
The last thing I can't figure out is computer use. Apparently all the vendors say that their models can use a mouse and keyboard, but outside of the agent-browser skill (which presumably uses playwright), I can't figure out what the special sauce is that the Cloud versions of these Agents are using to exercise programs in a VM. That is another reason why there is a switching cost between vendors.
Loved the themes of this article. It's inspiring me to make my own agentic coding system modeled after the Napoleonic Wars. You'll be able to command an army of agents to battle! My boss will be so happy
I've been wistfully watching people enjoy Framework Laptop from the sidelines for years now. One doubt that has always plagued me: realistically how long can the backwards compatibility for new improvements last? Surely there must be some point where a new processor, or chassis, or airflow improvement must necessitate the complete reconfiguration of the laptop internals or would be just plain unsupported? I don't have background in industrial design or electrical engineering so I've never been able to lay these doubts to rest.
We know how to make laptops now, and the framework is fine. A major development, like Apple-level power efficiency would require less airflow than x64. Don’t think there’s anything major to worry about. May need the 16 for pro-level local LLMs for a while.
Looking at that email, I felt it was a bit of an overreaction. I don't want to delve into whataboutism here but there are many other sloppified things to be mad about.
I was following the first half of the post where he discusses the environmental consequences of generative AI, but I didn't think the "thank you" aspect should be the straw that breaks the camel's back. It seems a bit ego driven.
Well. If you cannot comprehend that the man gets angry to be thanked at the pursuit of simplicity by a creation of billions and billions of dollars sunk into non-recyclable electronics deployed in hundreds of datacenters requiring nuclear power plants and maybe sending shit into LEO… I genuinely feel sorry for you.