skysight-inc/HackerNews huggingface dataset:
Gas stoves have several advantages over electric stoves. One of the main advantages is that they heat up quickly, allowing you to start cooking right away. This can be especially useful for tasks like boiling water or sautéing vegetables that require high heat.

Another advantage of gas stoves is their ease of control. The flame can be adjusted instantly, which allows for more precise cooking. This can be especially useful for tasks that require a consistent, low heat, such as simmering sauces or keeping food warm. This also allows for adjusting the temperature more quickly and easily than an electric stove, which can take longer to heat up or cool down.

Gas stoves are also generally more energy efficient than electric stoves. They do not use electricity to produce heat, which can save you money on your energy bill. Additionally, they do not rely on heating elements that can wear out over time, which can save you money on repairs or replacements.

In addition, gas stoves can be less expensive than electric stoves in the long run, because natural gas is generally less expensive than electricity. Another advantage is that gas stoves can be used during power outages, whereas electric stoves cannot.
The same reason your cell phone fell out of your pocket in the driveway before the trip. So that it never happened.

I think this is easier with bikes because there's more repair culture and more off-roading. Off-road bikes generally have all non-essentials stripped and left in a box, blinkers, odometer, fancy fenders...
That is a decent analysis.

This is also why the government tries to persuade people away from auditing the Fed, as it would be the nail in the coffin to the ongoing crime that has been perpetrated for the past 110 years: unchecked government spending would be impossible without the money printer at the Fed, and would collapse the military industrial complex.
> California is the fifth state to legalize the practice, following Colorado, Oregon, Vermont and Washington. Under the law, human composting will be allowed starting in 2027. The process involves placing human remains in a steel box with biodegradable materials, which help the body naturally decompose.

A steel box? What if I want a tree to grow out of my organs?
I was curious why it was a big deal either way for a smaller codebase/documents to use a monorepo or not. It's mentioned:

> You may be reading this short essay and thinking: "Yeah, no shit! Of course you do not need a monorepo when you're talking about, like, 150K lines of code."

> Maybe it's some abstract sense of purity; maybe it's because you didn't realize most IaaS let you deploy from a subfolder. Whatever the reason is: trust me. Move it into a monorepo. If you do and you end up regretting it, [email me] and I'll donate to the charity of your choice.

So the new thing being said here is that a monorepo makes sense even at smaller scales. This seems to on the far other end of the scale with a main app, supporting infra, docs, marketing, etc.

I've certainly used fullstack repos with backend and frontend together and it's fantastic to use and deploy from commits. I can't infer from this article or my experience what it would be like to work with a monorepo at medium scale say 10-100 apps with 10s of teams. That would take more adaptation than simply "deploy from folder". Dependencies as mentioned in another comment and being able to detect if each target should be retested/deployed seems like the tough one.
Could easily be fraud depending on what’s being said or implied.
Well, I started as an electronic technician, then progressed to EE, then firmware, then software, etc.

At one time, I could tell you what every FET junction on a microprocessor was doing.

Those days are long past, but the basic knowledge helps me to write really robust, harwdware- and server-connected software.
But the tool that jepsen uses to check whether a schedule is serializable would still be useful for any database that supports concurrent operations.
aging population, lower birth rate, zero interest policy, QE policy, massive debt, have been thing since 90s-00s
Paywalled but I agree about the appeal of opinionated articles written by experts - basically the antithesis of wikipedia.

Encarta was another cool pre-wikipedia thing.
While temperature of boiling water has mostly academic meaning for everyday life, freezing point is much more important. I would say the most important temperature point for us humans. That point affects driving, walking, taking care of pipes, outside plimbing, plants, etc. Everything else doesn’t have to be that precise, 20C or 25C doesn’t make much difference. But whether it’s +2C or -2C could have huge impact.

