skysight-inc/HackerNews huggingface dataset:
Single photon detecting eyes or not, most of us drive and know how hard that scenario would be to prevent.

I doubt I would have seen it or reacted in time.

There was a human in the Tesla that apparently didn't see it either.

- edit -

Sure... maybe a human could have "lessened the blow", maybe some humans, but now we're hindsight backseat driving and pulling things out of our ass.

As a human there's a lot that goes into it, it depends on how long you were driving, your vision at the time, whether you were talking, your driving skills, your reaction time, your handling of accidents, knowing where you can swerve to.

Some humans with full attention may have prevented it or weakened the crash, but that's a maybe, and assuming full attention.

Many people in this thread who think they would have noticed the subtle lighting effects on a pitch black pickup in the middle of the road. I've nearly hit blacked out cars on the road, you don't see them. You could go back and probably see it in a dashcam, but you know it's there then.

The uncompressed version you're still expecting a truck, it seems like it's much slower than what rounding a corner going 75mph on a freeway is, I don't think any of us could judge without being in the seat at the time.

All in all, this is the most speculative thread I've ever seen on HN. Very reaching, but anti-Tesla is hot news here so...

The big takeaway for me is how that Tesla just took that head-on collision at 75mph without compromising the cabin.
All the data should be there for the computer to decide that yes there is a large object, yes it is in the road, and yes we are on track to hit it.
I remember being assigned to look into Solaris when working as a volunteer sysadmin in grad school, where we were a SunOS shop. I took a sparcstation, wiped it, and installed Solaris. This was 1992 or so, so it must have been 5.0 or 5.1. I hated it, but I don't remember very many specifics about why I didn't like it. I think it was partially the unbundled compilers, combined with everything just being "different", combined with perceived slowness. That was the last place I worked with Suns, as my first job was sysadmin'ing DEC Ultrix boxes, and DEC Alphas. Ultrix & OSF/1 were much closer to SunOS than Solaris, ironically.

I do wish that Sun would have evolved the BSD kernel rather than jumped to System V.
Prior to VoIP it was easier to trace the source of a call. With VoIP, the call could come from anywhere. Also, that VoIP service may have been resold several times and the end of that chain might look like a shady foreign entity with fictitious names. You kill one shady reseller and 3 more pop up.
Derailing, I wonder how hard it would be to have emergency lights on a vehicle that trigger after an accident.
https://wjmn.github.io/posts/j-can-look-like-apl/ uses Emacs.

Discussed at https://news.ycombinator.com/item?id=20728715
> The cut-off speeds are orders of magnitude lower than thought before.

So what are they? (ideally to the nearest 5% of C)
In a few weeks it will be everywhere. It has crazy infection rate, look at super spreader event in Norway. I would just recommend to do periodic self tests not to "miss it". Reinfection may be hard.
Why on Earth one would want in a character-oriented text (i.e. where every character matters separately) to have some of them collapsed into one is beyond me. Why not take it further and have IDE render all occurrences of "cat" with an emoji.
If I send you a file I edited with ligatures you can't see them, not true with a file with unicode-only chars.
> At this point it is very clear that anyone using FSD/Autopilot is risking their lives by trusting their lives on a beta, or perhaps even alpha product.

Somewhat. The product costs $10,000 and has been enabled since 2015 (originally $5000). Its reasonable for people to think that this thing works. Sure, perhaps those individuals should do better research, but there's a huge degree of misinformation coming in from the top here.

