frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Start all of your commands with a comma

https://rhodesmill.org/brandon/2009/commands-with-comma/
58•theblazehen•2d ago•11 comments

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

https://openciv3.org/
638•klaussilveira•13h ago•188 comments

The Waymo World Model

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

What Is Ruliology?

https://writings.stephenwolfram.com/2026/01/what-is-ruliology/
35•helloplanets•4d ago•31 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
113•matheusalmeida•1d ago•28 comments

Jeffrey Snover: "Welcome to the Room"

https://www.jsnover.com/blog/2026/02/01/welcome-to-the-room/
13•kaonwarb•3d ago•12 comments

Unseen Footage of Atari Battlezone Arcade Cabinet Production

https://arcadeblogger.com/2026/02/02/unseen-footage-of-atari-battlezone-cabinet-production/
45•videotopia•4d ago•1 comments

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

https://github.com/valdanylchuk/breezydemo
222•isitcontent•13h ago•25 comments

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

https://github.com/pydantic/monty
214•dmpetrov•13h ago•106 comments

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

https://vecti.com
324•vecti•15h ago•142 comments

Sheldon Brown's Bicycle Technical Info

https://www.sheldonbrown.com/
374•ostacke•19h ago•94 comments

Hackers (1995) Animated Experience

https://hackers-1995.vercel.app/
479•todsacerdoti•21h ago•238 comments

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

https://github.com/microsoft/litebox
359•aktau•19h ago•181 comments

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

https://eljojo.github.io/rememory/
279•eljojo•16h ago•166 comments

An Update on Heroku

https://www.heroku.com/blog/an-update-on-heroku/
407•lstoll•19h ago•273 comments

Vocal Guide – belt sing without killing yourself

https://jesperordrup.github.io/vocal-guide/
17•jesperordrup•3h ago•10 comments

Dark Alley Mathematics

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

PC Floppy Copy Protection: Vault Prolok

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

Delimited Continuations vs. Lwt for Threads

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

How to effectively write quality code with AI

https://heidenstedt.org/posts/2026/how-to-effectively-write-quality-code-with-ai/
245•i5heu•16h ago•193 comments

Was Benoit Mandelbrot a hedgehog or a fox?

https://arxiv.org/abs/2602.01122
14•bikenaga•3d ago•2 comments

Introducing the Developer Knowledge API and MCP Server

https://developers.googleblog.com/introducing-the-developer-knowledge-api-and-mcp-server/
54•gfortaine•11h ago•22 comments

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

https://infisical.com/blog/devops-to-solutions-engineering
143•vmatsiiako•18h ago•65 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/
1061•cdrnsf•22h ago•438 comments

Learning from context is harder than we thought

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

Understanding Neural Network, Visually

https://visualrambling.space/neural-network/
284•surprisetalk•3d ago•38 comments

Why I Joined OpenAI

https://www.brendangregg.com/blog/2026-02-07/why-i-joined-openai.html
137•SerCe•9h ago•125 comments

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

https://github.com/phreda4/r3
70•phreda4•12h ago•14 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...
29•gmays•8h ago•11 comments

FORTH? Really!?

https://rescrv.net/w/2026/02/06/associative
63•rescrv•21h ago•23 comments
Open in hackernews

The History of Xerox

https://www.abortretry.fail/p/the-history-of-xerox
73•rbanffy•1mo ago

Comments

santiagobasulto•1mo ago
Very interesting story and well written so far, I'll finish it after work.

One very interesting thing about Xerox was not only their technology but their choice of business model. As smaller companies couldn't afford an expensive copier, they'd "rent" it and charge per copy. From the article:

> The company placed machines in well-traveled public spaces where it was on display, and in addition to sales, they also offered machine rental for smaller organizations. This was a low price for up to 2000 copies, and each copy after was 4¢. They also promised that a machine could be returned within fifteen days. The 650 pound behemoth was wildly successful.