Because of that it makes sense that it’s zero instead of some magical number that you have to compare in your head. I’ll take zero as a win for Celsius.
It’s always easy to say that in hindsight. But keep in mind this is an environment with many core components built in the 80s. Regular reboots on old AIX systems wasn’t a common practice - the sheer uptime capability of these systems was a big selling point in an environment that looks nothing like a modern cloud architecture.

But none of that is really the point. The point is that even with every correct procedure in place, you’ll still encounter failures.

Modern dev teams in companies that build software have more checks and balances in place from the get go that help head off some categories of failure.

But when an organization is built on core tech born of the 80s/90s, there will always be dragons, regardless of the current active policies and procedures.

The problem is that the cost to replace some of these systems was inestimable.
Honestly, if it weren't, what would you even do about it? Do you really have the time and resources to pursue it? Did you suffer damages from such?
i recommend active voice over passive. i also tell students to strive for clarity.

"don't write like you have a pole up your ass."
Report finds Psyche mission endangered by culture issues at JPL
>Telling a lie or pretending to be someone is not a crime or illegal in civil law.

It should be. Times have changed, and now it is possible to impersonate someone "perfectly". This has a negative impact on both the one being impersonated and the people that are being lied to. It is a form of fraud. The requirement to connect this to actual damages is an exercise. An exercise lawyers have convinced a population of scared, ignorant people, demands $300/hr to complete. Let me put it simply: you cannot speak as me, and if you do, you're wrong and should be punished.

Now, maybe it's not the law, but it damn well should be. It seems common sense to me. If you cannot imagine the consequences of allowing an employer to impersonate you (especially in the age of AI), then I will say you lack imagination.
He makes a ton of money, but if we look what he’s accomplished since he took the helm at Apple, I think it’s fair for him to be immensely compensated.

Many thought Apple was dead when Jobs passed. What Cook did is nothing short of phenomenal. I’d argue he did better than Jobs would have done.
I don’t understand the reason for the triple cost for curtailment. Like it seems the obvious options would be:

- pay $x for y joules of wind

- pay $x for y joules of gas; ask wind farm to generate y joules less and pay them $x +/- epsilon for the lost income. Total cost: $2x

I would have guessed that if you’re a big generator then your national grid contract would say something like ‘you turn off when we say so but we’ll pay you for lost revenue.’ I don’t understand why the wind farm, according to the article, is paid twice, both for the energy (not) being generated and to turn off some generation?
Royal Mail hit by Russia-linked ransomware attack
My Life as a Disagreeable Giver (2017)
Also worked for the food pyramid...
I was just thinking about video games where vegetation, animals, and hills spring into existence when you get close enough. Far away, and they don't bother to render the little things.

Depending what generation tech we're running on in the parent reality, JWST may be causing a noticeable jump in system load.
It really would depend on the quality of the work/paper. I bet mis-identification by humans of hand written or generated abstracts goes down in higher tier conferences vs. lower tier ones, since the writing standards in lower tier conferences can be pretty bad (well, in CS at least).
The default assumption should be that the solar system is typical and that would lead to numerous earth-like planets in the galaxy and that would give hope to a lot of (intelligent) life. But untiol a few years ago, this was just a very plausible explanation. Since then we have confirmed thousands of planets. So while there are still a lot of unknowns for a good prediction, the planet count is at least consistant with the assumption, that solar-like systems are not an exception.
> how do you get over the embarrassment of how ugly your keyboard is

Step 1: I don't get embarrassed by something that is functional.

Step 2. I don't get embarrassed by something that isn't ugly.

How do you get over the embarrassment of not being able to work and play as fast as the people who have a functional numpad?
So the rest of the UK essentially subsidizes the electricity price to South East England, is that correct?
Please explain the food pyramid?
For the most part, I only hear from typescript when there's a type mismatch.

Understanding the type mismatch is ofter difficult, but it does solve a real problem.

I also like that it gives escape hatches, for when I know what the type should look like, or I don't care what it looks like

