Day 1: Google buys Wikipedia

Day 100: Wikipedia is shut down

Google would probably asset strip it for all the info it could sell on or import into AI models.

Google knol

That’s not my experience. I've had an OLED TV going on 7 years now and it still looks better than any of my LCD screens.

My PC monitors are my only remaining LCD screens largely due to the text fringing issues mentioned in this article and bezel size.

I feel similarly. Hacker News is the nicotine patch of social media.

Given the attitude of both you and the GP, maybe this site isn't for you then?

Yeah, I’m wondering if it could be a Tesla strategy of starting with the something imperfect but niche.

If the product is on the market and you can buy one and walk out the door, I feel like claims can easily be validated or invalidated with a tear down.

Not even a teardown. Just a few charge + discharge cycles, measuring the energy.

This feels strange and biased, and I’m not sure it belongs on HN.

The only context in which DHS claims Real ID is “unreliable” appears to be during mass detentions. That framing reads less like a genuine critique of Real ID and more like a convenient justification: “Sorry, we detained you because you look Mexican. Your Real ID isn’t sufficient.”

The author then shifts blame onto Real ID itself, rather than on DHS agents who are choosing to ignore it.

I’ve heard (but don’t have an inside source) that Meta’s Horizon was built on Unity and then ported to a custom engine implementation.

I wrote the Circuits programming system for Rec Room, and we took a similar approach: keeping the core logic free of Unity dependencies so it could run and be tested on CoreCLR.

The results were similar as well with significantly better performance outside of Unity. There are also secondary benefits. Unity’s API surface is huge, and it’s easy for code to accidentally entangle itself with engine details in ways that confuse or constrain other developers.

By isolating the core in a separate DLL, we only expose Unity concepts where they’re actually needed, and we enforce that boundary with tests. That logic constraint ended up being just as valuable as the performance gain

Agreed, my company has some helper hooks they want folks to use which break certain workflows.

We’re a game studio with less technical staff using git (art and design) so we use hooks to break some commands that folks usually mess up.

Surprisingly most developers don’t know git well either and this saves them some pain too.

The few power users who know what they’re doing just disable these hooks.

I agree with this argument but it goes both ways. We run on monkey hardware… and our leaders run on monkey hardware.

Those unethical leaders are monkeys like the rest of us. Pointless status hoarding at the expense of populations is part of it.

It’s monkeys all the way down.

The point of assigning blame here isn't so much a moral exercise as it is to decide what went wrong, how to deal with it, and how to prevent the same failure modes in the future.

That’s what I’m talking about too. Understanding that we’re all monkeys is an important piece of the puzzle if you want to deal with the problem.

There’s folks who perform like juniors but have just been in the business long enough to be promoted.

Title only loosely tracks skill level and with AI, that may become even more true.