skysight-inc/HackerNews huggingface dataset:
This trend to lower cost has downsides. My local Home Depot has become horrible to visit. Last time I was there I had to wait 40 minutes for a piece of hose to be cut from a reel. Workers in an adjacent aisle said they weren’t authorized to cut the hose, and the one worker on shift who was authorized was apparently busy. Once someone called for him it took ~15 minutes for him to arrive followed by 15 minutes of him helping the one guy there before me. So ~30 minutes later he cut my 4 foot length of hose, then discovered there was no SKU to scan for by-the-foot measurement. Another ten minutes passed of him radioing for a SKU to give me on a slip of paper. I felt like I should not have bothered, apparently the workers are all overworked or not permitted to help.

Meanwhile at my local ACE hardware store they manage to have everything I need in a MUCH smaller building, but they always have someone on hand if any help is needed.

So I’d rather the shop cut costs in other ways, like use smaller buildings and narrower aisles to save on rent. I like people.
Nvidia still doesn't work as well as other gpus under wayland, which is why GbOME still uses X by default for NVIDIA
People in Spain and the rest of the Mediterranean have managed to live without AC for millenia. Some old houses, centuries old, are cool as a cucumber during some of the worst months of summer.

And yet, in my experience, it’s like Americans are allergic to insulation and building houses appropriate to the climate. Something is very weird when houses in SF look just like houses in Portland which look just like houses in every suburban photo of the US I’ve ever seen.

In Europe architecture changes with the climate, in the US it doesn’t seem to (or at least I haven’t noticed and please tell me that i’n wrong)
How did people get anything done in Houston before ACs became common in the mid 20th century?
Here's my anecdata:

I had a house in the Mojave Desert. In summer the temperature would run 105-115° during the day and 95-110° at night for most of July, August, and September.

I'm not from the desert, so I racked up $200/month power bills for my small home. (I kept it set at 80° when I was home, and 76° when my wife was home.)

My neighbor across the street (with a wife and three kids) didn't seem to mind for the most part. He would have his windows open until the temperature got to 105°. Then he'd open them again at night on those days when it dipped below 100°.

Even if the temperature was over 110° there were plenty of people driving around with their car windows open. And I'm talking brand new luxury cars, not junkers.

Some people are just bothered more by heat than others.
I doubt that any solutions which start off as “let’s change the whole universe” are going to get very far.

Yes, the situation sucks. I just looked at the frontend of a relatively small app we use for administration, and it depends on almost 5000 node modules versions. But this problem needs to be dealt with as soon as possible, and I don’t think that a fundamental change in development culture—making everything harder for developers in the process—is going to help.
In Phoenix yes, but I can get through winter without using a heater.
I've been reading about hurd for so long, today is the day I try it in Virtualbox! Cool stuff, good work people!
> > My point, which you seem to be avoiding, is that words are a lot less ambiguous than symbols.

> Sorry, I don't accept this and you haven't demonstrated it except to say "well we can use an appeal to other things for words, but not for symbols." That really dosn't fly at all, for me.

Nobody is a blank slate. When we learn things we associate with what we already know. The power of symbols is that they are inherently abstract and are not associated with what we previously knew, but when we're learning things that makes symbols harder to understand, not easier. "Sum" is a lot clearer than "Σ" if you're starting out. Quick, what do you think this means?

{↑1 ⍵∨.∧3 4=+/,¯1 0 1∘.⊖¯1 0 1∘.⌽⊂⍵}

(That's an actual program, btw, I didn't mash my keyboard). If you don't know any of those symbols, where would you even START?

But wait, let me make it easier on you:

life←{↑1 ⍵∨.∧3 4=+/,¯1 0 1∘.⊖¯1 0 1∘.⌽⊂⍵}