I haven't found the typescript updates to be difficult, nor situations where packages I'm depend on require incompatible typescript versions

My pains are on that it's hard to get the setup right where you aren't depending on a giant set of types packages, giving you size bloat for things you mostly don't care about.
I always find monorepo/polyrepo discussions tiresome, mostly because people take the limitations of git and existing OSS tooling as a given and project those failings onto whichever paradigm they are arguing against.

I'm pretty excited for new OSS source control tools that would hopefully help us move past this discussion. Particularly, Meta's Sapling[0] seems like a pretty exciting step forward, though they've only released a client so far. (MS released its VFS for Git awhile back, but unfortunately now is deprecated.)

[0] https://engineering.fb.com/2022/11/15/open-source/sapling-so...
> you need a way to distribute them all which is super annoying

Only if your tools are bad. In the stack I'm used to they're just another artifact that gets published as part of a module build.

> Additionally, in some cases there isn't a clear single owner of a particular IDL struct, for example let's say you have some date or time struct that many protobuf messages want to use in their fields. Which service do you define it in?

A common library, just like any other kind of code.

> Ignoring that, it is REALLY USEFUL to be able to modify the code for the producer of a message and the consumer of a message all at once, without having to make multiple commits in multiple repositories. This is especially true when it comes to testing. I have thing A producing a new field X, I want B to use the new field X, and I want to test that B uses it correctly. When everything is in one repo this just works, with multiple repos I need to first add the code to thing A, do a release of A (even if that's just making and pushing a git commit), then update B to consume the new thing and add the test, then if I realize I messed something up I the new version ofneed to go update repo A again to test it, and so on.

That's actually really important because it forces you to test all the intermediate states. If you can just change everything at once then you will, and you probably won't bother testing everything that actually gets deployed, and so you get into a situation where if you could deploy the new version of A and B at exactly the same time then it would work, but when there's any overlap in the rollout everything breaks horribly.
You might not. But at least you have the option not to do that.
I don’t know, I heard housing is really expensive in the Bay Area :D
CRISPR for high cholesterol: 10 Breakthrough Technologies 2023
It's well known that us-east-1 (the very first) is a pet among AWS's cattle regions.

It has failure modes that none of the other regions have.
This might be the first article I've read where Node's module resolution algo is touted as a benefit.

Just how complex is your command line app if you need to have multiple transitive versions of the same library?

Coming from the same company that is so heavily invested in Ruby that they contributed to a new JIT for it (YJIT), built a static type checking layer (sorbet) for it, and built a module system that prevents you sharing code between those modules (packwerk), etc.

Unrelated but it is reminding me of my attempt to integrate with Zapier. Zapier doesn't document an API anywhere, you have to use its 'CLI app'. The CLI app of course just calls undocumented HTTP APIs behind the scenes.
I believe the author's point is that you should care about the relation between your technical decisions and actual benefits for the user. It is true that many technical people develop an appreciation for tech choices that is driven by aesthetics more than by actual impact.

That being said, caring too much about customer success also has its pitfall, businesses can be driven by the present more than by the future, and by low-impact guaranteed results more than high-impact hypothetical risks.
It's not. Supervisors and managers have the right to request access for business continuity purposes. They have to carry any business in-flight to its conclusion. Of course audit logs will show how access an account when and form where, etc.

People have to remember, these are business accounts, not personal accounts and all their content belong to the business --which is why one should avoid using business accounts of any type for personal use.
Paizo Announces a New Gaming License Amid Dungeons and Dragons' OGL Controversy
I've had the exact opposite experience. We have a polyrepo setup with four repos in the main stack (and a comical number of repos across the entire product, but that's a different story). My top pain point - almost painful enough to force a full consolidation - is trying to find the source of a regression.

When semi-regularly discover regressions on production and want to know when it was introduced. Any other project I've worked on, that can be done with a simple git bisect. I can tell you that trying to bisect across four repos is not fun. If everything were in a monorepo, I would be able to run the full stack at any point in time.

