Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
gcp
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
88 ms
·
841.
▲
by
gcp
10y ago
It'll also cover OS crashes or power failures. Agreed that those aren't very common either.
842.
▲
by
gcp
10y ago
Samsung's low cost line is under warranty up to 40TB/year. Tests have shown that the actual drive lifetime is several times that. So basically, no, you don't have to worry about this. Essentially, people are complaining that
843.
▲
by
gcp
10y ago
A state sponsored attacker has some (easy) possibilities that are normally out of the league of a normal attacker. Like showing up on the doorstep of a CA and asking them to issue forged SSL certificates. This was relevant for the pinning b
844.
▲
by
gcp
10y ago
H264 isn't proprietary, it's patented. Anyway, like my own post here, what you say is factually right but besides the point. Users expect H264 to work or the web will break. Like -webkit prefixes.
845.
▲
by
gcp
10y ago
But didn't KPart rely on KDE (libs)? That's hardly embeddable in any meaningful sense. Gecko was embeddable too if everything you wrote was XUL :-)
846.
▲
by
gcp
10y ago
Video playback doesn't work even on twitter and vimeo This is because they use H.264, a patented but common video codec. Chrome includes a licensed decoder for it, but Chromium cannot include that because it's open source. Firef
847.
▲
by
gcp
10y ago
Well yes, but there was also significant outreach effort to get rid of the most egregious IE specifics and show how things could be done better and cleaner with (non IE specific) web standards. And that part was rather successful.
848.
▲
by
gcp
10y ago
Chrome is one of the most web standard compliant browsers out there It helps if you're the one making the standards. Much of the current web standardization effort is just documenting what Chrome does and what particular bugs Blink h
849.
▲
by
gcp
10y ago
Google hired away some key developers, yes. Chrome was insurance for Google. Even with IE's monopoly broken, their search engine could become under threat if someone else outbid them for Firefox's default search. With Chrome havin
850.
▲
by
gcp
10y ago
Disable your echo cancellation. It breaks DTMF.
851.
▲
by
gcp
10y ago
If you do an outbound call (i.e. outside Skype, to something that would actually use DTMF) Skype doesn't use SILK/Opus on the outbound connection. You can tell because the quality is way worse. There are also issues with the echo
852.
▲
by
gcp
10y ago
I also tried to hide the popup before I saw the close button. It's very hard to find. But I'm sure that's intentional?
853.
▲
by
gcp
10y ago
If you type system.web into the address bar, Firefox gives you a list with 2 choices: a) Visit system.web b) Search google for system.web
854.
▲
by
gcp
10y ago
Exactly! It's even worse because Netflix has specific deals with Microsoft/Edge that use a different DRM technique - they announced so publicly as a reason to restrict Chrome and Firefox to non-HD video.
855.
▲
by
gcp
10y ago
I guess having a topographical map helps too.
856.
▲
by
gcp
10y ago
4 saves in 2 years does sound very impressive. I guess these accidents were relatively common. That would certainly explain the development of this system, and how aggressive it's allowed to act.
857.
▲
by
gcp
10y ago
I would assume that it keeps the last known offset between the radar altimeter and the pressure altimeter. It may have also pulled up based on the pressure altimeter, as obviously the plane won't be flying below sea level regardless. B
858.
▲
by
gcp
10y ago
Would it have overruled the pilot input if that would have been the case?
859.
▲
by
gcp
10y ago
> far fetched assumptions I don't think considering how to actually implement the basic operation without a terrible performance penalty is a "far fetched assumption". > That document does not explicitly forbids this. Y
860.
▲
by
gcp
10y ago
ARM ARM, section B2.2.6 The CTR holds minimum line length values for: - the instruction caches ...this value is the most efficient address stride to use to apply to a sequence of address-based maintenance operations to a range of addresses.
861.
▲
by
gcp
10y ago
Yes, I am sure. If we forget about the ARM spec explicitly enforcing this anyway, here's some food for thought: how exactly do you suppose the GCC people could write correct code, if they aren't allowed to make that assumption?
862.
▲
by
gcp
10y ago
The assumption isn't faulty, it's guaranteed to be right. And it has to be, or there's no way to write functional code for ARM.
863.
▲
by
gcp
10y ago
This is exactly the fix used in the kernel, yes. The trickiness and complexity comes from the cache line size probe having to be intercepted.
864.
▲
by
gcp
10y ago
Samsung's design breaks correctly written user-land code. Hence, they're 100% at fault. Going to 128-byte cache lines was fine, but they should have made the lower-power part of the chip match (which in this case they likely could
865.
▲
by
gcp
10y ago
ARM's own designs (A53, A57, A72, A73) all have 64-byte cache line sizes and avoid the problem entirely. The one at fault appears to be Samsung, who designed M1 Mongoose with 128 byte lines and packed it together with A53 cores in thei
866.
▲
by
gcp
10y ago
>> user_pref("dom.battery.enabled", false); In current Firefox this is AFAIK whitened exactly to prevent fingerprinting. Disabling it will increase your footprint because it's not the default.
867.
▲
by
gcp
10y ago
They list the battery API in Firefox, but that is actually whitened exactly to prevent user tracking.
868.
▲
by
gcp
10y ago
Now to have its hand tied because of his job at facebook is the worst thing possible. If you accept the job you give up your work. It's not like there's no compensation. Am I correct in that. Yes, the retaliation (and hence, i
869.
▲
by
gcp
10y ago
Facebook's license seems superior for those parties who wish to end software patents It's mostly superior for Facebook. If you're a party that wants to end software patents, but intends to use zstd in any place you might wa
870.
▲
by
gcp
10y ago
Don't tell firmware/embedded programmers :-/
More ›