skysight-inc/HackerNews huggingface dataset:
It's a mix of three different cultural factors long extant in the programming community which came together to create today's keyboard culture:

1. Keyboard elitism

Until as late as the early 2000s, there was a lot of elitism in programming circles about how using the mouse was something only "lusers" did. Keyboarding was supposedly faster than mousing (even though programmers do a lot more thinking than either keyboarding or mousing) and was the mark of an expert user. These communities would often shill certain keyboards, like the IBM Model M, or the Happy Hacking Keyboard (HHKB) because of their resilience and the feedback one felt from clacking the keys.

2. Customizing/Hacking

Not much has to be said here. Hackers have been customizing their setups for as long as setups could be customized. The ability to program custom keyboard layouts and make custom keyboard firmware is as iconic hacking as it gets.

3. Setup as identity culture

From the late 2000s, Unix Porn and a lot of other "setup porn" stuff became very popular. People would make cool setups that they really identified with and so setting up your keyboard to express your personal identity became a bit of a hacker rite of passage.

While keyboard culture may have started with these ingredients, it's definitely its own thing these days. I'm not in it myself but I like watching it from the sidelines and it's really cool to see what people come up with. Cool layouts, custom firmware, colored keys, experimenting with different layouts. It's just like trying to get the perfect emacs config: more bikeshedding than productivity hack, but I mean it's a hobby, and a fun enriching one at that.

As you say the more practical thing is to just buy an ergo keyboard that works with your wrists/shoulders/neck and call it a day. I have a Model M from when I was an impressionable teen who thought owning a Model M and not using the mouse was the be-all-end-all of being a power computer user, but I mostly use a Kinesis Ergo for my day-to-day computing needs. I'm at a (hybrid) startup these days and we don't really have a dedicated office to store stuff in so I bring an HHKB in to the office because of its portability. I use trackballs for my mousing. That's about it. Holding my arms, wrists, and back in ergo positions is much more important to me than any keyboard really. Though really rock climbing has been the single thing that helped my wrists beat RSI where nothing else really could.
It depends on the exact elements that are causing that emission level. Heavy metals such as those present in nuclear waste tend to bio-accumulate in marine organisms, that then find their way into the food chain.

This is unlike, say, naturally radioactive carbon or potassium isotopes, that have a relatively constant concentration in the animal's body over it's life time - if a fish eats some high potassium food, it will excrete an equivalent of his own equally radioactive amount to maintain homeostasis.

It's for this exact reason the net "banana dose" of radiation, unless you are potassium deficient, is in fact zero.
Wolf Haven International
Unfortunately, humans generally don't care about what they can't see.

We can see pollution in water, on land, but not in the air.
It’s not possible to have a license over an ML model trained on other peoples’ works, since such models are uncopyrightable. They’re more like a phone book; a collection of facts trained by an entirely un-creative process. https://news.ycombinator.com/item?id=36691050

This hasn’t been proven in court, but it seems the most likely outcome.
Not all questions need a variety of answers. If its good enough for your needs go for it. Saves some time searching.
> I've noticed that dark-theme users (eg during live streaming) crank up their brightness/contrast to compensate for the low-contrast dark themes

On the whole, this actually allows you to achieve the same contrast level with lower total light emission. If you are in fact clinically light sensitive and you also have difficulty with low contrast, you just can't achieve the balance of contrast you need as effectively with light themes.

> then they are surprised to be blinded when they open a webpage, which is extremely likely to be light themed

For me it's well worth it to sacrifice the 'artistic integrity' of web designers' intentions and use something like Dark Reader or Midnight Lizard to force a dark theme across the whole web.
> I used to work in trading and I think some of the principles I learned there apply directly to salary negotiations.

I think exactly zero of those principles apply (assuming you are talking about stock exchange trades).

All these types of "technical analysis" on price-discovery during negotiations is fairly pointless.

There's only one rule that works when personally doing a trade with someone:(whether you're negotiating salary, buying a property or selling car) be likeable!

The more the other party likes you, the more flexible they are going to be on their price-points.

So, sure, the hiring manager has a band (say $100k to $140k). What you want is for him to make an offer at the top of his band ... or even higher - if you interview well they may decide on a more senior role for you.

This is why, even if your minimum is above his maximum, be likeable!

Even if you have already decided you don't want that job, be likeable!

Even if you don't want to work for that particular company, be likeable!

Even if you already have an offer in hand that is way above anything anyone else can offer you, be likeable!

What likeable means depends on context.

When selling a car, being upfront and having all the paperwork up to date, and all the services done on time and recorded as such, a clearance certificate to prove "not stolen", etc ... makes you likeable.