Another similar interesting business model was pioneered by Rolls-Royce in their airplane turbine business. Instead of selling their whole turbine, they'd "rent" it and charge it "per flight hour", derisking both parts.

ErigmolCt•1mo ago
It's interesting how these models keep reappearing whenever technology gets expensive, complex, and mission-critical
ewa-szyszka•1mo ago
Solid read! I started my career of at a former Xerox R&D that was acquired by NAVER Labs, which is an interesting story in itself of passing of time and the new (AI R&D) replacing the old (print technology): https://www.news.xerox.com/news/NAVER-to-acquire-Xerox-Resea...
intrasight•1mo ago
My father worked for Haloid for a bit. Worked there while also attending NYU. Layer he moved to Kodak and in 1967 our family moved to Rochester. My father retired from Kodak in 1985.

Xerox and Kodak were both amazing companies, and created a comfortable middle or upper middle class lifestyle for many thousands of Rochesterians.

MinimalAction•1mo ago
As someone who has lived in Rochester recently, I am incredibly curious to hear from folks who saw the peak of the city. I often hear of Kodak and Xerox providing hefty bonuses which also made the local businesses offer deals then for a better turnover. Would love to hear more from you.
intrasight•1mo ago
The main "hefty bonus" was treating employees exceptionally well and providing a lifetime of employment. And for us kids, it was an idyllic environment in which to grow up.
Stratoscope•1mo ago
> the computer they wanted was DEC PDP-10. At this point, Paul Strassman was replacing every IBM and DEC machine at Xerox with an SDS machine.

This scenario must have played out in multiple places. I was involved in one of them.

I was working at Tymshare, and we were evaluating the PDP-10 and the Xerox (XDS/SDS) Sigma 7.

My manager called me into his office.

---

Mike, this conversation is strictly between you and me. If anyone asks, I will deny it happened.

You are our best Sigma 7 expert, and even you prefer the PDP-10.

We're doing final acceptance tests on the Sigma 7. If all the tests pass, we have to commit to it. If enough tests fail, we can return that machine.

---

I got the hint. Challenge accepted!

Knowing all the ins and outs of the Sigma 7, I found a few subtle ways to make it crash at random times, without any indication that anyone had interfered with the tests.

Eventually I slipped up and left my username visible in a core dump.

Back to my manager's office.

---

Mike, we have a problem. Xerox figured out that you were messing with the Sigma 7 system software. We told them we would fire you. So, you're fired. You can't be in the office any more.

But you do have your Teletype at home, right? You have some projects to do on the PDP-10. Can you work on those and stay away from the Sigma 7?

Keep track of your hours, and after this blows over we will hire you back and give you that back pay.

---

So I did. And they did!

panick21_•1mo ago
That's a great story.

From the Oral History of Synertek, they wanted to buy some buy some PDP-11 but they had been bought by Honeywell. Honeywell had told them they would not be controlled and have a free hand. Honeywell of course wouldn't not allow it and told them they would get a free Honeywell mainframe. And they got send a mainframe that was completely useless and didn't have any relevant software. So eventually Synertek collapsed and many of those people founded VSLI Technology.

At AT&T they bought a lot of PDP-11s, they were the biggest DEC costumer and they also moved 3B series computers because they wanted to be a computer company too. Cost them a lot of money.

I think the story of everybody wanted PDPs but cooperate didn't want.

roflmaostc•1mo ago
Whenever I read about Xerox, it reminds me of the story that their scanners would randomly change numbers on prints

https://dkriesel.com/en/blog/2013/0802_xerox-workcentres_are...

1718627440•1mo ago
I actually don't expect other scanners to preform differently.
roflmaostc•1mo ago
Why? Can you share any examples?
1718627440•1mo ago
No, I don't have any. It is because it was not so much a bug, but a decision about a tradeoff. They compressed by unifying similar looking glyphs. Sure, these glyphs weren't representing the same character, but they did look similar. It is the kind of error an human could also have made, except humans also know that sums are supposed to match, so they take that into account when reading. Also they have a probability score and when they are unsure they read again or ask. This are all things these printers can't do without doing supervised OCR.

