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•1m 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•1m 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•1m ago•1 comments

The Wonder Drug That's Plaguing Sports

https://www.nytimes.com/2026/02/02/us/ostarine-olympics-doping.html
1•mooreds•2m 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•2m ago•0 comments

Federated Credential Management (FedCM)

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

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

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

The Story of Heroku (2022)

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

Obey the Testing Goat

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

Claude Opus 4.6 extends LLM pareto frontier

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

Brute Force Colors (2022)

https://arnaud-carre.github.io/2022-12-30-amiga-ham/
1•erickhill•7m 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•7m ago•0 comments

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

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

Software development is undergoing a Renaissance in front of our eyes

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

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

https://tryward.app/aiquiz
1•bennydog224•10m 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•10m ago•0 comments

Agents need good developer experience too

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

The Dark Factory

https://twitter.com/i/status/2020161285376082326
1•Ozzie_osman•11m 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•12m ago•0 comments

Interop 2025: A Year of Convergence

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

Prejudice Against Leprosy

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

Slint: Cross Platform UI Library

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

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

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

Maple Mono: Smooth your coding flow

https://font.subf.dev/en/
1•signa11•19m 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•23m ago•0 comments

Take Back the Em Dash–and Your Voice

https://spin.atomicobject.com/take-back-em-dash/
1•ingve•24m 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•24m ago•0 comments

Teaching Mathematics

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

3D Printed Microfluidic Multiplexing [video]

https://www.youtube.com/watch?v=VZ2ZcOzLnGg
2•downboots•27m 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•28m ago•0 comments
Open in hackernews

The fix to the iPhone Antennagate in 2010 was 20 bytes

https://hachyderm.io/@samhenrigold/115330105694760262
53•todsacerdoti•4mo ago

Comments

stephenlf•4mo ago
I love that this whole thing was a non-fix to a non-issue. The fix didn’t change any signal strength issues. It just changed the UI a bit.
47282847•4mo ago
A cosmetic fix to a cosmetic issue. Still a fix and still an issue :) Some might even say UX is more important than the underlying tech!
philipallstar•4mo ago
Only if you define UX as including all the really hard stuff that goes into engineering the device, and not just the externalities. A car that looks nice but doesn't go isn't as important as a car that goes but doesn't look nice.
cut3•4mo ago
of course, why wouldnt you intclude all the experience
philipallstar•4mo ago
Because the people doing UX are generally just UI people who want to claim credit for all the hard stuff as well. So they have no ability to change any of the experience other than redesigning the cosmetics.
jebarker•4mo ago
I remember this episode but not the details. Why was it a non-issue if holding the phone did cause the signal strength to drop? Is it just the case that the drop was too small to affect call quality/stability?
danhau•4mo ago
I don‘t remember it at all, but based on the post it sounds like it was just a UI quirk that made the signal loss look much worse than it really was.

I‘m guessing gripping any phone will drop signal strength, but the iPhone made itself look worse.

lern_too_spel•4mo ago
That's exactly the opposite of what the post says. It says that holding the phone wrong caused the signal strength to drop precipitously, but the UI still showed that the signal was strong.
danhau•4mo ago
Ok, then I guess Apple changed the UI to more reflect reality?
jml7c5•4mo ago
No, it was a real hardware issue, too. Applying a thin layer of kapton tape would reduce the drop by 8 dB.

https://web.archive.org/web/20241210053556/https://www.anand...

addicted•4mo ago
This wasn't a non issue. You touched the phone in the wrong places and you would drop off an existing call.

Most people solved this by indeed not "holding it wrong" or getting cases (I don't know if the cases worked, but there was a whole industry built around advertising cases that solved this problem).

jerlam•4mo ago
Apple's interim fix was to give all the owners a case.
pipe01•4mo ago
AFAIK the cases worked because they prevented the hand from making electrical contact with the metal parts
cainxinth•4mo ago
Steve Jobs solves iPhone 4 reception problems: 'don't hold it that way'

https://www.theguardian.com/technology/blog/2010/jun/25/ipho...

actionfromafar•4mo ago
That's weird, "don't hold it that way" is 22 bytes, not 20 bytes.
daveoc64•4mo ago
Apple changed the antenna design in the iPhone 4 Verizon variant, and in the 4S to really resolve the issue.

That fixed the actual problem in hardware - the software fix just made things look better.

jerlam•4mo ago
It probably didn't help that AT&T service was poor during this time, as they were the only iPhone carrier in the US, their backend was quite unreliable as everyone was discovering streaming video.

All my iPhones, not just the 4, regularly dropped calls with AT&T until I switched to Verizon.

lapcat•4mo ago
> the software fix just made things look better

The software fix made things look worse. The "bug" was that the number of bars was misleadingly high.

willidiots•4mo ago
To TFA's point - "Bars" are relative and relatively meaningless - [SS]RSRP, RSRQ and SINR are your real numeric signal strength / quality measurements.

Not sure about Apple, but on Android, individual carriers can set the number-to-bars thresholds. Two otherwise-identical signals could be represented as a different number of bars depending on your particular carrier: https://source.android.com/docs/core/connect/signal-strength

addicted•4mo ago
There are 2 problems to this.

1. I seriously doubt Apple was accidentally displaying more bars on the phone. If it was a "bars" issue then it was almost certainly done deliberately to make the iPhone reception look better than what it was.

2. It wasn't just bars. I had this phone and you would literally drop off calls by holding the phone differently when you hadn't done anything else. There was a genuine problem with the phone that I don't think was ever resolved other than people getting used to holding the phone differently like Steve Jobs told us to.

I lost my iPhone and switched to a hand me down from my parents which was a generation older and the service was significantly better.

ghoulishly•4mo ago
Author of this thread here, thanks for sharing! This was the first time I publicly went into assembly code so I was a little nervous about screwing up a detail but glad it’s getting a warm reception.