Now, if all your APIs are stable, this won't be as bad. But if you're actively developing your project and your APIs are private, I can only assume this pain will be ever present.
Something I needed to hear when I left my first company: you lose all battles you were fighting, you lose all investment in the work being done, you lose everything you've built when you leave. Just let it be, it's part of life.

This is not important now, it won't be important in a week, and you won't remember this in a year.

Look forward.
Typescript is significantly better than java imo, in that it can figure out what the right object shape is on its own for the most part, rather than needing to write another file for every intermediate data object in a process flow
Loss of epigenetic information can drive aging in mice
By knowing the weight of similar Ford trucks, we can better see why the weight of the Ford Lightning is what it is.

The Ford Lightning is heavier because it is an electric vehicle.

Below are some of the weights as well as the dimensions of Ford F150’s throughout the past few years.

The weights shown do not include every year of the Ford F150.

And when averaging every year of the F150’s weights, the average comes out to be around 5,400 pounds.

2010 F150 – 5,600 pounds, 229 X 71 X 77 inches
2011 F150 – 5,625 pounds, 228 X 70 X 76 inches
2012 F150 – 5,665 pounds, 227 X 71 X 75 inches
2013 F150 – 5,700 pounds, 225 X 73 X 77 inches
2014 F150 – 5,715 pounds, 224 X 74 X 76 inches
2015 F150 – 5,730 pounds, 223 X 78 X 79 inches
2016 F150 – 5,745 pounds, 222 X 70 X 78 inches
2017 F150 – 5,760 pounds, 221 X 70 X 80 inches
2018 F150 – 5,780 pounds, 226 X 76 X 70 inches
2019 F150 – 5,790 pounds, 227 X 78 X 73 inches
2020 F150 – 5,815 pounds, 228 X 79 X 75 inches

By looking at the recent Ford F150s we can see that slowly more and more weight was added on the vehicle, the Lightning however was a considerable jump.

This jump is also understandable, however.

The 2020 F150 comes stock with a 5.0L V8 which weighs around 450 lbs and a transmission weighing around 250.

If you subtract 5,815 lbs by those you will get 5,115 lbs.

The Ford F150 Lightning has a battery pack of around 1,800 lbs, and if you subtract 6,500 lbs by that, you will get 4,700 lbs.

These are not the only differences in the trucks but just some of the heavier ones.

2020 F150 at 5,815 pounds vs. Ford F-150 Lightning at 6,500 pounds - 6500 pounds − 5815 pounds = 685 pounds

See: https://gearandcylinder.com/how-much-does-the-f150-lightning...
Close it how? I just closed the window. What's the handle, then? Do I have to open it again to go to some menu (or a shortcut) to close it?

This is completely unintuitive, unless you are a long term mac user. Neither windows nor any of the hundreds of linux window managers work so unexpectedly.
>the fault of a single-lane rear end collision is always the fault of the following vehicle.

