skysight-inc/HackerNews huggingface dataset:
Your reference for [1] just states that bypassing the turbine is a thing, not that it's normally used.

First, reactors are in a stable equilibrium when operating, so one will actually increase their power by increasing the rate at which heat is removed (and v.v.). Alas, that's workable only within some small range.

A reason[1] load-following with PWRs was originally difficult is that traditionally PWRs use boron concentration in primary loop to regulate power and that can be decreased only slowly. The reason it's done that way is that it's the easiest way to ensure that power is adjusted uniformly throughout the core; if instead some control rods were partially inserted, the top part of the core would operate at lower power (and thus lower fuel burn-up) than the bottom part, which would cause compounding control issues later on.

France is using their PWRs in load-following mode by (a) having additional less absorptive control rods ("gray rods") that can be inserted fully to adjust power by smaller increments (b) more complicated schemes to decide which combination of available actuations to use to change power. See https://hal.science/hal-01496376/document for a paper that tries to optimize control designs so that power changes are more possible (and describes how the control schemes work).

Note that the total heat capacity of even just the primary loop in usual reactors is quite large: in PWRs it usually requires ~0.5s of full power output of the reactor to warm it by 1degC, so this can easily cover, say, ~5% variations for something like a minute.

[1] Another is that reactors are not stateless due to xenon poisoning.
https://hpbn.co/ is a good resource on protocols.
But that's just that one scenario you've described.

It's also common that if you have a dozen repos that maybe only one has changed and so when there is a defect it's trivial to determine what caused the regression.

I don't think mono or poly repos are better when it comes to triaging faults. They each have strengths and weaknesses.
If you haven't used high refresh monitor. You probably won't notice the difference. But after you do it once, there is no way to go back. Just like high resolution monitors.

Mouse and scrolling feels so much more smoother on a high refresh rate monitor. To the point if windows messed up the refresh rate, you can instantly feel it.
That's if you don't consider having rootkit-like Google play services as a threat vector or don't mind its impact on the Privacy/Battery backup in the first place.
sure, and i knew the pedantics would beat me up over it (maybe rightly so, but i tried to use a number hyperbolically to make it obvious). however, it's not the full resolution of the chip. hence the use of monochrome chips for "full" resolution.
Amazon’s tech stack did become the product
I'm 100% fan of high refresh rate on smartphone, because smartphone UI is aimed for scrolling forever. Difference between 60Hz vs 120Hz is night and day.

So then I replaced a PC monitor from 60Hz LCD to 144Hz 4K LCD, I expected such difference before buy. After setup, I can find difference but don't find much difference like smartphone. I don't scroll so much on bigger screen PC, and maybe I'm too used to Windows' crappy scrolling. Anyway my mouse has classic wheel so non-smooth scroll is fine unlike touchscreen/trackpad case. Mouse cursor isn't smooth but it's just that. Finally I bought second 60Hz 4K LCD after that because it's cheaper, it's fine.
As you scale a small company its exceedingly rare to not need 10 root canals along the way. Meanwhile it's exceedingly common to need to pivot quickly even if it comes at the cost of near-term engineering rigor.

I feel obliged to point out that I work at a company that uses a monorepo, so this isn't a "never use monorepos" counter-post. Instead my points are borderline tautological:

There's a balancing of near-time sacrifice vs long-term sustainability. But you need good reasons to pick the side of the scale that historically got less resources invested into it and puts an impetus on your engineering team to adjust to the knock on effects of that disparity while still building a fledgling company.
Ah yes, the old "if FAANG does it, it must be right" argument. You love to see it.
1. There has to be some gems on there, surely.

2. Never heard of it. Will look into that.

3. Because this guy is coding for other WooCommerce shops, making me worry about other people’s shops - if I was more trusting an naive, I’d have ran this on my site. If the dev doesn’t understand security, maybe my intervention could help him and his customers businesses.
It depends on your architecture.