Now what do you think it means? Does it give you a place to start, at least? (That's the APL version of the game of life)

That version of the game of life is much simpler than if I were to write it in C#, which would be hundreds of lines longer. But is it easier? Of course not. It's absolutely baffling.

> Imagine, if you please, a world where people in industry and on Hacker News repea an untrue mantra that one language is "simpler" from first principles, confusing familiarity with simplicity?

Simple and easy are not the same things. Familiar IS easier, even if it's not simpler. I can imagine that world, but I also live in this world, where people have a current set of knowledge and it's easier to bridge the gap between what they don't know and what they do know by using what they already know.
Can we stop saying that pgp is busted and just talk about how the keyservers are the problem with how people decides to exchange keys ?

I don't use key servers. So when I get an encrypted message from my friend I have no issues.

Allowing a third party such as a key server to play some role in veifiing the authenticity of a key is basically broken from tht start, and has nothing to do with pgp it's self.
I remember seeing something about how a last resort action against climate change would be to seed massive amounts of fertilizer across the ocean to cause a super alage bloom (and fuck everything else living in the ocean). I wonder if this fertilizer abuse may end up saving us from (one) global disaster after all.
To be clear: this is a subhed from Filippo's email newsletter (which you should subscribe to), relating a news item about the ridiculous SKS/GnuPG-key-handling fiasco from last week; it is not a comprehensive summary of all the ways in which OpenPGP is broken, despite the title.
Lotus Improv. Closest today are Quantrix and maybe Airtable.
There are ways to architect software so that it can be cooperatively developed, so that you can fork and maintain an individual component instead of an entire stack.
"By my invention you can sit down in your office in Chicago, take a pencil in your hand, write a message to me, and as your pencil moves, a pencil here in my laboratory moves simultaneously, and forms the same letters and words in the same way. What you write in Chicago is instantly reproduced here in fac-simile. You may write in any language, use a code or cipher, no matter, a fac-simile is produced here. If you want to draw a picture it is the same, the picture is reproduced here. The artist of your newspaper can, by this device, telegraph his pictures of a railway wreck or other occurrences just as a reporter telegraphs his description in words."

I'm amazed how much this reads like a modern pitch. Fascinating
I made a comment on this below, X already exists, why can't people live with X/fix X and thus utilize the already existing code vs recreate all the interfaces that X already has?
The neurology of the Cuban “sonic attacks”
99PI did a wonderful episode on this:
https://99percentinvisible.org/episode/thermal-delight/

Basically, the US abandoned their regionally different architecture once AC became common.
Hm, interesting. One way to solve this would be to have a language with a very rigid import system - it should be _impossible_ for a library to use a module it hasn't imported, even if that module has been loaded elsewhere in a process. This is probably harder than it looks, and many languages have introspection features that are incompatible with this goal.

With a rigid import system, each library would be forced to declare what it's going to import (including any system libraries), and then you could e.g. enforce a warning + confirmation any time an updated dependency changes its import list.

It doesn't prevent you from getting owned by a modified privileged library, but it's better than the current case. Unfortunately, it probably requires some language (re-)design to fully implement this approach.
The Hayward fault seems to have the most seismic activity lately. You'll feel them 2+ times a year in the East Bay--especially if you're in an older, multi-story building when it strikes.
That's actually a very good point. From my anecdotal experience, I actually vastly prefer Lisp like syntax to basically any other syntax because it's so regular and clearly delimited, so I can grab whole expressions and move them around and transform them really easily. It also makes it easier to navigate code, and in my opinion easier to read since I don't have to remember "syntax", just the behavior of functions and macros.

Weirdly enough, even if a language isn't "lispy" I would still consider a expressions a point in it's favor.
That's ok, pgp is also terrible to use on the command line so we can complain about that.
Modern windows can greatly interfere with wireless signals. I believe many make use of a very small (barely noticeable) metal mesh which can break havoc with wireless signals.

Manufacturers are likely aware of the issue and test for it but still, I get better wifi through the wall to my house rather than through a large window with line of sight to the accesspoint.
How did people get anything done in Houston before ACs became common in the mid 20th century?

Swamp coolers. When I lived in Houston, they were very common.

https://en.wikipedia.org/wiki/Evaporative_cooler
You didn't actually answer the OP's question. There is nothing Wayland does that could not have been done via the X11 extension mechanism. X has already been reinvented several times --- few things use the core protocol nowadays, after all! For example, XRender for text is now universal.

The thing that's different about Wayland is that for reasons that nobody ever explains clearly at a technical level, this time, a few influential people created a new and (IMHO, inferior) protocol instead of continuing to use the X extension mechanism.

Security? Isolate the X session data to individual client connections. Buffer management? Do it like GLX does. Want server-side decorations for some reason? What's stopping you? Sure, ICCCM isn't trivial, but it exists, and it's flexible.
I fail to understand. Thick stone walls yield cold rooms passively.
OpenPGP is broken in the sense discussed in this newsletter: the keyserver system interacts in a catastrophic way with GnuPG's naive key parsing code, and OpenPGP's deployment at scale depends on keyservers.

OpenPGP is broken in other ways! But this is a headline given to a particular current events story about OpenPGP.
Will definitely try waking up earlier but when the little one is older so I do not wake up several times during the night when she cries for food. I managed to do it just before she was born and absolutely loved the quiet house and possibility to focus.

Growing kids is a concern and absolutely love spending time with them but sometimes just need time to myself.
Unpopular opinion...

So four hours later it's buried under the "didn't fail" and "killer app" explanations.

When a question is raised over and over again through the ages, it's because the answer (in this case, usability) is being dismissed every single time.
Can you please not post in the flamewar style to HN? Both this and your previous post have been so, and it's a thing we're trying to avoid here.

https://news.ycombinator.com/newsguidelines.html
The problem is, that your sentiment misses the point. The most valuable years can be wasted, as long as one thing remains: this feynman like spirit, to discover and conquer topics, interests and obsessions.

Everything else, can be done later.

So what is gained, if you extuingish that flame and heap tons of dead information into there lifes?
another case of technological dead end
Yeah the benchmarks aren't quite the clear AMD win (in performance/price) I was expecting for gaming. That said, it's important to factor in all the other stuff such as motherboards and coolers. Until there is a cheaper chipset, I expect a B550, the scales are tilted a bit further towards the 9700K. The CPU prices are intersting, but for anyone upgrading the total upgrade cost is what counts. So the minimum to compare would be CPU, cooler and motherboard.
I agree that deterministic would've been a better choice in this context.

I work on things close to Bazel, and the word "hermetic" gets thrown around a lot. And because of that, hermetic in my mind gets translated to "how an ideal build of a project should behave" (which obviously is wrong).
Helium Hotspot
I believe that's correct. There's an 8 core with 65w TDP which has a confirmed single chiplet; my guess is the 8 core with 105w TDP is two chiplets with several cores disabled.
Sean D'Epagnier and SV Alexandra – The Shipping News
I’m pretty sure Go does not do any LTO at all.
How to Remove Bixby from Samsung Phones
5000? Wow. That's gotta be a pretty sizable fraction of the entire Node library ecosystem. Does it count duplicates?

With a dependency forest that large, it's small wonder that not more JS projects aren't compromised by bad dependencies...
Yeah it's possible, but it leads to somewhat awkward languages where you have sometimes multiple levels of desugaring going on and it's annoying. The last time I looked into Julia (IIRC >6 years ago) it had something similar going on and it really scared me off. The problem with having a "technically homoiconic" language is that you're going to end up with not only lots of desugaring, but multiple syntaxes for the same things.
This might be of interest for you then, for stats on what people actually suffer from: https://twitter.com/billgates/status/1138520780042465280
I have a gvido device, which you seem to be referencing here. If I could return it, I would have, but their return policy is extremely restrictive and basically amounts to no returns.

It's waaaayyyy to slow to truly function. It can take several seconds for it to process a page turn, and their official fix for it is to change so that it only turns one page at a time.

I make it work when I'm practicing, but I will not use it for a performance, or ensemble work. I recommend staying far away until they can turn out faster devices.
can you tell me more about your use of autohotkey ?
The "lack of a killer app" point made in the comments below is interesting in light of the Perl6 story today.
Things we can learn about productivity from some pretty women
The big windows in office buildings exist to create a sealed envelope to more efficiently heat and cool the air inside. They are far more efficient than the windows in your home.
Yeah really depends one distance and local conditions. And sometime 'micro' local conditions.

Friend of mine that lived in Oakland during the 89 earthquake mentioned seeing a 'line' of damaged buildings that snaked through a neighborhood. One or two houses on a block were wrecked. The houses across the street were also wrecked. Houses next to them were fine. Go the next street over same thing.

He thinks that line followed an old creek bed that developers filled in. So those houses were built on mud overlain with poorly compacted fill. During the earthquake the mud liquefied and sloshed around and the fill settled.

Flip side, friend in the Santa Cruz mountains a couple of miles from the epicenter. His house is built on top of a hard shale outcrop. His house suffered no damage at all.
All languages are slowly converging back to being a LISP.

It's just time.
Yes, seven "you"'s in a row coupled with negative statements crosses into personal attack. Please follow the site guidelines so we don't have to ban you again.

https://news.ycombinator.com/newsguidelines.html
An example: your server is handling requests to two endpoints. Endpoint A responds in ~100ms, B in ~200ms. You start caching some responses to A higher up. Now your P99 across all servers is higher even though you improved the performance. (Potentially setting off alarms on previous thresholds)

While it doesn't solve the alerts, for viewing the data like that heatmaps are amazing. But you need the raw numbers (or predefined bands for aggregation, but that limits flexibility)
> I doubt that any gamer need more than 4-6 cores, but single thread is very important.

That's largely false for modern engines.
Reinventing the wheel is one end of the spectrum, but so is putting a bunch of magic words in a file and thinking you needn't worry. (To be fair, too many tutorials hand wave away what really happens in Gemfile/package.json/etc and barely pay lip service, if at all, to the responsibilities that come with having those dependencies) I don't miss the "old" days of searching for libs, extracting a zip, and trying to figure out the integration steps, but there is something to be said for there being a bit more of a sense of ownership.
Yeah some people (locals) are just more used to heat/cold. I moved around every few years so I'm kind of prepared to most of the weird weathers (no desert heat though, but wet heat and super cold winters).
> Looks like AMD is the way to go for desktop Linux boxes going forward.

Problem is: desktop Linux has an irrelevant market share, and the trivial workaround (use intel IGP or go buy and AMD graphics card) do not work when you don't just manage your one PC but actually maintain a system that is produced in series...

And honestly being upset at nVidia leads nowhere. The architecture of Wayland is complete bullshit to begin with and I'm not sure any other graphic stack of competing systems went that way, EVEN for systems that have a single window manager (well, that's most of other systems... -- so the situation is strangely kind of reversed). So hopefully wlroots will eventually improve the situation or something like that, but is it even convenient to build something that does not link the graphics session to the low level graphics stack with that? I hope it is, because if not, that is hopeless... :/

