So creating unsafe software is the new norm?

I’d bet good money that at leasy 2/3 of all software ever made, the decision makers couldn’t care less about security beyond "let’s get that checkbox to show we care in case we get sued". Higher velocity >> tech debt and bugginess unless you work at nasa or you're writing software for a defibrillator, especially in the current "nothing matters more than next quarter results".

I have worked over two decades creating government software, and I can say that this is not new.

Security (and accessibility) are reluctant minimum effort check boxes at best. However, my experience is focused on court management software, so maybe these aspects are taken more seriously in other areas of government software.

Yes pretty much. See the Windows 11 security vulnerability chaos going on.

> the new norm

More like the same as it always has been.

Always has been.

Is the problem solved that training on AI generated data makes the model worse?

If not then updates to the current models will become harder and harder

.NET versions are faster outdated then .Net Framework 4.8

Point? I’m SRE on .Net project, we have been through 6-8-10 and its cost us about 2ish hours of work each time. As long as you don’t get crazy, .Net upgrades is just matter of new SDK and runtime and away you go.

You're talking about .net for server applications right? The discussion above is for client apps being distributed for windows endusers.

Just ship a self contained build?

This was a sidecar application distributed by literally millions of installs per day - so having a 25MB "self contained" build was out of the question - we were targeting KB-sized distributables not 10's of MB.

We have a small MAUI part of the application, it's not massive but it's working fine with .Net Upgrades.

A .net framework 4.8 app has zero hours of work.

Why is it ok that you have to invest 2 times number of apps hours just because MS has such a short life cycle for its .NET versions.

.Net Framework 4.8 has a longer life cycle as the current .NET version

When I first worked with dot NET I was confused with the naming and version numbers.

It does, but current versions can be shipped with the application.

Thus this should be less of a problem.

Are the early tricks for LLMs still useful today?

I mean the high level stuff is still there right? Be straightforward, leave the right kind of pointers into the thing, say the right kind of things.

But... I guess nowadays you can be vague and it'll get the gist of it.

Maybe we should start with those who made such copyright claims a possibility in the first place

They're long, long dead.

There are still people who help extending it

If copyright can be used to prevent the archiving of ToS documents, a copyright duration of 3 years would be sufficient. Not all objections to copyright boil down to "the Mickey Mouse Protection Act should never have passed!".

Remember, it’s only censorship if they block what I want to say, if the block what I don’t like it’s for the greater good

I think because B5 had already a story to tell from the beginning while DS9 was a setting at first.

I doubt that the changelings and the dominion where planned from the beginning.

There's an interview somewhere indicating they didn't come up with the Dominion until the second season, explicitly saying they put the first reference to it in a Ferengi episode to mislead and surprise viewers.

Strange that security still isn’t a first class feature when something new is developed.

I'm slowly beginning to doubt that people can learn from the mistakes of others. Why do we keep making the same mistakes over and over again?

Fwiw the sensibilities of the --yolo AI-maximizing "I vibe coded a Hospital Information System this afternoon" crowd isn't really representative for the greater dev community I think

I'm thinking more about developers of tools like OpenClaw or MCP.

>basically required

doesn't sound like a hard requirement