If I have a services based architecture then I can jump straight to the repo for that particular service and have confidence that it is the code that is running.
Agreed. Love the size and aspect ratio, I just wish it was a bit higher resolution so I could use 200% scaling.
That's becasue the other goal would be way longer term. But it's not a bad goal to use a complete replacement if they could get resources for it.
Trial settles debate over best design for mRNA in Covid vaccines
It sounds like you really want to say, "people who care about pronouns[trans people] do so because they are narcissistic," but you really don't want to because you understand the implications of such a statement. Personally I think the idea is abhorrent, but correct me if I'm wrong about you.
See https://news.ycombinator.com/item?id=34309306
Ask HN: Tech Stack Visualization / Monitoring Tool?
Same as title. As a full stack web developer who sometimes procastinate my full-time job to create my personal projects, I wonder if there are any tools out there to visualize and monitor my tech stacks. I want it to be as lightweight as possible, and quickly see the server status (sometimes simply down or up) at each layer (e.g. front-end, back-end, database etc)

I have seen the tool CloudCraft, but it seems to only work with AWS, but I’m running my stacks almost entirely on Netlify / Vercel, so it’s of no use to me.

Any input is hugely appreciated!

(BTW thankfully some users suggested Grafana and DataDog last time, yet I would prefer the tool to be as easily visualized as CloudCraft, as most of my apps uses a pretty straightforward MERN stack)
Have, like, ANY of these state corporate boons actually worked out?
How often do people use Elasticsearch without Kibana? I would use something that empowers Kibana's amazingly powerful UI, but like you called out, that would need to be "binary" compatible since Kibana is expecting the Elasticsearch API.

> (Kibana is not supported with zinc. Zinc provides its own UI).
haskell,
ocaml,
golang,
rust,
functools python,
erlang,
elixir,
sql
The funny thing is that since we've been observing the universe for so little time, and we're so small, most of the evidence for the big bang and expansion is not direct, but a chain of deductions.

I mean that we can't observe the expansion because we can't really triangulate at galactic scale. If there is another reason the light from distant galaxies turn to red, kind of a long-distance light fatigue, we couldn't really know.

The reason I always heard that would be a confirmation, because it comes from a different causal path, was precisely the different composition of old galaxies. And now it seems they're not so sure.
> I was frustrated with what I thought was a poor interface for Kibana

I can't think of a better/more well done user interface than Kibana. Am I missing something?
Right, foolish Meta paid $19.0 billion for it when they could’ve had an intern hack it up on the weekend
> Right. The "once in X years" reporting is always exaggerated, by subtly constraining it to a specific geographical point.

Not really. You got it exactly backwards. The return period of an event is determined based on all recorded events. This does not mean that massive events that took place in the past didn't existed if no record was kept. Consequently, massive events are underrepresented both in magnitude and in frequency, and consequently estimates of their return period tend to be larger.

