skysight-inc/HackerNews huggingface dataset:
That's one of the reasons. Others include, but are not limited to:

1. The EPR is a FOAK build of a new design

All of the EPR instances were started before any other instances were completed. FOAK (First of a Kind) builds are notoriously more difficult, costly and risky than NOAK (Nth of a Kind) builds.

Think how much more a prototype of car costs than one you get off the assembly line. The difference is not quite that pronounced, but it's there.

2. No nuclear industry/workforce

I think the article goes into this, but a lot of the cost of HPC, Olkiluoto and Flamanville (as well as Vogtle-3/4) is simply for rebuilding nuclear expertise both in industry and in the workforce.

China also buit both EPRs and AP-1000s, and they did it quite a bit more quickly and cheaply, because they have an experienced workforce and industry at hand. They current have 20+ reactors under construction. That makes a huge difference as we know from experience. Just in Germany, the difference between one-off reactors and the Konvois that were built at the same time in series was around 2x.

However, even in China the EPR took longer than other reactors. Partly due to it being a FOAK design, but also for the third reason:

3. The EPR is too complicated

For various reasons, the EPR is far too complicated, and in the end not a good design. Which is one of the things you find out in FOAK builds (see point 1).

That's not me saying this, it's the manufacturer, EDF. They have abandoned the EPR design, all new French reactors will be the vastly simplified EPR2. I haven't been able to find out whether Sizewell C and subsequent will also be EPR2 or whether the UK will stick with its heavily modified EPR.

One example is that the EPR has quadruple independent cooling systems. This is in order to maintain triple redundancy while doing maintenance on the cooling system, so being able to do that maintenance without having to take the reactor offline. Considering the German PWRs were above 90% capacity factor with "just" triple redundancy, this seems to be gold-plating. Nice-to-have if you can pull it off, but it appears they couldn't pull it off.

Also, all those cooling systems have to be active in order to comply with German nuclear regulations. The somewhat silly reason is that German regulators both (a) had no experience with passive cooling systems and (b) had a prescriptive approach to regulation, rather than a requirements-based approach. So "you must build a cooling system like this" rather than "your cooling system must be able to do this".

It's is also obviously a bit redundant considering that Germany no longer operates nuclear power plants and isn't exactly currently in the market for an EPR.

The Westinghouse AP-1000 uses at least some passive cooling, which is not only more reliable but also simpler, smaller and cheaper and makes the total plant a lot smaller.

Once you've built one, the EPR is apparently a great reactor (the Fins are very happy with theirs), and should last a long time, but it's just a pain to build.
This sounds like the engineer / designer dream. Make the best product possible, and the users will follow. Vibes work in a world where money is free and timelines are endless (low interest rates, funding the business with contract work, lots of angel investors, side projects, the innovation team).

It’s also a function of what phase the product is at. Do you have users yet? Do they use the product yet? Do they stay retained? What features matter to them? All of those questions are very quickly answered with data. They help align a group of collaborators on what matters.
Not more bad than C++ :-)
Tandem OLED is OLED's latest weapon in holding off MicroLED, QDEL
Today on HN : "Coffee Stats – Maximize Caffeine Intake and Get to Bed at Night"

https://news.ycombinator.com/item?id=41620002
bullfit ?
> instead of actually creating a proper document, it’s easy to say, “Meh, I’ll do it later it’s in slack.”

Seems like an actual use case for LLMs. Yeah I understand the potential issues but (worst case) confusing documentation with some errors and flawed assumptions yet proper citation and sources (so it can be manually improved and eventually turned into thoughtfully constructed document) seems better than having no docs or entirely outdated ones.
Except those other compilers offer multiple toolchains, including interpreters, that are faster than rustc.

Standard ML, Idris, ..., F#, Haskell and OCaml have interpreters, and REPLs, in addition to the full blown AOT compilation.

Naturally Rust can also have those, however they aren't here today.
I generally don't read anything by gh but I think he is cryptically just referring to something like XLA, whereby your NN architecture gets compiled straight to hardware, say to a custom asic, or to an FPGA bit stream, etc.

It's definitely going to happen but I don't think it will replace CPU's much like human brains can't quite replace CPU's and what they are optimised for.

Trying to make out that TinyGrad is leading the charge in this is quite self indulgent.
20 year war killing millions in Iraq and Afghanistan

Are you sure about the "millions" part? In you know, the factual sense?

Or does it just feel like something neat to say, to get your point across?
The government already mandates all sorts of conditions around work practices, right to breaks and special provisions. Given the dissolution of the Unions by vested interests like Amazon, combined with their refactoring and min/maxing things like performance metrics and KPIs for use in downsizing and PIP scenarios, the government is probably exactly the appropriate entity to step in.
The UK has almost 7GW of shovel-ready pumped storage hydropower projects with over 135GWh storage capacity.
Seriously, why ? :-)
What's the motivation for the bogus data? Just adding noise to obscure real vessel activity?

Similarly, the entire AIS tracking system needs a layer of authentication. I ran an AIS station for several years that fed data to Marinetraffic, and I could have stuffed whatever data I wanted into their database with no apparent restrictions or checks.
Oh yeah I'm curious about the specifics.
I first realized that glue is the "glue" holding the world together when I read about this: https://en.wikipedia.org/wiki/Big_Dig_ceiling_collapse

It was caused by using the wrong glue to hold up a 26 ton slab of concrete - which immediately caused me to say "There is a right glue?"
USB-C has a tiny fragile 0.7 mm thick PCB levitating mid-air right in the middle of the port, just attached to one end (enabling it to irreparably bend in any direction if anything pushes it). This is in my experience way more fragile than the internal tried-and-true spring fingers.
We only have so many lochs/valleys, realistically we will need to rely on batteries after about 20GWH or so.
> I’ve never been diagnosed with ADHD and don’t feel that I have it, but there’s a little sparkle at starting a new project and a certain amount of slog in following certain ones through to their logical end.

Every now and then (usually after reading something on here that brings it up) I wonder about this for myself as well.

I don't think it's ADHD, it's just... normal life, surely? New projects are always more exciting than the last, boring, grindy bits of a side project.
Now, I should port this to my smartwatch. Great.
Which is exactly why we traditionally don't build the world from scratch in C++, rather rely on binary libraries for 3rd party dependencies, or component frameworks.

Additionally rely on dynamic libraries during debug builds.
How about make it so you can smash the whole rack with a sledgehammer or datacenter burn down and system hums along like nothing happened.
GLPK or GLPK_MI? GLPK is probably the worst tool you could pick. I tried it before on some of my problems, and it would not ever finish. Use OR-Tools, if it will work for your problem, or maybe one of the other free solvers with CVXpy will help you (https://www.cvxpy.org/tutorial/solvers/index.html), if you really need a free tool.

GLPK should not be used as a guide for the general field. The commercial solvers will do infinitely better than GLPK.
Indeed, that is decided on a case-by-case basis. So if a company determines that moving on-premise is cheaper than AWS, perhaps that is actually true for them.
Black hole radiation paradox could be solved – if they aren't what they seem
Users are beta testers, and always have been.
I think the big issue here is that drivers are tested (poorly) and licensed. Cyclists aren't, which is good because it includes kids. Are we going to hold 8 year olds legally liable? They're allowed to bike on the public streets and roads, after all.
GTFO yes !
Reread the quote -- You're misinterpreting the sentence.

70% of Americans are overweight. But not all of those are obese.
> A Proton like layer would also totally make sense on Windows

it is not full Proton, but DXVK is used on Windows as it has sometimes better compatibility and/or performance for older titles.
1Password Deepens Partnership with CrowdStrike
Same reason as usual. Not every application has been ported.
Not the same people
The classic one is the number of cyclists riding along with their helmet dangling from the handlebars.
Excuse me for my naive question, but why don't we use native Docker Desktop? What are the advantages of this tool?
I've found that high caffeine drinks make me very sleepy. I'm still trying to get hold of some kind of ADHD medication
That's Hydro (and it's a bit more than that now).
Of course, one thing leads to the other.
Lest we forget that Popper was describing a specific type of "intolerance" that existed in the 1940s.

