skysight-inc/HackerNews huggingface dataset:
It seems like you maybe just don't know what the SAT is.

It's not an exam like any other high school exam, it's totally unique. It's not meant to be studied for -- it's meant to give a general overview of your total scholastic ability. (It's also not even run by the school system, it's a private company that you have to pay in order to take the test.)

But the reality is that you can "game" it by learning patterns in the types of questions they ask, and how to give the answer they're "looking for" on the verbal section, when the correct answer is often highly subjective for questions on analogies and reading comprehension. And you can also focus on a very narrow subset of words and math problems that tend to statistically recur. There's also literally strategy around when you should guess vs. when you should leave an answer blank, depending on your confidence. These are what test prep focuses on -- not on improving your general scholastic aptitude in any way.

So it's not studying for an exam in any normal sense. It's more like "gaming" it.

As for children being failed on such a basic level in many public schools in America -- on that, you couldn't be more correct, sadly.
> pushback from the legal system regarding standing

well that's just cold.
A hiring manager that assumes businesses are, by default, good unless proven otherwise is a red flag for anyone looking to work at that business. Not only is it typically the opposite, but advertised jobs are disproportionately bad because people tend to hang onto the good ones. Workers are far more likely to cycle through a batch of bad jobs that, at best, nobody wants (and just as likely include unlawful worker exploitation) before finding a job that doesn't suck to the point of being abusive.

I can't tell that a job is toxic until I've been there a bit, any more than a hiring manager can tell that an employee is toxic until they've been there a bit.
Only ThreadRipper Pro mobos support that much as far as I know. ThreadRipper Pro CPUs are AMD EPYC server grade CPUs that are customized/rebranded for the workstation market segment. The regular “gaming CPUs” and motherboards support only 64-128 GB of RAM. Some have 4 DIMM slots, but the CPU still has only 2 channels, so with 4 DIMMs you won’t get any memory access throughput increases, just more space for caching stuff to avoid disk IOs. EPYC/TR Pro have 8 memory channels…
Dino Buzzati
There's studies from the 80's & 90's showing direct destruction of neurons in mice and chimpanzees with depression like symptoms. Depression it seems literally eats away at the brain, at least in mammals, likely due to inflammation.

What's perplexed me is why this mechanism would occur in evolutionary terms, or if it's really just a byproduct.
This is going to get exactly zero people on board with this cause.

It will alienate many and will lead to harsh, exemplary punishments for this behavior.
Gotcha, what you have looks great nonetheless. Congratulations! I'm just one of those who likes self hosting on cloud based solutions.
Except for the part where if we keep burning fossil fuels there will be no future, it's brilliant.
Someone commented about running challenges. Similar. I need a target to achieve and a reason to motivate myself. Frankly speaking, I’m terrible at writing code but I do it for fun.
Ask them why they added it. It could be a poorly received joke, or a serious misunderstanding.

Until you talk with them assume joke (prior knowledge you haven't shared not withstanding). It's not clear who poorly communicated, and the worst thing you can do is say nothing after having posted here. Part of clearly communicating is catching when you're making assumptions, and asking questions directly to the person to learn more.
Get Blogging
Async by default. Promise chains. Strange unpredictable typing. Many more strange things.

It was half ass browser language originally with improvements bolted on.
Totally awesome rendering, but how do I keep from dropping through the floor? I’m on a laptop+Chrome. The shift keys seem to be the only way to change elevation and both go down. Would be nice if Q & E would go up down, since they’re in the locus of the WASD controls.

Is this really ray tracing the glass bits? The way it turns on & off when passing through the glass surface hints at some hybrid shader tricks, perhaps?
It is a bit of a fair point though: you're only measuring "the success of people from HN who engage with your game", so it's not sound to draw conclusions about "the population of all HN users". Even if it is true that HN has a junior-skew, it wouldn't mean there is necessarily "somewhere else" -- lobste.rs aside, the eternal september effect (or other things) could be enough to keep the demographic population skewed junior.

I've been programming for about 15-20 years, and using HN since 2007 or 2008 or so. I opened your site while reading the voxel thread, and was a little baffled about what I was encountering -- "why am I suddenly reading buggy go code? I thought this was an example of a spacial curve!" -- so, I went to check out your other posts to figure out what your deal is, and here we are.

I don't know Go, and I don't really want to "play a programming game" right now. Your code seemed a little obtuse and intimidating -- long bitmasks and combinations of xors and abstract names -- no thanks! There's a bug in there? How surprising!

I do lots of programming at work and in my spare time, and to a degree, I just can't be arsed when someone jumps out of the woodwork with "a bug" that it isn't going to mean anything to fix, so I moved on. I'm an experienced programmer who you likely aren't measuring.

So I saw your comment here, and my first thought was: well, that's a big (logic) bug in the reasoning of a person who made a game of fixing bugs! Kinda tasty irony, and totally fair game for the poster above to call out, in my opinion.

(anyway, after all this, I am a little bit more interested to go try out the above-mentioned challenge. It's a neat idea for a game, and you seem to have put a lot of work into it. Best of luck!)
In my experience vim emulation is great, almost as good as using native vim for keybindings, navigation etc but still not so comfortable. Like cuddling someone you love wearing blizzard clothing - better than no cuddle for sure but not the cuddle you'd choose as your favourite.

Depending on what you're doing, the native vim plugins might well be vastly better. I swear by YouCompleteMe as a wrapper for clang-complete for navigation of a C codebase. The autocompletion is pretty good too. I Haven't seen anything better with any other editor/ide vim key bindings or not.

I'm sure if you work hard enough at your s-exepression configs emacs can be as good if those are the keybindings you know and love. But why look elsewhere? <- Not rhetorical, genuine question - have you found a reason?
You’re not wrong, but there are also any number of rules about building code that try to prevent water infiltration, which makes the wood last many times longer.

For instance, wood laid horizontally in water doesn’t wick water as far as wood standing vertically in water. If you look at deck and house designs you see a lot of horizontal pieces. Especially in new construction.

That said, letting water pool at the corner of your house can eat your foundation too. Water is bad. Get rid of it.
"Relapse rates after ECT are similar to those in resistant
depression treated with antidepressants (37% after six months)
and are a function of the illness, reinforcing need to continue
with antidepressants, ECT, or both after a successful acute
course of ECT.37 Emerging evidence suggests maintenance ECT
to prevent relapse.38"

https://www.bmj.com/content/364/bmj.k5233

This article is arguing ECT as acute treatment for resistant depression. In most, if not all, cases a patient would become eligible for ketamine treatment at the same time if not sooner than ECT. Memory loss directly due to ECT is the reason most people are strongly against using it. Treatment options are based on minimizing risks, not guaranteeing success. Unless ketamine is contraindicated, it will always be a safer treatment than ECT.
Your points make sense, but I don't think they're relevant to this article. His point in this particular article isn't about individual home heating systems, it's about residential heating in aggregate, and the distribution of energy required to support them.

I thought his general point made sense: that gas distribution systems are more readily (and cheaply) able to meet "peaky" demand for heating than electric ones.
Personally, I haven't even noticed any of these...
Not exactly.

The government pension schemes do not provide anything back to the chumps of the next generation.

Savings are put in financial institutions and earn money based upon how much money those financial institutions are able to earn by redeploying that money to help businesses grow.

There's quite a bit of difference between investing and extracting donations
Having once worked at a publisher (although in IT not ad sales or product, so call it “adjacent” rather than inside baseball), I’m certain this is about negotiating with publishers rather than apple’s own priorities.

A platform like Apple News does very little to redirect traffic back to the home page where you show the big 1st party ads that actually bankroll the org. Users stay in the app. From a publishers pov it’s really unattractive unless you can show ads.
The hypersane are among us
People are naturally averse at recognising issues which require them to take actions that might impact, however slightly, the lifestyle that they have grown used to. They will prefer to dig their head in the sand and keep driving towards much bigger problems rather than take moderately inconvenient action now.

This is a behavioural/psychological flaw that prevents necessary action from being taken.
What does "consume more code and tech than we produce" mean?
XDG has real practical benefits, though.
> A forest at equilibrium is carbon neutral

We have been cutting down forests and killing the soil for 200 years.

So there is a lot of natural (re)sequestration available to us

Europe is re-foresting simply due to demography and urbanization. The amazon. Etc.
Oh, interest. So something like `sleep_ms(0, hash(input) % 1000)`
And bad legistlation gets exploited by scummy lawyers to hurt everyone except themselves, which is the topic of this thread.
I saw it today in someone who announced a package and in their README had a gif of a mouse clicking to add a "star" to the repo. Like the youtube videos that ask you to "like and subscribe".
> People have just stopped thinking for themselves.

I see the opposite. People are thinking for themselves and are looking at empirical evidence like TFA to boot.

Edit: your other comment about needing targets makes me suspect you'd benefit from using a personal task manager that can clearly and tangibly visualize progress if you aren't using one already.
> You will most likely want to create a default configuration file with sane and sensible default values the first time your program is executed.

Please don't. Include the example configuration in your docs (/usr/share/PROG..) and mention it in the manual. Statistically user will have hundreds of apps installed but will only ever customize a small fraction them. So creating config unconditionally on first run is one of the worst contributors to homedir pollution.

Another argument is version upgrades: if you create configur on first run, you forever bake in the set of options present in that version. If later a new option is added, user will have no idea about it.
How does embedded programming square with the "safety shaming" rust culture?

Surely you're transmuting all over the place.
I'm curious if anyone here has projects that already use Rust on the Espressif platform.
> Would you go to a pub with me?

My answer to that one is yes for most people on this site. :)
It's just nature's way of filtering out people who like sex but don't want kids.

Prior to birth control, having a genetic predisposition toward liking sex was enough. In the future, most people will also have a genetic or cultural disposition towards wanting kids.
This was fun to read through.

I would need to profile the code, but the startup time being bad for Deno seems like maybe a combination of the code in here being unoptimized:

https://github.com/denoland/deno_std/blob/0ce558fec1a1beeda3...

(Ex. Lots of temporaries)

And usage of the readFileSync+TextDecoder API instead of readTextFile (which is also a docs issue since it suggests the first one). It seems the code loads the 100MB into memory, then converts to another 100MB of utf8, then parses with that inefficient csv parser. The rust and go versions look to be doing stream/incremental processing instead.
Many are not so loud. The issue being confirmation bias in noticing them.

Sure, the activities listed are different. But they were not meant to be exhaustive either. Merely to demonstrate that "save lives" is not the one true rule for decision making.

As you allude to in your first sentence, it is about risk management.

Managing little risks (will loud bikes upset someone?) and big risks (will people die doing this?). The issue with risk management is everyone has their own perspective on it.

So then the question comes as to what the balance is for society.
I'd argue that "affecting others" is car accidents more than motorcycle noise.

Mind you, I'd be happy with more policing around loud bikes AND cars.
This paper is about how gamification affects behavior, not about it being some sort of social platform. Every platform was "social X" around the time github started up. Lots of sites have social elements and it never amounted to them being called social X either. Sure you can use those features in some sort of gamesmanship, but generally it's not used that way and so few people care that it's laughable.

> "social coding"

Social coding is not Github's primary function and it's hasn't been promoted in earnest, this way because it's secondary at best. Ostensibly, it's hosted git. That's the naming, the function, and most developers think of it as such. The vast majority of users are either corporate developers who work for some company and can't care less about the "social" aspects of it or insular developers with projects that never see the light of day.

Notably, this paper only sourced public repositories, where many people use it as an element of their work portfolio. This doesn't speak to "all of github".
This was my experience as well. I really tried to use the vim plugin for vscode but there were too many behavior differences between it and native vim. And VSCode just has too many features that I've grown to love that I just find myself learning the native VSCode bindings and using those most of the time now.

I miss VIM, I really do, but I really only use it these days if I need to ad-hoc modify an individual file while I'm in a terminal somewhere.
First computer I used was running Dos and Windows 3.1.

But my favorite Windows version is XP, I was doing service desk / junior sysadmin at the time and XP was just so easy to work with. You could fix a lot of problems by simply editing the registry or files in the windows folder directly and you could re-image a machine in about 2 minutes. The control panel was really easy to navigate and consistent.

I really wish XP was still supported.
One possible replacement for vim fugitive is tig. It’s very vim-like and gets the job done.
I believe this attitude goes hand-in-hand with the idea of jumping ship every few years. As an employee, your impact only extends as far as the projects handed to you. You offer no growth potential to an employer.

Similarly, management that only looks for this is offering no reward for better, and deserves the attrition they'll see.

There are roles and companies where growth is both valuable and rewarded. I think it has to be an org where the technology is the product, and not a cost center (necessary, but not sufficient). I think you really have to be paying attention to know what type of org you are in. Taking this attitude up-front at any new job, you may not even see the opportunity.
We don’t know how much of that video is real and how much was pre-recorded (as they knew what the speaker would say).

During that same presentation, we also know that Zuckerberg lied about the metaverse and how characters are able to move their legs (it was filmed).
Not sure if you are aware of the projects mentioned here: https://github.com/esp-rs/awesome-esp-rust#projects
I linked a video below of Jensen Huang founder of NVIDIA speaking at Stanford. He says at one point in the 90s there were 100s of companies in their space and he goes on to list a series of unique insights/perspectives they had that led to become the last one standing. NVIDIA understood the insights that mattered.

I would say a more modern example of this the insight that to build the best mobile phone product, you need to design the hardware, operating system and APIs (and thus first party apps) together as a single thing. Apple brought this insight from their past experience building less sophisticated computers. They knew a phone given it's size and use case would require this to an even _greater_ degree.

Google on the other hand, based on their experience of working in open ecosystems and linux machines from server to desktop, thought the phone market would extend from an open OS platform. This was their perspective/insight.

Ultimately, the company that won this argument was Apple. We know this because Google has finally adopted this truth that Apple knew all along with the Pixel hardware lineup. Furthermore, the Android phones that succeeded today have nothing to do with the fact they are "Android". Samsung phones are about the Samsung ecosystem. Choosing Android is more important to the OEM than the user because of the app ecosystem that cannot be bootstrapped from scratch any more. Android is the developer/oem platform, not the user platform.

Now, think about how long it took Google to finally give in to that insight? These perspectives lead to very stubborn decision making. This perspective was often a debatable thing for a long time. It's no longer. Hence I think everything you said here is right and aligned what what we see in one of the biggest product categories on the planet right now.
The Reuters article quoted below says children rarely suffer severe outcomes from Covid. Why should a healthy child take the risk of this emergency authorization medical treatment when children are generally okay?
NATO has been very clear about where the red line sits and the specific consequences that will result. There is no gauging to be done.
A piece comes up on HN about Apple’s purported pending foray into capital A Advertising once a month.

I have no idea if they will ever do it. We live long enough I am sure we will see it, but as it stands it would remove the biggest product differentiation and advantage Apple has as a company:

Apple does not need advertising for revenue.

Google can’t say this; Samsung can’t say this; even Amazon and Microsoft can’t say this anymore. They all need it to balance their books.

If Apple goes down this road it ruins their differentiation. The thing no one, with any real size and therefore capacity, can touch. Apple would be crazy to eliminate it.
Sadly even a kinetics level simulation for anything remotely complex is far beyond what current compute is capable of. Even simplified models of basic biological processes are immensity complex, and still potentially incomplete. Just as neural networks do not even attempt to reach the level of molecules, (practical) models must necessarily exist at a much higher abstraction.

Although alphafold is a breakthrough, this is less optimisation, more chaos theory.
Where in San Francisco does a beer cost $20 with tip?
This was a huge battle for the heart & soul of promises leading up to es2015, & convenience won. But wow, I think there's still so much missing capabilities that we prevented.

This is a great discussion here. At the heart, to me, is what a promise represents. If it's just some future value, and the promise itself is inconsequential, of no value, that means it's ok to keep forgetting the promises & just keep relating values.

But a promise isnt just the eventual value. It's a thing unto itself, another first class object. I think there's a totally missing but extremely valuable view, that Promises represent the compute that is happening. They are values we can pass around in their own right, & which properties & control methods can be attached to. That we built a language that erased chain, that forgets the process is unfortunate.

I further think it would have been worthwhile for promise handlers to receive not just the eventual value, but the promise they are handling too (give them the process!). Conveniently the chief question in the article, of whether we blow up intermediary promises, can be perhaps addressed with this same technique: promise handlers could, rather than having a handler(value) function signature, be handler(value, ...promises), where we could see the lineage of promises present.

I confess: there is some speed boost we get, particularly I believe when using async/await syntax, which lets us forgoe creation of an intermediary promise entirely, but it's still wild how much possibility we sacrificed, and how readily & quickly (albeit not without some fierce debate!).

Also just wild to me we decided to make promises fully async, that their resolved status & resolved values would not be knowable except asynchronously. Seemingly just because we were afraid of users being too creative. It's a different but related fear, but fear of unleashing Zalgo was extremely extremely high, a panic about mixing async and sync, that we put on the level of a fear of summoning out of control super demons who would rain anarchy down on earth, but it just... never became a problem. And with async/await, it's basically inconsequential, practically good practice, to return a sync object if you have it and async if thats all there is. It is confusing as heck to me whether any of these fears are at all justified or real. I still genuinely am confused by the arguments made a decade ago; they seem full of charactures of perceived lowly common developers who must be given only blunt instruments. Fear Uncertainty & Doubt ruled this decison making process, & there was surprisingly little effective counter resistance.
Sure, here we go [1]

Land Use and Forestry (13% of 2020 greenhouse gas emissions) – Land areas can act as a sink (absorbing CO2 from the atmosphere) or a source of greenhouse gas emissions. In the United States, since 1990, managed forests and other lands are a net sink, i.e., they have absorbed more CO2 from the atmosphere than they emit.

[1] https://www.epa.gov/ghgemissions/sources-greenhouse-gas-emis...
I’m not sure the linked app is ray tracing voxels per se, but can confirm the active bitmask and Morton tricks work really well. I’ve actually just built a renderer with some co-workers that does both of these things. We have not used the trick you show of stepping without de-interleaving Morton, that is very clever! I’m going to try it and see if it speeds things up.

BTW, on the GPU Morton is handy and convenient but not the absolute fastest. You can do simple tiling and get all the cache benefits in fewer instructions. It’s kind-of like one single Morton interleave step, say, for example, interleave the bottom 3 bits and then the top 7 bits. (But note you can’t blindly interleave any number of top bits anymore, it needs to be the exact number of bits you’re using, or a row-major indexing calculation using a multiply instead of bit shifting.)