And I've not even talked about extra deps like Cuda, or the general lead nVidia still have in perf/W and/or perf/price (IMO AMD is close, but no cigar)

The X proto was maybe shit, but at least the general approach did not lead to the kind of insanity we are currently seeing. And people discussing the Death of X when Wayland ecosystem is maybe still 5 years away from decent quality and some reasonable feature completeness... (remoting, anybody? anything good enough for Wine?)

Oh well, we will see...
Archival footage, audio immerses viewers in Apollo: Missions to the Moon
How to Structure Product Management, According to Rich Mironov
Huawei Technologies’ Links to Chinese State Security Services
I fail to understand. Thick stone walls yield cold rooms passively.

For a while, not not indefinitely.

In European climates, it cools off at night or through moisture, allowing the stone to release the heat it stored during the day.

There is a vast swath of the United States larger than Europe where it simply does not cool down at night and/or moisture is insufficient, and so stone buildings become ovens.
I read the summary, and I don't agree. The tests being done are used under special circumstances. No way a camera mounted 12 or 14 feet up at an angle is going to provide the same type of results as youtube videos which are at a flat angle. There are simply too many "angle" like issues that will result in the accuracy being quite poor.
If you look at dependencies as black-boxes that contain their own transitive dependencies, then sure, any given "root-level" dependency of sufficient complexity might end up requesting every permission.