The root-cause of the problem is Tesla. Its unreasonable for Tesla to pretend it works, charge significant sums of money for the "feature", and ignore the difficult questions when this thing crashes into stopped Firetrucks over-and-over again (https://www.consumerreports.org/autonomous-driving/nhtsa-saf...)

At some point, we as a society need to accept and admit that Tesla is __lying__ about this feature. That it is dangerous, and always has been dangerous.

There's a degree of blame we can assign to the Tesla-fanboys who accept this marketing without any level of critical thinking. But the root cause of the problem is Tesla's marketing.
...yes. As long as neither of those things are used to harm another person, this should be legal.
There's nothing about his suggestion that requires use of a Blockchain. IA could certify authenticity easily without it.
Thank you! Very interesting.
the author almost went there with photo from a printed page: ligature could confuse people learning how to program. That's an actual point that matters to some people, which I would give a shit about. Instead they presented such mind blowing discoveries as ligatures "contradict Unicode" and "are wrong sometimes". I don't use ligatures in anything other than code, why are those problems?
I think it is kind of unfair to apply your own intuition without any tests. Perhaps the average human will see there is something weird in front without being conscious of it (e.g. the lack of the white lines etc.) that is you would see it without seeing it. Or at least enough to slow down a little and be more cautious going forward. It is pretty hard to know this without doing tests.
Jackson Hole is certainly not in the Midwest. I'm not especially familiar with exclusive rural areas in the Midwest but they may well exist.
>GPUs, even the primitive PSX one, will draw many in a single CPU cycle. I can't find information on the PSX GPU fill rate but I'm sure it's faster than 1 pixel per CPU cycle.

Two pixels per cycle for flat shaded or rectangular primitives. Add another cycle for color interpolation, and another for on-cache texture reads (divided by how many texels are packed into 16 bits). The GPU is clocked around 53MHz so the range of 'many' here is roughly 1 to 4, ignorning that a CPU renderer would probably write two pixels at once. The CPU is also hampered by main memory reads taking a minimum of 5 cycles. Pipelining helps a little but extensive scratchpad use, such as putting the stack on it, was essential.

DOOM PSX did use triangles for the walls, just that they were a single pixel wide.
The feature I most want from the Internet Archive is the ability to donate them an old domain name and enough cash to renew it for the next hundred years such that they can keep an archived version of a site available (without breaking any incoming links) for a very long time.

They would also need to be able to handle legal administration costs of things like DMCA take-down notices, but I assume they already have to deal with that for the rest of the archive so hopefully that's not an extra complexity for them.
I think it's pretty likely that a human driver would have collided with the truck.

A major difference is that (from watching the uncompressed footage), a human driver would likely have stomped on the breaks before impact. That last minute breaking could make a world of difference.

A collision at 75 mph has a lot more energy (4.5x ish) than a collision at 35 mph. So every 1/10s of breaking will do a lot to reduce the damage of the impact.

That's one of my concerns about driverless vehicles that I want to see the statistics on. I have a hunch that automation will reduce the absolute number of impacts, but may lead the impacts that remain could be higher energy impacts, because they result from a classification error.
Ignore the last bar (2021.50) - there are reporting delays, and the total goes up as more data comes in. The following day [1] shows it at 6887, +1292 for the day, and the day after [2] shows it at 8019. This is good practice for any very recent (< 1 week old) data - expect there to be reporting delays, and that the most recent totals will be updated in the future.

If you look at the bars for 2021.46 - 2021.49, there's a clear exponential trend with a doubling time of about a week, going from 715 to 1446 to 3994 to 7558.

[1] https://www.nicd.ac.za/wp-content/uploads/2021/12/Datcov19_N...

[2] https://www.nicd.ac.za/wp-content/uploads/2021/12/Datcov19_N...
Pickup truck, crashed on the highway, and the tesla cabin looks pretty good.

Scary, but it happens all the time to humans too.

I'm more impressed how the Tesla looked at that 75mph accident, the cabin really was not compromised at all. Wow.
Many people would have hit the pickup. But some would have been able to respond and manually brake before impact, and this is the exact sort of collision that Automatic Emergency Braking (AEB) is supposed to mitigate, and there are dozens of cars of different makes that have it installed [1]. It's not like Tesla is the only car on the road with sensors. This is a failure. The fact that a radar-equipped "full self-driving" car doesn't even tap the brakes in the two seconds before hitting a unavoidable solid object in the middle of the road is a travesty.

[1] https://www.consumerreports.org/car-safety/most-new-cars-hav...
The demand curve of deep pocketed buyers is just as important as the supply curve of housing they want (location, size, quality, etc).
The non-compressed video[0] is much clearer. I can clearly see the truck ~1s before the crash

[0]. https://twitter.com/haenschengross/status/147332613675511808...
Basically nonstop advertising
Monte Carlo Options Pricing
> Given that European law is fairly well aligned when it comes to labor law,

Is it? My impression is different. Do you have any links?
But how does memorizing all 33 methods of your AbstractBeanFactoryProviderImpl enrich anything?

Learning to play an instrument is enriching because you start to understand the logic/inner workings behind the music you listen to. You need the same skill for programming, sure, but I don't see how autocomplete would replace that.
To me it seems the paper's conclusion is more that to a KII civilization, a Bussard ramjet is already a toy. If you have the energy output of a sun at your disposal, laser propulsion seems like a vastly more attractive solution, except for the problem posed by deceleration which is not insurmountable. Indeed, the ~Mm scale solenoid discussed in the paper seems something that should be easily within the reach of a KI scale civilization if they really want to build one. Or several.
Semantics. E2E is necessary against a wide array of threat models and is a fundamental part of what can be considered 'pretty good privacy' by 2021 standards (pun intended).

If a government, possessing a working set of quantum computers, chose to ban post-quantum crypto algos only, by the same semantics it could be argued that it would not be a general "encryption ban" either.
Assuming anybody else reads your code -- this will just enable you to write code that is visually ambiguous to people using normal fonts.

Ligatures, on the other hand, don't hurt anybody else.
Why isn’t the earliest sunset on the shortest day?
> If you want "spies" to use it, you don't want them connecting to known gateways.

The best place to hide a tree is in a forest.

If you have both 'normal' users and spies connecting to this host, who will tell who's the spy?
>They're entirely different animals

They're not, though. I only used notifications and the like because they were common things that people probably have experienced outside of this specific situation. It doesn't have to be that. It could have been a microphone icon or a speaker icon or literally whatever the OS wants to display. And I'm not even arguing that it's unreasonable to complain about the recording indicator. I'm arguing that people who claim that something being on screen that they didn't want makes their workflow "unusable". If that was the case, there are solutions for that and they've been around for years. Just because they weren't affected by their ignorance in the past doesn't excuse that.

>clearly non-technical individual

If this person is that non-technical, then something like this is definitely not a showstopper that makes it "unusable". They are not the people I'm directing these comments at.
How did they even justify the use of a camera-only sensor system for low-light conditions? At least the radar sensors had some complementarity with visible light sensors but they decided to get rid of those too.
Code completion is basically the way you get structured code capabilities in a non-structured editor. Ah, but it was invented to solve an input problem in Alice Pascal (circa 1985) which was totally a structured programming environment, so in a way code completion is a product of the environments you are wishing for.
> They could still have been case sensitive (C was), so I don't understand how that's relevant to the idea that "case insensitivity is a problem".

The point here is that case insensitivity is only a viable option if you severely limit the encoding allowed in whatever you are using - be it a programming language, filesystem, etc. If the encoding of your files is something is basically akin to ASCII or ISO-whatever (which was what BASIC and Pascal used back in the day) then case insensitivity is trivial and safe.

This whole thing breaks apart as soon as you enter a Unicode world and start accepting identifiers containing more than ASCII, and then the whole concept of "case insensitive" becomes obsolete and outright wrong.

The Unicode equivalent of "case insensitive" is Normalization [0] and it's a big heck of a minefield because it is defined depending on the locale in use. For instance, "FILE.TXT" and "file.txt" are to be considered equivalent under en_US, but not under tr_TR, where the lower case version of "FILE.TXT" is "fıle.txt" and the upper case version of "file.txt" is "FİLE.TXT". This means that normalizing strings can cause to unexpected results depending on the locale, which is especially problematic with filesystems (where a path may exist or not depending on the locale).

> Nim only folds the lower 7-bit by a 32 difference in ascii code, so it is well defined regardless of locale

yes, it is well defined but allowing the entirety of the Unicode letters also means that identifiers may contain glyphs from alphabets that have separate cases, chiefly Greek and Russian, or even accented letters such as `è` or `ö`. Case insensitivity instead of proper normalization makes them potentially confusing, and quite breaks the intent behind allowing Unicode identifiers by making non-US locales second class citizens.

IMHO it is arguably very confusing to non-English speakers that 'mela' is equivalent to 'MELA' but 'tè' isn't equivalent to 'TÈ' while 'Tè' is. It basically means you have to remember what letters are ASCII and what are not, which makes the whole "case insensitive" a potential source of confusion.

I think it is safe to say that in 2021 case insensitivity is an obsolete concept and an obstacle to proper internationalization. Case insensitivity only really works on legacy encodings and with the basic Latin alphabet, and you can rest assured it will be almost always improperly implemented anyway.

[0] https://en.wikipedia.org/wiki/Unicode_equivalence
Great news! Congratulations to everyone involved.
I don't know how much is from knowing there was a truck in the road, but I noticed in my first viewing how something was blocking oncoming headlights.

If you're going 75mph, that should really get your spidey-sense tingling. At least let off the accelerator/cancel cruise control. Be prepared to brake. Once you're closer and lined up, it's harder to tell there's anything going on because you're no longer approaching a bend with headlights on the other side of the truck, so by then it's too late.

But this is, again, all hindsight talking. In the moment, it's much harder to assess how a "typical human" might have reacted, if at all.
Cadillacs have had infrared night vision since the year 2000, how is it teslas cannot see in the dark?
So I wonder how well is this lobbying group (European Purpose Project) doing?

> The founders and CEOs of Delivery Hero, Bolt, Glovo, and Wolt have joined forces to work on a better model for regulating platform companies with the aim of providing specific commitments and recommendations to governments.

https://tech.eu/brief/delivery-hero-bolt-glovo-and-wolt-foun...
I feel like you would definitely notice the broken white lane lines ... You can see it pretty well in the uncompressed version.
They're too cold to be "observers".

The "observer" thing is something of a red herring. It's a very old misunderstanding of quantum mechanics that attracts a lot of attention despite being discarded a very long time ago.

What happens is that entangled states are unstable. It's very hard to extend them to larger, more energetic objects without de-stabilizing them. Since human beings are "large, energetic objects", anything we do necessarily causes the state to "decohere" (fall into one state or the other). But that's not because we're "observers". We just happen to be observing.

This experiment works (if it does) because the thing was frozen to almost absolute zero, and this stopped being an energetic object. It's remarkable that you can do that to tardigrades at all, though it's still not really clear that they were actually part of the entanglement.
The Developer Advocacy Handbook (2020)
You have to remember that you have a much greater "dynamic range" of vision as a human. That means that you can see much darker and brighter things at the same time.

The thing that would(or should) have alerted you as a driver is the reflecting of the truck's lights on the paint of the broken down pickup as it drove past. Although why the truck driver didn't slowdown as it passed a crash is a bit of a mystery.

However, Teslas have radar for this sort of things. On the other hand this does kinda underscore the problem of using cameras with global shutter control for self driving. The auto contrast couldnt cope with the oncoming lights, so stopped down the sensitivity of the camera, leaving it blind to that broken truck.
Our earliest, ‘half-alive’ ancestor needed little boost from heat
> Wow. I don’t know how anything without night vision wouldn’t have hit that. It’s practically invisible.

Radar and Lidar work in the dark. But yes, this is a problem with optical-only, especially since the camera-systems Tesla uses are pretty badly spec'd (1.2MP, not even 1080p)

Tesla _used_ to have a RADAR system installed. But stopped installing them and rewrote the software to get rid of it earlier this year.
You can also see the system does apply brakes just before crash or before the system aborts if you frame by frame
Boston has the combination of yankee hospitality and New Jersey charm, just substitute rotaries for “no left turns”.

It’s also an old place with weird enclaves unknown to outsiders. You may find your lovely townhome is adjacent to a superfund site.
Don’t be so sure. The lines on the road have a obvious break where the truck is. You might have noticed that and slowed down as a result, even slowed down enough to be able to notice the truck in time.
I haven't heard anything about not using enough rounds, so it's possible that my information is just out of date. My understanding is that AES-128 was chosen to be resistant against classical attacks, and AES-256 was chosen to achieve the same level of security as AES-128 against attacks that incorporate quantum computers and Grover's algorithm.
>It exists. But it's viewed as houses in the middle of a cornfield or a decaying steel town, no decent jobs, no culture, lousy weather, etc.

Who views it that way? People who have never been there and also know nothing about it? People who have never left California?
This looks very interesting, but I have a question: how to deal with multiple independent projects in the same repo? Say I have projects A, B, and C, and I made a change to a file in C. How can I make mypy run inside C only? The command would be `mypy C` from the repo root, but how can I configure pre-commit to do that?

This question also applies to GitHub Actions, which is something I'd like to implement too.
In short, register the domain name.

My method of escaping this problem is to develop things iteratively and have a minimum viable product in mind. I'm going to release something that's 80% there very quickly, and its success, if there is any, will spur me on to do the last 20%.
> Humanity advances when it can hide complexity. Tools help with that. To argue against tooling because it makes you dependent on the tooling is like telling the construction worker to put away the jackhammer and pick up the pickaxe.

Calling replacing ">=" with a ligature for "≥" "hiding complexity" strikes me as more than a bit of a stretch. They're two different visual presentations of the same thing, neither more or less complex in-and-of-themselves.

The ligature has some external complexity, though, in that for certain things I have to remember that that's "really" 2 characters in the file, and backspacing directly in front of ≥ will net me > instead of deleting the entire thing.

So if anything, ligatures are introducing a small bit of complexity that otherwise isn't there. Any relation to Socrates' quote seems forced.
Only if you don't stream it to any more compute intensive process, so you'd need to leave cycles free for that, and you are reading it from a cache cold buffer instead of eg a network buffer which would be already in cache coming out of the net stack.
Everyone’s calculation of utility is different, but Chicago/IL land also has a non explicit cost of land prices being held down by expected increases in taxes disproportionate to increases in other parts of the country, due to disproportionate levels of debt per taxpayer.

Instead of your land appreciating by a few hundred thousand, it might only appreciate by a hundred thousand, which is a decent difference in return for many people.

Obviously, that is offset by needing less cash upfront, but it does make the CoL calculations less obvious in favor of Chicago.
This is not against encryption, this is about decryption of encrypted data upon request by the authorities.
As a Belgian I guesstimate that WhatsApp has more than 80% of IM market share here.

> it's probably not a bad guess that they would lose more users globally due to the bad publicity it would generate than they would lose by cutting off Belgium.

But this is what all the tech companies do in China.

I don't think its hard to "defend" complying with the Belgian government that faces a terrorist network and drug cartel problem bigger than any other 1st world country (in relative terms).

> Poking a hole in that seems non-trivial.

They operated without E2E for many years though. I doubt that non-encrypted chat is even revoked.
And even if they pulled, there's many alternatives available. It's not like Belgium is worried about Meta's revenue.
at 75mph, even with a very quick reaction time of 0.7 seconds to shift your foot from gas to brake, your already approching 80', and haven't even started slowing down. Yanking the wheel sideways on most vehicles that speed means you either roll-over, or side-swipe a vehicle in the next lane, since you didn't have time to check that lane before swerving. I think you are drastically overrating your driving abilities.
What laser system do you think Teslas have?