> "In this formulation, I do not imply, for instance, that we should always suppress the utterance of intolerant philosophies; as long as we can counter them by rational argument and keep them in check by public opinion, suppression would certainly be unwise."
If only they'd used the f-word instead of Ook...
My employer had a great culture of talking things out in public channels, but after the acquisition, nearly everything is in private channels & DMs now.

For some things, I've explicitly told people: "can you copy and paste this question in our support channel, so I can answer there?" But for a lot of things, I've just accepted that this is the new normal, and for some of it, I even understand why it is the way it is.
Could be a good test for future GPT intelligence but probably not hard
Here is my double-edge-sword one. (A recipe for interesting yet unsuccessful paths).

- Don't start something until you have set a finish line.

You have full freedom on how you set the finish line.
If the finish line is too far away, split into subproject for which you can set a closer finish line. Sometimes you will fail to reach the finish line for some unforeseen reasons, that's OK, just reevaluate if this impact the feasibility of the upper projects.

- Don't start something you don't have the resources for. If some project are expected to be long-running, you should plan for the resources needed for their being interrupted. Because you can interrupt and restart projects, advancing is just picking some task for the day from your priority queue.

This one is tricky because if you start to define a subproject that you have the resources to do (like building a prototype), once it is done, people will tell you it's just a prototype, and you don't have the resources to build the full thing nor find investors or customers). So maybe you shouldn't have built the prototype knowing you wouldn't be able to scale it up later. And then you get sunk-cost fallacy put on a dead-end road.

- Don't share your projects.
Uncouple task completion from external validation. External validation should be avoided. At anytime, you'll most likely be working on a subproject of a subproject. It's likely to be specific, boring, or some very valuable key brick that can be used for many other projects.

If you chase the high of sharing a successful project and rely on it for taking each step, and at the end external success doesn't come, you are killing your future motivation source (in a kind of learned helplessness fashion).

It often kills motivation, transforming the intrinsic reward of completing subprojects fully in your control into external rewards out of your control. Inversely it can lead you to delude yourself if you surround yourself with sycophants.

External validation will want to set arbitrary finish lines upon you without regards for feasibility or resources needed.

"Just turn it into money", "It's useless", "Don't give it for free" are things you don't like to hear when you run on an empty stomach after pouring your soul into making some great things.
Pascal -> Oberon -> Go

Languages that cared about compilation speed from the start.

And it shows.
Is it true that after a battery replace or other service the waterproof seal is compromised? Maybe they'd be able to restore this after a battery replace in some way.
Banks usually have information they can ask like Social Secuirty Number (which is inevitably in some leak).

eBay is the first one that comes to mind. I know I've run into it a couple of other times where a website will just offer to text you a code, but usually there is a small link you can click that says "use my password instead".

Facebook and Amazon don't have my cell phone number, but I bet they have an option.

I don't usually try to reset my passwords since I use a password manager, so it's probably more common than that.
>> you are ordering food and drinks, speed is not essentials, if you're in a hurry you don't sit down in a diner/restaurant

> Honestly if I received poor/slow service and management came back with this I'd be pretty upset.

Plenty of places will tell you not to expect fast service for certain dishes or drinks. If you order a cocktail at a bar and complain when it arrives after the cola, you'll raise eyebrows.

The confusion between you two in this thread may be partly due to the conflation of 'slow service' with 'poor service', they're not necessarily the same. Sure, if I ordered a cola and was still waiting after the table next to me received their 5 different cocktails, something would have gone wrong.

Here's a fun story. The other day, I was in Belgium. We ordered food at a restaurant. While we were waiting I had a beer, my partner had a negroni. We waited... and waited... and waited. Other diners arrived, ordered food, their food arrived, they ate it. And still we waited.

After a while we asked a waiter if our food order had got lost. They were apologetic, and pointed to my partner's still-unfinished drink, but said they'd get our food out ASAP. The food arrived rapidly (it was delicoius).

