skysight-inc/HackerNews huggingface dataset:
"I have no delusions that it's going to pass... I wouldn't probably vote for it myself."

Well, at least he's not totally out to lunch.
> "I have no delusions that it's going to pass," [the state senator who introduced the bill] told reporter Eric Blaisdell. "I wouldn't probably vote for it myself."

So it's not a serious bill. But I don't get what conversation the guy's trying to start. The full bill -- under two pages of generously spaced text [1] -- cites four justifications, conveniently arranged by decreasing plausibility:

> (1) The use of cell phones while driving is one of the leading killers of teenagers in the United States... (2) Young people frequently use cell phones to bully and threaten other young people, activities that have been linked to many suicides. (3) The Internet and social media, accessed primarily through cell phones, are used to radicalize and recruit terrorists, fascists, and other extremists. (4) Cell phones have often been used by mass shooters of younger ages for research on previous shootings.

And then it proposes prison sentences up to a year just for possession? Yeah, weird.

My best guess is it's a publicity-seeking protest against Vermont's recent decisions to raise the tobacco [2] and firearm [3] purchasing ages to 21. The last bit of the cell phone bill suggests this.

> (5) In light of the dangerous and life-threatening consequences of cell phone use by young people, it is clear that persons under 21 years of age are not developmentally mature enough to safely possess them, just as the General Assembly has concluded that persons under 21 years of age are not mature enough to possess firearms, smoke cigarettes, or consume alcohol.

[1] https://legislature.vermont.gov/Documents/2020/Docs/BILLS/S-...

[2] https://liquorcontrol.vermont.gov/Tobacco21

[3] https://dps.vermont.gov/content/new-vermont-gun-laws-faqs
And that no one had done it before (apparently).
Great. So it does actually help.
That is a plot point in Vernor Vinge's Deepness in the Sky
Learned about exa from you and immediately replaced my shell aliases from `ls` to `exa` with flags. Thanks a lot!
I think this is a good reference for anyone who touches computer graphics. It's not really clear enough for Physics (see all the comments here), but as tips for understanding how computer tend to model things, it's fine.

For example, a raytracer can simulate specular (mirror) or diffuse (matte) reflections by simply playing with the incident angle when the ray hits an object. The more jitter, the more matte the object appears. Similarly, you can get very nice "milk" or "skin" coloration by following the incoming ray slightly below the surface before reflecting back out, the same way this discusses having a thin layer of water would prevent some of the light from reflecting back out.
It actually worked pretty nicely - if anything better back in those days when software expected to run on different unixes, before the linux monoculture of today.
Email is in their contact link (with other stuff). Phone number is likely available with a bit of searching.
There's differing opinions of BTRFS's suitability in production - it's the default filesystem of SUSE on one hand, on the other RedHat has deprecated BTRFS support because they see it as not being production ready and they don't see it being production ready in the near future. They also feel that the more legacy linux filesystems have added features to compete.
I really think you and the poster above are disagreeing a lot less than you think. The older post is being vague on the conspiracy and using an unnecessary amount of hyperbole - but what you've stated is the actual source of the conflict of interest... Drugs aren't being sunsetted because they're ineffective but because they're unprofitable.

There are some pretty crazy effects from all the ridiculous players involved in this market with manufacturers plying clients with financial assistance, PBMs extorting manufacturers for rebates and providers over-billing everyone... the beautiful thing is this sunset effect is clear to see even through all that haze.
Well the companies don't need your DNA to decline you health insurance. If that condition appears and you go to the doctor to get it treated, the companies will cover it your first year but then raise your rates so high that you will be forced to find other companies.
https://explorabl.es acts as sort of a repository for it. Unsurprisingly created by the irreplaceable and aforementioned Nicky Case.
I don't doubt this but do you have any documentation?

Asking for a friend who uses XFS on LVM for disk heavy applications like database, file server, etc.
I'd take my bike everywhere if I knew it'd still be there after I finished having lunch, visiting friends, grocery shopping etc.

As it is though, my bike isn't even safe chained up in a locked garage.
To be fair, it's really cheap to issue a DMCA notice—that's even part of the problem with them, one might argue...
They really needed to rename it.
IIRC you can do this by using AWS Backup. There's a setting in the... Plan? Policy? Sorry, it's been a while and there was a weird mismatch between the terraform documentation and the official Amazon documentation... anyways, there's a setting somewhere that says to move the backup to cold storage after a certain amount of time.
It took more time for me to read your complaint about "bloat" than it took to load the site, read it all, and come to the comments. This type of elitist posturing is more corrosive to my enjoyment of this profession than any poorly optimized website.
Actually these days, Haiku will probably at least boot on $random laptop, and if you have a WiFi chip that FreeBSD also supports (we reuse their network drivers), you can probably even connect wirelessly.

I run Haiku on my ThinkPad E550 (2015), I know some of the other devs run on Dell XPS 13, HPs, etc. And the same is true in towers (Ryzen is becoming a popular pick.)

GPU acceleration drivers are the one real kind of driver we lack at this point.
For me when rarely riding a scooter (in Berlin) it is always frustrating that I am (at capped 20km/h) a bit slower than the flow of numerous bicicles. This also understandably increases frustration for the cyclists (I feel the same when usually taking a bike to work).
This alone rules out taking a scooter over a bike whenever possible.
Depending on the prognosis, what you describe is a feature, not a bug. Pneumonia and aspiration of food (often these are causally linked) is one of the more likely causes of death in advanced dementia. If well-meaning staff are running interference here (hello, feeding tube!) you can wind up living considerably longer in a state where you no longer recognize anyone, are bedfast, incontinent and have no real ability to communicate.
> The rapprochement – which also saw the purchase of a Czech brewery, television station and Slavia Prague football club by a Chinese energy company, CEFC

It is so convenient that ownership can change, while viewers think they're still watching the same, local station. There should be a periodic, mandatory disclaimer, informing viewers who the owners are, just like for medicine side-effects.
- I'm a developer.

- Huh ?

- I build websites types on an air keyboard.
Protecting property is not the only use-case for locks.

There are also locks on e.g. cell doors in prisons. Those are pretty essential to the function of the cell, and tend to survive anything prisoners might try to do to them.

There are also locks (specifically, interlocks) on e.g. dam spillways, or on the airlocks on submarines. (For these, the "key" is a button somewhere else that's not necessarily itself secured, but it is still very crucial that they keep things out when that button has not been pushed.) They hold up pretty well—even against malicious infiltrators—mostly because they fail closed and have no UI components mechanically linked to the locking mechanism.
He's probably doing it for the "boomer memes", I'm sure a large part of his constituency thinks this is the funniest thing ever.

You probably know the sort; those who laugh at those comics where the kid says "Dad, this iPad is broken." and the old wise boomer says "Son, that's a magazine." Side splitting stuff.
So it's purely a bill to spawn discussion... again 18 year olds are old enough to join the military but "it is clear that persons under 21 years of age are not developmentally mature enough to safely possess [cell phones]", the bill reads." Waste of everyone's time.
The solution to bad working conditions at FB is not to stop using FB and assume FB will correctly interpret the resulting market signal.
X4200s were the devil's work. Terrible BMC, raid controller, even the disk caddies were poorly designed.

The BMC controller couldn't speak to the disk controller so you had no out-of-band storage management.

I had to Run a fleet of 300 of them, truly an awful time.
"Sorry, this content is not available in your region."

Second time today in HN while reading from the EU.
The slowest thing CPUs do by far is access memory. I don't see any possibly way that, for the given example, using more memory would ever be faster. At best 3*N all fits in cache and it's not as bad, but even then it's still at least one more cache miss which means it will still be slower even if it's not by much. Temporary memory is the worst type of memory. It's cache misses & pipeline stalls for no point.

"Premature optimization" is not an excuse to write obviously bad code. Fixing this simple thing now is much faster, and simpler, than digging a big hole, jumping in it, and then hoping you can find something to pull yourself back out later.

In the same way it's important to scatter about asserts and verify parameter arguments do in fact conform to the documented contract, it's also important to always keep an eye out for openly wasteful code.
The famous "fast inverse square root" was in Quake 3.
Some features such as Raid5 were still firmly in "don't use if you value your data" territory last I looked. So it is important to be informed as to what can be used and what might be more dangerous with btrfs
My terrible experiences with thin pools makes me see btrfs as a pool of wonderful, trouble-free and perfect code.

Just ask yourself what happens when a thin pool runs out of actual, physical disk blocks?
Maybe you are not 21 yet :)

