Recent submissions

Comment · 3 days ago
Citation needed. For example Flamanville 3 (France) was estimated to cost around €3.3 billion, costs ballooned to over €13-19 billion. There are other similar examples such as Hinkley Point C (UK). Also maintenance is much more expensive and don't forget the cost for storing nuclear waste + decomissioning. Compare that to renewables...
Comment · 7 days ago
It took 2-3 hours, not 19. The first version was a static index.HTML file and was not exploitable. People found out and contacted the challenge author. After the fix was public it has been exploited in a couple of hours.
Comment · 2 months ago
Padding is typically part of the hitbox, margin is not. What you are describing sounds like margin to me. Especially for Firefox since their UI is made with web tech.

But besides being overly pedantic I agree with your general point. If their is a small gap between hitbox and edge of the screen it is very annoying.

But the worst thing IMO is Windows 11 windows which you can grab by the titlebar but not the content area. However often there is no visual indication of where the titlebar starts/stops.

Comment · 8 months ago
With signals you can avoid the prop drilling. I think signals can help a lot with this approach
Comment · 8 months ago
Well, someone has to start. It's ok if you use the alternative with a subset of your contacts.
Comment · 9 months ago
True, but considering that the extension was bought in 2022 by Avast, maybe it has its own tracking built in by now or will have something concerning done to it in the future. So even if the user does not care about cookies that much I would still recommend this new extension over "I don't care about cookies"
Comment · 10 months ago
For panning you don't need a 3D view/reconstruction. This also allows translational camera movements, but only for nearby views. Maybe I am overly pedantic here, but for HN I guess thats appropriate :D
Comment · 10 months ago
Should you optimize for resize performance? I guess that depends on the app. Use the tool that fits the requirements.
Comment · 11 months ago
The problem is content exclusivity. It would be great if all the content or at least most would be available on all platforms. At least eventually. That would be great for consumers. Mergers like this typically not.
Comment · 11 months ago
Another reason I can think of is the requirement not to introduce a breaking change. It is very frustrating if the codebase has a lot of hacky/bad code in it but a lot of it can't be changed...
Comment · 11 months ago
Because updates don't just include new features but also bug and security fixes. As always, it probably depends on the context how relevant this is to you. I agree that cooldown is a good idea though.
Comment · 11 months ago
> The government is.

Companies too.

Comment · 1 year ago
I think the problem is that they cannot communicate that they don't know something and instead make up some BS that sounds somewhat reasonable. Probably due to how they are built. I notice this regularly when asking questions about new web platform features and there is not enough information in the training data.
Comment · 1 year ago
Ain't gonna happen (unfortunately). Somehow people (outside of HN) seem to like to use apps for everything. EVERYTHING.
Comment · 1 year ago
I also get this. Firefox on Android in Germany.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton