dbaupp

10 ms·

91.
by dbaupp 5y ago
Thanks! That’s true, the business name could be uppercase, but it feels suboptimal to be changing text displayed to users (and shouting at them). It would drop the final version from 5 to 4.
92.
by dbaupp 5y ago
I’d guess it was probably a combination of a quick roll-out, and also concern that people wouldn’t know what to do with them hence a lot of the text is emphasised. (I could also imagine there was mostly testing in “laboratory” conditions, s
93.
by dbaupp 5y ago
Thank you! And interesting. It seems like the trade-offs are slightly different, although, unless I’m missing something, using URLs does work slightly nicer for people without the appropriate app installed (or scanning with the built-in cam
94.
Mechanical sympathy for QR codes: making NSW check-in better(huonw.github.io)
134 points by dbaupp 5y ago|64 comments
95.
The Select Story(aqjune.github.io)
1 points by dbaupp 5y ago|0 comments
96.
Optimal text segmentation for QR Codes (2018)(nayuki.io)
1 points by dbaupp 5y ago|0 comments
97.
by dbaupp 5y ago
That's a cool exercise! :) However, it loses some of the niceties for offline check-in (the business name, in particular), without an in-app data source. And, unfortunately, it low resolution doesn't help that much with error corr
98.
by dbaupp 5y ago
Cool, nice tip.
99.
by dbaupp 5y ago
Thanks! Yeah, glossy paper (or glass) leading to reflections can be bad. The worst one I’ve seen is printed at A5 size (on an A4 page…) and then placed behind glass, outside. Basically useless! I would imagine that NFC requires too much act
100.
by dbaupp 5y ago
Yeah, the NSW ones contain a base64-encoded JSON blob storing: the id of a business (a short numeric string), the business name (shown in the app even during an offline check-in) and the business address. I haven’t investigated the Victoria
101.
by dbaupp 5y ago
You’re even understating the impact of the quiet zone: at version 1, the QR code itself is only 52% of the code + quiet zone area (21**2 modules out of 29**2). Almost twice as bad! :) That said, in practice, a quiet zone of one module or ev
102.
by dbaupp 5y ago
That’s actually exactly the topic of my next post, and the reason I even started looking at this. :) As the sibling says, there’s some data that is useful to store in every code to enable user-friendly offline check-ins, but they could inde
103.
Flexible unsupervised and semi-supervised graph models with Deep Graph Infomax(medium.com)
3 points by dbaupp 5y ago|0 comments
104.
QR error correction helps and hinders scanning(huonw.github.io)
72 points by dbaupp 5y ago|42 comments
105.
by dbaupp 5y ago
Yeah, you’re right that was the 2008 version. Fair enough.
106.
by dbaupp 5y ago
I get the sense that implementation efficiency was considered as part of the spec: if it wasn’t efficient, vendors with existing FP hardware would have less incentive to switch. Allowing operations to happen via simple bit twiddling (in s
107.
by dbaupp 5y ago
This would mean hardware/software tricks like those below wouldn’t work directly and would need additional gates/operations, because they’d noticeably change the meaning of NaNs. -x => x xor 0b100…00 abs(x) => x
108.
by dbaupp 5y ago
I think that’s not the full story. The standard says: A quiet NaN bit string should be encoded with the first bit (d1) of the trailing significand field T being 1. A signaling NaN bit string should be encoded with the first bit of the trai
109.
The Joy of Cooking (An App)(medium.com)
2 points by dbaupp 5y ago|0 comments
110.
The Joy of Cooking (An App)(huonw.github.io)
1 points by dbaupp 5y ago|0 comments
111.
Tuplex: Fast Python Data Science(tuplex.cs.brown.edu)
7 points by dbaupp 5y ago|0 comments
112.
by dbaupp 5y ago
The author of curl wrote https://daniel.haxx.se/blog/2021/03/09/half-of-curls-vulnera... which fundamentally disagrees with your assertion about it.
113.
by dbaupp 5y ago
It's somewhat meaningless to compute exact cross-overs for big-O complexities without the constant factors. That is, the actual times for the algorithms are C1 * sqrt(n) + ... and C2 * log(n)^3 + ..., where the ... are lower-order term
114.
by dbaupp 5y ago
Parsing a single header file in isolation is cheap, but each header will include others, and templates mean many headers contain large amounts of code inline. For instance, just including <vector> results in the compiler having to loo
115.
by dbaupp 6y ago
I think the trick of using a separate file per target works just as well in Rust, where each one imports the appropriate HAL(s) and they all expose the same interface as each other. “Circular” imports across the files should work too. This
116.
by dbaupp 6y ago
Sure, it sucks that unpinned dependencies lose historical context as the deps move forward, and I’ve personally suffered this in my own library maintenance work... but there’s still the fundamental issue of conflicting pinned versions if th
117.
by dbaupp 6y ago
Libraries pinning dependencies only fixes a narrow portion of the problem and introduces a bunch of others (particularly in ecosystems where only a single version of a package can exist in a dependency tree). In particular, it is great beca
118.
by dbaupp 6y ago
> But 'answer' is of course not owned by the current function As you imply later, ‘answer’ itself is owned by the current function, but the ‘answer’ value is a pointer that doesn’t own what it points to. This subtlety, that ref
119.
by dbaupp 6y ago
You may be also interested in the many existing teaching resources published by non-language-designers (whatever that means for a community-driven project like Rust), such as Rustlings and Rust by Example at https://www.rust-lang
120.
by dbaupp 6y ago
A type constraint like T: ‘a or T: Trait is constraining values of type T, not the type T itself. That is T: ‘a is saying “all references in values of type T live at least as long as ‘a”. This includes ‘a = ‘static and the vacuous case of T

More ›