frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

1•jstoppa•26s ago

What Happens When Technical Debt Vanishes?

https://ieeexplore.ieee.org/document/11316905
1•blenderob•1m ago•0 comments

AI Is Finally Eating Software's Total Market: Here's What's Next

https://vinvashishta.substack.com/p/ai-is-finally-eating-softwares-total
1•gmays•1m ago•0 comments

Computer Science from the Bottom Up

https://www.bottomupcs.com/
1•gurjeet•2m ago•0 comments

Show HN: I built a toy compiler as a young dev

https://vire-lang.web.app
1•xeouz•3m ago•0 comments

You don't need Mac mini to run OpenClaw

https://runclaw.sh
1•rutagandasalim•4m ago•0 comments

Learning to Reason in 13 Parameters

https://arxiv.org/abs/2602.04118
1•nicholascarolan•6m ago•0 comments

Convergent Discovery of Critical Phenomena Mathematics Across Disciplines

https://arxiv.org/abs/2601.22389
1•energyscholar•6m ago•1 comments

Ask HN: Will GPU and RAM prices ever go down?

1•alentred•7m ago•0 comments

From hunger to luxury: The story behind the most expensive rice (2025)

https://www.cnn.com/travel/japan-expensive-rice-kinmemai-premium-intl-hnk-dst
1•mooreds•8m ago•0 comments

Substack makes money from hosting Nazi newsletters

https://www.theguardian.com/media/2026/feb/07/revealed-how-substack-makes-money-from-hosting-nazi...
5•mindracer•9m ago•1 comments

A New Crypto Winter Is Here and Even the Biggest Bulls Aren't Certain Why

https://www.wsj.com/finance/currencies/a-new-crypto-winter-is-here-and-even-the-biggest-bulls-are...
1•thm•9m ago•0 comments

Moltbook was peak AI theater

https://www.technologyreview.com/2026/02/06/1132448/moltbook-was-peak-ai-theater/
1•Brajeshwar•10m ago•0 comments

Why Claude Cowork is a math problem Indian IT can't solve

https://restofworld.org/2026/indian-it-ai-stock-crash-claude-cowork/
1•Brajeshwar•10m ago•0 comments

Show HN: Built an space travel calculator with vanilla JavaScript v2

https://www.cosmicodometer.space/
2•captainnemo729•10m ago•0 comments

Why a 175-Year-Old Glassmaker Is Suddenly an AI Superstar

https://www.wsj.com/tech/corning-fiber-optics-ai-e045ba3b
1•Brajeshwar•10m ago•0 comments

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

https://iocombats.com/blogs/micro-frontends-in-2026
1•ghazikhan205•12m 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•13m ago•1 comments

The Wonder Drug That's Plaguing Sports

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

Federated Credential Management (FedCM)

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

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

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

The Story of Heroku (2022)

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

Obey the Testing Goat

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

Claude Opus 4.6 extends LLM pareto frontier

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

Brute Force Colors (2022)

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

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

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

Software development is undergoing a Renaissance in front of our eyes

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

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

https://tryward.app/aiquiz
1•bennydog224•21m ago•1 comments
Open in hackernews

Making iText's table rendering faster

https://kb.itextpdf.com/itext/how-i-made-pdf-table-rendering-faster
33•whizzx•8mo ago

Comments

mmastrac•8mo ago
It's funny that iText is still around. I used this 20 years ago in a hybrid .NET/Java web app that needed a PDF renderer and it was pretty much the top choice. The rendering still looks the same!
nine_k•8mo ago
Heading compaction buried the lede: "made rendering faster" vs "made rendering 95% faster".

Dear @dang, may we have the "95%" back?

tomhow•8mo ago
It's standard practice to take those kinds of numbers out of title, because they make the title more baity, and often cause much of the discussion to focus on debate about how accurate/normal the figure is. It's sufficient for the title to say "faster" then let the article demonstrate how much faster it can be in different scenarios.
nine_k•8mo ago
But there is a qualitative difference between 5% faster and 95% faster: the latter usually meaning a serious rework, and the former being a small incremental improvement.

I'd be okay with replacing "95% faster" with "several times faster" to still convey the point.

tomhow•8mo ago
It's not about the size of the number or improvement; we do the same thing when the number is "10,000%", which is not unusual in the titles we see here.

The problem with these kinds of titles – and this is no comment on this particular article (I haven't checked, because it's irrelevant) – is that sometimes writers will put a figure in the title that was achieved in a one-off result under very specific/unusual conditions, whereas the realistic improvement under more normal conditions is like 20% or 50% – still great, just not what the title claimed.

Then when that happens, the discussion becomes dominated by comments pointing that out and debating the validity of the tests and results – even if the article does a good job of revealing those details.

We've found we can reduce that effect by taking the numbers out of the title altogether.

canucker2016•8mo ago
Always love optimization posts.

A few things caused some confusion while reading the post.

For the first 50,000 cells flame graph, the post identifies two methods as the main time sinks, com.itextpdf.layout.renderer.TableBorderUtil#createAndFillBorderList and com.itextpdf.layout.renderer.CollapsedTableBorders#getCollapsedList.

I looked for those two methods in the flame graph and couldn't find them.

Only when I realized that the flamegraph had truncated the full method names to show just the method name, did the graph make sense.

I think circling in red (or whatever high contrast colour you want) the method names in the flame graph would've made drawing attention to them much quicker.

The second problem is a display problem.

The third table, displaying the results of post-optimization for collapsed table borders only displays three columns on Firefox (hiding the fourth column, containing the post-optimization runtimes). If the user moves the mouse over the table, then the horizontal scrollbar for the table appears, hinting that there's more data hidden off the right end of the table.

The third quibble I have with the post is the display of large numbers in the tables. Actually the last table fixed the problem, using '_' as a thousands digit separator. If that change could be applied to the other tables in the post, that'd make discerning the differences in runtimes easier.

Thanks