barelysapient

Yes.

Poor judgement, open ai

Another reason to avoid windows.

That remains to be seen. Individuals absolutely can be held to account. Corporations are not pass to behave illegally.

My version of a similar tool; but written in Go with a compile time guarantee.

https://github.com/swetjen/daggo

Microsoft isn’t known for great judgement.

I hate how this sounds...but this reads to me "we lack the confidence in our code security so we're closing the source code to conceal vulnerabilities which may exist."

But we're not talking about speed cameras or a private entity with exclusive contract with the police to provide traffic enforcement.

We're talking about Flock. A company offering surveillance as a service. Per their website:

>Trusted by over 12,000 public safety customers including cities, towns, counties, and business partners.

If Flock's argument holds then most of the CCPA be circumvented this same way. All it takes is a few entities and clever contract language.

If that's a valid excuse than the CCPA isn't worth the paper its written on.

Unlike the author, I run SeaweedFS without issue locally and with acceptable transfer speeds.

Is it just me or does this describe most of Microsoft software at the moment? I tried to sign into my personal microsoft account to setup an oauth flow and I was greated by an infinity repeating error dialog about some internal service that had failed.

At work, I use outlook. The number of times I've gotten caught in an auth loop where I enter again and again my creds + tfa only for the screen to flicker and start all over again.

Complete garbage.

Cloudflare tunnels

Heavily regulated industry with a lengthy change control process for this sort of thing.

Personally, I love all of the new Go stuff and I'm using the current version on my personal projects.

Different users. Many people care about privacy and aren’t using Meta products. And many businesses care about it too and have information policies to protect their IP.

This just got me. Datadog decided that they only support the current and last major versions of Go. So, 1.26 and 1.25. But in my cause we're still on 1.24.13 which was released by the Go team less than two months ago.

Datadog won't be getting a renewal from us.

I'd prefer we instead all use Non-violent Communication. No need for permission. The world would be more beautiful place if we all had giraffe ears.

I had the same experience looking at thinkpads a few years ago. I finally just gave up and bought a macbook.

Wow. We need this so bad.

Or send your own email recapping the conversation.

Love SQLC, this looks good too. Syntax is almost identical.

This assumes companies would have refunded consumers.

Obviously if a company did this, refunding consumers was the last thing on their mind.

The more things change the more they stay the same.

Completely agree with this take.

I've started what I'm calling an agent first framework written in Go.

Its just too easy to get great outputs with Go and Codex.

https://github.com/swetjen/virtuous

The key is blending human observability with agent ergonomics.

Go got a ton right. Especially for being almost 20 years old. But errors is one thing that needs a v2. I love Zig's enumerable errors and deferErr function.

After spending way too much time debugging runtime problems with python based workflow tools, I’ve been implementing something very similar: DagGo.

DagGo is a type based workflow tool with observably written in Go. Jobs are compile time safe. I’m planning to bring it to feature parity with tools like Dagster over the next few months.

https://github.com/swetjen/daggo

I completely agree. I'd vote that person regardless of party.

Apologies, I meant federally.

Since D's control California, no need to work with R's there.

I also think they could get creative. Eg., without an attestation validated by <agency> products can't be sold.

For example, this is already done with controlled substances and food.

I'd be curious to know if this is really the case.

States have a lot of power to regulate commerce, interstate commerce and the products their citizens have access too.

If indeed they can't, then perhaps its one subject dems and r's could get together on. Instead of blanket tarrifs, tarriffs on products made with slave labor or without strong consideration for environment impact.

Should California be treated differently than the rest of the world?

In addition to banning these manufacturing processes in California, we should ban the products manufactured with these processes from California. This would require products to "green up" in order to access California's vast market.

By allowing dirty products manufactured elsewhere, we've simply moved the problem and its harms out of our line of sight. And frequently to a place where the people are poor, non-white and under represented.

I feel for this guys path. Rust has a place but not for the type of applications he’s writing.

Personally would look at Go over Node as it gets a lot of the systems language patterns without the overhead.