What had happened? Well, a negroni is an apéritif, so is drunk before a meal. The staff hadn't been inattentive; quite the opposite -- they were waiting for the apéritif to be finished. Serving the meal beforehand would have been... rude? Undignified, perhaps. And certainly something that all the other local diners would have been well aware of.

Sure, it was a leisurely situation, nobody was in a rush, this isn't a daily occurrence, blah blah. Anwyay, I learned a thing about apéritifs. Cultural heterogeneity is educational and enriching in a way that QR codes and social isolation are not.
The UK’s average nuclear load factor for 1970 to 2017 was 67.4 per cent. Furthermore, France demonstrated the correlation of nuclear downtime in the summer of 2022 when it was too summery, compounded with overrunning maintenance. At its lowest point, France’s nuclear availability sat at around 40% of maximum capacity for about a month.

All single power generators need to be backed up for downtime.
A container that traps flammable gasses is called a bomb

This is not usually a design goal
This principle is clear if you apply a real world analogy. Just because you happen to have keys to a building doesn't mean you can enter without authorization from the owner. (E.g. you may have kept copies after a lease expires or a sale, it maybe you found them, etc.)
> I think hybrid orgs are going to be viable in some cases

I think it depends a lot on the company. If your company was remote to begin with and you go hybrid, unless you happen to have team mates who are local to you, it's very possible you'll still never meet them in the office.

This place I'm at recently mentioned if you're > 50 miles from an office and within a 3 hour 1-way commute it's expected you go into the office at least once a month.

No one from my team is near the office I'd go to, I'd basically be working alone in an open floor style layout while I work remotely with my team mates in the same way I would at home.

Except now there's an extra 4 hour round trip commute and $65 cost ($40 train + 2 meals for a 14 hour day) per visit. Over the year that's $780 and 6 extra work days from travel time just to go in once a month.
If iteration speed is the main priority, I'd suggest you go with Django.

I've worked with Java and Spring/Spring Boot for years and while you can get most stuff done reasonably quickly, there are stacks out there that will let you iterate faster (Ruby on Rails, Python with Django/FastAPI, PHP with Laravel, Node with Express etc.).

