Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
vardump
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
22 ms
·
421.
▲
by
vardump
2y ago
Driving in a torrential rain can be terrifying. Literally can't see practically anything in any direction. Haven't seen an equivalent snowstorm so far. Even in the worst case there's still at least 30 ft / 10 m visible r
422.
▲
by
vardump
2y ago
They'd probably want to pay if you were coding in Python.
423.
▲
by
vardump
2y ago
Tesla should have R&D in Europe as well. Then they probably would have gotten matrix lights right earlier.
424.
▲
by
vardump
2y ago
Waymo is hardly large scale.
425.
▲
by
vardump
2y ago
Tesla does use lidars for validation: https://www.notateslaapp.com/news/2125/tesla-vehicles-spotte...
426.
▲
by
vardump
2y ago
If the cameras (or our eyes) are obstructed, you shouldn't drive at all.
427.
▲
by
vardump
2y ago
I read that "probably some AI is used" as that it's human controlled. Otherwise it would have been "completely AI controlled" or something similar. I think "AI" did control their walking. Although calling
428.
▲
by
vardump
2y ago
I think it was fairly obvious from the show that the Optimus bots were remotely operated. Not like they tried to hide it at all. Just listen to the responses of the bots, they practically admitted that. The cars, however, were almost certai
429.
▲
by
vardump
2y ago
That's a bitewing, intraoral.
430.
▲
by
vardump
2y ago
What kind of dental x-rays they took? Panoramic (shows the whole row of teeth in one image), CBCT (volumetric 3D) or intraoral (a digital sensor or film was put inside your mouth)?
431.
▲
by
vardump
2y ago
Once you put something big in the LEO, you'll have to be able to boost its orbit indefinitely, because the orbit will otherwise slowly decay.
432.
▲
by
vardump
2y ago
> Starship should bring those costs below $1000. It might even bring the costs below $100/kg.
433.
▲
by
vardump
2y ago
850 km without breaks?
434.
▲
by
vardump
2y ago
This would make the cars significantly more expensive and heavier, negating any advantage.
435.
▲
by
vardump
2y ago
Surely you meant: s[i] &= ~0x20; We're talking about converting to upper case after all! As an added benefit, every space character (0x20) is now a NUL byte!
436.
▲
by
vardump
2y ago
I said use a Unicode library if input data is actual human language. Which names and addresses are. 99% case being ASCII data generated by other software of unknown provenance. (Or sometimes by humans, but it's still data for machines,
437.
▲
by
vardump
2y ago
Here's an example. Hypothetically say you want to build an HTML parser. You might encounter tags like <html>, <HTML>, <Html>, etc., but you want to perform a hash table lookup. So first you're going to normalize
438.
▲
by
vardump
2y ago
File paths are scary. The last I checked (which is admittedly a while ago), Windows didn't for example care about correct UTF-16 surrogate pairs at all, it'd happily accept invalid UTF-16 strings. So use standard string processing
439.
▲
by
vardump
2y ago
You just want a banana, but you also get the gorilla. And the jungle.
440.
▲
by
vardump
2y ago
> as there is almost no language that can be written using just that. 99% of use cases I've seen have nothing to do with human language. 1% human language case that is needs to be handled properly using a proper Unicode library. You
441.
▲
by
vardump
2y ago
I don't know whether Rust will ever be the right language for GPU programming, however your take feels somewhat unfair. Please remember there's a lot of optimizations put in the legacy compilers. What makes you think Rust compile
442.
▲
by
vardump
2y ago
As always, Raymond is right. (And as usually, I could guess it's him before even clicking the link.) That said, 99% time when doing upper- or lowercase operation you're interested just in the 7-bit ASCII range of characters. For t
443.
▲
by
vardump
2y ago
Yup. Learned so much from that page in Amiga Hardware Reference Manual!
444.
▲
by
vardump
2y ago
I was expecting same. Names are so overloaded nowadays.
445.
▲
by
vardump
2y ago
H've never hAd any issues wiphout ECC.
446.
▲
by
vardump
2y ago
> No need for a checksum, since you can use monetonically increasing version numbers and CRDTs! How does that help against random bit flips?
447.
▲
by
vardump
2y ago
Just an idea: perhaps all of the end devices should have at least some high reliability storage. This would enable local applications that require high data durability and integrity. Probably it'd require ECC RAM to prevent in memory b
448.
▲
by
vardump
2y ago
Oh, it divides only once every 8 pixels and interpolates in between and still looks so good? I stand corrected. By the way, it's "d_scan.c" for anyone who's trying to web search for it.
449.
▲
by
vardump
2y ago
Agreed on other counts except for FPU. Quake performs one FPU divide per pixel for texture mapping perspective correction. ARM7TDMI does not have any kind of divide, so perspective correction is tricky, even if it's just 120 px horizon
450.
▲
by
vardump
2y ago
But with a fraction of CPU resources. Arduino Nano's Cortex M33 is overclocked at 135 MHz, while GBA's ARM7TDMI is running at mere 16.78 MHz. ARM7TDMI takes 1-4 cycles to perform a simple 32bit x 32bit multiply, depending on the m
More ›