frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Listen to Mixtapes from Before

https://intertapes.net/
1•poniko•1m ago•0 comments

My First Impressions of MeshCore Off-Grid Messaging

https://mtlynch.io/first-impressions-of-meshcore/
1•mtlynch•3m ago•0 comments

I built a tool to restore old family photos without ruining them with AI

https://forevi.ai
1•poznerd•3m ago•1 comments

Designing Electronics That Works

https://nostarch.com/designingelectronics
1•0x54MUR41•3m ago•0 comments

Most LLM cost isn't compute – it's identity drift (110-cycle GPT-4o benchmark)

https://github.com/sigmastratum/documentation/blob/main/sigma-runtime/SR-EI-03/benchmark_report_S...
1•teugent•4m ago•1 comments

Show HN: PlanEat AI, an AI iOS app for weekly meal plans and smart grocery lists

1•franklinm1715•4m ago•0 comments

A Post-Incident Control Test for External AI Representation

https://zenodo.org/records/17921051
1•businessmate•5m ago•1 comments

اdifference gbps overview find answers

1•shahrtjany•6m ago•0 comments

Measuring Impact of Early-2025 AI on Experienced Open-Source Dev Productivity

https://arxiv.org/abs/2507.09089
1•vismit2000•7m ago•0 comments

Show HN: Lazy Demos

http://demoscope.app/lazy
1•admtal•8m ago•0 comments

AI-Driven Facial Recognition Leads to Innocent Man's Arrest (Bodycam Footage) [video]

https://www.youtube.com/watch?v=B9M4F_U1eEw
2•niczem•9m ago•1 comments

Annual Production of 1/72 (22mm) scale plastic soldiers, 1958-2025

https://plasticsoldierreview.com/ShowFeature.aspx?id=27
1•YeGoblynQueenne•10m ago•0 comments

Error-Handling and Locality

https://www.natemeyvis.com/error-handling-and-locality/
1•Theaetetus•11m ago•0 comments

Petition for David Sacks to Self-Deport

https://form.jotform.com/253464131055147
1•resters•11m ago•0 comments

Get found where people search today

https://kleonotus.com/
1•makenotesfast•14m ago•1 comments

Show HN: An early-warning system for SaaS churn (not another dashboard)

https://firstdistro.com
1•Jide_Lambo•14m ago•1 comments

Tell HN: Musk has never *tweeted* a guess for real identity of Satoshi Nakamoto

1•tokenmemory•15m ago•2 comments

A Practical Approach to Verifying Code at Scale

https://alignment.openai.com/scaling-code-verification/
1•gmays•17m ago•0 comments

Show HN: macOS tool to restore window layouts

https://github.com/zembutsu/tsubame
1•zembutsu•19m ago•0 comments

30 Years of <Br> Tags

https://www.artmann.co/articles/30-years-of-br-tags
2•FragrantRiver•26m ago•0 comments

Kyoto

https://github.com/stevepeak/kyoto
2•handfuloflight•27m ago•0 comments

Decision Support System for Wind Farm Maintenance Using Robotic Agents

https://www.mdpi.com/2571-5577/8/6/190
1•PaulHoule•27m ago•0 comments

Show HN: X-AnyLabeling – An open-source multimodal annotation ecosystem for CV

https://github.com/CVHub520/X-AnyLabeling
1•CVHub520•30m ago•0 comments

Penpot Docker Extension

https://www.ajeetraina.com/introducing-the-penpot-docker-extension-one-click-deployment-for-self-...
1•rainasajeet•31m ago•0 comments

Company Thinks It Can Power AI Data Centers with Supersonic Jet Engines

https://www.extremetech.com/science/this-company-thinks-it-can-power-ai-data-centers-with-superso...
1•vanburen•34m ago•0 comments

If AIs can feel pain, what is our responsibility towards them?

https://aeon.co/essays/if-ais-can-feel-pain-what-is-our-responsibility-towards-them
3•rwmj•38m ago•5 comments

Elon Musk's xAI Sues Apple and OpenAI over App Store Drama

https://mashable.com/article/elon-musk-xai-lawsuit-apple-openai
1•paulatreides•41m ago•1 comments

Ask HN: Build it yourself SWE blogs?

1•bawis•41m ago•1 comments

Original Apollo 11 Guidance Computer source code

https://github.com/chrislgarry/Apollo-11
3•Fiveplus•47m ago•0 comments

How Did the CIA Lose Nuclear Device?

https://www.nytimes.com/interactive/2025/12/13/world/asia/cia-nuclear-device-himalayas-nanda-devi...
1•Wonnk13•47m 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•6mo ago

Comments

mmastrac•6mo 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•6mo ago
Heading compaction buried the lede: "made rendering faster" vs "made rendering 95% faster".

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

tomhow•6mo 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•6mo 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•6mo 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•6mo 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