My two-year-old son had started saying "turn around" in a sing-song kind of way several months back, and thus my wife and I, both babies of the 80s, had to start singing the song whenever he would do it. It became a fun thing that my son enjoys more than we do. That turned into regularly playing this song (and its covers) in the living room. We just did this again a few nights ago because he loves the song so much and requests it now.
One thing that MCP solves well, that neither CLI apps (like the `gh` CLI for example) nor letting your LLM call arbitrary APIs via CURL does, is setting granular permissions per tool.
Most agent frontends I've used like Claude Code only give you one level deep of CLI commands to authorize, which works fine for allowing commands like `docker build:*`. But for complex CLIs like GitHub, Azure, etc. it just doesn't scale well. It is absurd to grant Claude Code permission to `az vm:*` when that includes everything from `az vm show` to `az vm delete`. Likewise, the argument that says that you should just let your LLM call APIs directly via curl or whatever, does not hold up well when Claude Code just wants raw access to all of `curl:*`.
Meanwhile, MCP tools are (currently, at least in CC) managed at the individual tool level, which is very convenient for managing granular permissions.
Perhaps there could be some "CTCP" (CLI tool context protocol; the CCP acronym does not work well) where CLI apps could expose their available tools to the LLM, and it could then be dynamically loaded and managed at a granular level. But until then, I'm going to keep using MCP.
As a vegetarian of 20 years, I like being able to go to restaurants and have something that is on par with what my friends and family are eating (although I do prefer Impossible to Beyond, by far). Even without friends and family, there's a social (and distinctively American) aspect to being able to have a realistic burger and beer at my local sports bar/grill and not just have a salad or some Sysco frozen black bean burger.
Avalonia is FOSS (MIT licensed). You only need Avalonia XPF if you are migrating legacy stuff.
Moq is largely unnecessary today with LLMs being able to easily generate mock classes. I personally prefer to hand-roll my mocks, but if you prefer the Moq-like approach, there's NSubstitute (3-BSD).
Automapper and MediatR are both libraries I avoided prior to the license change anyways, because I don't like runtime "magic" and not being able to trace dependency calls through my code. But, there is Mapster and Wolverine to fill those needs (both MIT). Wolverine can also replace much of MassTransit.
Telerik stuff - there are many good FOSS alternatives to these UI components; too many to list since it depends on which stack you're using.
PDF is indeed a sore spot. PdfPig is good, but limited in capability. I've started offloading PDF processing to a separate Python container with a simple, stateless Flask API with PyMuPdf.
> we have a problem with opensource being asymmetrically underfunded and if people going commercial is the cost perhaps we've failed.
Completely agree with this, though. My company and myself personally contribute a lot of time back to OSS, and I feel like that is part of the social contract of OSS. To have these libraries rug-pulled feels like a slap in the face as a OSS contributor and maintainer.
I am excited about the potential of EV trucks and a Tesla truck especially. Absolutely I'll consider it once it's reviewed well and it actually ships. After the Model 3 situation I'm not going to put down a deposit or anything, I'll wait and see. But it's certainly a vehicle I'd strongly consider switching to.
Hi, F-350 owner here. My wife and I's other car is a Prius.
In addition to woodworking and desiring a truck bed for that, we tow a camper with which we can boondock (dry/off-grid camp) via solar power. I purchase carbon offset credits for our trips. Not ideal, but better than nothing. I have not modified my truck in any way, especially not to "roll coal", and I report others that I see doing that. I take pride in my truck passing emissions tests and would never attempt to defeat ("delete") those controls. I would never consider blocking a charging station, and in fact we almost bought the Prius Prime plug-in hybrid when it was first released but it wasn't available in our area yet at the time. Otherwise my other car would need those chargers. We also take the Prius as much as possible, and only use the truck when necessary. I enjoy hypermiling in the Prius, too. I hate that diesel trucks like mine create other non-carbon pollution like NOx so I try to only drive it when needed, and would gladly adopt new hardware to reduce those emissions further if it didn't hurt overall efficiency. I also would love for carbon-neutral (or at least carbon-reduced) biodiesel that doesn't come from destroying palm tree forests to be an option until EV trucks are more available. I have other truck-owning friends that are also not obnoxious intentional polluters that hate EVs. Anecdotally at least, my friends and I are the exact market for the Tesla Cybertruck. My gut feeling is that there are more truck owners that think Teslas are cool and want one than those that block charging stations.
I guess my point is, next time you pull up behind a heavy-duty truck, it could be me, a vegetarian EV/hybrid lover driving a carbon-offset, emissions-compliant truck on their way to go off-grid camp via solar power, waiting for the Cybertruck to launch.
RIP Bonnie.