When negotiating a salary, gush about how nice their offices are, how their mission statement resonates with you, how wonderful the interviewers have been up to that point.[1] Make a list of things you admire about the company/its products/its vision ahead of time so that you can truthfully tell them all wonderful things about themselves.

Practice telling people horrible things in nice ways (called constructive criticism?). Practice, Practice, Practice! They will give you stupid challenges, maybe even broken code. How you respond must make them like you even more for the role.

You must come across as a collaborator and leverager, not as a coding genius. Coding geniuses are a dime a dozen. Competent coders who can act as a force multiplier for their team, their manager or their company are rare gems who get offered much more than genius coders.

Everywhere I've been at, or done work for, for over 25 years, has been filled with people who would rather work with pleasant people who are basically competent (or even slightly below average) than work with unpleasant people, no matter how good they are technically.

Look at highly paid surgeons: the ones making the most money are the ones filling every single one of their slots. They know - bedside manners matter.

[1] I spent a full day interview for a senior-ish (L5? L6? Dunno now) position at AWS. It was hard work, with challenges coming at me the whole day, coding, design, etc ... and yet I thanked every single interviewer for their time, and told them how much I appreciate them making the effort to interview me. I was warm, pleasant and friendly the whole day, not just civil, in spite of the constant set of new problems thrown my way.
To be fair, current Korean regime is calm.
I remember there was a blog post saying that everyone should write an ARCHITECTURE.md file as well for their projects. It’s content can be a great starting point(s).
I think the word "exploitation" colloquially has the connotation of exploiting the poor as they cannot afford to leave the exploiting conditions.

Exploitation is labor is never usually headlined in the context of $400k/year salary. Technically, you're right. But we can take this to the limit, instead of $400k, let's say $4M/year for a job that's worth $5M/year? Are they "exploited". Yes, but not by the common use of the term.

Perhaps the reason for GP's take was that it robs away the colloquial definition of exploiration in an entirely different context where it's the least meaningful, i.e. exploitation of Bangladeshi child laborers vs. a programmer earning $400k year salary.
Why does this only compare tritium, which is the supposedly safe material? What about "cesium, cobalt, lithium, and strontium" which are supposedly more dangerous?
I think you're judging him by values of "normal" people and weigh the average outcomes of choices. But criminals are known as people willing to take risks and would bet on low-probable but very lucrative outcome.

A route in Hague was a guaranteed lifetime sentence, while playing some role in the elites gave some low-probable possibilities.
> So people continue to predict doomsday and most of the time it doesn’t happen.

Well, the same is true for any prediction of anything unlikely. People continue to predict world-changing innovations, and most of the time they are wrong. That's the reality of any low-probability/high-impact prediction, in the positive or negative direction.

As a specific case of that: most startups fail, so predicting a startup will fail is safe.

I'm pretty prone to exactly that prediction. But I like this quote from Erik Davis (https://www.google.ch/books/edition/High_Weirdness/Rcq2DwAAQ...): "In the court of the mind, skepticism makes a great grand vizier, but a lousy lord."
All I want is a landscape oriented b5 notebook, not that many around.
Nationalistic flamewar will get you banned here, regardless of which country you have a problem with. No more of this please.

https://news.ycombinator.com/newsguidelines.html
In a world where transistor-per-$ growth is running at most 10-20% per generation, you have to get more out of the transistors you have, or else prices go up. Or both.

So raw performance has stagnated and gains have been concentrated in things like DLSS 2.5 that let you get native quality at a 30% speedup or better than native DLAA at 0% speedup, or FSR2 Quality level quality at 50-70% speedup. Cause that gets you more performance out of a small increase of transistors/cost.
[R5RS][1] is simple.

To get any work done with it, though, you need to write your own Python.

[1]: https://conservatory.scheme.org/schemers/Documents/Standards...
> Isn’t it possible that there was a period before the Big Bang, and then for some reason the universe became hot everywhere?

Well, sure, it's possible. I was assuming the current cosmological standard model is correct, which might in fact be wrong, or at least incomplete. Actually, I'm certain it's incomplete.

Today we can trace back the universe to when it was a tiny fraction of a second old using standard physics. Everything is well understood. Before that: who knows?

> An apple is a definite size, and can fit only a certain number of atoms.

There were no atoms when the current observable universe was the size of an apple. It was too hot for atoms. It was more like a quark-gluon plasma.

> Therefore all apples would’ve been the same size they were today, just packed more closely together. Hence “the size of an apple” seems to lose all meaning.

Obviously "the size of an apple" is a phrase for laymen. We could say "10cm in diameter" using the standard definitions of the meter and second.

>This contradiction seems to clear itself up if one allows for a “before the big bang”, since there’s no need to say that everything was compressed to a single small volume.

There is no contradiction.
Currently React and HTML. You will also be able to choose between Chakra UI, tailwindcss and more
There is no base time. In the point of view of the thing moving quickly away from us, OUR clocks are slower. For both of us, the other’s clock seems to tick slower. The situation is symmetric. This is why it’s called relativity, there is no objective static frame of reference

And yes even if you were moving back and forth by one micron at close to the speed of light then an observer stationary relative to you would see your clock tick slower
> I think the best outcome possible for Spacelift and companies like it now is the OpenTF route (assuming you can't get a suitably proper BUSL license grant from HashiCorp, which it seems like you might if you get them to declare you "not a competitor" even once, according to the FAQ as it reads today. IANAL.)

IANAL as well, but this sounds like a HUGE trap. Will that protect you from their next licensing change and its restrictions?

Is such a declaration transferrable? Would it limit Spacelift's exit strategies because they would be unable to ship their product if acquired?

If there is a community where the new licensing terms no longer meet people's needs, then something like OpenTF is absolutely the right way to go. Anything else, and your company is operating by the grace of Hashi.
I think this is a case of mis-assigned blame (on the tool’s part, not the author’s). My semi-educated guesswork follows:

Looking at the disassembly screenshots in the article, the total runtime for the benchmark doesn’t appear to have decreased by very much. “Time per op” has decreased by half in max_lol(), but the total number of ops being performed has likely increased, too - Specifically, extra work was done “for free” (As was shown in min_max).

This experiment is showing us that the compiler is in fact doing exactly what we want - maximizing throughput in the face of a stall by pipelining!

In this experiment, maxV is potentially being written to with each iteration of the loop. Valid execution of the next iteration requires us to wait on that updated value of maxV. This comparison and write takes longer than just running an instruction - it’s a stall point.

In the first profile, the compare instruction gets full credit for all the time the CPU is stalled waiting on that value to be written - there’s nothing else it can be doing at the time.

In the other profiles, we see a more “honest” picture of how long the comparison takes. After the compare instruction is done, we move on to other things which DON’T rely on knowing maxV - printing “lol”, or doing the other compare and write for minV.

I propose that the processor is doing our added work on every iteration of the loop, no matter what (And why not? Nothing else would be happening in that time). That BLT instruction isn’t making things faster, it’s just deciding whether to throw away the results of our extra work or keep it.

Throughput is important, but not always the same thing as speed. It’s good to keep that in mind with metrics like ops/time, particularly if the benchmarking tool tries to blame stuff like cache misses or other stalls on a (relatively) innocent compare instruction!
Ireland’s wild data is leaving economists stumped
Surely this is an observer dependent effect due to the expansion of the universe?

For example, if a light ray was emitted each second billions of years ago, by now we observe that a redder light is emitted every 5 seconds. Because while it was travelling, the space through which it travelled expanded.

When the article says things like "time was slower in the past" it makes my head hurt. Don't they mean "events in the past appear to run 5 times slower when observed today?"
As cool as that would be, most experiments still believe the curvature of space to be flat, which means if you travel endlessly in one direction relative to a starting point, you will never return to that starting point.

https://en.m.wikipedia.org/wiki/Shape_of_the_universe
(An ((Even Better) Lisp) Interpreter (In Python))
I wonder if there would be any way to make use of whatever network acceleration hardware this thing has for file serving.

Could you tell it "Here's a list of 500 people, I want you duplicate all the packets I'm sending to all of them", and run all of Netflix on a few of these playing movies at different time offsets?

Why does everything need so much electricity and giant servers, when these things can push so much data around, and so much Internet traffic could be done just as file streaming with a bit of control data?

Routers always seem super impressive. The switch insane amounts of data, and often do some processing on it too, on really low power. Shouldn't every server have that kind of acceleration built in?
Sounds like a complicated way of saying every developer should have their own DB instead of a shared dev instance.
Tech investors should start backing worker-owned co-operatives (2021)
>CFM

Cubic feet per minute?
> he'd rather throw the cake into a furnace than allow someone to have a piece

Funny, that's exactly the view I have of progressivism as an envy-driven ideology that would rather see everyone be equally miserable than some few being less miserable than others.
> the CEO announced a 10% paycut across the board

Which is still better than a 10% layoff, anyway!
I'm kind of lost here. It's been ages since I wrote anything frontend related so here the question: how does it matter?

I mean unless you have pure front end app - you are still going to talk to some backend. Regardless of how you got your frontend part - generated by the server or a static file served by nginx.
I think most people recognize that you don't get every job you apply for, but there are people who contact hundreds to thousands of organizations, apply with custom crafted letters and tailored resumes, put in thousands of hours of job searching time over months of time and get jobs well under the median of their cohort.

The assumption that other people's experiences are like yours is a key cognitive bias. A 90% fail rate means 10 offers after a hundred applications - that's an incredibly solid success rate. Now imagine some people have orders of magnitude more difficulty because their name is strange, or because their social class shows through in their dress or mannerisms.

If I can offer a comparison, most people on this forum have it made. It's like asking a group of models how difficult online dating is and having someone say "I can't fathom anyone having trouble keeping their weekends full of new people to date... It's just so easy!"

Also, I note that you seem to assume I'm talking about my own experiences; I'm not. I am a very well established professional in a lucrative field.
Engineers with a bunch of hard to find skills are still hard to find.
Intel has senior engineers who received two and three digit retention bonuses this year, on top of the 20% pay cut.

Principals usually broke into the three digit range from what I hear.
The future will probably have amazing computers and models, but what we already have has the capacity to profoundly change the world.

I don't think you are focusing on what matters most. It's really the language itself that contains the intelligence, not the AI models. The models are just vessels for absorbing all that knowledge encoded in text. Just like human brains - we can have different neural wiring but learn the same things through education.

So the huge datasets these AI systems are trained on are key. That's how models like GPT-4 gain such language understanding. The architecture matters less than all that linguistic data it ingests. And language has been evolving for millennia, long before AI. It replicates through culture, speech, writing. Now with AI it has a whole new medium.

Fascinating question - how will AI affect language evolution going forward? As models produce more human-like text, which can further train better models, it's like a Lamarckian evolution. Acquired linguistic intelligence gets absorbed by AI then improved and propagated back into the corpus.

So while AI tech will keep advancing, it's language evolution that's most profound. By creating this new way for language to evolve, AI could really reshape cultural evolution. Since language enables intelligence, it'll have big impacts on where AI is headed next.
I think that's supposed to refer to the currently observable bit being the size of an apple; though given how bad newspaper analogies are, this may all derive from misunderstandings one hungry physicist 60 years ago and subsequently all quoting each other.
If the JSON license isn't considered open, due to requiring that "The Software shall be used for Good, not Evil.", then I don't see how tacking an additional financial threshold onto it makes it more open. I don't think meta even released the training dataset, so you cant even replicate it (should you have the funds to do so).

There are other LLMs that don't have such restrictions, and publish their training data.
CSEL is a conditional move, they’re usually used to avoid branches (and branch predication) entirely.

Here it turns out to be a very bad choice, because it creates unnecessary data dependencies. But a cmov would be a fine choice if the branch was impossible to predict (e.g. if the input was random, well even then I’d expect the limit to mostly creep up so it should be predicated as mostly cold).
Same with Auckland, but we need higher intensity, not more land. Public transport that’s useful seems very unlikely here.

We tried looser regulations and got a massive fiasco of leaky buildings due to poor design, poor material choice, poor workmanship, poor auditing and inappropriate sign off.

It’ll be interesting to see how all goes for Hawaii.
They didn't just develop software and give advice. They ran the service itself.

If they had just written some software and told people how to operate it anonymously, they could not be prosecuted under these laws.
John Locke kept one: https://fs.blog/john-locke-common-place-book/
ZFS has RAIDZ1, RAIDZ2, RAIDz3 and Ditto blocks, which do much the same thing, although a bit differently.

My point was that even if you have 4 copies of your data, you still only have a single machine where your data is stored, and you're essentially just one flood/lightning strike/house fire/burglary away from all of it being gone. Or one bad power supply away from 4 dead drives.

With versioned backups, you have higher latency on restoring data in case a disk dies, but your data is also safer.

As i initially stated, RAID is for availability. It is great for making sure that data is available 24/7, but that is rarely what the average home user needs. Most home users access their data infrequently, and would be perfectly fine waiting a couple of hours while restoring data from a backup.
Funny how personalist most of the West suddenly becomes when things don't go their way, case in point the current government in Moscow. Nevermind that Putin is by far not the only highly placed Russian official that was of the opinion that this current war should take place, it all happened because he is an "insane" person, damn the system as a whole.

As a matter of fact that's also what happened with the Nazi white-washing just after WW2, it was all because Hitler and some of the guys around him were insane and blood-thirsty, ignore the system as a whole, ignore the Wehrmacht which was directly responsible for the death of millions of non-combatants on the Ostfront. That's how many of those high-placed Wehrmacht officials got cushy jobs in Western military structures not long after the war had ended, after all they weren't the "insane" ones.
It isn't an excuse, but having worked with C and Rust programmers, C programmers IME tend to have attitudes blaming users for not RTFM and Rust programmers (again IME, not generalizing) have more of the opinion that illegal states should not be reachable through public API, i.e. blame the designer, not the user.

I think it's reflective of Rust vs C design philosophy.
Also if you are using Safari, you can always just highlight the text in the image and have voiceover speak it.