Single AZ S3 has other benefits. The point isn't the price, it's that it's _highly performant_ since you can keep all of your reads in the same AZ

Isn't openrouter the exact opposite of caring about security and privacy?

I guess you can choose your provider still? But isn't the point that the lowest bidder is doing inference?

You can set privacy requirements and define an allow list. To me the main value prop is that I get one bill for all models and can quickly try new models without signing up anywhere or changing my code. Oh! Also you can pass an array of models and if the first provider is down it automatically falls through to the next provider. More useful than it should be...

That's still ultimately privacy by contract (where you have to trust the inference providers to uphold their end of the deal), rather than privacy by design.

I always setup guard rails so that only zdr providers are used.

> suing a torrent aggregator

Which has also been done :|

Right, which is why it is a charitable comparison of the lawsuit, showing how it may be successful.

Bedrock is an option. Multiple platforms with solid data sovereignty.

If you don't want them slurping your data, you're gonna have to pay more.

Same as it ever was.

The classic slashdot comment!

Simple solution here, use a high quality OS.

Windows has never felt more archaic than now. I can't imagine trying to do work on a Windows machine in the age of LLMs.

If there is anything that LLMs are rock solid at these days, it's unix terminal usage.

They're also great at powershell, you just need to tell it to do so. sh is neat but it's 55 years old, there are newer and better shell environment concepts out there and the robots can handle them well too, try it some time!

PowerShell unfortunately just isn't that first-class, even on Windows. You'll inevitably discover, if you do this, that certain things simply can't be automated via PowerShell, that some PowerShell modules wrap or lag behind older Windows CLI tools, that various things you want to do still require manual registry hacks, etc.

Try starting from a blank slate Windows machine and making a commitment to only changing settings via PowerShell, and ideally only declaring them using DSC. You'll soon discover settings where the best you can do is snapshot the registry, change a setting in the GUI, snapshot the registry again, then take a diff so you can write the registry change into your PowerShell automation. If you're on a corporate machine, you'll also likely find many corners of PowerShell that you need closed off to you, anyway.

At the end of the day, Windows is not friendly to automation because it's not CLI-first (not culturally and not technically).

Your argument is directed at Windows, not PowerShell. The shell is just a shell, if a certain thing you're looking to configure doesn't have an easy cmdlet, that doesn't mean powershell is bad, just that MS didn't give you the easy button. Similar to many unix tools, some of what you need to interact with has a dedicated CLI, other things have you poking at the configuration database directly (ini or yaml or whatever for unix, registry for windows).

If you don't like the Windows style of configuration, run powershell on linux - it's awesome there too!

I'm not sure why reading and writing the registry is considered a bad interface for programmatic system administration.

I realize text files can be processed by utilities for working with text files. And text files can be read by humans without any tools, and in that sense are rather universal.

I wonder what I'm missing.

I'd go so far as to think an OS that had a database at its core, or perhaps a persistent lisp would be even more programmable and legible.

Maybe better tools for dealing with structured data would help this?

How do you work on Windows in the age of LLMs?

That’s easy: you activate WSL and then ask the LLM how to get networking and stuff working since they changed it with WSL2. You need a config file flag to setup network mirroring now.

Ironically, I feel like LLMs have really unlocked Windows work since they all know how to use Powershell and all the weird Windows commands/hacks that you otherwise either wouldn't even know about, or would have to Google every time.

I used to hate working in Windows, but now it feels roughly comparable to Mac (though at the risk of inciting an OS war, I do feel like Linux still beats both out...)

I totally agree. Powershell is a bit cryptic but it's really powerful especially on Windows. LLMs have smoothed out the learning curve.

It doesn't fit the narrative that they need to adhere to. I'm a skeptic through and through, but yeah... This article reads like propaganda.

I got here and... I agreed with everything up to this point.

The author makes a good point. If you don't know what you're doing, AI accelerates that. No question.

But they put a whopping... ten bucks into using DeepSeek and weren't impressed with the initial results.

I know they try to cover this with "you just aren't prompting correctly!" but if, in 2026, you aren't able to have an LLM generate decent quality code... IDK what to tell you. Good luck I guess?

> in 2026, you aren't able to have an LLM generate decent quality code

Nobody is. The only difference is that some of us are willing to say the emperor has no clothes.

The workflow isnt a single prompt then you have working code from the LLM, its 30 prompts of discussion and then reading each proposed edit and having tangent discussions until you're somewhat ok with it. Then reviewing the changeset as a whole and refactoring a few times

I am.

> but if, in 2026, you aren't able to have an LLM generate decent quality code... IDK what to tell you.

I think the author's point still stands. At some point you need to determine whether the output is of decent quality. A lot of people don't have the ability and experience to do that.

What part of this was lying about what she had said?

I think the entire thing is absurd but libel usually requires falsehoods to be published. Slander is similar. It isn't just "damaged reputation"

>What part of this was lying about what she had said?

Swatting is illegal in some states (not enough, but some). I'd liken an escalation to authorities by a corporate entity as such. The lie is about the projected intent to harm.