skysight-inc/HackerNews huggingface dataset:
Press release/ad? Also blue light glasses are probably just placebo.

https://health.clevelandclinic.org/do-blue-light-blocking-gl... (with link to a paper)
But it does .. It does happen on Android. Plenty of banks refuse to support Google Pay, and will instead leave you with their own crappy app. They all support Apple Pay though.
How can it guarantee that the OS doesn’t just lie about having allocated that space? As far as I know they are unallocated until a write to a given page (by default on Linux at least), and thus any write could potentially fault.

Unless it zeros every page it allocated, I don’t see it being able to defend against it in practice.
> The other thing is, once disks are as fast as RAM, there's really no point in having RAM.

You make it sound like RAM is only used as a cache for disks, but there are other reasons to have RAM:

* RAM supports basically unlimited number of reads and writes, which (to the best of my knowledge) our current disks don't

* it serves as a central integration point for all sorts of IO: disk IO, network, interface to GPU etc

* volatility can be a feature (switching off a device wipes RAM)
But wouldn't you use the word "valuable" in those cases?
I don't understand why fixing issue 358 in the Zig compiler isn't trivial. I don't understand the reluctance. I don't understand why:

for (var i: usize = a; i < b; i += 1) { foo(); }
for (var i: usize = a; i < b; i += 1) { bar(); }

Is worse than:

var i: usize = a;
while (i < b) : (i += 1) { foo(); }
while (i < b) : (i += 1) { bar(); }

Which is what happens without the for-loop scoping of the variable. (ie when I cut and pasted, I introduced a logic bug where I forgot to initialize i for the second loop).
When I say the redesign I audibly groaned. Just another bland, featureless, nothing website. While I certainly don't agree that the old one was "perfect," it at least had some sort of character.
Also they finished the work in a brisk sprint-like pace towards the end, knocking out the pages in record time. I think that was more indicative of the actual effort required to finish the work, not all the hours they billed. There is a perverse incentive when the client has a retainer to bill hours and make up excuses to line their pockets. They finessed the author and preyed on his naivety
I was way too heavy when I started getting fit again so squats hurt my
knees and I frequency lost balance. Switching to supported squats with
a table and executing them really slowly worked wonders [1]. Now my
legs are strong again and some weight has come off, my form for
unsupported bodyweight squats is great and I can do dozens without
joint pain.

