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/
142•theblazehen•2d ago•42 comments

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

https://openciv3.org/
668•klaussilveira•14h ago•202 comments

The Waymo World Model

https://waymo.com/blog/2026/02/the-waymo-world-model-a-new-frontier-for-autonomous-driving-simula...
949•xnx•19h ago•551 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
122•matheusalmeida•2d ago•32 comments

Unseen Footage of Atari Battlezone Arcade Cabinet Production

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

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

https://github.com/valdanylchuk/breezydemo
229•isitcontent•14h ago•25 comments

Jeffrey Snover: "Welcome to the Room"

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

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

https://github.com/pydantic/monty
222•dmpetrov•14h ago•117 comments

Vocal Guide – belt sing without killing yourself

https://jesperordrup.github.io/vocal-guide/
27•jesperordrup•4h ago•16 comments

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

https://vecti.com
330•vecti•16h ago•143 comments

Hackers (1995) Animated Experience

https://hackers-1995.vercel.app/
494•todsacerdoti•22h ago•243 comments

Sheldon Brown's Bicycle Technical Info

https://www.sheldonbrown.com/
381•ostacke•20h ago•95 comments

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

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

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

https://eljojo.github.io/rememory/
288•eljojo•17h ago•169 comments

An Update on Heroku

https://www.heroku.com/blog/an-update-on-heroku/
412•lstoll•20h ago•278 comments

Was Benoit Mandelbrot a hedgehog or a fox?

https://arxiv.org/abs/2602.01122
19•bikenaga•3d ago•4 comments

PC Floppy Copy Protection: Vault Prolok

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

Dark Alley Mathematics

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

How to effectively write quality code with AI

https://heidenstedt.org/posts/2026/how-to-effectively-write-quality-code-with-ai/
256•i5heu•17h ago•196 comments

Delimited Continuations vs. Lwt for Threads

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

What Is Ruliology?

https://writings.stephenwolfram.com/2026/01/what-is-ruliology/
43•helloplanets•4d ago•42 comments

Where did all the starships go?

https://www.datawrapper.de/blog/science-fiction-decline
12•speckx•3d ago•4 comments

Introducing the Developer Knowledge API and MCP Server

https://developers.googleblog.com/introducing-the-developer-knowledge-api-and-mcp-server/
59•gfortaine•12h ago•25 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...
33•gmays•9h ago•12 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/
1066•cdrnsf•23h ago•446 comments

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

https://infisical.com/blog/devops-to-solutions-engineering
150•vmatsiiako•19h ago•67 comments

Why I Joined OpenAI

https://www.brendangregg.com/blog/2026-02-07/why-i-joined-openai.html
149•SerCe•10h ago•138 comments

Understanding Neural Network, Visually

https://visualrambling.space/neural-network/
287•surprisetalk•3d ago•43 comments

Learning from context is harder than we thought

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

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

https://github.com/phreda4/r3
73•phreda4•13h ago•14 comments
Open in hackernews

R0ML's Ratio

https://blog.glyph.im/2025/08/r0mls-ratio.html
77•zdw•6mo ago

Comments

jiggawatts•6mo ago
I see this regularly in large enterprise. My favourite example is getting a 20-30% discount on rack-mount server hardware purchased up-front for the next 3 to 5 years of growth requirements. Invariably, the executives that signed this "great deal" treat themselves to a champagne lunch to celebrate the savings.

Never mind that most of that capacity will sit around unused for years. The real problem is that by the time they get around to filling the last half of the capacity, the exponential march of Moore's law -- or the equivalents for storage and networking -- will have discounted the cost of that capacity by 50% or more anyway.

Similarly, I saw a corporation "lock in" a sweet discount for the WAN network provider for 7 years where they got an upgrade from 1 Mbps to 2 Mbps and a discount of 40%. At the same time, residential broadband was already 25 Mbps minimum and business-grade fibre had three-digit Mbps speeds within months. The sales rep that got that deal signed probably laughed his ass off.

It's a fundamental misunderstanding that it's easier or better to purchase things in big stair-step increments when following an exponential curve. The waste will be exponentially higher the longer the steps. Ideally, one would want to purchase hardware in the smallest possible time-steps, following product release cycles exactly. That's one of the benefits of the public cloud, you can switch CPUs (or whatever) with a button-press.

The example of this that's burned into my mind is that a vendor (Dell or HPE, I can't remember) convinced a government department to buy a 48-core AMD EPYC server for bioinformatics. This is one of those problems where you want the biggest possible single box because of the way the algorithms scale ("up", not "out"). They're stuck with that box for the next five or so years. Meanwhile the cloud public cloud is making available these monsters: https://techcommunity.microsoft.com/blog/azurehighperformanc...

Check out that beautiful exponential curve! If you "lock in" just 2 or 3 generations back, you're missing out on 90% of what you could be using.

maxbond•6mo ago
As a point of information (I don't disagree with anything you've said), just because public clouds advertise a gigantic instance type doesn't necessarily mean you can provision it. I saw a situation at work once where the ML researchers couldn't figure out why they were failing to provision a box. The request would be pending for a few hours before failing. AWS eventually said they simply didn't have the capacity in that AZ, and it was unlikely to ever succeed.
jiggawatts•6mo ago
Conversely, if you're in some co-location facility and they run out of space/cooling/power, then you might be painted into a very small corner for an extended period. This happened to several government customers because they all shared a common facility. Entire departments were squeezing blood from a stone because they had an iron rule that "no more servers", not even VMs... for years.