Think of it this way: the concept of the return period of an event (i.e., this is a one in X year's event) is determined based on the average time between similar events.
Problem is which foundation to learn, for software is learning cpu pipelining foundational? machine or assembly, or compiler, or C or C++? and also depending on what you are trying to too.
The owner of Kiwi farms also had his personal phone number terminated despite presumably not engaging in any illegal behaviour on it. I don’t believe you can do a number transfer when you get banned either.
Now that's pretty funny.
> dozens of repos, and they all have separate CI needs and test suites

Standardizing all of this is one of the advantages.
Last I heard the goal of servo isn't to have an actual browser, but basically build an engine that can be used somewhere else and that all the "good stuff" from Servo goes into Firefox, basically.
In the Netherlands they are going to build two new nuclear power plants but the company wants assurance that they don't have to compete with the massive wind mill parks on the North Sea.

Not really a new problem for the Netherlands whenever there is a problem the country tends to overreact with massive infrastructure spending. It hasn't been that long that brand new coal power plants had to be closed.
You're moving the goalposts, but keep on digging I guess. I suppose your anecdotal and theoretical stories trump Tracy's lived ones and mine as well. No reason to continue this discussion.
I strongly agree with #1 and #2 and that is why I like typescript. It keeps things simple for me. I can look at what a function's inputs and outputs are without having to guess. I don't have to worry about having an array of strings and then someone deciding to throw a boolean in the middle. I know what all the keys on my object are and what kind of values they will contain. Code I have never looked at I can quickly figure out the structure.
Rare had many teams working siloed and independently. The team that made Diddy Kong Racing made a custom microcode based heavily on the official Fast3D with several differences. This microcode was updated and used in that teams next N64 games Jet Force Gemini, and I believe it was also used in their next cancelled game Dinosaur Planet, which later was released on GC as Starfox Adventures. I'm reasonably certain it was used in Mickey's Speedway USA as well, but I'm not certain.
If you post a paywalled article please have the courtesy to post an archive link or workaround. I wish this was built into HN like it used to be.

https://archive.is/B9zT6
I was randomly banned from Telegram once for a month. My meta account also strangely got banned from advertising yesterday despite me hardly ever using the account and never having advertised before.
> Servo’s mission is to provide an independent, modular, embeddable web engine, which allows developers to deliver content and applications using web standards.

What is the business use case for this?

As in, if each of those people costs $100k/yr, that's $400k/yr+

How will this product make (whoever is paying for it) money (profit)?

If that answer is "it won't, not everything needs to make money", that's totally fine. Could you then explain why this company is willing to shell out at least $400k/yr to have 4 people work on it? What do they get out of it (if not money)?
There was a lot of rewriting stuff to make the engine GraphQL-first. Before, the engine received a different spec as input, and GraphQL worked behind an adapter. Now, the engine speaks GraphQL language.

Then completing the GraphQL schema, fully complying with the spec, and adding all the new features. That was quite a bit of effort.

Yes, there were many "typo" commits, changing simply one word. But there were also plenty of commits with dozens of changes and, in the initial rewriting stage, even hundreds of changes.

It really took 16k commits. I'll write a blog post on graphql-api.com and provide some more info (maybe sometime this weekend?).
Love this article. Thank you for sharing. Read it and felt seen and less isolated as I reflect on some of my own similar mistakes. My colleagues loved it too!
Yeah if you punt the complexity to run time you can burn run time cycles instead of compile time cycles. Make your user pay to run your code instead of your developers. Go is more anti-end-user than Rust.
It is an important discussion to have, but too much religion is brought into the discussion. There is not god that will be after you for a bad choice.
Not necessarily instantly, but our CD is fast enough that changes are in production 5-10 minutes after hitting master.

But what's more valuable is that our artifacts are tagged with the commit hash that produced them, which is then emitted with every log event, so you can go straight from a log event to a checked-out copy of every relevant bit of code for that service.

Admittedly this doesn't totally guarantee you won't ever have to worry about multiple monorepo revisions when you're debugging an interaction between services, but I haven't found this to come up very much in practise.

Edit: I should also clarify, a change to any internal library in our monorepo will cause all services that consume that library to be redeployed.
Would be awesome!
I've been getting more and more into the idea of we've lost a lot of knowledge (whether truly understood or just accepted) of plants and their benefits. I have been more and more disillusioned with Big Pharma and the bullshit games they play. I am not willing to throw the baby out with the bathwater as modern pharmacology has brought us some great things. But they are definitely guilty of some super shady shit to the point of my disillusionment and learning that a lot of what they do can be found naturally (if not as well refined).

So the moved too far past rings true to me
The scientist behind the study has both a book and podcast called Lifespan. They are both focused on the epigenetic cause for aging and solutions to slow aging. There are several supplements that the researcher believes will slow aging. The study above is more confirmation of the problem he identified, not a brand new discovery.

Cutting to the chase, David Sinclair (the scientist from the article), thinks resveratrol may reverse aging. NAD, which the body produces might also reduce aging. The theory around producing more NAD is that you can actually supplement with the precursor to NAD which is called NMN.

If you are really interested, there is an email in my profile. I listened to the entire podcast twice and took a lot of notes. Email me and I will send them.
My understanding is that the standard model likely does predict static electricity, but since it's a phenomenon bigger than a few molecules, we have no way to actually run the simulation. The physics is willing but the computers are weak.
Banning construction of wind farms on all of England is possibly the stupidest governmental decision I've ever heard of. This entire problem would go away if they had just allowed some wind farms.
It is absolutely a correctness issue. Panics do not provide safety guarantees that generalize enough that it is safe to arbitrary recover from them. The statement in the previous sentence is not a subjective opinion, it's a statement of fact. I'm not sure how else to convey this information.
3 is greater than 0.
"Maybe it's some abstract sense of purity"

Someone gets a few lines of code under their belt and now they overwhelmingly know what is best for all.

It's simple, if it gets released together, put it in the same repo (even if it's a big repo like the Linux kernel). If not, separate it out so you can stay sane.

