frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

OpenCiv3: Open-source, cross-platform reimagining of Civilization III

https://openciv3.org/
499•klaussilveira•8h ago•138 comments

The Waymo World Model

https://waymo.com/blog/2026/02/the-waymo-world-model-a-new-frontier-for-autonomous-driving-simula...
836•xnx•13h ago•503 comments

How we made geo joins 400× faster with H3 indexes

https://floedb.ai/blog/how-we-made-geo-joins-400-faster-with-h3-indexes
53•matheusalmeida•1d ago•10 comments

A century of hair samples proves leaded gas ban worked

https://arstechnica.com/science/2026/02/a-century-of-hair-samples-proves-leaded-gas-ban-worked/
109•jnord•4d ago•18 comments

Monty: A minimal, secure Python interpreter written in Rust for use by AI

https://github.com/pydantic/monty
163•dmpetrov•8h ago•76 comments

Show HN: Look Ma, No Linux: Shell, App Installer, Vi, Cc on ESP32-S3 / BreezyBox

https://github.com/valdanylchuk/breezydemo
166•isitcontent•8h ago•18 comments

Dark Alley Mathematics

https://blog.szczepan.org/blog/three-points/
59•quibono•4d ago•10 comments

Show HN: I spent 4 years building a UI design tool with only the features I use

https://vecti.com
279•vecti•10h ago•127 comments

Microsoft open-sources LiteBox, a security-focused library OS

https://github.com/microsoft/litebox
338•aktau•14h ago•163 comments

Show HN: If you lose your memory, how to regain access to your computer?

https://eljojo.github.io/rememory/
222•eljojo•11h ago•139 comments

Sheldon Brown's Bicycle Technical Info

https://www.sheldonbrown.com/
332•ostacke•14h ago•89 comments

Hackers (1995) Animated Experience

https://hackers-1995.vercel.app/
420•todsacerdoti•16h ago•221 comments

Show HN: ARM64 Android Dev Kit

https://github.com/denuoweb/ARM64-ADK
11•denuoweb•1d ago•0 comments

PC Floppy Copy Protection: Vault Prolok

https://martypc.blogspot.com/2024/09/pc-floppy-copy-protection-vault-prolok.html
34•kmm•4d ago•2 comments

An Update on Heroku

https://www.heroku.com/blog/an-update-on-heroku/
360•lstoll•14h ago•246 comments

Female Asian Elephant Calf Born at the Smithsonian National Zoo

https://www.si.edu/newsdesk/releases/female-asian-elephant-calf-born-smithsonians-national-zoo-an...
15•gmays•3h ago•2 comments

Delimited Continuations vs. Lwt for Threads

https://mirageos.org/blog/delimcc-vs-lwt
9•romes•4d ago•1 comments

Show HN: R3forth, a ColorForth-inspired language with a tiny VM

https://github.com/phreda4/r3
57•phreda4•7h ago•9 comments

How to effectively write quality code with AI

https://heidenstedt.org/posts/2026/how-to-effectively-write-quality-code-with-ai/
209•i5heu•11h ago•155 comments

Introducing the Developer Knowledge API and MCP Server

https://developers.googleblog.com/introducing-the-developer-knowledge-api-and-mcp-server/
33•gfortaine•6h ago•8 comments

I spent 5 years in DevOps – Solutions engineering gave me what I was missing

https://infisical.com/blog/devops-to-solutions-engineering
121•vmatsiiako•13h ago•50 comments

Learning from context is harder than we thought

https://hy.tencent.com/research/100025?langVersion=en
159•limoce•3d ago•80 comments

Understanding Neural Network, Visually

https://visualrambling.space/neural-network/
257•surprisetalk•3d ago•33 comments

I now assume that all ads on Apple news are scams

https://kirkville.com/i-now-assume-that-all-ads-on-apple-news-are-scams/
1013•cdrnsf•17h ago•422 comments

