skysight-inc/HackerNews huggingface dataset:
> If I chuck a baseball out of an airplane I don't have to worry about accelerating the baseball to the airplane's speed, as I am also traveling at that speed.

But the speed of the baseball you just thrown out will be (ignoring air friction) that of the airplane +/- 40 m/s, assuming you're some super strong thrower.

> if a satellite is light enough in low-G

Microgravity doesn't mean the satellite is light now. It still has the same mass, it's just that you're both in free fall, so it doesn't pull away from you. For the purpose of throwing it, the satellite is just as hard to throw as it would be on the surface of Earth.

But even assuming it weighs as much as a fastball, when you throw it super hard, you'll change its velocity by... 40 m/s at best. Compare that with the orbital speed, which is many kilometers per second (e.g. about 7.6 km/s if you're on ISS). So e.g. instead of going 7.6 km/s, the thrown satellite now goes... 7.56 km/s. Which translates to one end of the orbit dropping by a couple hundred meters. So instead of 408km, it'll now go as low as... 407.5km, or something in that ballpark.

That's the limit of what you can achieve by just tossing things with muscle power.
What makes you think lowering the number of immigrants coming in would lower the prices of housing? Any thesis around it?
> Before you were saying it isn't a problem at all

It isn't a problem - I was responding to what you thought was a problem - having to bump multiple times in loop - that's what you asked me about? The bumps are tiny to start with, but even from that tiny start point they still get collapsed. You said collapsing them was important, so I showed you how that also happens.

> as I keep saying, anyone optimizing software knows that lots of small allocations are the first thing to look for

In some cases I've made code faster by putting allocations back in that other people removed without enough context on how allocation works and based on cargo culting of allocation being simply bad like you're pushing. Sometimes allocation is much better than reusing existing allocated space, due to reasons of spatial and temporal locality, cache obliviousness, escape analysis, publication semantics, coherence and NUMA effects, and more.
That's not what the post is claiming.
On one hand, it's hard to imagine a craftsperson considering the life of a piece beyond the life of the craftsperson themselves.

But I suspect a craftsperson is first and foremost focused on the quality of materials, quality of the construction — no doubt in large part so that the piece is durable. The degree to which that adds to the longevity is probably unimportant.

Like arguing wether the workbench you built will last 200 years or 400. What does it matter and who could know?
This app doesn’t seem to allow SIM swap attacks like Authy does, so that’s pretty nice.
The last point is the most telling; when you've got more effort invested in a lower level toolchain already; the candy version has little to offer.

Many Arduino users don't care about these points, they'll never need to know the difference between the 16kb part and the 64kb; they'll never care about the higher performance available with tighter code either. When some of them do hit a situation where it becomes relevant, articles like this will help them figure out where they need to go.
Electric pressure cookers can achieve the same thing and arguably produce tastier food. The electricity use is probably even less than a microwave due to the lack of evaporation.
There is undefined behavior in Rust affecting real-world code, including Tokio's scheduler, and code produced by async fn definitions. UnsafeCell doesn't solve the problem. There's more information at https://gist.github.com/Darksonn/1567538f56af1a8038ecc3c664a....

Bug report at https://github.com/rust-lang/rust/issues/63818.

Reddit threads at (older) https://www.reddit.com/r/rust/comments/l4roqk/a_fix_for_the_... and (newer) https://www.reddit.com/r/rust/comments/lxw6cl/update_to_llvm....

Somewhat related HN thread at https://news.ycombinator.com/item?id=26406989.
Don't ever change the massive car obsession.

To Europeans used to small, cramped spaces - the great open roads and huge comfy cars of America are much appreciated.

I actively avoid driving in the UK. I adore driving in the US.

edit: Downvoting an outside perspective, how very Reddit!
Definitely not capitalism to blame here, but the fact stands: despite an electric kettle being a very basic household appliance that is used everywhere, it is almost impossible to buy a product, that would reflect how long they have been around. Ideally, you would assume that todays kettles are the end product of decades of refinement and engineering and do their principal job well and last long.