If it's not released together then it's a monorepo, also defined as a big ball of spaghetti.
I think they're being sarcastic.
check my response above
Almost all of those PRs are made by bots for updating dependencies
Classic Rick Beato - shitting all over modern music for no reason. I understand that he doesn't like it - fine. I don't listen to much rap, but I can still understand it and appreciate it for what it is. Rick is smart about the music he knows and grew up with, but he's a moron regarding the music he doesn't know. It's literally the stereotypical "music was better back in my day, modern music sucks". He should know better; he's from the generation that remembers the days of "all rock music is the music of the devil". The idea that "modern music is shit" has never been true, it isn't true, and it never will be true. There are far better music YouTubers out there, don't bother with Rick Beato.
I read a John Lilly book about 30 yrs ago and then made a mental note to revisit, so thanks for the reminder
The problem is pricing, which directly affects demand. Obviously, if there was demand, the factory would be humming.

$55k for a solar roof which is 2-3x a panel setup? This system is not 3x better and doesn't represent a fundamental shift (like Starlink).

There are lots of people who want solar, but my guess is very few are willing to pay even +25% to make it "look seamless", let alone 3x. That's the primary benefit, "looking seamless", and that's not a mass-market selling point. That's a luxury, so the market is tiny.
SMS needs to stay. It works without functional data unless some carrier really screws the pooch. I’ve had to revert to it numerous times at random especially in BFE to get in contact with a client or my wife etc. no data? But signal? SMS.

Otherwise anyone I wanna chat with I have on Telegram. Heh
personally I don't think there is that much value in society in endlessly vendoring exactly the same code in various places. This is why we have checksums!

I understand that Google will do this stuff to remove certain stability issues (and I imagine they have their own patches!), but I don't think that this is the fundamental issue relative to practical integration issues that are solvable but tedious.

EDIT:I do think people have reasons for doing vendoring, of course, I don't think that it should be the default behavior unless you have a good reason.
Would be nice if google3 as a service were a thing.
The software is good, but your point is about the flight model. The flight model is all about tuning. That was not my area but I watched it being done. It started with curves from the flight testing program and then many hours of trial and error parameter tweaking until the test pilot said that it was right. I saw a session in the middle of the night where the engineer tweaked, the pilot said it needed a little more, the engineer undid the tweak and the pilot said it was perfect. I also saw some Air Force pilots in a C5 sim (they were commercial sims) who could tell if the model was right by judging when they passed over the (simulated) highway in Dover, DE for a given engine setting. They were right, according to the engineer.

The point is, if you spend enough time on [1] you can tune the model. No one spends that much time on the MSFS. But for logic based stuff, like the working title VNAV implementation in the CJ4 it’s just a matter of understanding the expected logic and implementing. It is very impressive stuff.