You are just plain wrong. Tons of people who thought they were "right" like you have gotten rear ended by doing things like putting on a blinker, slowing for a turn and then at the last second getting back into the travel lane in time to get hit by whoever was behind them. Or they stopped in the travel lane on a blind for some dumb reason and some trucker traveling at/below the speed limit (and with the data logging to prove it, because that's how commercial trucks are these days) comes along and can't stop in time. Or they pulled out in front of other traffic and didn't accelerate appropriately (I hit someone that did this once, they paid).

> Always. if they were following at a safe distance, they would necessarily have had time to stop. that is what it means to follow at a safe distance.

The world doesn't run based on this circular logic.

Insurers are quite reasonable about this sort of thing. They all know that they all win if the more deviant driver pays and winds up with the black mark on their record.

Moreover, while you may very well dodge financial liability because the other guy can't prove it was your fault, the responding officer may very well read between the lines and issue you some sorts of moving violations that you can't dodge with court and will have the same effective net financial result.

>“refrain from personal attacks” no. they earned what i said.

Well since we're going there...

It is really a shame that drivers of your bent don't more often cross paths with someone prone to violent road rage. Society as a whole will benefit if two bad actors wind up off the roads in a "papa loved mamma" sort of way.
No one thought Apple was dead when Jobs died.
makes sense. crestone has an interesting sense of spirituality about it. it’s about 30 minutes north of where my family is from and i went there with a group of friends to see what it was all about

https://www.uncovercolorado.com/things-to-do-in-crestone-co/
It literally drives me around every day. Seems pretty good for a product that is "not available".
USC is removing the word “field” from the curriculum
I did a lot of paper doctoring when I worked in a foreign research lab, and I can agree a bit. But conference standards would push for good writing if the conference was good enough, and bad writing would be grounds for rejection (or at least heavy shepherding). So the easy conferences would get a lot of bad writing and the really competitive conferences would get much better writing (or the papers wouldn't make it past the crap filter in the reviewing round).

But first you need something good to write about, and a lot of papers fall short at that point. It doesn't matter how well it is written at that point (getting the "this is well written, but not interesting" rejection is painful but usually obvious).
Hmm, seems like the linux foundation is a nice retirement home for ex corporate projects that are popular enough that people feel sad seeing them die, but not actually popular enough to live. (See RethinkDB)
'80s VHS Sold for $80,600 After YouTubers Said They Destroyed 100 Copies
Since everyone is mentioning their favorite whacky theories, mine is the one that says within every particle is a whole universe, made up of particles with their own universes and so on, and what we call our universe is really just a particle in an even bigger universe. And what if all of those universes were actually the same universe, like some infinite recursion?

Is there a name for this?
Putting the photo of the woman on a toilet in the article seems a bit dubious even with the face obscured, particularly given that this is an article about lack of consent.
You need to parse and/or validate any external input before you declare that a variable or field is a certain type, as you probably should be doing without Typescript anyway. Being strict in what you accept and ensuring that you're not lying to the type checker solves the vast majority of these types of issues.

It's been a few years since I worked with TS professionally, but at least at the time, I saw it as 95% value, 5% BS. It provides such plainly obvious value in my eyes that I've decided I'll never write JS again unless it's a single file script or a small throwaway project/PoC.
This is huge. Like, is this legal? Is it ethical?
I have to say, I really enjoy using Google monorepo and all tools available to me.

Having said that, it's not free of course. There are many engineering teams and computer power being invested to provide this environment to all googlers.
It seems that you are proposing being even more fearful and taking a more conservative approach due to lack of information. If I followed your advice, I would never leave the house for fear bullets.

If I want more detailed information on a bridge shutdown (which is available), your recommendation is to suck it and just go by whatever erroneous prediction google gives.

It seems like you providing contradictory advice:

1) Always take the most cautious approach to your environment. (if you see cops:hide, hear shots: hide)

2) Don't pay attention to the live crime feed for more information.

The problem is that the live crime feed adds meaningful information to the environmental data for me.

I guess we disagree on what information I find useful: Whether that is the nature of a traffic jam so I can plan my drive, or how often people get shot in my neighborhood.

This strikes me as a position hostile to information, knowledge, and learning.
My interest in not publicly available models is very limited.
I'm not sure I understand how that scenario would arise with a monorepo. The whole point of a monorepo is that everything changes together, so if you have a shared internal library, every service should be using the same version of that library at all times.
>> IMO the biggest drawback to a monolith

Mono-repo and monolith are orthogonal concepts.

>> I'm pretty staunchly in the "one service, for one deployment artifact, for one CI pipeline, for one repo" camp

This seems reasonable if nothing is shared. If there are any shared libraries then you are back to binary sharing (package managers, etc.) with this approach.