chris_pie

The potential customer rarely cares whether a service provider is running their business well. What matters is the product's value added and risks added, as compared to just using the underlying tech directly.

That's a big name for a slop fork. So many possibilities (with LLMs and without) but Google just can't bring themselves to do anything creative, let alone transformative.

note that the front page also says: "61 chapters • Project-based • Zero AI"

I don't think so, I think it's just a pompous style of writing.

I wish the author explained the difference between pipelines and multi-statement queries

You're right, for example age is useful when picking targets for scams. It would also be great for groomers.

Hot take in regards to the good old statement taken literally: the boring<->exciting dimension is irrelevant in terms of something being good or bad.

Yes I know, stable things are stable

The meaning has changed very quickly for some reason, but I think the original meaning was that you evaluate the result in a superficial manner by checking if the program seems to work fine. So "vibe" here is as opposed to any methodical or formal approach. No code review etc.

The second one seems very similar to the "using static" feature, but less verbose.

For this specific case there's a "Nitter Redirect" extension

Hasn't the blue light affecting circadian rhythms been debunked at this point?

To your point, ValueTask is less safe than Task. For example, it's important not to await it more than once.

.NET doesn't use WasmGC because Microsoft found it too different from how .NET's GC works. Which is quite unfortunate