[1]https://docs.flightsimulator.com/html/Samples_And_Tutorials/...
This is kind of a fascinating idea - wouldn’t it be kind of an amazing “public service” to just deploy a large reflective perfect sphere into space at the galactic restful reference frame?
yes (in oracle - at least the early 21st century version I'm using you have to roll your own boolean-ish - traditionally char(1).
Show HN: Vent: Anonymous Topic-Based Microblogging
This is a new social network that takes a different approach to anonymous and short-form social networks like Twitter and Reddit.

It is built using Golang and Sqlite. Its purpose is to encourage short posts, or quips, grouped together by topics. It also encourages posting in the face of shyness or unsureness, as posts are anonymous and they can be deleted any time.

I took a lot inspiration from Hacker News as well. In spite of its associations to the aforementioned social networks, I think that it brings something genuinely new to the table.

If Vent (name subject to change) seems interesting to you and you would like to work on it with me, please reach out at lafuentemercado@college.harvard.edu.

Somewhat related: I am recent graduate from Harvard College in Applied Mathematics and Computer Science and am seeking full time roles in software/tech.
Rather than scrolling through the obligatory endless speculation in the comments, I encourage all of you reading this to open up the section entitled "Long time coming" at the end of the article, and reflect on the fact that worthwhile science is hard and takes a long time to do, and nearly every incentive in academia or industry works in opposition to this.

How many other teams could we get working on projects in this field, were it not for funders preferring less risky but far less valuable studies?
It's definitely surprising, for a couple of reasons:
1. It isn't just the uninteresting result that the set of trees has the same cardinality as the set of 7-tuples of trees; the bijection here is given by a finite, non-looping program built out of `isEmpty : Tree -> Bool`, `getLeft : Tree -> Maybe Tree`, `getRight : Tree -> Maybe Tree`, and the constructors `empty : Tree` and `join : Tree x Tree -> Tree`
2. It isn't true for any number 1 < x < 7
3. In any case, why should it work out exactly? Why not "one tree can be encoded into seven trees, or one of these 13 remaining cases"?

The paper is quite good, but Dan Piponi has a great blog post that recasts the isomorphism as a game of "nuclear pennies", which is a fun puzzle to work out yourself: http://blog.sigfpe.com/2007/09/arboreal-isomorphisms-from-nu...
> on any real life project

Could you elaborate on what the barometer/measuring stick for what makes a project real life?

I think I know what you mean. Bigger than ____ lines of code/files I'm guessing?

X number of classes/interfaces/APIs?
I’m getting Flash flashbacks. Flash apps had filesystem access in a designated area, with some amount of user control, that is not easily wiped from the browser; Flash games used that for saves and data. Years after the demise of Flash, the web platform is still catching up.
We should run these tests on capybaras.
> The entry for Christmas in this set calls it a pagan ritual. More recent editions no longer refer to it that way.

Ha! That's fascinating. And true of course.
One has to wonder if the fixed costs of some kind of electricity -> fuel production will ever get cheap enough to solve this problem. If it would pay, it would be great for there to be a factory on stand-by to make, e.g., hydrogen or ethanol using the extra energy.
> raising fears that the fragile U.S. economy could be rattled by a calamitous self-inflicted wound

If the article starts this way talking about having a _balanced budget_ it's hard to trust anything else they say. Borrowing ever larger sums of money from foreign creditors will be the fall of the republic, not fiscal responsibility.
Yeah, Tesla's core lifeline for years was state-level ZEV credits, not to mention the various EV subsidy schemes.
>what THE HELL do you think "single-lane" means? your example is not a single-lane scenario, is it?

Have you ever actually driven on two lane (one in each direction) roads?

Whether you have or haven't I'll have you know the normal way things work is that someone slows for a turn (usually crowding to the right if their vehicle length and nature of the turn permits) the person behind them crowds toward the center line and passes them just as they're turning in. If the person turning aborted without warning at the last second and got into the middle of the lane it would necessitate some serious braking by the following person and maybe cause a rear ending depending on the speed of the road. Nobody is changing lanes during any of this.

Please never drive. You don't understand how the roads actually work in practice.