aloha2436

> You cannot even tell if a car is a Ferrari these days, unless you can see the badge.

This seems like excessive hyperbole, I can reliably tell apart every marque on the road in my country by lights and grille shape.

Some of these warts are problems with security, or data integrity, or resource usage, etc.

It's a difference of opinion more than it is a conflation with something else.

My _personal_ preference is that software does the "correct" thing by default even if it breaks my build or my tests or even running software; I would rather it break visibly than work nefariously.

It doesn't have to be a direct stand-in. It's mentioned in the article that people suspect McCarthy of reveling in the violence in his novels. Whether he does or does not he would certainly have been aware of that perception. Judge Holden as a character embodies many distasteful qualities of mankind, it would make sense that the qualities he embodies the most distinctly are the ones McCarthy sees in himself.

> and people still buy them

You skip over a very important step here, where people keep buying the MBSes because the ratings agencies are knowingly rating the securities incorrectly. If that didn't happen, the market would be too small to blow up in the way that it did, all of the safe money can't invest if the MBSes aren't AAA.

It's not that no-one noticed in time, it's that the people responsible for noticing were paid to pretend they hadn't. That is the corrupt part.

> MIE will make sure we can never take back our freedom.

Is the implication here that making phones more secure is... bad? Because it makes jailbreaks harder to develop?

Why would the product have to be available new for the project to be worth it? There are still many M1 chips out there, and this helps prolong the usefulness of those chips.

Maybe I'm just lucky to work at a place with good tools, but in my experience Temporal isn't super heavyweight to use compared to building your own even-very-simple scheduler.

And it's worth it because now you have Temporal, which is the bees knees as far as I'm concerned. I will gladly sing praises of any tool that saves me getting paged, and Temporal has that in spades.

> remains the same whether they pull source or binaries.

I don't think that's exactly true, it's definitely _easier_ to sneak something into a binary without people noticing than it is to sneak it into rust source, but there hasn't been an underhanded rust competition for a while so I guess it's hard to be objective about that.

Those are alternatives for youtube _consumers_ but none of those are replacements for _producers_ on youtube.

> Domain discovery is so underrated. LLMs remove so much friction that makes everything so incredibly accessible.

And, unfortunately, a lot of friction from not having access to information in the first place. I've read a bunch of docs from people talking to Glean in order to explore a new topic; if it's a topic I'm actually very familiar with then four out of five times it is somewhere from misleading to catastrophically wrong. Any internal terminology that doesn't match the common usage outside of our organization poisons the whole session and it will make up things to join the meanings together, and the prompter is none the wiser.

I trust AI only as a gap filler in domains that I'm already an expert in or where there's little internal context, anything else is intellectual suicide.

> Now reuse the same connection to request the nested data, which can all have more nested links in them, and so on.

This still involves multiple round-trips though. The approach laid out in the article lets you request exactly the data you need up-front and the server streams it in as it becomes available, e.g. cached data first, then data from the DB, then data from other services, etc.

The article doesn't advocate sending it progressively to make it smaller on the wire. The motivating example is one where some of the data (e.g. posts) is available before the rest of the data in the response (e.g. comments). Rather than:

- Sending a request for posts, then a request for comments, resulting in multiple round trips (a.k.a. a "waterfall"), or,

- Sending a request for posts and comments, but having to wait until the commends have loaded to get the posts,

...you can instead get posts and comments available as soon as they're ready, by progressively loading information. The message, though, is that this is something a full-stack web framework should handle for you, hence the revelation at the end of the article about it being a lesson in the motivation behind React's Server Components.

> Why make source available at all if you are just going to release proprietary software?

Because there's years between one decision and the other, and in that time it turned out that because the software was open source they were structurally disadvantaged versus large cloud providers in being able to make money from it.

It seems disingenuous to suggest that the open sourcing was in bad faith given it happened years and paradigms apart from the closed sourcing, even though I don't agree with the decision either.

Safari is too valuable of a platform for web developers to ignore, but otherwise yes it's the only real exception to the Chrome monopoly and still certainly much smaller in terms of absolute users.

It's barely one step removed from just being burned in an incinerator, it's maybe recycling in a very strict sense but it's definitely misleading to say that.

Easy access to the videos without having to download them from Google (and without Google trying to stop you from scraping them, which they will) is an enormous advantage. There's way, way too much on Youtube for to index and use over the internet, and especially not at full resolution.

I'm on a four year old mid-tier laptop and opening VS Code takes maybe five seconds. Opening IDEA takes five seconds. Opening twitter on an empty cache takes perhaps four seconds and I believe I am a long way from their servers.

On my work machine slack takes five seconds, IDEA is pretty close to instant, the corporate VPN starts nearly instantly (although the Okta process seems unnecessarily slow I'll admit), and most of the sites I use day-to-day (after Okta) are essentially instant to load.

I would say that your experiences are not universal, although snappiness was the reason I moved to apple silicon macs in the first place. Perhaps Intel is to blame.

"I don't like any of the rat-bastards." "I don't care." "I think it's funnier to draw a dick. (And I don't care.)" "I trust other people to make the right choice." "I refuse to participate in this bourgeois sham election." ...are all reasons I've heard, even if I don't actually understand any of them.

The implication is that the users that are being constantly presented with CAPTCHAs are experiencing that because they are unwittingly proxying scrapers through their devices via malicious apps they've installed.

Worth noting that, neat and tidy migration path aside, context receivers are deprecated[1].

[1] https://blog.jetbrains.com/kotlin/2025/04/update-on-context-...

I'm reliably informed they do it for free.

Vibe coding is not using a chat interface to explore an unfamiliar domain like GP describes, it's letting an agent tool like Cursor or Goose do most of the work semi-independently.

> Bad actors acting in bad faith, causing damage? Totally fine.

Who in this thread is saying this is totally fine?

> vista based server products are terrible.

The first generation of tabletised 8/Metro interfaces made me audibly groan every time I had to RDP into machines running 2012.

Not to the same degree that Python does (then again no other general-purpose language does!), but it does have the start of one and it's fairly cohesive.

https://github.com/elixir-nx

> does that mean they have a ton of users following an unreasonable number of people

They do, there are groups of users on bluesky who follow inordinate numbers of other accounts to try and get follows back.

I believe the issue with CNTs and asbestos is that once they're in your lungs, your body won't be able to break it down. This is literally made of flour.

I've been hearing about this for a while and many of the entities holding the bag are publicly traded, given there's plenty of mercenary firms out there able and willing to make a buck off of a catastrophe is there any reason to believe this isn't already priced in?

> an application shouldn't be able to do this kind of damage to an operating system

Antivirus software by its nature probably needs the kind of access that would let it bluescreen your computer.

I would assume the Fed thinks it's not actually an ideal time to raise rates. Real growth is in the dirt, they have a dual mandate, and the funds rate is an indiscriminate weapon. Given the circumstances the ideal intervention would be fiscal policy aimed at reducing the supply of money in less CoL-sensitive areas but the people in charge of _that_ are uh, somewhat more susceptible to political pressure.