frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Micro-Front Ends in 2026: Architecture Win or Enterprise Tax?

https://iocombats.com/blogs/micro-frontends-in-2026
1•ghazikhan205•26s ago•0 comments

Japanese rice is the most expensive in the world

https://www.cnn.com/2026/02/07/travel/this-is-the-worlds-most-expensive-rice-but-what-does-it-tas...
1•mooreds•49s ago•0 comments

These White-Collar Workers Actually Made the Switch to a Trade

https://www.wsj.com/lifestyle/careers/white-collar-mid-career-trades-caca4b5f
1•impish9208•49s ago•1 comments

The Wonder Drug That's Plaguing Sports

https://www.nytimes.com/2026/02/02/us/ostarine-olympics-doping.html
1•mooreds•1m ago•0 comments

Show HN: Which chef knife steels are good? Data from 540 Reddit tread

https://new.knife.day/blog/reddit-steel-sentiment-analysis
1•p-s-v•1m ago•0 comments

Federated Credential Management (FedCM)

https://ciamweekly.substack.com/p/federated-credential-management-fedcm
1•mooreds•1m ago•0 comments

Token-to-Credit Conversion: Avoiding Floating-Point Errors in AI Billing Systems

https://app.writtte.com/read/kZ8Kj6R
1•lasgawe•1m ago•1 comments

The Story of Heroku (2022)

https://leerob.com/heroku
1•tosh•2m ago•0 comments

Obey the Testing Goat

https://www.obeythetestinggoat.com/
1•mkl95•2m ago•0 comments

Claude Opus 4.6 extends LLM pareto frontier

https://michaelshi.me/pareto/
1•mikeshi42•3m ago•0 comments

Brute Force Colors (2022)

https://arnaud-carre.github.io/2022-12-30-amiga-ham/
1•erickhill•6m ago•0 comments

Google Translate apparently vulnerable to prompt injection

https://www.lesswrong.com/posts/tAh2keDNEEHMXvLvz/prompt-injection-in-google-translate-reveals-ba...
1•julkali•6m ago•0 comments

(Bsky thread) "This turns the maintainer into an unwitting vibe coder"

https://bsky.app/profile/fullmoon.id/post/3meadfaulhk2s
1•todsacerdoti•7m ago•0 comments

Software development is undergoing a Renaissance in front of our eyes

https://twitter.com/gdb/status/2019566641491963946
1•tosh•7m ago•0 comments

Can you beat ensloppification? I made a quiz for Wikipedia's Signs of AI Writing

https://tryward.app/aiquiz
1•bennydog224•9m ago•1 comments

Spec-Driven Design with Kiro: Lessons from Seddle

https://medium.com/@dustin_44710/spec-driven-design-with-kiro-lessons-from-seddle-9320ef18a61f
1•nslog•9m ago•0 comments

Agents need good developer experience too

https://modal.com/blog/agents-devex
1•birdculture•10m ago•0 comments

The Dark Factory

https://twitter.com/i/status/2020161285376082326
1•Ozzie_osman•10m ago•0 comments

Free data transfer out to internet when moving out of AWS (2024)

https://aws.amazon.com/blogs/aws/free-data-transfer-out-to-internet-when-moving-out-of-aws/
1•tosh•11m ago•0 comments

Interop 2025: A Year of Convergence

https://webkit.org/blog/17808/interop-2025-review/
1•alwillis•12m ago•0 comments

Prejudice Against Leprosy

https://text.npr.org/g-s1-108321
1•hi41•13m ago•0 comments

Slint: Cross Platform UI Library

https://slint.dev/
1•Palmik•17m ago•0 comments

AI and Education: Generative AI and the Future of Critical Thinking

https://www.youtube.com/watch?v=k7PvscqGD24
1•nyc111•17m ago•0 comments

Maple Mono: Smooth your coding flow

https://font.subf.dev/en/
1•signa11•18m ago•0 comments

Moltbook isn't real but it can still hurt you

https://12gramsofcarbon.com/p/tech-things-moltbook-isnt-real-but
1•theahura•22m ago•0 comments

Take Back the Em Dash–and Your Voice

https://spin.atomicobject.com/take-back-em-dash/
1•ingve•22m ago•0 comments

Show HN: 289x speedup over MLP using Spectral Graphs

https://zenodo.org/login/?next=%2Fme%2Fuploads%3Fq%3D%26f%3Dshared_with_me%25253Afalse%26l%3Dlist...
1•andrespi•23m ago•0 comments

Teaching Mathematics

https://www.karlin.mff.cuni.cz/~spurny/doc/articles/arnold.htm
2•samuel246•26m ago•0 comments

3D Printed Microfluidic Multiplexing [video]

https://www.youtube.com/watch?v=VZ2ZcOzLnGg
2•downboots•26m ago•0 comments

Abstractions Are in the Eye of the Beholder

https://software.rajivprab.com/2019/08/29/abstractions-are-in-the-eye-of-the-beholder/
2•whack•27m ago•0 comments
Open in hackernews

Apple is reportedly going to rename all of its operating systems

https://www.theverge.com/news/675945/apple-operating-systems-new-name-year-ios-macos
13•thesuperbigfrog•8mo ago

Comments

thesuperbigfrog•8mo ago
Does the new naming scheme imply yearly releases for all of the Apple operating systems?
soxfox42•8mo ago
They've all been receiving yearly releases for a long time now – macOS has had them since Lion, iOS had them from the beginning, and the others are similar.
laborcontract•8mo ago
I don't think so. It could possibly hint at a reduction in cadence for releases. There has been an open line of reporting about Apple that yearly releases were important to Apple but that the yearly release schedule also made it hard for them to divert engineering resources into more experimental projects like LLM-related development.

Linking version numbers to years could be seen in effect to make each one seem less monumentally important.

Maskawanian•8mo ago
Can't wait until MacOS 95 (then Mac OS XP of course). I can only imagine the discourse if this happened 25 years ago.
armchairhacker•8mo ago
> Instead of just notching up the version number, Apple will instead mark them by year.

IMO this makes sense when a product lasts for so long. Unity and JetBrains have also done it for their products. It’s easier to remember, especially when related products have different versions like in Apple’s case.

> However, the numbers will apparently align with the year after the one the update is actually released in, similar to cars. That means that the next big iOS update will be iOS 26 instead of iOS 19.

I don’t understand that (or why it’s done for cars either). Are they afraid the OS will be delayed into the next year and would rather its name be a year ahead than behind?

bennettnate5•8mo ago
> I don’t understand that (or why it’s done for cars either). Are they afraid the OS will be delayed into the next year and would rather its name be a year ahead than behind?

My understanding is that it's a marketing gimmick--_you're buying the car/phone of the future!_.

More importantly, once a few sellers do it, game theory pushes the rest to follow the same convention (otherwise their flagship models could be mistaken as last year's by buyers on first glance).

If Android moves to the same year-numhering convention, I'd bet they'll do the same year-in-the-future strategy for this reason

Arnt•8mo ago
I remember that magazines stated doing that a few decades ago. The October issue world go on sale in the final days of September and be on sale for most of October, then the November issue World go on sale in the final days of October.

It makes sense of you compare the month on the front page with the one on the calendar. Similarly, if you're still running macOS 26 in 27, it's time to upgrade, 26 in 26 is still fine.