FORTH? Really!?

https://rescrv.net/w/2026/02/06/associative
51•rescrv•16h ago•17 comments

I'm going to cure my girlfriend's brain tumor

https://andrewjrod.substack.com/p/im-going-to-cure-my-girlfriends-brain
92•ray__•5h ago•43 comments

Evaluating and mitigating the growing risk of LLM-discovered 0-days

https://red.anthropic.com/2026/zero-days/
44•lebovic•1d ago•12 comments

WebView performance significantly slower than PWA

https://issues.chromium.org/issues/40817676
10•denysonique•4h ago•0 comments

How virtual textures work

https://www.shlom.dev/articles/how-virtual-textures-really-work/
35•betamark•15h ago•29 comments

Show HN: Smooth CLI – Token-efficient browser for AI agents

https://docs.smooth.sh/cli/overview
81•antves•1d ago•59 comments
Open in hackernews

The Halo Effect

https://kwokchain.com/2025/07/15/the-halo-effect/
31•iamwil•6mo ago

Comments

tbrownaw•6mo ago
This name is already taken: https://en.wikipedia.org/wiki/Halo_effect
JadeNB•6mo ago
It probably matters that, despite the title mangler, this is the HALO effect, not the halo effect.
827a•6mo ago
Well, the blog post is called "the HALO effect", which isn't even the same as that wikipedia page, but even if it were, the proposed nomenclature is simply a HALO deal or HALO acquisition, which is very different from the blog post title and wikipedia page.
bravesoul2•6mo ago
Same for SAFEs?
IAmGraydon•6mo ago
We should probably call this what it is - a loophole for large tech companies to engage in anti-competitive practices and skirt the law. This article's framing of it as a positive, creative new way to do acquisitions is hilarious.
Avicebron•6mo ago
> “Halo” comes from “Hire and license out.” > "Besides being a backronym" > "People with halos have left their bodies to live somewhere in the cloud giants."

It's so...evangelist?

samrus•6mo ago
In a suck and wierd way, its kinda not anticonpetitive. Onky because alot of entrprenuers arent actually trying to sell their product/service to customers, theyre actually trying to sell their company to investors, and have been the whole time.

So in the startup industry, the industry of making and selling startups to rich people, the point is to sell and this is just another intriment for that. Its kinda like two wrongs making a less wrong

pxeger1•6mo ago
I don't think a HALO is anti-competitive if the IP licence is non-exclusive as TFA says. The only exclusivity involved is that only (really) one company can hire a given team, but hiring is already exclusive in nature, and not considered anti-competitive. (Am I missing something on how a HALO is exclusive? To be honest I was surprised when I read in TFA that the IP licence is typically non-exclusive.)

If companies think the paperwork is too onerous for acquihires (convincing regulators the exclusivity inherent with acquisitions isn't creating an illegal monopoly), and they can get a satsifactory result with a non-exclusive HALO (which regulators therefore don't need to check), why shouldn't they do a HALO instead?

aabhay•6mo ago
I am deeply skeptical of the author’s conclusions to the point of being skeptical of their motive.

These HALO type acquisitions are awful for the tech industry and this trend is deeply concerning to me.

1. The author fails to consider the impact of this kind of acquihire on the company’s customers. We’ve already seen Scale AI have a dramatic change in customer behavior post hire. Windsurf was a real company with real revenue. How many of those customers want to use a product with a much less predictable future now? Where the team was basically disembowled?

2. The creation of a “class hierarchy” both within and between companies has a dis-spiriting king-maker vibe. 1/5 of the company ascends to heaven through this process and the other 4/5 is left to manage a shell corp? How is that supposed to feel?

