skysight-inc/HackerNews huggingface dataset:
Just to clarify because the message might have been lost: I'm not saying you're wrong! I'm saying you're right, and...

Quoting a comment from the issue you linked:

> This is not specific to Promise.race, but for any callback attached a promise that will never be resolved like this:

x = new Promise(() => {});
for (let i = 0; i < 10e5 ; i++) {
x.then(() => {});
}

My point is if you do something like this (see below) instead, the same issue is still there and cannot be resolved just by using `Unpromise.race` because the underlying issue is promise cancellation:

// Use this in the `race` instead
// Will also leak memory even with `Unpromise.race`
const interruptPromiseAndLog = () =>
interruptPromise()
.then(() => console.log('SIGINT'))

`Unpromise.race` only helps with its internal `then` so it will only help if the promise you're using has no inner `then` or `await` after the non-progressing point.

This is not a theoretical issue. This code happens all the time naturally, including in library code that you have no control over.

So you have to proxy this promise too... but again this only partially solves the issue because you'd have to promise every single promise that might ever be created, including those you have no control over (in library code) and therefore cannot proxy yourself.

And the ergonomics are terrible. If you do this, you have to proxy and propagate unsubscription to both `then`s:

const interruptPromiseAndLog = () =>
interruptPromise()
// How do you unsubscribe this one
.then(() => console.log('SIGINT'))
// ...even if you can easily proxy this one?
.then(() => console.log('REALLY SIGINT'))

Which can easily happen in await points too:

const interruptPromiseAndLog = async () => {
console.log('Waiting for SIGINT')

// You have to proxy and somehow propagate unsubscription to this one too... how!?
await interruptPromise()

console.log('SIGINT')
}

Since this is just sugar for:

const interruptPromiseAndLog = () => {
console.log('Waiting for SIGINT')

return interruptPromise()
// Needs unsubscription forwarded here
.then(() => console.log('SIGINT'))
}

Which can quickly get out of hand with multiple await points (i.e. many `then`s).