[1[ advice in Wade's convict conditioning programme.
>Just because you can insider trade doesn't make something a security in my view.

I'm not an expert on security law. All I know is that there needs to be far better regulation around crypto whether it's labeling them as securities or creating brand new regulation. It's just way too easy to scam people in crypto.
Finally producing 4 yr old tech with unknown yields and costs is not exactly leaving anyone in the dust.

If they did achieve this by IP theft then they’ll face sanctions as well so whether they ship 7nm or not won’t matter if Western countries aren’t allowed to buy them.

Ask Huawei if you think import bans don’t work.
This is true, but while that is annoying for an able bodied individual, it can be a crisis for someone who is not. The one time I successfully called an Uber WAV only to have it be a crazy long wait, I canceled not because of the annoying wait because by then I had no faith that I would ever be able to hail a ride back, and I was trying to get to an area with steep hills in every direction.
There is a missing section in you quoted part

> I believe over here the traffic inspectorate would want the plates back if you stop paying the insurance

I guess the insurance/traffic inspectorate can mark your plate as stolen-like if you stop paying without giving it back

So either the first cop that sees you without a place or the first time your plate is checked by any automated system.
You're describing Gamer's Nexus pretty well I think -- easily the highest quality and most transparent/trustable PC hardware reporting I've personally come across. They frequently burn bridges with manufacturers because they refuse to stay quiet about major flaws in products.
I have always wanted to really understand this data structure. Sure, I can follow the analysis with the potential functions and all, but I never really understood how Tarjan came up with the functions in the first place. Does anybody have a resource which intuitively explains the analysis?
The lives of a man’s eighteenth-century coat (2014)
"NAND optimized key value store" doesn't do it justice ;-) The fact that it's SSD optimized has nothing to do with key sharding across trees, the latter is what gets you the absurdly low latency and near infinite scale out. This link gives an overview: https://vldb.org/pvldb/vol9/p1389-srinivasan.pdf And it's open source...
If you're doing ATG squats and you're over, say, 5'10"ish (though there's skeletal variation), it's impossible to do a squat without the knees going over the toes (simply because of the proportions of your femur to your tibia). I'm pretty sure this myth started on idiotic bro-science forums like bodybuilding.com or the like.
7nm doesn’t require EUV, 5nm does. You can do 7nm with DUV.
And that's why you shouldn't be that afraid of competing against them as a startup.
Don't forget said pre-release devices are often different, sometimes substantially, from the released version.

LTT and many other reviewers don't even go into depth and often get details critically wrong, such as falling victim to Nvidia's GTX 970 "4gb memory" scam, because they didn't know how to test VRAM and discover 0.5gb of that memory was severely degraded in performance.

They also don't appear to have any process to vet people they take money from, given they're partners with Gigabyte who dumped PSUs onto the market they knew were dangerous, and several exploded as a result.

They aren't reviewers because they have a conflict of interest. If they fairly review products, companies will not send them review units.
Other than banning some universally agreed upon deprecated feature from a project, I don’t see these dialects worthy. The rules also often fail to change with times, often causing the detriment of the project if anything (thinking of some of these rules making C++ projects stuck pre-C++11)
Relatedly, RRB trees for immutable vectors with good constant factors.
And this law is taking away my preference. I WANT to pay through Apple, because they make it easy. Subscriptions through Apple are super easy to cancel. That will for certain be gone, because now they get away with all their shady schemes that make it close to impossible to cancel. I want to pay with Apple Pay, because it is rock solid. I don't want to be forced into the banks half-baked crap app.
> the survey evaluates the median spending of a sample of Americans, but the median American spends pretty much all of their money.

I feel like this is relevant. If you already don’t save anything, then your spending power decreases drastically over a year or two, you still spend all of your money but just buy fewer of the nonessential or “nicer” things.

So CPI adjusts and assumes that “this is normal spending now”, but really there was no flexibility in someone’s spending anyways.

They would’ve kept buying more if they could, but now their quality of life has decreased but CPI treats it as if the product has improved & they don’t need as much anymore (even as a QOL increase).

Am I understanding this correctly?
> Golomb Coded Sets are similar to bloom filters but the storage space is much smaller. Worse performance though.

Humm. A link to these would have been good[1], but anyway I understand that an optimally filled bloom filter takes ~1.44 times more space than the optimal theoretic value (which I understand Golomb encoding gives you?), so 'much smaller' is not a helpful measure. Likewise the 'worse performance' is not a helpful phrase, I believe a linear lookup time is needed for decoding, but a small amount of space for an extra indexing structure can speed things up lots. Bloom filters are updatable (addition only in the simplest bloom filter), golomb coded sets practically can't be updated except by rebuilding AIUI.

I suppose binary heaps should get a mention <https://en.wikipedia.org/wiki/Binary_heap> cos they barely seem to figure in other comments here. The neat bit is they are trees but implicit (stored in an array) not explicit (which would use pointers) and are always balanced giving you log access times in a compact form.

[1] <https://en.wikipedia.org/wiki/Golomb_coding> but there are simpler explanations on the web
What's this ?
How about some tech files ?
Economists rediscovering 1980s cogsci, and it's problems, or am I missing something? If not, they should really be ashamed.
The amount of driving 'necessary' for commuting is zero. You can live in a homeless camp next to your job, or the postage-stamp sized studio most people could afford within walking distance of where the jobs are. You may get hassled by police every once in awhile, but then again seems safer than driving. Perhaps roll yourself in bubble wrap as well and wear a helmet while walking there. I can name quite a few cities where you can wake up in a heroin daze and shit in the streets and be within walking distance of someplace to earn some cash.

Personally 99.9% of driving I do is for pleasure, the lever I have to adjust is miles I drive not the miles the average person drives. On an individual level, each person can directly move their "miles I drive" lever but only barely move the "average miles a person drives" lever. Deaths/capita is a societal measurement that only has limited usefulness to the individual human, who is determining his own behavior. Deaths/mile is more useful as it actually allows me to examine how dangerous the roads are and plan how far I want to commute or pleasure drive accordingly.

Deaths / capita also allows the twisted viewpoint that someone driving a million miles for pleasure gives a very wrong view to the person driving a few miles for necessity. You claim to care about the amount of driving 'necessary' but then use a figure that includes deaths from people driving to the cinema or bar or a road trip to Vegas, which are not necessary. If you only include deaths per capita based on 'necessary' driving it would be a hell of a lot smaller, especially in comparison to the change in deaths per mile.
Academic researchers who make it to a tenure track position and stick with it for the rest of their career spend the majority of their career in tenure or in PhD. Most do not make it this far because there are fewer positions than applicants.
They maybe had 100m of ‘free’ hardware kicking around after the failure of Microsoft and Telekom’s German cloud offering…
We've got a mix of a few but are recommending use of https://github.com/gorilla/mux due to it using the net/http interfaces and types, great performance and some configurability which can be handy.

In particular, my team is using it in conjunction with generated code https://deliveroo.engineering/2022/06/27/openapi-design-firs...
Should mention Kerbal Space Program in this context. Rather than deal with complicated IO, moving data between disks and ram, the devs just loaded absolutely everything into memory at program start. This had all sorts of trickle-down benefits. In my experience, many Linux versions of that huge game were more stable than basic office software.
Seconding the RTCD recommendation. Handy code examples, and my favorite part is that the book is real-world-performance-conscious (hence the "real-time" in the title).
If anything, shirts should get negative hedonic adjustments as the quality of the fabrics and craftmanship decrease. But I’m guessing negative hedonic adjustments isn’t a thing.
It does not make sense to have a fixed salary decided upfront for a position. Candidates profiles rarely exactly match the job description. You might decide to take a risk on a promising junior candidates or decide for a more experienced candidates that you had in mind at first. Often, you end up also end up adapting the role the new hires to their qualifications which might differ from the original posting requirements.

The goal of a salary negotiation is to find common ground between what would make the prospective employee happy and what the company wants to pay to hire this specific person. If you are not willing to negotiate, you will surely hire even less people because most employment deal is a custom one.

Even if you post a range, you might end up going above or higher. The range is good to showcase what you would pay the hypothetical role and profile described in the job description. Depending on who's applying, there's always room for adjusting it to each specific case.
That's probably just a habit. It's the same for me when I enter the bathroom in the evening before going to sleep.
Maybe there is a good reason. I'd just like to know what it is. My guess is that fixing issue 358 with syntactic sugar would mean that the debug info would show scope blocks that don't correspond to {} in the source, and that is annoying.
Scrum is really for low-trust environments where management fundamentally don't trust the developers to deliver - whether because the developers aren't experienced, not very good at self-management, or too easily distracted by shiny things, or because you're an archetypal MBA type who distrusts any underling who might be smarter than you.

If you trust your developers (whether in-house or contractors) to do the job you can pretty much let them manage themselves with whatever kanban-ish system that works for them. If you don't, you have a ready methodology that gives you meetings upon meetings and two week deliverables and every little thing broken down to the smallest unit under the guise of "empowerment".
Oop, I'm aware of this, it is very annoying, I think I just hit it just the other day; just had no idea what you were referring to from the description.
The Covid Super-Dodgers
Ask HN: Can you browse the web via taxonomy?
I'm wondering if anyone has attempted to categorize sites or domains into a taxonomy and allow for browsing (and searching) within a well defined structure?
The author is someone I wouldn't like to have a discussion with at a party, because he insists if one character looks like the real actor in that movie, then every other character must have their actor doppelganger in that universe...
I have this new channel. Tell me your thoughts~
I do recall Asami using a HAMT and it is written in Clojure. [1]: https://github.com/threatgrid/asami
I want to hear more, esp about the distributed applications, do you have any useful links, or can I buy you an "e coffee" to pick your brain for a few minutes?
I feel like in the last years the level of arrogance of developers has reached a peak - somehow the market being full of opportunities, people seem to forget that there are others out there getting paid way less, doing critical things for society and going through way more stressful situations than the pain of not knowing what new shiny language to chose for your next microservice.

As having a developer background that switched more towards management now, how do you expect companies to hire? From what I see take at home tasks are not ok, making everyone loose their minds, technical interviews are also not ok, then what? The attitude of developers now is: 30 minute interview in which the company needs to offer 100% salary increase compared to previous job, pay the developer a full day as he took 30 minutes for you and then just hire him based on his CV in which he lists all possible technologies in the world that he read about once in an article or wrote a to-do app 3 years ago.
The whole ecosystem is a mess. Not only did Google Wallet get renamed three times (as posted in the other comment) but the other functionality doesn't even work. The other day Google prompted me to store a boarding pass in Google Pay, but when I got to the airport the scanners didn't recognise it and I had to go requeue for 20 minutes. The PDF code scanned fine.
The evcxr project https://github.com/google/evcxr is implementing what amounts to an experimental Rust REPL. (Though there's inherently something a bit weird about a REPL for C/C++-like languages, where the phase separation between compile- and run-time is so inherent to the programming model.)
Un-paywalled: https://archive.ph/jEXLV

tl;dr: We're all doomed to get COVID because it's super contagious now. When it happens, don't beat yourself up, you've had a good run.

Gross.
I will probably be leaving my current position in a few weeks. I have some money saved up. I think I will go through "How To Design Programs" and then SICP.

I know it doesn't work for everyone, but all of the (admittedly few) people that I have met who have been through SICP said it helped them get to the next level.
There always is - that is why the sunk cost fallacy is so attractive. But still, this seems one of the most clear cut example of the switching costs being worth it, i have ever seen.

I'm doubtful that the author learned the correct lesson even by the end. I suspect if a similar thing happened again the author would fall victim to it again.
I don't believe that's the case, looking at the commit [0]

[0] https://github.com/tzinfo/tzinfo/commit/01bcca5de920093b52fb...
Sssh! The official line is that only China does this.
There are a variety of solutions to this but CRDTs are a very good one (CRDTs solve your problem (https://en.wikipedia.org/wiki/Conflict-free_replicated_data_...). If the operations you're doing commute (that is a ○ b = b ○ a, e.g. the order in which you apply the operations doesn't matter) then one could apply all operations in parallel, and only send the final result of doing them all. Casandra uses LWW-Element-Set CRDTS to solve this exact problem (https://cassandra.apache.org/doc/latest/cassandra/architectu...).
You only notice the cases where you try to reproduce things, and time being limited ,you only reproduce obscure results.

As a comparison: I did a bunch of math too and in some cases just accepted the proofs I build on.

Same for programming: I neither audited lapac not GCC.

For the engineering crowd software dependencies are a probably a good comparison. If they come from a credible source you trust them and build on top of them.

Nobody blames companies for not auditing the kernel if there is a security problem in it, but everybody screams: “You should have verified the result”, if some paper is redracted.
Number of papers or patents published is not a good metric. Just look at 5G. Huawei has the most patents but 99% of the patent revenue goes to Nokia, Ericsson, Samsung, Qualcomm and others because their patents are more foundational and frankly many of Huawei’s patents are trivial.

It’s pretty easy to cybersquat with patent spamming. Likewise, you can publish lots of papers which are small extensions of existing papers but most of the papers that spawned new large scale improvements came out of the West like “Attention is All You Need” which introduced transformer models and is much more important and notable.

Quantity != quality.
Georgi Dinkov AKA Haidut on Vaccines, mRNA therapies, Genetics, Transhumanism, Metaverse, Cancer Stocks, Big Pharma/Tech, Coffee, Metabolic Diseases, Stress and Fatigue.
I wouldn't call that invented... "LSI-11 (PDP-11 LSI CPU implementation) clone" :)
My guess - contractual obligations or some other liability?
The agency is incentivized to draw out the work to maximize billable hours
On the contrary, there is absolutely no way this started on bodybuilding.com. Even a quick Google search attributes Karl Klein with this brilliant myth
Tangentially, the non-100% DCI-P3 gamut (or better) display made it a no-go for me. Color gamut and accuracy is a must for any visual or visual-adjacent work.
Not a very deep CS-y one, but still one of my favourite data structures: Promise Maps.

It only works in languages where promises/futures/tasks are a first-class citizen. Eg JavaScript.

When caching the result of an expensive computation or a network call, don't actually cache the result, but cache the promise that awaits the result. Ie don't make a

Map<Key, Result>

but a

Map<Key, Promise<Result>>

This way, if a new, uncached key gets requested twice in rapid succession, ie faster than the computation takes, you avoid computing/fetching the same value twice. This trick works because:

- promises hold on to their result value indefinitely (until they're GC'ed)

- you can await (or .then()) an existing promise as many times as you want

- awaiting an already-resolved promise is a very low-overhead operation.

In other words, the promise acts as a mutex around the computation, and the resulting code is understandable even by people unfamiliar with mutexes, locks and so on.
You can always calculate your personal rate of inflation

https://www.destatis.de/EN/Themes/Economy/Prices/Consumer-Pr...
I imagine you can have one thread modifying the vector while trying to read its length from another thread.
1. Things have already gone wrong...

2. I guess I would add "slowly and carefully".
The baggage weight limit has nothing to do with the weight of the aircraft. It is about keeping the bags light enough for handling, to protect the backs of baggage handlers (and automated equipment/belts). Unlike thier heavy bag, a heavy passenger is generally capable of walking themselves onto the plane.
UK blocks China from licensing Manchester Uni's robot vision tech
An even better link:

https://old.reddit.com/r/raspberry_pi/comments/w37gx2/i_free...
This post: http://www.frankmcsherry.org/graph/scalability/cost/2015/01/...

"Scalability! But at what COST?"

In it Frank McSherry uses a handful of data structure tricks to make graph algorithms like connectivity and PageRank run progressively faster on his laptop, beating distributed cluster implementations. It's actually a version of their HotOS paper with Isard and Murray.

Admittedly it's the opposite of obscure, being kind of a myth busting piece about distributed processing being faster and how even largish data sets can fit on a single node (and even your laptop).
Mark Zuckerberg: Could Facebook move faster? (2012)
> ... we find the USA fighting wars disheveling millions over weapons of mass destruction that never existed.

This violates all forms of acceptable reasoning.

> Nothing has really changed, it only became easier to automate what was already there before.

But even if we would accept that kind of reasoning, your excuse is that it will cause the same problems, but faster?

I don't get your position. I really don't get it.
In terms of that product, it has.

And if that product was as essential to life for as many people as food and gas are, that might be important.
We all know about the immutable vectors of clojure (tries, basically). I always preferred the RRB-tree which is the same thing, but relaxes the leftwise dense requirement. This means you have a bit-partitioned trie until you do a split, merge or insert, after which you get a slightly slower operations, but still very competitive.

It is actually a quite trivial change until you come to the merge algorithm which is finicky in all the wrong ways. The benefits are (in clojure terminology) O(1)ish splits, inserts and concatenations instead of O(n).

I don't know if it can be called obscure anymore, since Scala's vectors are RRB-trees and clojure actually has an implementation of them, but I often see people talk about ropes in situations where an RRB tree should be a no-brainer.