RIP Bonnie.

Does my laptop have to pass my age verification to a Docker container?

Am I at risk of government censorship (or worse) if I create a hobby smart home app that boots bare metal on a Raspberry Pi?

Or even the shell apps that I run daily. Does curl (which can access any web url) have to validate my age? What about AI models/ollama?

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.

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.

This is, IMO, a bad thing, and Microsoft needs to break this chain at some point, at least for ASP.NET. But, it is still technically supported.

I have a M5 that I got through the original Kickstarter campaign. I love this printer. I use it casually, but I rarely have a failed print that I can't attribute to i.e. poorly chosen supports. Almost all of the parts on it are still original and working well, apart from the hot end that I've had to replace a few times due to accidentally breaking the screws when changing nozzles. (It was a poor design of the original hot end where the very thin, long screws did not have the shear strength in aluminum to not break when accidentally torquing the nozzle head. This was fixed with the all-metal hot end, which is not ideal for all filaments.)

Despite my issue with the hot end (which I believe could easily be fixed with an updated design), and the nearly useless "AI" feature, I feel like this printer was a great value at the time. It's very well built, looks great, and very reliable. I really enjoy every opportunity I have to use it and do not regret my purchase decision at all.

I'm saddened that they seem to be pulling out of the market, even though it makes sense compared to the competition. It really seemed like they had a promising start. If this is truly the end, then RIP with positive sentiments from me.

I've helped create apps that support millions to hundreds of millions of revenue on Azure SQL Databases that cost at most a few hundred dollars per month. And you can get started with a S0 database for $15/mo which is absolutely suitable for production use for simple apps.

Unfortunately, I think Microsoft realized how good of a value the DTU-based model was, and has started pushing everyone to the vCore model, which dramatically increases the barrier to entry for Azure SQL Database, making PostgreSQL a much more attractive option. If Microsoft ever kills off the DTU purchasing model of Azure SQL Database, I likely won't be recommending or choosing Azure SQL Database at all going forward. It'll 100% be PostgreSQL.

If that is true, it sounds like having a plan to scale to millions of logical qubits on a chip is even more impressive.

> Cadmium is bad news. Lead and mercury get all the press, but cadmium is just as foul, even if far fewer people encounter it. Never in my career have I had any occasion to use any, and I like it that way.

It seems clear that he doesn’t want to work with cadmium, regardless of the compound.

I see you plan on making money by charging for the hosted service. Given that, and given recent history in the industry with companies starting out with this model only to rug-pull it from users later and move to a more restrictive license, can you publicly commit to keeping the code MIT/AGPLv3-licensed into the future?

It should be noted that $419/year is $35/mo, which is still $10/mo cheaper than the Visual Studio 2022 Professional monthly subscription at $45/mo. $21/mo at 3+ years is less than half.

This is a gratuitously negative comment that is unfair and uses an incorrect metaphor. Rent-seeking is trying to charge for something without providing any new value, usually from something already established as free. I don't believe Rider was ever available for free, but even if it was, they certainly have improved it with loads of new value since then. You're welcome to your opinion (that I don't share) that their IDEs are not worth the cost, but you're also free to not buy them. That's not rent-seeking, it's the free market.

I personally am a big fan of Rider and the JetBrains Toolbox suite, and I get several times more value out of my subscription than it costs. YMMV.

... or at least allow API access for third-party/OSS apps to do this without needing full screen recording permissions!

Take a look at CAR T-cell therapy, used for Leukemia and blood cancers (and mentioned in this article). The first trials were happening around 2011, and now there are several FDA-approved therapies using this breakthrough. LLS notes [1]: "In some studies, up to 90 percent of children and adults with B-ALL whose disease had either relapsed multiple times, or failed to respond to standard therapies, achieved remission after receiving CAR T-cell therapy." These are people that would have died 10+ years ago.

My younger brother passed away from ALL in 2012 after a clinical trial for one of these treatments didn't work. His participation in the trial, even with the unsuccessful result, helped further the research that is now saving lives that weren't saved before.

CAR T-cell therapy is perhaps the most powerful breakthrough against blood cancer in history. Now, it might be able to tackle other cancers as well. We're making progress. Of course we all want it to go faster, but it's happening.

1: https://www.lls.org/treatment/types-treatment/immunotherapy/...