cirrus3

Lost me when it was framed as a binary decision.

During the attack window, malicious firmware versions were distributed to users who updated their devices. This compromised firmware contained vulnerabilities that allowed unauthorized access to device functions. We have confirmed that approximately 74,00 devices received the affected firmware before our security team isolated the compromised systems.

This isn't the first time an article is also marketing. Besides, what is wrong with marketing something via a use case article? This is a fairly tame example of it and I found it an interesting and useful read, knowing full well it was also marketing.

> how much does it decrease the fuel economy of the towing plane

Probably a lot, but I'd assume it is by less than the fuel that 1-2x more planes would use, otherwise there wouldn't be a point to doing this.

I did a lot of testing with Krea. The results were certainly very different than flux-dev, less "ai-like" in some ways and the details were way better, but very soft and bit washed out and more ai-like in other ways.

I did a 50% mix of flux-dev-krea and flux-dev and it is my new favorite base model.

Firefox on a mac, totally hijacked my back button.

Anything the requires me to use a different IDE is a non-starter for me.

I can imagine it is a lot easier to develop these things as a custom version of VSCode instead of plugins/extensions for a handful of the popular existing IDEs, but is that really a good long term plan? Is the future going to be littered with a bunch of one-off custom IDEs? Does anyone want that future?

> Hot take: if your job can be partially or wholly eliminated by AI, that’s a GOOD THING. If your job has patterns that predictable or labor that routine, AI automation is a GOOD THING.

The article never says why this is good. It just states it then moves on.

> As a whole, I’m sure it’ll give birth to entirely new systems we haven’t even conceived of yet and, one can hope, free up that time and energy towards more meaningful or creative pursuits.

The people's who job it takes probably don't give af about the patterns of their job, or creative pursuits they can do while unemployed. They are probably just trying to pay their bills and feed their kids.

I think they meant "stable" as in the demand for the product isn't easily going away anytime soon.

> one of the worst misconceptions in product design is that a microwave needs to have a button for every thing you could possibly cook

"Worst" is a stretch. Not to mention these often actually do more than just power and time. For example detecting humidity and/or varying power over time.

> You can just have a time (and power) button. People will figure out how to cook stuff.

You could, but people don't always want to figure it out, especially when they are hungry.

This would have been a better article if the takeaway wasn't basically "people are smart, make them learn the underlying structure".

I think good design is recognizing when and how to either expose the structure or paper over it, all while making it pleasant to interact with for all users at either end of the spectrum of willingness to learn it.

For a bike, it pays off to learn. For other things maybe not so much. Combining these two very different cases and then making a blanket statement that "Good designs expose systematic structure" doesn't land well.

I think the microwave ones are useful even if they are just presets for time and power.

With a new bike, you can get a feel very quickly for what "5th gear" works well for and experiment with it and get immediate feedback and try other options pretty much no downside.

With a microwave, I don't necessarily want that level fine grain control. I probably just want to eat and not ruin my food and I certainly don't want to spend time running experiments. Having a preset at least gets you in the ballpark.

I've tried to watch Louis many times.. can't do it. He is just so whiny and annoying, it is really off putting to what might be otherwise interesting topics.