Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
amaranth
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
17 ms
·
121.
▲
by
amaranth
8y ago
> if you sell it on Steam you can't sell it for cheaper elsewhere My understanding is the actual rule is a bit narrower than that. You can't sell _Steam keys_ cheaper elsehwere. If you sell it as a non-Steam game they don'
122.
▲
by
amaranth
8y ago
This is just the mitigations at the kernel level, to protect the kernel from applications and applications from each other. Without this applications can't even attempt to secure themselves from these issues. I think to allow applicati
123.
▲
by
amaranth
8y ago
The GCC C++ ABI got a major overhaul in 3.4 so any C++ API won't be compatible. There may have been more platform-specific ABI changes too, I know mingw had one in the 4.x series.
124.
▲
by
amaranth
8y ago
OpenBSD has been accused of breaking embargoes in the past. They are pretty open about their policy of pushing their fix as soon as it's ready and not doing anything to obfuscate what they're fixing and why.
125.
▲
by
amaranth
8y ago
Maybe but I wouldn't be so sure. Mobile browsers today don't use JPEG hardware decoders and for a single frame HEVC isn't _that_ expensive to decode. I believe the argument is that hardware decoders are inconsistent (what you
126.
▲
by
amaranth
8y ago
I've seen suggestions from ex-Microsoft employees that the only reason they were even charging money for Visual C++ and the rest of their toolchain was to avoid killing off the third-party market. They wanted to be as developer friendl
127.
▲
by
amaranth
8y ago
Of course, guess I shouldn't comment before the caffeine kicks in... I was thinking without reified types the JIT can't optimize it easily then got stuck on that. Of course the compiler could do so, Java just doesn't have an
128.
▲
by
amaranth
8y ago
This is an argument against specialization, not against reification. With type erasure your compiler can't perform type-specific optimizations, at least not without a JIT and borrowing some optimization techniques from dynamically type
129.
▲
by
amaranth
8y ago
For the most part it was documenting the common subset of how the browsers actually worked. Only one browser implemented ActiveX or ever wanted to so it isn't in the spec.
130.
▲
by
amaranth
9y ago
I don't think Uber's safety drivers have any domain knowledge. The law says you need bodies in seats so Uber is paying as little as possible to put bodies in seats. They aren't engineers or professional (as in stunt/tric
131.
▲
by
amaranth
9y ago
The bots are manipulating the trending topics which means they're driving the kinds of conversations happening on twitter.
132.
▲
by
amaranth
9y ago
So you agree the US is in another Cold War with Russia then? Otherwise how is that relevant?
133.
▲
by
amaranth
9y ago
Inventing people and getting someone to show up and vote as them isn't what you'd do with write access to voter rolls. Instead you'd want to remove or corrupt existing voter information. This would cause huge delays at pollin
134.
▲
by
amaranth
9y ago
Thanks to Spectre I don't think we'll be seeing threads anytime soon. Well, not threads with shared memory anyway which removes a lot of the point of them. Same reason JavaScript just lost SharedArrayBuffer, too easy to make a hig
135.
▲
by
amaranth
9y ago
It's also not using the AMD-style interposer but Intel's EMIB which they claim is much cheaper.
136.
▲
by
amaranth
9y ago
They aren't webapps but they're each a different ecosystem and workflow entirely separate from the rest of the OS. You can add integration to various parts of the OS via extra scripts/plugins but that you need to do so proves
137.
▲
by
amaranth
9y ago
Compression via next-symbol prediction seems to be what you'd be looking for. That's what the PAQ compression schemes focus on, although they're very slow and definitely overkill for non-archival purposes. You'd probably
138.
▲
by
amaranth
9y ago
According to https://plus.google.com/+jwildeboer/posts/jj6a9JUaovP Google was deploying a retpoline-based mitigation in production in September. Seems likely that existed _before_ any thought of microcode fixes. I
139.
▲
by
amaranth
9y ago
It's an almost stock Tegra X1 reference system. The hacks that got access to the system recently started with a Tegra backdoor/debug option Nvidia and Nintendo apparently forgot about. https://www.youtube.com/watch
140.
▲
by
amaranth
9y ago
I suspect it's because they can't get out of sync in a way that causes OOB reads. You could have the null too early in the buffer but can't have it too late. With Pascal strings you could have a buffer of size 18 but with a l
141.
▲
by
amaranth
9y ago
According to their patch notes Apple's ARM cores are also vulnerable. And it's not just the latest ARM, the A15, A57, and A72 are vulnerable to a less severe variant of Meltdown.
142.
▲
by
amaranth
9y ago
The result might not be glorious but the fire is amazing to watch.
143.
▲
by
amaranth
9y ago
I think this could occur on any CPU that doesn't have a separate TLB for kernel mode and has speculative execution. So far it looks like it only occurs on Intel's CPUs but I don't think that has anything to do with RISC vs CI
144.
▲
by
amaranth
9y ago
> System updates have been seriously optimized in the last few Android releases. They used to take like 5 minutes. On the Pixel phones Google uses two system partitions. One is the one you're currently running and the other one gets
145.
▲
by
amaranth
9y ago
I'd guess that, along with converting all of their artwork to bitmaps, this was needed because Haxe+OpenFL didn't support what they were doing before. If they were going to have to change it anyway better to make that change befor
146.
▲
by
amaranth
9y ago
More like how Sears used to work but with more locations so you don't have to go (as far) out of your way on your commute from work. You order stuff from a vast catalog (Amazon website) and then when it's available you go pick it
147.
▲
by
amaranth
9y ago
4% of all BitCoin that will ever exist.
148.
▲
by
amaranth
9y ago
It's going to be heavily dependent on what you're doing. WASM can be as fast as native code but is more likely to be 1/2 the speed of native on realistic benchmarks. However, the overhead of moving between WASM and JS is quit
149.
▲
by
amaranth
9y ago
DSL started life considered a common carrier, it wasn't until 2005 it was reclassified, to match a previous decision that cable internet wasn't a common carrier.
150.
▲
by
amaranth
9y ago
I imagine the main potential source of expense would be covered by them still being considered DMCA safe harbors. So long as they're still considered a "mere conduit" the most you can compel them to do is stop providing servi
More ›