Well, they don't. Besides the points the author goes on about I have two primary issues:

- Most kettles are not efficient. Stop the time they take to heat 1l of water from tap temperature to boiling. You get anything between 1:40min and +3min depending on your kettle. Mostly irrespective of price range. (Physical limit for the power plugs in my region would be ~1:30min).

- Virtually all kettles have plastic that comes in contact with the water, specifically in their lid. While I am definitely not one to support fearmongering of "all these bad plastics" and "bad chemicals", I also believe this is a situation that should be avoided. We know that plastics in general but sometimes specifically in cheap products contain chemicals that are bad for our health. Now, at the lid of your kettle you condense boiling, distilled water which is quite perfect for chemical extraction. Even if I would trust the producer of my 20$ kettle to only use food-safe plastics that are even safe under long term contact with boiling water (I do not), I would prefer to have a lid from stainless steel. Now try buying that...

Long story short: I think kettles (and toasters) would be a perfect start for an open hardware household appliance initiative. Spend some time and money on really engineering the shit out of some simple but ubiquitous household items and make the design freely available. Design kettles that do just one thing: boil water well. IMO this would be a boon for humanity.
If I understand right the ETH chain will be integrated as a shard. This would mean it would just live on inside the new Ethereum ecosystem until it is ice aged - so one could say it's not a fork but a wrap of some sort.

Unfortunately not a single resource I found actually describes this process in an easy to understand fashion - pretty amazing considering we are talking about $200+ billion dollars....
Actually I never see any occasion that a C guys jump into a well establish project and ask them to rewrite that in C.

And TBH I rarely see other popular language did the similar things either, including very popular ones like python, Java or Go.

And you even observe there is thing called "C evangelism" actually exists?
> ...when was the last time Google spent their money on smear campaign and negative ads on a rival?

Somehow, of all the abuses and injustices Big Tech commits, this one is way, way, way down on the very bottom of my list.
Quick tips to find out if your any of the tests in your project are actually making outbound calls: Run it without networking (--network=none)
As of 01 Dec 2020, there is already another Ethereum mainnet chain (Eth2 Phase 0) running in parallel with and dependent upon the Eth1 mainnet chain:

https://beaconcha.in/

https://beaconscan.com/

https://github.com/ethereum/eth2.0-specs/tree/dev/specs/phas...

Vitalik is proposing a role reversal to take place earlier than it was previously planned (not completely accurate in a technical sense re: previous plans, but effectively the same):

Eth1 mainnet will hand-off consensus responsibility to Eth2 mainnet (PoW -> PoS), while Eth1 nodes continue to "run the code" that executes smart contracts / processes transactions.

If the plan is put into motion, and as long as some miners / mining pools don't yank the plug on their mining nodes in the canonical Eth1 mainnet, then the canonical mainnet — per consensus among the Ethereum Foundation and aligned developers, Eth2 validator operators, orgs/companies/exchanges/etc — will transition suddenly from Eth1 (PoW) to Eth2 (PoS). And that will be the end of all mining on the canonical Ethereum mainnet.

Miners/pools who find it impractical or undesirable to reallocate resources from mining to staking may band together to continue running an alternate mainnet chain based on PoW (ETW?); market forces would then decide whether that chain is viable, as well deciding the fate of the evolved (PoS) Ethereum mainnet chain.
"Mayor of small town, Maine, finds angle to tax lost tourists for life"
I bought my dad a kettle from Tesco 5 years ago for £5. He uses it daily and it still works.