Hence why I say the underlying issue is overall promise cancellation and how you actually have no ownership of promises in JS userspace, only of their completion handles (the event loop is the actual promise owner) which do nothing when going out of scope (only the handle is GC'd but the promise stays alive in the event loop).
It’s the same in America, there’s actually more trees now than at the time of European settlement. A combo of the large buffalo herds that used to roam and native land management that often involved burning entire forests.
Would like to see a link where I can read the whole thing.
Congrats, you have a very good work ethic but a very poor personal health ethic.

I was like you, and probably still am deep below, and I will fall again in the same trap. But please, try to think about flipping your point of view here and instead of being your manager generous and your company good for not taking into account the time you failed to answer on duty, think about how you are being exploited covering 75% of on duty alone, and the money the company didn't loose just because of you. And how much of that money you got.
I agree with the others here that classic assert statements are in a weird spot. You enable it when testing, in other words when the data flowing through your program is likely to be constrained and lazy. And then turn it off when your program is about to meet real data (production).
There's some wrinkle to this where you might want to log certain things in production instead of aborting with an assertion failure. But let's assume failing hard and fast is preferred for now.

Basically there are three cases.

1. The performance hit of the assertion checks are okay in production

2. It has a cost but can be lived with

3. Cannot be tolerated

For number two there is some space to play with.

What I've wanted is something more fine-grained. Not a global off/on switch but a way to turn on asserts for certain modules/classes/subsection, certain kinds of checks, and so on. It would also be nice to get some sort of data about the code coverage for assertions which have lived in a deployed program for months. You could then use that data to change the program (hopefully you can toggle these dynamically); maybe there is some often-hit assertion that has a noticeable impact which checks a code path that has been stable for months. Turning it off would not mean that you lose that experience wholesale if you have some way to store that data. I mean: imagining that there is some history tool that you can load the data about this code path into. You see the data travels through it and what range it uses. Then you have empirical data across however many runs (in various places) that indeed this assertion is never triggered. Which you can use to make a case about the likelihood of regression if you turn off that assertion.

That assumes that the code path is stable. You might need to enable the assertion again if the code path changes.

Just as a concrete example. You are working with some generated code in a language which doesn't support macros or some other, better way than code generation. You need to assert that the code is true to whatever it is modelling and doesn't fall out of sync. You could then enable some kind of reflection code that checks that every time the generated code interacts with the rest of the system. Then you eventually end up with twenty classes like that one and performance degrades. Well you could run these assertions until you have enough data to argue that the generated code is correct with a high level of certainty.

Then every time you need to regenerate and edit the code you would turn the assertions back on.
Dutch person here (have been told we are some of the most direct people): my experience is that it is not the words but the intention. E.g. the
'give more training' example: 'I do not understand why we do not give more training. It seemed to help with Steve, why are we not doing more so'. And being genuinely interested in the answer.
Do not assume you are always right in assuming more training helps, but ask yourself why it may not be. Having an open mind can really help. And perhaps you were right to be astonished in 95% of situations, in 5% (or more) you might learn something.
Other things are certainly true: it may be better to ask that question in private, as opposed to while the leader addresses the whole staff.
From what I can tell, this 14-year-old kid showed the clock to other teachers (including his engineering teacher whom he said was the reason he brought it to school to show) before the English teacher, and they told him to keep the device in his backpack and to stop taking it out.

It wasn't until during English class, when he took it out, plugged it in, and set the alarm, that's something happened.

I have to wonder if the GP would have a similar experience if he kept waving the water gone around after being told to keep it in his bag.
a good reminder on how much we can be tracked
Feeding people is a sacred task. Food is literally the base pillar of various human needs pyramids.
related: How to Entertain with Your Pocket Calculator (33 comments) https://news.ycombinator.com/item?id=35941315
The usual example used in teaching is Ansombe's Quartet: https://en.wikipedia.org/wiki/Anscombe%27s_quartet

It consists of 4 datasets with the same summary statistics, but when plotted look very different. It's much easier to see the patterns in the plots than in the data table.
The author of the paper is not competent in the subject matter.

A compiler can make assumptions that behavior is well defined, and it can also identify situations where it is confirmed undefined.

All of that reasoning happens before runtime.

For instance, and unreachable assertion works by invoking undefined behavior. What identified by the function-call-like syntax unreachable().

If we have:

S; unreachable();

then, ostensibly, it looks as if statement S is something that happens at run time before the unreachable construct is executed. (S is a simple statement which passes control to whatever follows; it does not hide a go to).

And so we could naively argue that undefined behavior cannot travel backward in time. Of course S must successfully execute, and only then can things go haywire due to the undefined behavior of unreachable.

But that's not the way it works. The compiler is looking at this before runtime. The compiler is free to assume that behavior is well defined. That's what makes unreachable work: if the program's behavior is well defined, it must be that the unreachable statement is never reached. Which implies that S is never executed. If S is never executed, it can just be deleted.

If S and the unreachable statement are deleted, but control ends up there anyway, the program will go haywire. And it will go haywire without producing the effects of S. So in effect undefined behavior has gone backwards into S, so to speak in naive language.

Logical reasoning over code while translating it does not follow runtime chronology. It follows chains of inferences.
This is very accurate
The challenge we all have is, that just leaves everyone angry with each other and unable to actually make progress or solve any problems together.
Bash: Creating and Managing Child Processes
The alternatives is planning for the max disaster- and that means ordering and storing coffins in bulk. We could get a pretty good deal if we order NOW.
This is how the energy grid operates everywhere, it's not some uniquely German mistake. Renewables require an incredibly huge grid investment - it's the same story they keep telling about external costs, only this time they don't want to hear it. I don't want to subsidize others' cheaper energy, I don't have any place to put my panels and batteries, I was happy with how it was before. But they would do anything to avoid the fees when they can.
And why do countries want to join NATO?

BECAUSE OF RUSSIAN THREAT.
you need to put your phone upside down for the link to open
This is one of the most toxic blogs I’ve ever read - so much swearing, vile hate while criticizing various persons they dislike, rambling incoherence. Wow.

And their specific criticisms of the contributor this post is discussing, are very mild but full of personal attacks and expletives?
It's worth pointing out that Python's asserts can also be "compiled" away if you use the -O flag (or PYTHONOPTIMIZE=1), which eliminates their runtime cost.

It's also worth pointing out that this is the reason you should *never* put side-effects or security-relevant checks in assert statements. For example, you should never do something like this:

assert f.read(4) == b"\x89PNG", "Not a PNG file"
# proceed to read and parse the rest of the file

but rather, you should do

magic = f.read(4)
assert magic == b"\x89PNG", "Not a PNG file"

so that your code doesn't suddenly break when someone decides to be clever and use -O.

Also, fun unrelated fact: Python does have something like a preprocessor, although it's rarely used. If you condition on the flag __debug__:

if __debug__:
expensive_runtime_check()

and then run Python with -O, the if statement and its body will be entirely deleted from the bytecode - even the `if` check will be deleted. It can be used for including "debug" code in hot code, where the extra flag check itself might be expensive.
I guess distance yourself emotionally from your job, but continue looking and be picky about your next role.

I'm in a similar boat, but my engineering manager wants to get rid of them, so I'm being dragged into office politics now.

Other than a few rotten apples, the company is great. So, I'm also somewhat reluctantly looking for a new role.
> Legally, yes. Practically, many employers bounce paycheques and get away with it. It’s tedious to enforce worker rights in a way it isn’t for consumers. (In most states, you can get the AG basically working for you by copying their office on a complaint to the company.)

Not sure what the point of your argument is. Many employers get away with bouncing paychecks but you can get the state AG working for you by CCing them on email? The above comment claimed the law favored consumers and investors over employees and I gave a common case where they are not. Not the practicality of enforcing the law.

The same goes for employers too where employees steal or skip work and they are just fired instead of paying a lawyer (if they are incorporated a small business the owner can not represent the company usually) or going through the hassle of collecting proof, filing a factual police report and showing up in court to testify.

Doesn't change what the law is when it is worth it to pursue, and it was worth it to pursue against Meta for withholding material info to investors.
I look around using a torch and everything I look at, everything I can see, is lit.

So the natural and correct conclusion is that all objects are lit, right?
> Maybe another LLM and/or other system that doesn't even see the instructions from the user and tries to stop the other one if it seems to be going off the rails.

I sometimes wonder if that is what our brain hemispheres are. One comes up with the craziest, wildest ideas and the other one keeps it in check and enforces boundaries.
Personally for me a big thing is how finicky EVs are.

If there is no electricity you are out, if it's snowing too much you are out and so on.
I don't want to buy something that stops working when anything isn't optimal.
Is it dying on a hill or is it keeping up healthy boundaries and standing your ground?
Food security is not an issue at all. For example in Germany around 20% of all farmland is used for "energy plants" (biogas etc.). Even in Germany solar planels have around a 28 times higher efficiency per area than biogas plants, so there is a lot of potential to repurpose farm land without changing food production at all.
Lazydocker sure looks interesting, but self-promotional ads - for products in an entirely different space - in an OSS project's README.md? Seriously? At least for me it is the first time I have come across anything like this.
I'm wondering if advertising like this is even allowed under GitHub's TOS and AUP.
We KNOW that quantum mechanics is incomplete. Everything is definitely not described by quantum mechanics.
That is entirely possible. We simply lack corroborating sources at the moment so we can't jump to any sort of conclusion.

As far as I am concerned this whole thing might not have happened until I see another couple of sources.
I think you mean Czechoslovakia?

As soon as you got fascist militias roaming around and you can't quench them, you are screwed.

I don't think ceding to them was the way to go. They are essentially warlords and those are destabilizing for tge central government. It is a bad idea to cooperate with them due to having a common enemy in the separatists.

Also these fascists are ideologically accelerationists, not reactionaries like in e.g. Spain.
When dependencies don't deliver 100% of what you want, you should be able to work with upstream to get what you want added.

If upstream won't cooperate with you, then fork. It's still usually better to start from a battle-hardened codebase than it is from complete scratch.
Sure enough, they will invest it, because we are speaking of marginal incomes of the rich that could be taxed away and spent by government - these people already consume everything they want, the only thing they do with extra cash, is investing it.

There are already more than enough available investment dollars in the USA. More of them than viable business ideas. Adding even more means only asset inflation and even higher P/Es that progressively make stock market resemble a Ponzi scheme, and further increase of real estate prices that are already unaffordable in most of the country.
I believe that's actually the point! Choosing the right way to display information is a skill all on its own!
TFR is total fertility rate. GP is saying "the problem is not the overconsumption in the rich countries with low TFR, it's the poor countries with high TFR getting richer and consuming more and people migrating to countries where they consume more".

Which falls apart looking at the map of highest ghg emissions
https://ourworldindata.org/grapher/per-capita-ghg-emissions vs the negative impact caused by climate change and the ability to mitigate https://gain-new.crc.nd.edu/ranking .

curtailing migration without massive reduction in the overconsumption by the rich countries amounts to having the poorer nations pay bills (via enduring disasters) for damage they didn't cause, which I find an injustice. Doing that and limiting economic growth and thus limiting the capability of dealing with the disasters would just be cruelty.

If you want to reduce migration without injustice or cruelty, you need to make sure other countries remain livable and thrive, hence the OPs hook.
I watched somebody on YouTube solve some AoC problems in Excel, so I’m going to try that this year. Not sure how far I’m going to get, but it’ll be a fun challenge!
These details are not in the Wikipedia page. Care to cite how can we get accurate description of the order of what really happened?

And even though, I don't think suspension and police overreaction and taking a kid to be questioned without his parents present is justified. This is my problem and this is what makes this no just an ordinary incident that just happens everywhere. There was a racial profiling involved.
Some big issues were:

- they were manually tracking the "versions" of documents by copy-pasting them in some folders
- and even this was only done for each "release" of each document; inbetween two releases all the changes were made to files shared on Onedrive (possibly concurrently by two people, sometimes leading to conflicts with the loss of days of work)
- at every release the changes since the last release had to be looked up manually every time and included in a document; this was very time consuming.
- informations were duplicated in multiple documents, with no way to relate them; every change to one of them had to be manually replicated to the others.

I would argue that a correctly versioned document should not have these issue. A dedicated software should track all the changes, including individual ones inbetween releases. It should also provide a way to list them, possibly relative to some milestore (like the last release). Data should be kept in a format that's easy to automatically compare for changes, and hopefully in a deduplicated way so that changes need to be made only in one place. If that's not possible I would argue there should be a software that checks for inconsistent informations and prompts for them to be synchronized.

In the software development world this has mostly been solved by version control systems like git and continuous integration to ensure that the codebase is in a consistent state after every change.
Can't you see how extremist this viewpoint is? Raising issues about DEI and diversity hires is not "obviously hostile nonsense".
For the UK the Scottish national library has a similar map finder.

https://maps.nls.uk

With a bit of a london focus (since that's where I live)

https://www.layersoflondon.org/

https://mapco.net/

https://mapoflondon.uvic.ca/agas.htm

Finally this site:

https://www.oldmapsonline.org/
I don't understand, what's wrong with assert and doAssert?

They are both enabled in release AND debug modes.
You would have to explicitly compile code with -d:danger flag to disable any assertions.

> And they didn't even name the safe version clearly!

In this context safe version is clearly named as "release" mode, and unsafe one is even more clear - "danger" mode. "danger" obviously implies it should be used with caution.
Based on the replies to this I didn't realize how bad we have it in South Africa. I was on call 24x7 for 2 years and was not paid anything for it.

Big ecommerce companies and even global brands like AWS and BMW require 24x7 on call without any compensation.
Wonderful! Thank you! That's what the Internet was made for :-) Love it!
> Our role as technology leaders is to support this transition to AI-assisted living

Why is it that we all woke up one morning and every corporation is suddenly saying this same thing?
ICE vehicles can be finicky as well (but the technology has matured over a century) but yes, they aren’t quite totally better in every way.

They certainly work in the snow though, but there is range penalties in the cold. Gas cars stop working when they aren’t in their optimal conditions as well than includes having enough fuel.

I think requiring reliable electric infrastructure for charging cars is a good investment in the future because reliable power is good for more than just cars.
Sure, but it’d be a lot more interesting and challenging to build a 100 visualizations where each gives a unique insight of the same dataset. An isometric 3d bar chart is just going through the motions.

Next, 1 essay, 100 fonts!…
> The Americans learned that the hard way in the 1930s.

Grasses, not trees, maintained and protected the soil for what became the US Dust Bowl.

The "Great American Desert" was essentially treeless. As your [2] links points out, European agricultural methods "[exposed] the bare, over-plowed farmland. Without deep-rooted prairie grasses to hold the soil in place, it began to blow away."
Tardigrades are not "extremophiles", which refers to organisms that live (grow, reproduce) in "extreme" environments ("phile" = "like, love"). Tardigrades can temporarily survive some rather extreme conditions, but they generally require fairly ordinary environments to actually live. (As suggested by common names like "water bear" and "moss piglet".)
A Free Link-in-Bio Portfolio for Your Domains with Instant Valuation
The Nautilus as predecessor to the Arcadia?

If his propaganda turns out to be more effective than 林白乐's, maybe I'll have to call him 刘仙?

[could that last character really be read as a combination of its radicals or am I overinterpreting?]

EDIT: was this straight from the horses' mouth (hooves?)? https://blog.sina.com.cn/lcx

if so, what are the funny sN hosts?
StartupBolt is a streamlined boilerplate to help developers and entrepreneurs build SaaS apps in no time. Skip the headaches of setting up payments, authentication, and SEO. Save 43% this Black Friday and get launched faster.
[https://www.startupbolt.com/]
(Happy to answer any questions in the comments!)
Breaking out of VRChat using an Unity bug
Sounds like our laws and lawyers.
I always feel rendering such blurred panes takes quite a performance hit. Do we have any numbers on this?

I might just be old - when this was done on the CPU.
Movement, yes, but does it explain why they just keep moving about in that cloud?

I don't think so, but I'm open to learning.
Not convincing to me. The world of UI design is too agitated with copycat and fads to be a solid reference.
If you want to understand "face" here's a 56 min video : https://library.biblicalarchaeology.org/video/honor-and-sham...
Should be renamed: "How to not offend people with fragile self-esteem"
A lot of popular wealthy systems are 'easy' to re-implement. I thought the value was in Docker images? Or is that not how Docker is used? The only way I've used it is to be able to import someone's virtual build setup so I could build something from years ago.
Don't Take Away Americans' Freedom to Charge It
> Gladwell gets a lot of flack, but he's told some interesting stories.

Isn't the flack he's getting due to exactly that, that his stories would be interesting if true but often aren't?