Seriously, I guess it's one of that web sites blocked for EU readers because of fear of GDPR. Well, I guess I can survive without that article.
> That's a hell of an understatement right there. It still doesn't have any capability for accelerated video, does it?

We do not. But that (and proper power management) basically all that's missing at this point; the rest are "just bugs".

That is to say: WiFi, ethernet, USB, SSDs, EFI, etc. should all work on the majority of hardware, both current and past.
When to Write?
FusionAuth is great for those who want a solid self-hosted auth solution. It's open source & has many of the same features as much more expensive Auth-as-a-service providers. -> https://fusionauth.io/
Let's follow energy, after all darker = less energy. For simplicity let's consider the sum of energy over all observer angles, to get rid of the "it's shiny only from one angle" problem.

Reflection on the surface of the water is "free" both ways (from air to air bounce, and from water to water bounce), no energy loss. Travelling through water - similar, lite energy loss, though not exactly zero. The only way we can really lose energy is on the cloth reflection. Therefore (almost) all of the darkness effect should be attributable to increased number of cloth reflections, via the total internal water reflection mechanism.

This also explains why colors are more vivid when the cloth is wet - after all the same ray of white light bounces off the cloth several times, increasing the "color filtering properties" of the cloth.
mdam + LVM + ext4 does everything I need to do and more. Thin and thick provisioning, ssd caching, snapshots. If I were to use another file system it would be something like ceph or glusterfs.
Surely the kernel developers can do whatever the hell they like.

If you don’t like that don’t use it.
> If you think carbon taxes are going to stop a 3 year drought from occasionally hitting Australia, a region with thousands of years of documented dry spells

Are you implying that the rate and duration of dry spells have been the constant for thousands of years? If so, do you have data back this up?

If not, is it possible that we're living in exceptional weather conditions? A quick google gives me an article from the Bureau of Meteorology, an organization with a wealth of data, the requisite compute power to analyze the data, and actual expects of climate modelling:

http://www.bom.gov.au/climate/updates/articles/a010-southern...

> The only sensible thing Australia can do is prescribed burning and bush thinning.

Do you think that fire authorities haven't been doing this already?

If anything their capacity has been reduced by recent budget cuts from NSW Liberal Party - the core policies of the Liberal Party are smaller government, individual responsibility, and hence lower taxes across the board. The Victorian Labor party, on the other hand, increased their capability.

Unfortunately there's a number of forests that are exceptionally dry due to recent long term trends, and Australia just needs more and more resources to manage its land.

So sensible things to do are:

- provide more resources for land management
- stop making the world hotter
It's worth noting that node_modules is for project dependencies and most of it won't be included in the final assets. Many projects make use of build tools, command line utilities, testing suites and other libraries in development which don't get deployed. Even for actual app dependencies, many packages include source code, type definitions and multiple choices of builds which inflate the size of the node_modules folder but don't get used in production. So hundreds of megabytes of dependencies can easily be used to make something only a few megabytes in size.

Your point still stands of course!
OK, if we explore this idea, I think there is a valid question of what are the effects of prolonged cellphone/laptop/screen on development. There could be negative consequence to individuals (micro-level) and society (macro-level).
https://web.archive.org/web/20200109230545/https://www.mynbc...
Because people can't afford dignity and care, for the most part?

It sounds good, but if you've ever cared for a severely demented person who can no longer safely walk, you will have to make the choice between (a) strapping someone to a bed or (b) paying for 24/7 care (or, to some pro-rated amount, giving up your own time) to ensure that they don't get up, fall, and break something.
His comment is a textbook example of the kind of nihilistic antagonism so common in the security industry.
If you have an issue with the numbers take it up with the Japanese government, they commissioned the study. Source was provided.
If I am a facebook user who is upset about this, and I boycott, how does FB know that my boycott is in relation to working conditions especially? Maybe it thinks I am boycotting because Mark Zuckerberg isn't paid enough.
"Rodgers writes within the proposal that cellphones are a large factor in teenage driving deaths and can lead to bullying and radicalization.

"In light of the dangerous and life-threatening consequences of cellphone use by young people, it is clear that persons under 21 years of age are not developmentally mature enough to safely possess them," the bill reads. "just as the General Assembly has concluded that persons under 21 years of age are not mature enough to possess firearms, smoke cigarettes or consume alcohol.""
“New service launches ahead of the Beijing Winter Olympics in 2022, with trains making the 108-mile trip from the capital to ski slopes in only 45 minutes”

Is driverless for safety reasons?
Things like string manipulation, array manipulation or similar are pretty well understood and could be put into a comprehensive library. On the few more projects I have seen there were some trivial packages like “isodd” or something like this which then recursively pulled in dozens of other trivial stuff. This just doesn’t seem to be a problem in other languages.
Omnigraffle - high fidelity mockups

Balsamiq Mockups - simple views