Re scaling, he uses bottled water (which may upset some people, I'm sorry) but you can buy 5 ltr bottles for £1 and you get no scaling at all. His kettle inside is as good as new. inside.
Reprojecting the Perseverance landing footage onto satellite imagery
The Unexpected Loneliness of Being a CEO
It was so popular it displaced the french word for fox. Foxes were called "goupil", "renard" in modern french.
The short answer is, companies produce what most people are willing to buy and produces most income. That is not the same as producing best products for customers.

Some companies found the way to produce most income by offering best products for customers.

I am not an expert on kettles and might of course be oblivious to some glaring obvious facts about kettle-making business.

But it seems that it is very likely that good kettles just don't differ much form mediocre ones, when put on the shelf of the supermarket or when put on Amazon against competition that can buy a bunch of fake reviews. There would be no practical reason to spend a lot more on research to produce something that would not at all bring more income for the company.

Most people will buy cheapest kettle that satisfies their basic requirements. For me this is: it keeps proper volume of water, it heats water quickly, does not smell, is easy to clean from scale. Mine is quite expensive compared to most kettles only because "does not smell" is very difficult to meet (or it was when I bought it a decade ago).

There are good kettles. These are produced by companies who found their niche producing for customers who just don't care about how much stuff costs and will buy the best of each category regardless of how expensive it is. So while they might be good mechanically, I think overall they are not as good products when comparing return on the investment.

**

Now, as to filters, I would NOT buy a kettle with a filter.

Filter is something that keeps impurities and I definitely don't want that sitting hot in my kettle.

Also, filter will not prevent scale from depositing. There is no practical way to prevent scale depositing other than using distilled water which will make everything taste awful and will probably not be good for your health.

Contrary to popular opinion, "hard" water with lots of minerals is better for your kettle than water with little minerals. The scale that deposits from hard water is very porous and it practically cleans itself and is easy to remove with a little bit of citric acid.

The scale that deposits from water that has little minerals, depending on composition, can be very dense, hard and nonporous making it difficult to clean.
Can we get rid of 'sealed'? I really hate that keyword. Sometimes there's a good reason for it, sure, but sometimes it's used gratuitously, and then I have to work around it for no good reason.

Eg, in C#, SqlDataReader is sealed. Which means I have to do this:

reader.GetString(reader.GetOrdinal("FirstName"));

When I just want to skip the verbosity and be able to do this:

reader.GetString("FirstName");

So the logical thought there would be just to inherit from it, add an extra overload to those functions, and life got more comfortable, plus you can still pass it to anything that wants a SqlDataReader. But oops, you can't do that, because somebody at Microsoft decided the interface for this thing was perfect is not to be messed with.

If there's something that really gets me annoyed is when I run into a limitation that seem completely arbitrary but intentional. It's not there because of the technical limits of the hardware, or because the compiler isn't clever enough, but purely because somebody intentionally decided 'nope, you don't get to do this particular thing you can do all day otherwise'.
Buried by the so-called British Broadcasting Corporation in the UK regional news section, yet if he'd been some random US 'rapper' his death would've been on the front page.
The electrician, drywall repair, and other skilled labor costs of running a thicker gauge wire to the kitchen from the circuit breaker would far outweigh the cost of the wire itself. By orders of magnitude.
Interferometric Imaging with Allen Telescope Array
Exhaust pipe should end in the cabin. Then people will stop their excuses.
Consider a hardware wallet if you’re new to Bitcoin
"We're not going to 51% attack the network. We're just going to allocate 51% of the hashrate into a single pool to demonstrate that we could 51% attack the network"

Why should this threat of violence be treated differently than the act itself? Miners are threatening to do the one thing their entire existence is supposed to prevent. They're cutting off their noses to spite their faces, instead of enjoying another year or so of profitability
Show HN: Live Man Switch
That's the problem with language design: too much opinion, too little decision making based on actual data.

The author says there should be no Exceptions and there should be multiple inheritance... I mean, these seem like pretty extreme positions to have when talking about an OO language... if I remember correctly, multiple inheritance, in particular, was one of the features the languages from the late 90's had actually stayed clear of as it had been shown by the previous generation of languages that it was a mostly bad idea. I think even inheritance as done in Java is not the best of ideas, and there seems to be evidence extension methods or, similarly, type classes, are better suited to add behaviour to data structures.

IMO languages like Kotlin and Swift are much more like what modern OOP languages should be than what the author proposes.
I know all too well the consequences of injecting a whole bunch of "empty" money into an economy as a Venezuelan. I can't tell you if it's the right call on the short term or not in the case of US, but I'm sure the real consequences will be felt for years, if not decades after the pandemic is over.
For some time I was thinking about what would happen with my crypto if something happens to me. I don't have much crypto, but still, I would not like for it to get lost if something happens to me. There are a lot of stories of lost crypto, and about 1/5 or 1/6 of all the Bitcoins is already lost because keys to the wallets were lost. That is A LOT of money lost.

Because of its decentralised nature and of how wallets are accessed, most of us keep wallet keys very private and they would be lost if we forget them or die or aliens abducts us or something else happens to us

I wanted to build a solution for that for myself but later decided to make it as a very simple service and make it available for everyone.
So this service is called Live man switch. It is a digital version of dead man switches used to shutdown various critical devices if operator drops dead in the real world (think of a train operator dying and train stopping).

You define how often should service checkin on you (via email or sms), trigger condition (for example you did not checkin for 30 days), and messages (emails/webhooks) to be sent if trigger condition is met. So in case that you fall in the black hole, disintegrate, corona pwns you or you die in any other old fashioned way, you can pass on messages to your loved ones including explanations on how to access your crypto or any other digital assets and accounts you own.
And of course I implemented crypto payments for the service.

You can check it out here https://livemanswitch.com

This service has many other use-cases. It can be used by terminally ill patients or anyone in general as a digital will, by elderly people so that their family can know that they are alright (by checking in), for enforcing habit forming etc.

p.s. If you deicide to check it out: NEVER EVER UPLOAD YOUR WALLET SEED OR ANY OTHER PLAIN PASSWORD AS IS to my service or any other online service. You can do it more securely in several ways:
Use a cryptographic mechanism, encrypt the seed/password or any other credentials or private message with a cryptographic algorithm like PGP or AES, send the cryptographic keys to your contact in advance so he would be able to decrypt the message, and upload encrypted text to Live man switch.
Store the seed/password somewhere safe offline and in livemanswitch explain to you contact how to access it
Store part of the message offline and other part you can send with Live man switch, and you can combine this method with other cryptographic mechanisms
etc... And again please, data is stored securely, but you should never ever trust a stranger online, and never show very important credentials in plaintext online.
Well sure, but I'm not using systemd. If I wanted a container runtime written in C, I would use crun. But I'd rather not use that either.
I know Pascal isn't perfect, and lots has been learned since then... this is genuine confusion on my part. So tan in your system returns a variant type (could be Error, could be Double), right? (I didn't get that)

