kornholi

Latest iterations (NG-PON2 and XGS-PON) are 10G symmetrical, and XGS-PON is now cheap enough that GPON doesn't make much sense. AT&T Fiber in the US has been deploying it for the last few years.

[1] https://directory.eoportal.org/documents/163813/5615117/SkyS...

No, that's up to the user. If you include protobuf in your Bazel workspace and have a toolchain configured, protobuf will be built with that toolchain (this is also how you would cross-compile). Bazel workspaces are still a little rough around the edges and interactions between them can be very confusing, as Google doesn't need them internally (everything is vendored as part of the same tree).

Under the hood there's a default auto-configured toolchain that finds whatever is installed locally in the system. Since it has no way of knowing what files an arbitrary "cc" might depend on, you lose hermeticity by using it.

Of course, the whole model falls apart if you want to depend on things outside of Bazel's control. However in practice I've found that writing Bazel build files for third-party dependencies isn't as hard as it seems, and provides tons of benefits as parent mentioned.

For example, last week I was tracking down memory corruption in an external dependency. With a simple `bazel run --config asan -c dbg //foo`, I had foo and all of its transitive dependencies re-compiled and running under AddressSanitizer within minutes. How long would that take with other build systems? Probably a solid week.

https://github.com/bazelbuild/bazel/issues/4558

The NSA's Neuberger said this wasn't the first vulnerability the agency has reported to Microsoft, but it was the first one for which they accepted credit/attribution when MS asked.

Sources say this disclosure from NSA is planned to be the first of many as part of a new initiative at NSA dubbed "Turn a New Leaf," aimed at making more of the agency's vulnerability research available to major software vendors and ultimately to the public.

Since these repeaters are typically placed every 50-80km, there's a significant number of them in long systems and powering them becomes a challenge. These cables usually operate around 10kV DC at 1-2 amps, and I'm not sure how realistic it would be to go higher. The wire resistance losses are probably already more than 70% of the voltage budget, so you can't really use more current (voltage drop = I^2 R). Higher voltages cause other issues such as dielectric breakdown. Deep ocean cables are actually pretty thin, about as thick as a garden hose, and I doubt you could easily pass more than 15kV. You also have to account for ground voltage shift between the continents which may be as high as 1kV and depends on the weather.

Expires somewhere around 2018 (17 years after issuance)

I've been hearing discouraging things from both architecture and silicon people at Intel. It seems like they lost direction, probably because of the recent explosion of mobile/ARM.

At first I was going to blame all of the garbage from rockstar brogrammers, but even the simple HN comment page tab is using 264MB of RAM on macOS. The browser itself uses an additional 208MB according to Chrome's task manager, not counting all of the extensions. Where is it all going? There's 10 lines of JS on this page and a tiny amount of CSS. Has Chrome become that bloated?

This is especially annoying when many modern "desktops" apps are just Chromium wrappers that bleed memory.