On the other hand, if each dependency in the deps tree had its own required permissions, and you had to grant those permissions to that specific dependency rather than to the rootmost branch of the deps tree that contained it, then things would be a lot nicer. The more fine-grained library authors were in splitting out dependencies, the clearer the permissions situation would be; it'd be clear that e.g. a "left-pad" package way down in the tree wouldn't need any system access.

On the other hand, it'd make sense if dependencies could only add new transitive dependencies during "version update due to automatic version-constraint re-evaluation" if the computed transitive closure of the required permissions didn't increase. Otherwise it'd stop and ask you whether you wanted to authorize the addition of a dep that now asked for these additional permissions.
Nvidia says 710 can do both, 3840x2160 at 60Hz supported over HDMI. 3840x2160 at 60Hz supported over DisplayPort. https://www.geforce.com/hardware/desktop-gpus/geforce-gt-710...

But it’s up to the manufacturers to decide what ports to include.

PS: That said it does seem like there is a premium associated with DisplayPort, are you sure you are not also paying that premium when looking at Intel motherboards?
> There's a reason that essentially zero websites default to a dark theme.

Yes, it seems like there is. I am wondering what that reason may be.

My preference for dark themes is based on my current typical viewing conditions, which are rooms with low to medium light levels where the brightness of my screen is also low. In such a situation, I do not wish to look at white-themed content because it is uncomfortably bright. In a place with a lot of light, I would not mind the light theme, but it still would not be my preference because of the established habit. With the sun shining directly into the screen, it may even be impossible to use the dark theme, but that is an edge case which, in my opinion, should not affect how a website looks by default.