3. The concept of windsurf rebuilding their product in google land is laughable. What product will they build but the same thing they already built? And windsurf is nowhere near the velocity of Cursor, so theyve burned months of time doing this and they’ll burn months more adapting to the new environment. How does this square with the thesis of google wanting their talent? Lets be real about the reason google bought windsurf — they got a discount from the $3B OpenAI acquisition and most of all — they wanted to fuck OpenAI. At this point, I would guess that these companies would do whatever they can to harm OpenAI, given the sheer velocity of their product and how terrified everyone is of them discovering something very soon.

4. I haven’t seen any example of a successful post-acquisition company operation. Inflection? Covariant? Character? What’s happened to these companies post change? Are all employees on strict NDAs? Why has nobody written about what it was like?

5. The conclusion I see here is straightforward — in a post AI economy, very very few people are “important” to these companies. The top 10 largest corporations in the world will basically be competing over a pool of ~5k individuals and everyone else is irrelevant.

If there’s anything that makes me wish we were living in Lina Khan’s world it’s this.

spearman•6mo ago
These HALO deals are in large part a consequence of Lina Khan style anti-trust enforcement making acquisitions more difficult.
wilg•6mo ago
On a recent episode of Dithering, Ben Thompson's claim is this is downstream of an effort to make acquisitions of small companies more difficult, and that this is worse than the previous regulatory status quo: https://dithering.passport.online/member/episode/techs-chest...

> Unfortunately, regulators didn’t listen. The effort to indiscriminately throw sand in the gears of the Silicon Valley machine — which, it should be noted, started under the first Trump administration, but was dramatically accelerated under the Biden administration — is undoubtedly the biggest driver of these stinky deals. Big Tech, starting with Microsoft, realized that the easiest way to avoid regulatory annoyance around acquihires was to separate the acquisition from the hiring; what has happened as these deals have evolved is that tech companies increasingly realize that if they are simply hiring and not acquiring then they don’t have to hire everyone. That, however, breaks the implicit social contract that made startup employment significantly less risky for rank-and-file employees.

> What is frustrating about this development is that there is a good chance we will never go back. The fact of the matter is that picking-and-choosing who to hire from a failed startup is great for Big Tech: they get the IP they want and the employees that matter, and get to jettison everyone else without having to do a future layoff. That they never thought to do so previously was, in retrospect, downstream of “the way things are done”, not some sort of legal requirement; once the law, in the form of over-eager regulators who didn’t understand what they were regulating, gave them no choice, it’s not at all clear why they would go back to the old model.

> This, in the long run, is very bad for startups. The incentives for founding a company do still remain; the founders of all four of the companies in the stinky list are doing very well for themselves. The people who are getting screwed, however, are the folks who were never necessarily going to get rich — that’s reserved for founders, and appropriately so — but who could justify rolling the dice on a positive outcome as long as they had downside protection in the form of guaranteed employment with a Big Tech company if things didn’t work out. Now, however, the best route for any non-founder is simply to pursue employment with a Big Tech company directly; the alternative, if the downside is unemployment or a contract with a hollowed-out doomed company, isn’t worth the risk (which, ultimately, again favors Big Tech, as it lowers competition for rank-and-file employees).

> It is, in the end, one of the clearest examples of a Chesterton Fence you can come up with: regulators didn’t understand the role that seamless small acquisitions played in making Silicon Valley work, so they made them undesirable and untenable; the end result is a diminished ecosystem that further entrenches the biggest players, reduces long-term innovation and risk-taking, and destroys individual employees’ opportunity and bargaining power with big companies and their chances of earning a nice payday if things worked out.

greatgib•6mo ago
The author looks clueless about this structure also.

But interesting to point out a trend that was maybe unnoticed.

One of the reason for an acquihire or something like that might also be because of other costly factors that is not taken into account: non competition agreement preventing you to poach employees/leaders from existing company to work on the same topics, cost to poach individual employees one by one, with individual negotiations, welcome bonus, the risk that some key asset refuse, ... With the acquihire, you have a whole team, used to work together, ready to work for you as they were before on day 1. And get the brand and possible IP in bonus.