Personally, in some cases I'd also limit the usage of Java/Django/whatever to the back end API (a boring RESTful one) and write a SPA in Vue to consume it, since it's powerful enough to get things done but not too much so to the point of getting in your way (e.g. React or Angular, personal preference, some people won't like Vue and will prefer Svelte, others HTMX, it depends). On the other hand, SSR still will be faster to iterate with, even with the coupling.

As for auth, I'd outsource to Auth0 or any other OpenID Connect provider. I've also self hosted Keycloak and use mod_auth_openidc to simplify it, but it was quite annoying to setup, so going for an industry standard protocol on top of whatever SaaS makes sense seems sane.
Takes a long while to get to any points..

> Chronic high carbohydrate consumption — especially of refined grains and added sugars — drives obesity, diabetes, heart disease and other metabolic disorders

Also, the article mentions saturated fats are over vilified.
Dot (YC S21) Is Hiring an Engineer to Automate Analytics (Remote)
https://www.tesla.com/megapack/design

500MW/1GWh of batteries will cost 254M USD (in California Q2 2025). Assuming a 10% revenue per year, and cycling once a day implies a storage cost of 24500000/365/1000 = 67 USD/MWh.
Not forgetting operational failures due to human mistakes when doing delicate stuff on complex environments, and setting up on-prem infra to work like a hyperscaler does... well, it's not easy.
It’s similar in Germany, where truck drivers regularly kill cyclists on right turns and get away with a four figure fine and (if the judge has a bad day) a few months of license suspension.
Wouldn't opportunities arise to where people live instead?

Things would just not be as concentrated in the areas surrounding commercial buildings.
I wish HN let us favourite comments, because I’d favourite this and then print it out and stick it on my wall. Really like this.
You can formalize vague instructions if you want to. Email them back with what you understood and questions.

Works for bosses and more importantly for customers who may not even know how to define the work properly.
Regardless of oem display cost, the new parts pairing feature in iOS 18 means no more loss of True Tone etc.
Yes, you could emulate an x86-64 CPU with SSE2 (aka x86-64-v1), but that is no longer sufficient for lots of modern x86 code. Windows 11 wants SSE4.2 at least or else it won't even boot.

As Arstechnica wrote, Intel specifically warned that they hold patents on emulating the more recent instruction sets.
It changed last week with iOS 18 release: https://www.macrumors.com/2024/09/11/ios-18-repair-assistant...
https://archive.ph/Z7eIg
At least for me, when I installed the Docker Desktop for Linux once, the docker daemon would not run again if the Docker Desktop was not running.
> you’ll have to manage to achieve SLAs like Amazon’s?

Aaah yes, those AWS SLAs that ....

- (a) Famously apply anywhere except US-EAST region which has a proven tendency to blow itself up on a scheduled basis
- (b) Are more marketing fluff than reality. A bit like the old Verizon leased-line 100% uptime SLA, nobody sensible who worked in IT believed it, but your boss was paying the Verizon-tax so that Verizon could afford to pay out some hard-dollars when (not if !) the SLA was inevitably breached.

I would also invite you to actually go read the AWS SLAs. The famous 11-9's S3 SLA for example[1] ? Barely worth the paper it is written on. The S3 SLA is silent on data integrity or any other data metric. It only covers you for 500's returned by the AWS S3 API, the "Error Rate":

"Error Rate” means, for each request type to an Amazon S3 storage class: (i) the total number of internal server errors returned by Amazon S3 for such request type to the applicable Amazon S3 storage class as error status “InternalError” or “ServiceUnavailable” divided by (ii) the total number of requests for such request type during the applicable 5-minute interval of the monthly billing cycle. We will calculate the Error Rate for each AWS account as a percentage for each 5-minute interval in the monthly billing cycle.

Also, its got the world's best get-out clause, the SLA only applies if you actively use the service:

"If you did not make any requests in a given 5-minute interval, that interval is assumed to have a 0% Error Rate."

So, yeah, give me a break about those "amazing" AWS SLAs. :)

Also what happens if AWS breach their over-confident SLAs ? Oh yeah, that's right, typical corporate style hand wringing, an apologetic sounding email written in corporate-speak and approved by legal, and that's that. Maybe a mea-culpa public blog post if you're lucky.

Also when you have your own datacentre, you don't have all the stupid nickle and diming of the cloud providers. The major cloud providers are particularly bad about it, all sorts of obscure "hidden" charges just waiting to bite you in the backside if you don't look carefully at the bottom half of their price sheets.

[1] https://aws.amazon.com/s3/sla/
Email at omni_vision_ai@proton.me
> The hard part is that you also need to build a cycling culture.

> You also have to change the regulations so that car drivers are (partially) legally responsible for accidents

This is all easy to create. It all starts with infrastructure. If you have infrastructure that is safe for bikes, you will create culture. You will also open up extra legal safeguards, but it has to start with infrastructure.
wish those images had individual captions instead of us needing to do work to figure out which image goes to witch caption
Oxide already showing up and eating AWS's lunch I see.

Seriously though, it does feel like above a certain company size you really do get into a position where, if you can hire the team to run it, on-prem just feels right. Especially if you're not even really in the "internet" business in the first place. Cloud is so costly!
> Make the best product possible

I disagree.

It's more of "Make a good enough product" with emphasis on trying ot yourself to see it's actually good enough. Finish up, try it out, then ask yourself "does this feel good to use?: or did you puncture your finger on some splinters?

The author has a successful business which he achieved following this mindset, so there is definitely merit in what he's talking about.

The author's main point is that too much of that data is shit, and thus following them will lead to shit.

This part is a highlight for me

> They’ll say “this user is 4.5% happy” and, okay, great. Now what? This numerical value sure is bullshit but it’s not even helpful bullshit because these numbers never explain why things suck.

> (Just look at the product and it will tell you why it sucks.)

And

> It comes down to this annoying, upsetting, stupid fact: the only way to build a great product is to use it every day, to stare at it, to hold it in your hands to feel its lumps. The data and customers will lie to you but the product never will.