I assume that many theme-related preferences are habit-based. In my opinion, a reasonable UI design should at least allow simple switching between dark and light themes.
Steam is a pretty niche userbase and not at all representative of the desktop market at large.
I interpreted that differently: it's fine to have many dependencies, even third-party ones. What's a problem is having many third-parties.

The maintenance and trust verification overhead for a micro "5 lines of code" dependency is usually way higher than just rewriting those 5 lines yourself.

As an aside: just because someone made their code available doesn't mean it's good or that it solves all your edge cases. Getting those fixed also takes up time.
I know this is about ruby, but it's worth noting that this kind of thing would be solved by effect systems, e.g. Haskell's IO type. If IO isn't part of the signature, you know it's cpu only. Furthermore, you can get more specific such as having a DB type to indicate some code only has access to databases rather than the internet as a whole.
I don't think Elixir is homoiconic.
Ostensibly, yes, but that would clash with the official narrative ("X is broken and bloated and needs to be deprecated"). If they can maintain Xwayland indefinitely, they can maintain a stub DDX that works with kms indefinitely also. What they are telling us is that they want to get rid of the entire thing. Pointing out that Xwayland would be relatively easy to maintain would be stating the emperor has no clothes.
You can get things same day, returns/replacements are much easier, price matching is often an option, you don’t have to worry about trickery with Amazon sellers or ambiguous listings (like laptops with similar yearly models) and sometimes outright lying listings, mixups, shipping problems (I had an entire computer go to the wrong apartment,) package theft (had a Unifi USG stolen even though it had been sitting for under a couple hours!) and honestly more.

Heavy stuff through shipping can be expensive if you can’t get it through Amazon Prime. Shipping with Li-ion batteries is restricted to ground shipping.

I still ship many of my electronics, but yeah actually it’s not a wash. Especially if you are buying used stuff, I find eBay is often a ripoff.
more like ml to be honest, static, pattern matched is taking roots