Compilers can find all sorts of things they couldn't in the past, which is amazing.

What happens at run-time if an overflow happens?

again... I'm sorry if I didn't express myself clearly enough. I'm coming at this from a Pascal programmers perspective... I've missed the past 20 years of compiler improvements.
> Of course we all know now that CDs must be treated with essentially the same care as vinyl records

Not really. There is really a magnitude of improvement here. It doesn't matter how many fingerprints you leave on the CD, just wipe them off with cloth (and particularly almost any cloth, since I don't know of many cloth types than can scratch plastic -- unless they are full of dirt+sand to begin with). If you put your fingers on a vinyl, the oil in your fingers is already degrading the data permanently. And if you try to wipe it off with cloth, likely you will only mess it even further.

And if you ever have a real problem with tape, good luck.

With all due respect, for a medium that has no fixed protective case, CD is almost indestructible. (For nitpickers: In comparison to everything else. It is obviously not truly indestructible. )
Function is compromised in a code base that must be maintained by multiple people over the course of years when if it is not written with both function and clarity in mind. I have never myself encountered a task where I have had to compromise functionality for clarity, or clarity for functionality.
So what's your proposed alternative that doesn't involve checking? Option-style wrappers enforce consistent checking and handling, but so do explicitly nullable type signatures. At some point you're going to need to know whether you have data or not, and that requires checks.
Right? The hand-drawn diagrams suggest they're being sent from prison.
We could maintain a few populations in labs and/or isolated areas. Inspects repopulate hella fast, so it’d be easy enough to undo such a project if we found that they were a lynchpin of some kind.
Yes, and the ability to annotate and block out parts of the image before saving. Simple tools that for some reason other screenshot tools have been mind-bogglingly oblivious to provide.

