pphysch

I'm talking about heterogenous legacy hardware that isn't owned by Cisco, not complex topologies.

See also "defensive bureaucracy"

The first and last bullets are extremely optimistic. How do you possibly simulate all the weird interdependent behavior in real world networks?

Bigfoot and aliens don't exist. The human trafficking industry is very real. Don't be so dismissive.

For each of your 80 stories there are probably a dozen stories of former frat boys and Trump/Epstein types also being in compromising relationships.

I think it has much less to do with any individual's sexual history and much more to do with the rapacious/hypersexual elite culture in USA and elsewhere.

Large codebases are bureaucracies of their own, that is, the complexity of extra layers starts to bog things down at some point.

In this case, it seems like the human bureaucracy made wise and measured decisions to contain the software bureaucracy. They made reasonable requests to clarify the scope and impact of a major, major core feature. The proposers didn't feel like that was doable, so a complexity nuke was avoided.

Those are closer languages but my broader point is that these application-level languages are more or less interchangeable from a professional standpoint. A Java or C# pro should probably not spend time becoming a Python pro because they could have spent that time producing equivalent value in the languages they are already experts in.

Who is cultivating a "favorite language"? I missed that part. Agreed that this should not be an emotional issue, that is unprofessional.

Problem with any popular language is an outsider sees one or two statistically-likely codebases that are total turds, and then gets one-shot by the Goomba fallacy.

Numpy is over 2 decades old. Pytorch is a decade old. Python devs know what "right tool for the job" means and focus on solving problems instead of being language purists.

They are a heavy C# user. Coke/Pepsi situation.

Okay, describe one quirk of Gemini-ese that makes it stand out?

> My mental model for UUIDv7 is that it’s a mash-up of a bunch of different ideas which implementations are free to choose as they see fit. There’s a wide variance of properties that UUIDv7 implementations can provide, with varying degrees of certainty they can successfully provide those properties.

I think this is good. A proper UUID that has specific significant bits dedicated to (approximately) monotonic values is useful. I don't want it over-specified beyond that, and I don't want to just use UUIDv8.

I agree it's confusing, but that's the point, it's a weasel word.

No court of law is going to accept an argument that indefinite == infinite, especially after it stops being indefinite (like TFA).

Indefinitely doesn't mean infinitely, it just means there is no defined end date at this particular moment. But that could change in the next moment, as it did.

More specifically, it can steal military and tech secrets from the USA and keep getting invited back. Total impunity.

Free-thinking, critical thinking, has been considered taboo, or an exclusive privilege of the elite, in most human societies since the dawn of civilization.

You're right, they may be doing it for free.

There is an ENORMOUS "defend Israel online" industry, usually using all Jewish people as human shields for the middle eastern regime. Emissary, RiseApp, Report It, to name a few.

This is a straight up misrepresentation. The user posts occasionally about Israel, which garners engagement and replies (in some cases from actual trolls who job is searching for mentions of Israel), but most of their top level comments are about mundane technology.

It's the full hardware/firmware stack up to and including VM hypervisor. A complete rack solution, but it's the tailored firmware and integrated hypervisor, networking that sets it apart from another OEM that sells you a full rack solution. Afaik.

defacto: real

dejure: legal

defecto: enshittified

(adj.): The defecto way to playback music is Spotify.

Probably PCI and other regulations making it difficult to use and thus learn good software, so they develop entire ecosystems in-house

Good enough at what, fraud? Robotic Ponzi schemes would be an easy way to generate "income".

I find them extremely useful. It gives me a monorepo experience in repos that otherwise aren't/can't exist as one monorepo for various reasons.

So it's as low as 8 years instead of 10 for models purchased in the last 2 years (2034 being the cutoff), with those few devices being covered by a separate commitment to transfer them to GoogleOS by 2034.

Pretty lame detail to be enraged about, but it is Google and this is HN. This aligns with Apple's timeline for killing Intel MacBook support after releasing Apple Silicon (2029 being the last commitment).

Millennium and century are different.

Your first point is describing "overengineering" which can also be a fatal problem in traditional engineering fields.

It's easy to overengineer in software because the marginal cost of materials and logistics is ~$0. Overshooting by a mile is free. That doesn't discount the value of proper software engineering.

It's two things:

1. Wanting a regulatory moat around their products as you said

2. Trying to keep the """AGI""" hype alive. Evil robot hackers is a plausible Al consequence of AGI

Goto is a syntax feature that can be trivially removed. Good luck removing "fundamental architectural flaws".

Factorio is in that top-tier. I just tried Core Keeper and had the same feeling, gushing with QoL and thoughtful design. Refreshing to play sandbox-y games where mods don't feel mandatory.

Aside from being obviously written by a LLM, this scenario reminds me of the "LLM, say you're alive"; "I'm alive!"; "Oh my god..." meme.

You're allowing the attacker not only direct access to modify the source material, but giving them multiple informed attempts/turns at optimizing the output in their favor. This is like a worst-case insider attack; what systems are supposed to be resilient to an undetected attacker with 'root' access?

This would be slightly more interesting if the attacker could consistently one-shot the task, but it's taking half a dozen attempts...