In the public cloud, you can almost always just pick another AZ, another region, or another SKU. Because of how Spot priced compute works, a PayG customer will essentially always be able to provision something, somewhere.

protocolture•6mo ago
>Similarly, I saw a corporation "lock in" a sweet discount for the WAN network provider for 7 years where they got an upgrade from 1 Mbps to 2 Mbps and a discount of 40%. At the same time, residential broadband was already 25 Mbps minimum and business-grade fibre had three-digit Mbps speeds within months. The sales rep that got that deal signed probably laughed his ass off.

Its actually one of the least bad ISP business models. Its fantastic for capacity planning. I worked for an ISP that got a lot of businesses signed up on 700 buck per month EOC services, 4-5 year terms, before the NBN rolled out and provided 20 times the bandwidth for 50 bucks.

Thing is, when the NBN passed those customers, they would reach out and try and move them sideways. Extend the contract for 2 years, drop 700 bucks down to 400 and bundle in voice and managed router services. Add in fixed wireless for backup. Offer them 100M business fibre for a transition up to 1k/ month.

An ISP that can do this can afford service techs, upgrades, more peering and transit. It can breathe. Trying to sell a 40 dollar TC-4 NBN service for 42 dollars is a losing proposition. The customer feels good when they get a good deal but they lose out when the ISP starts downsizing or crawling back costly transit. And if its month to month, the constant churn is crazy.

codazoda•6mo ago
I once worked for a company that went from 100k annually to over $1B in under a year. I was 18 and they gave me a corporate card and almost no particular restrictions on its use. I thought they were a bozo. Now I’m not so sure.
tekacs•6mo ago
I found this article somewhat confusing to read, so I asked for a synthesis of it, shared below for anyone else who might run into the same.

https://share.cleanshot.com/7zq42cMg

nighthawk454•6mo ago
Essentially, when you buy in bulk you trade upfront commitment for a discounted price. Which isn’t a good deal unless you’re confident you’re going to use all the units/seats you bought.

This is the same logic as over buying at the grocery store. The unit cost of bulk items may be less, but if the surplus is just gonna spoil you’ve wasted money in the difference.

1.0 * N * discount_rate * price <= certainty * N * 1.0 * price

—> discount_rate / certainty <= 1.0

—> discount_rate <= certainty

In the event your confidence/usage is lower than the discounted rate - say discounted to 80% of sticker price but you expect 60% utilization - this might suggest you buy 60% of your capacity at the bulk rate and fill any further demand with on-demand full-price option.

jerryjappinen•6mo ago
I saw Unsure Calculator on HN some time ago. Seems like the perfect use case. https://filiph.github.io/unsure/
valicord•6mo ago
So buy in bulk if it's cheaper then per unit and buy per unit if it's cheaper than in bulk? Truly a brilliant advice. What's next? "Get multiple quotes and pick the best one"?
jdpage•6mo ago
Buy in bulk if it's cheaper per unit that you buy, and per unit if it's cheaper per unit that you use. (EDIT: with the understanding that you're unlikely to buy much more than you use if just-in-time per-unit purchasing is available). No, it's not groundbreaking advice, but it's a very easy trap to fall into, especially if you're talking to someone who's good at selling you stuff.

I'm sure we've all had an experience at least once where we've bought something in a larger container from the grocery store thinking we were getting a deal, only to find that we didn't get through it as fast as we thought we would, it started spoiling, and we got to scrape our savings into the trash can.

And many of us have had an experience where someone higher up in the company has insisted that we use a tool that isn't very good "because we've already paid for it", so it's clearly needed advice, even if it's not groundbreaking. Everyone sometimes needs "obvious" conclusions pointed out to them, I think. It's a quirk of our mental processing as humans.

valicord•6mo ago
No, it's always "per unit that you use". Units that you buy and not use are wasted, so that's would be the wrong way to compare.

Dressing up an obvious idea with fancy-sounding math formulas and pages of text is exactly how you get trapped by someone good at selling stuff.

jdpage•6mo ago
You're right, but I think you're less likely to buy extra at per-unit pricing (since you can always buy just-in-time), so you're less likely to run into a situation where you overpurchased at per-unit pricing. (Edited to note that.)
osener•6mo ago
Ah the joys of enterprise.

Once, a team at my old job wanted to try A/B testing for the first time. After some research, they picked a SaaS tool to make it quick. Simple, right? Just sign up and go.

Of course not. First they had to go through THE PROCUREMENT! (dun dun dun dun)

Those legends weren’t about to let us limp along on a humble pro plan. They wheeled, dealed, and months later emerged triumphant: a glorious three-year enterprise contract. SLAs! Volume discounts! The whole nine yards. The art of the deal baby!

Small snag: by the time the ink dried, the original team had moved on. New PM, new priorities. No one even generated an API key during the whole time we paid for this top-tier enterprise service.