No functional prototype
Maybe not even malicious, maybe they just put in the wrong subscription ID :(
This reduces both income and wealth inequality:

At 2% inflation, it's not possible to maintain $100M of wealth without also having $2M in annual income. If every dollar over $1M in income were taxed at 70%, then you would need over $4M in annual income, plus more than twice your annual expenditures to maintain that level of wealth.

4% rent on $100M in assets is probably sustainable over a long time, so if you live frugally, you could likely self-sustain that level of wealth.

If you have $1B in assets and make a 7% return (which is my conservative estimate of the maximum long-term rent you could extract on a large fortune) then that's $70M return in income, essentially all of which is taxed at the 70% rate, leaving $21M remaining, $20M of which is "lost" due to inflation.

This means that if you have a billion dollars and want to live just off of rents, you would need to both invest prudently, and live on expenses of no more than $1M per year. Mess up either and you are on track to leave the billionaire's club.

In addition, consider an heir who gets a high-paying professional job with a rags-to-riches one. The one with no wealth isn't having unearned income to pad their tax bracket, so the marginal pay they get for working is much higher than the heir who is also collecting investment income, thus allowing them to grow their wealth faster if they have an identical savings rate.

The US right now has an income tax scheme that is regressive for wealth because wealthy people have a greater fraction of their income in the form of long-term capital gains. GP suggested making it extremely progressive vs wealth, and I'm merely pointing out that a properly implemented wealth-blind income tax will work out to be progressive vs wealth due to inflation.
Immediately installed and tried `hx` and liked it. Thank you for that.

Have you compared `skim` with `fzf`? And `lsd` with `exa`?
Facebook inflated viewership numbers 150-900% on videos
Posting links to XKCD like this is generally considered to be a low quality post, hence the downvotes. I’m not one of the downvoters, but thought I’d share the reason as nobody else did.

Edit: gotta love HN! I try to be helpful to someone else that was downvoted to heck with an explanation of why that was the case (based on past replies I’ve seen) and now my post is the own with a negative score. Cheers y’all!
Yes, you're correct! This is definitely a difficult problem with many nuances.

> This can be mitigated by enqueuing work in batches.

> Workers also hold the lock for much longer, adding more contention on the FIFO.

Fortunately, "true-FIFO" is the worst-case scenario. If you have a "Pseudo-FIFO", or "First-in USUALLY first out, but not guaranteed", you have a huge amount of flexibility with regards to avoiding contention.

The "classic" pseudo-FIFO algorithm is 1x thread-local true-FIFO per thread, with work-stealing taking from the LIFO-side from remote threads.

For example, Thread#1 push_back and pop_front on FIFO#1, which eventually runs out of work. Thread#1 now needs to grab work from another thread.

Thread#1 chooses to worksteal from say... FIFO#23. Thread#23 is still reading from pop_front side, but Thread#1 can pop_back concurrently without any contention (as long as pop_front and pop_back operate on separate cache lines).

The problem here is that Thread#1 just caused FIFO#23's data to look kinda-sorta like a stack, albeit temporarily. So you've lost the first-in-first-out guarantee. Fortunately, this isn't a major problem in many applications. (Ex: a Depth-first search becomes Depth-first when thread-local, but Breadth-first when load-balancing across cores. This is extremely good behavior in practice)

> If you're going to do that, you're usually better off just making the work items bigger on the producer side.

In my experience, that isn't always possible. A large number of problems are recursively defined, and splitting them up into tiny pieces is the most natural way of representing problems.

Take the case of parallel tree search ("mostly" depth-first search with the pseduo-FIFO defined above). Its non-obvious what the size of any node actually is! There's basically no way to predict the size of an a work-item (and we are thus left with the workEstimate(X){ return 1; } style estimate).

Other tasks (ex: Matrix Multiplication), allow for very easy tuning of work-item sizes. It all comes down to your specific application.
Does BLAKE3 reduce rounds vs BLAKE2s?
How far the destination of his final trip of the day is from the start of his first trip of the day.
Everything you say here is true, but at the same time it's just a fact that Gandi lost a lot of customers' data, and AWS, GCP, and Azure have never (as far as I know) lost a significant amount of it at once. You can talk about theoretical responsibility for data, and it's true, you are responsible for having backups of your data, no matter how many "9s" the service has, but the basic fact is that some services have been consistently good at not losing customer data, and others haven't. Even though I'm going to back up my data no matter where it is, I'd still rather use the service that's got a better track record with it.

I haven't ever even lost a file on Google Drive, which as far as I know provides no reliability guarantees at all.
One that’s activated by motion detection like the ones they use for tracking endangered species?
Good!

These scooters are at best a novelty and at worst a potential vector of serious injury. I know at least three people who have been injured through recklessness or malfunction. They also tend to be dirty.

They’re a nuisance in populated areas like San Diego (where I love). People already act as if no one else is on the road with cars and bikes. Scooters appeal to (inner) children, and they can really bring out the indifference in aggressive riders. Drunk scooting is basically a license to be a prick.

The business model was terrible from the beginning. Like should have learned from its bicycle department (as well as competition) that there simply isn’t much money in this market.
> You pack up, and move somewhere that's not the equivalent of sitting in the middle of a crude oil refinery.

I would posit that for many people (e.g. citizens of China or India), "moving somewhere" where you're not constantly exposed to small-molecule pollutants would require more effort (e.g. acquiring a different citizenship) than would be required to atmospherically decouple your house.
Cuttlefish Is Wearing 3-D Glasses: Exploring Cuttlefish Depth Perception
Cut up your credit cards and restrict yourself to $10 per day cash spending by only leaving the house with 10 bucks.
The situation rules out Linux for many potential applications and side projects I might undertake.
Most providers (notably: AWS) don't support DNSSEC, because DNSSEC doesn't matter.
Another poster mentioned https://github.com/lotabout/skim but I haven't compared it to fzf yet.
built in job security (if not for the original dev), but for those that come after the dev0.
I appreciate that it says you never SEE an unhappy person riding a jet ski.

Whether or not it generates happiness, money can make happiness more visible. That's worth a moment of reflection.
The tradeoff was the throughput of your compilation was terrible. BeOS wasn't magic, it just prioritized the UI over all else. That's not advanced, it's just one possible choice.

MacOS prior to OS X had the same property: literally nothing else could happen at the same time if the user was moving the mouse, which is why you had to take the ball out of the mouse before burning a CD-R on that operating system.