(It has a blur tool too, but I don't recommend blurring sensitive data as if the area under the blur kernel is 1, the sum of the pixel values will be the same before and after the blur, and if an attacker recognizes which font and size it is from other parts of the screen, they use could dictionary attack for the text with the sum of the pixels as the hash to be cracked.)
Paper Review: Searching for Fast Model Families on Datacenter Accelerators
xbar
Gonna check this out. I loved Brood War, but Starcraft 2 has too many "if they went this build you must have built this" situations. In Brood War, with enough Marines, medics, and Goliaths, you were probably good. I don't want to perfectly scout and play a counter meme build, I want to fight.
AMP was the defense against all content moving into native apps like Facebook. Antithesis of open web, with completely locked down content, applied DRM and no ability to contribute without the review of platform owners.

It's that the endgame you'd have preferred? Ecosystem of apps because news web developers refused to make their ad and autoplay video ridden websites usable on the mobile devices?

Look at the trends and tell me if you'd have preferred to read all your content in an Apple News walled garden instead?
> When was the last time someone bough[t] a physical [..] newspaper?

Sorry to sound like I'm stuck in a timewarp but we pay for our local newspaper to be delivered three days a week, it's waiting on the doorstep at 6am, I read it as I drink my first coffee.

I could also read the articles online, but the actual physical version is definitely better for our purposes.

Q: Is there really no-one else here doing this?
They don't, and no one is claiming that they do. The author is simply puzzled as to why capitalism (a system where maximizing profits is the goal) hasn't capitalized on the desire for a good kettle? And the speculated answer is that maybe there isn't enough desire for it to be profitable, because most people are happy enough with mediocre kettles.
DFIR Triage Disk Analysis Case 001
I don’t know about Canada and Mexico, but these are the search results for a popular US store:

https://www.target.com/s/kettle

I’ve been using this $25 kettle for many years now:

https://www.target.com/p/hamilton-beach-1l-electric-kettle-s...

The cord is “6 inches” (it’s actually 24 inches on my cheap kettle) because most kitchens in the US have many power outlets at the countertop, where the kettle sits. It would be annoying to deal with excess wire.
Explicit variance, especially for types, is just really confusing. Implicit variance has the risk of breaking APIs or overpromising a particular variance without developers realizing.

If you have subtyping you need to think about variance. That's led me to believe that subtyping's simplicity is deceptive, and that it should be avoided as much as possible. (Rust has subtyping but only for lifetimes, and it's confusing enough there.)
We get that you don't like rust. But it seems like a lot of people currently using C or C++ while like to use rust at work, and might disagree about the benefits of the language and tooling. I personally know a few friends in distinct domains who work on established C++ codebases and are in this situation.

There are also a lot of people who do not use C or C++, but use a bit of rust because it's so much easier to write fast little tools with it. I'm in this category. I even use threads sometimes, and it's reasonably easy. A crop of new unixy tools in rust seems to indicate other people also think alike.
Whats fascinating to me is that I had NO idea there was some battle of some sorts in the "screenshot biosphere"

TBH I use GreenShot exclusively as it is seamless and does every thing I Need [0]

[0] https://i.imgur.com/x0oMzb6.png

And I can do things like this

[1] https://i.imgur.com/ZtR60qw.png

Nested fucking screenshots.

All I have to do is hit prtscrn each iteration I want to capture
Lol, did you just make that up?
They are both collections of flawed humans. Accountability is necessary regardless of the collective noun you use.