The tested scans did look kind of crappy, so if you care about non altered glyphs maybe don't do a lossy compression on a low resolution scan. So these issue can totally happen with any printer if your resolution is too low, the glyphs are ambigous and you use a too aggressive lossy compression. This also happens with other approaches like vectorization or OCR.

panick21_•1mo ago
Yes and by default your tradeoff should be to have the correct information. And that's actually what Xerox claimed. They said this was false and it was correctly documented. They said only if you select it this would happen. Watch the CCC talk buy the person that figured this out. Turns out they were wrong.
1718627440•1mo ago
> Watch the CCC talk buy the person that figured this out. Turns out they were wrong.

I already did, although some time ago. Kriesel also has some other interesting talks, e.g. about the German Railway company.

Like I totally think Xerox is at fault, but what they actually did wrong was using bad defaults (and lying when they got told). This can totally occur with any software. From looking at the pictures I think part of the issue was that the input resolution was lower than what the compression was tested with, not the compression part per se.

Also I think the customers are at least partially at fault for digitalizing, but not checking. Don't be stingy on important data. And who in there sane minds throws away the originals????? Like you can throw away copies all the way you like, but NEVER the original. (Except when you really want to "destroy" information.) To me that was the most ridiculous part, assuming software (being famous for bugs like no other tool) can never be wrong and throwing away physical things only relying on your random files to exist.

panick21_•1mo ago
I haven't watched the talk since I saw it, but my memory was that they did it in a mode where they claimed it wasn't supposed to happen. So it would happen even if the costumer selected the right one. Maybe my memory is bad on that.
1718627440•1mo ago
My memory also tells me that.

> I haven't watched the talk since I saw it

Funny statement, sounds like a tautology and still contains information.

panick21_•1mo ago
I mean I never watched the video (or maybe I did and I don't remember), I only 'saw' the presentation live. And I remember that room being a riot. So I might get some details wrong. Not sure this is correct english.
tonyedgecombe•1mo ago
If you want to see what a dismal company Xerox is check its share price over the last fifty years. Even accounting for stock splits and dividends the performance is dire for a technology company.
ErigmolCt•1mo ago
That's fair if you look at Xerox through the lens of "tech company returns"
crawancon•1mo ago
there are many reasons for this, but I can only comment that they should have left GIS alone, and not let ACS divest. They'd have been stronger this decade with those performing assets.

so yeah, thanks Carl.

tonyedgecombe•1mo ago
>They'd have been stronger this decade with those performing assets.

Or they might have destroyed them. I wonder how Lexmark is doing under their control.

justin66•1mo ago
[delayed]
ErigmolCt•1mo ago
How hard it is for an organization to be good at both discovery and exploitation at the same time
pstuart•1mo ago
In the end it's all about managing the incentives to be aligned -- the exploitation side needs to not consider the discovery side a threat if it challenges their current exploitations.
mrbluecoat•1mo ago
Another decent read on this subject is 'Dealers of Lightning: Xerox PARC and the Dawn of the Computer Age' by Michael A. Hiltzik
ProllyInfamous•1mo ago
This is my favorite geeky non-fiction book.

[•] <https://www.amazon.com/Dealers-Lightning-Xerox-PARC-Computer...>

In addition to all the technical detail, you learn so much about corporate hubris in their massive quest for non-innovation (resting on their laurels).

C-level staff ignored the brilliance of their Alto computer, invited Steve Jobs over in exchange for a few shares of AAPL IPO [which they almost-immediately sold], and left all their computer researchers scratching their heads as to why staff were being ignored.

panick21_•1mo ago
Letting in Steve wasn't really an issue. Lisa failed and Mac wasn't a big success until the early 90s.

And tons of other people knew what they were doing. Andy Bechtolsheim visited there too. Sun workstation basically did the same thing and were very successful.

And its really the PC that would have anyway if they let in Jobs or not.