Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jfries
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
by
jfries
8y ago
Well, yes, using strtok works if the data happens to be structured in a certain simple way. Very often you want to do something more advanced though, and using regex for matching tokens is then necessary.
32.
▲
by
jfries
8y ago
160 bits per second is actually pretty high. As comparison the German radio time signal used by parts of Europe sends out 1 bit per second: https://en.wikipedia.org/wiki/DCF77
33.
▲
by
jfries
8y ago
Could also be used to accelerate the print of a single item by having different nozzles work at different parts of the design at once. Would need lots of updates to the slicer and solving some tricky optimization problems.
34.
▲
by
jfries
8y ago
Would be interesting if this kind of map was used to find previously known wolves by looking for appropriately sized areas not covered by any other wolf.
35.
▲
by
jfries
8y ago
Cool thinking! The linked printer can be seen as optimized for serialized throughput, whereas in the end the total amount of data transferred is what matters. So parallelize! Are there FDM printers with multiple nozzles extruding in the sam
36.
▲
by
jfries
8y ago
Probably missing some context, but why is it easier to evacuate in the morning than in the afternoon?
37.
▲
by
jfries
8y ago
If anybody else is curious how the pattern looks: https://en.wikipedia.org/wiki/Penrose_tiling
38.
▲
by
jfries
8y ago
In that case wrapper functions can be created where needed to normalize the signatures.
39.
▲
by
jfries
8y ago
What do you consider good hearing skills to practice, except echolocating?
40.
▲
by
jfries
8y ago
Seems to me that the size of the star would be a problem. Assuming the process of actually building stuff large enough to cover a star is solved, how do you control the polarizer to get any reasonable bandwidth? The light emitted from one s
41.
▲
by
jfries
8y ago
While definitely cool, I wonder how effective this is. Code/random binary data should have different characteristics than image data.
42.
▲
by
jfries
8y ago
This is fantastic and there is great potential, but would be better with better accuracy on driving time, and also public transportation times worldwide. Also an important input is commute start times for each entered address (in case spous
43.
▲
by
jfries
8y ago
The gps receiver's software could enter the pin. No buttons necessary.
44.
▲
by
jfries
8y ago
I don't think it's helpful to think of the structure as being based on a 2x2 grid. A bit down on this page (random Google hit) are ways to structure a character: http://www.guavarama.com/2015/03/07/l
45.
▲
by
jfries
8y ago
> They probably didn't spot this one because it passes too close to the Dead Sea, which is below sea level This is adressed in the paper. The relevant part of the problem statement: "the longest distance one could drive for on
46.
▲
by
jfries
8y ago
Just don't panic when the cruise ship you're on signals that it is operating in reverse by sounding the horn three times.
47.
▲
by
jfries
9y ago
I was waiting for the article to mention using those 6 sided pencil stubs in the first image as dice. Seems like a good way to disguise a die.
48.
▲
by
jfries
9y ago
Wow level 3 there was really elegant. In general I try to find use for a strong type system to force correct code, but here it's Rust's ownership model that ends up saving the day.
49.
▲
by
jfries
9y ago
Very cool, but can't help to wonder.. What is the likelihood of taking a random picture that captures the start of a supernova? How often does one happen in a given photograph-sized portion of space? Because astronomics is involved it
50.
▲
by
jfries
9y ago
This kind of thing always needs some arbitrary line drawing. Even if there no external libraries and only pure machine code, that machine code still runs in an environment defined by hardware components, and those hardware components have a
51.
▲
by
jfries
9y ago
Wow, that is fantastic! :) it looks like the same idea but developed.
52.
▲
by
jfries
9y ago
Well if the language is flexible enough it doesn't have to be a big annoyance to have types for both fp32 and nnfp32 (no-NaN fp32). nnfp32 guarantees things that a fp32 doesn't, for example that comparison is always legal and work
53.
▲
by
jfries
9y ago
This is definitely nice. But I'm thinking that NaN is a bit like null, in that it's a surprising value that may pop up which suddenly means something completely different, and code must handle it correctly. Just as some languages
54.
▲
by
jfries
9y ago
Sure, the worst case would have a large number of re-calculations. But it seems like the common case would converge quickly.
55.
▲
by
jfries
9y ago
Do you really need to regenerate the whole dynamic programming table though? It seems to me that it could be kept more conservative and only recalculate the needed parts.
56.
▲
by
jfries
9y ago
A dump of memory (several kilobytes, megabytes or whatever) is inherently big endian: it proceeds from the base address and goes up. It only looks "inherently big endian" when you print bytes on each line starting from the
57.
▲
by
jfries
9y ago
I don't understand what you mean. Line breaks can be inserted where ever suitable. Whether the bytes are listed left-to-right or right-to-left makes no difference.
58.
▲
by
jfries
9y ago
Not at all, you just list the whole dump right-to-left. Then it works out regardless of word size.
59.
▲
by
jfries
9y ago
Little-endian is slightly more confusing for humans I've heard this before, but the reason is that you view hex data and list numbers left-to-right as if they were letters. They are not. 0x12345678 stored big-endian, numbering
60.
▲
by
jfries
9y ago
For what it's worth, "Barcode Scanner" on Android was able to scan it effortlessly.
More ›