Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
lorenzhs
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
69 ms
·
691.
▲
by
lorenzhs
9y ago
Wouldn't it be Elsevierum ? You need an accusative, and –er nouns tend to be second declension iirc.
692.
▲
by
lorenzhs
9y ago
You specifically said the fix might be to permanently disable HT. The TSX situation was indeed unfortunate, I have one of the affected CPUs. But it was a new feature that was broken, not something that used to work, so the bug's impact
693.
▲
by
lorenzhs
9y ago
Seems like they do when it fixes serious bugs, a quick search yields e.g. https://support.microsoft.com/en-us/help/3064209/june-2015-i... (" This update fixes several issues with Intel CPUs that could ca
694.
▲
by
lorenzhs
9y ago
That's just the workaround until a fix is available for your CPU, if I understood correctly.
695.
▲
by
lorenzhs
9y ago
> Intel allowed a PROCESSOR bug to be reported, tested, and fixed without telling anyone that the bug actually exists That's just not true. Intel published the erratum in April: https://www3.intel.com/content/
696.
▲
by
lorenzhs
9y ago
Expectations of hardware are indeed higher than for software, but isn't it a valid trade-off for Intel to make as long as most of the issues can be fixed with a microcode update? On Windows, it's updated via Windows Update, and on
697.
▲
by
lorenzhs
9y ago
They forgot to follow up on a support ticket. As your quotation mentions, the issue was documented and fixed. Calling that "inexcusable" is a bit strong, don't you think? I'm not a particularly big fan of Intel's pr
698.
▲
by
lorenzhs
9y ago
Really? How is it different from a kernel bug that causes random behaviour? Both apparently can be fixed with a software update. They're both bad, but why should Intel be held to a higher standard if mitigation is similarly complex?
699.
▲
by
lorenzhs
9y ago
So it's okay for software to have bugs that get fixed (I think everybody here acknowledges that software will always have bugs), but Intel isn't allowed to have issues in their processors, even if they can fix them with a software
700.
▲
by
lorenzhs
9y ago
I don't think we're disagreeing. All I meant was that if a critical error arises at a certain stage of compilation, errors that would only be detectable in a subsequent stage won't be emitted. This is in no way limited to thi
701.
▲
by
lorenzhs
9y ago
Ah, right, I might have misunderstood you there. This is a bit of a special case though, as the preprocessor for C++03 messes up the code so badly that a later parser trips, and it never even gets to the pass that resolves identifiers bec
702.
▲
by
lorenzhs
9y ago
I wouldn't blame the compiler for missing make_unique in that scenario. Rather it would be nice if compilers warned that u8"foo" is a C++11 construct and any errors following could be due to it not existing in C++03. It n
703.
▲
Firmware vuln allows arbitrary code execution in System Management Mode
(twitter.com)
3 points
by
lorenzhs
9y ago
|
0 comments
704.
▲
by
lorenzhs
9y ago
Yes that's why they can set limits on unlimited plans and start charging "reasonably" after those limits are exceeded.
705.
▲
by
lorenzhs
9y ago
Right, but that's backbone traffic cost. The majority of total cost is going to be the wireless part of your data's journey. Interpolating from intranational data cost, 8€/GB is still a lot but maybe off by one order of magn
706.
▲
by
lorenzhs
9y ago
Note that the telcos don't stop charging each other for roaming, they just stop charging customers . This might even be good news for Spanish and Italian telcos.
707.
▲
by
lorenzhs
9y ago
They also have barcodes on just about every side of the packaging. The cashiers don't have to figure out which side is the one with the barcode, they can just slide it across the scanner in whichever orientation it's on the belt.
708.
▲
by
lorenzhs
9y ago
You've got your Aldis mixed up. Aldi Nord owns Trader Joe's (not the other way around). Aldi stores in the US are Aldi Süd . The two are separate companies, Aldi Nord serves the North of Germany and Aldi Süd the South. Their in
709.
▲
RadidCheck – property-based testing for C++
(github.com)
1 points
by
lorenzhs
9y ago
|
0 comments
710.
▲
by
lorenzhs
9y ago
I don't know, I'm perfectly happy with my iPad Air 1. It's not as fast as my fancy laptop, but it doesn't have to be. It's a very pleasant web-browsing device.
711.
▲
by
lorenzhs
9y ago
Signal for Android has reproducible builds, so you can verify that the version on the Play Store matches the code you audited.
712.
▲
by
lorenzhs
9y ago
I admire your confidence but I don't share it - showing universality for a complex construct like yours is rather nontrivial. You should really start by testing with SMHasher, though. Best of luck.
713.
▲
by
lorenzhs
9y ago
Doesn't mean that you can't write efficient heuristics that find close-to-optimal or even optimal solutions for a wide variety of practical instances.
714.
▲
by
lorenzhs
9y ago
Yeah, but then you've got cases like this: https://www.troyhunt.com/ad-blockers-are-part-of-the-problem... I've been using adblockers for about ten years now, but blocking that just seems over the top and I unders
715.
▲
by
lorenzhs
9y ago
In addition to the things others have pointed out, note that "universality" is a well-defined concept w.r.t. hash functions: https://en.wikipedia.org/wiki/Universal_hashing - you should probably not use it to
716.
▲
by
lorenzhs
9y ago
I wouldn't use steganography (it's not normally very space-efficient), just dump the payload data into a PNG's comment field. You can do this with exiftool "-Comment<=/path/to/inputfile" dummy.png
717.
▲
by
lorenzhs
9y ago
Agreed, streaming algorithms and sketches are a fascinating topic. The article's author, Graham Cormode, has been conducting research in that area for a long time and is one of the co-authors of the Count-Min Sketch paper. Basically
718.
▲
by
lorenzhs
9y ago
The sampling algorithm you describe becomes pretty slow as k grows. There are much faster algorithms. We wrote a paper on fast sampling: https://arxiv.org/pdf/1610.05141.pdf (page 11, what you described is labelled &
719.
▲
by
lorenzhs
9y ago
Dropbox did a thing a few years back where they gave you permanent additional storage for uploading photos. A jpeg header followed by gigabytes of zeroes supposedly worked just fine. This is very easy to catch, though. Abusing comment field
720.
▲
by
lorenzhs
9y ago
The video in no way supports your hypothesis: https://youtu.be/Er7qPv8jsZo?t=1h1m55s
More ›