That's no guarantee for anything. It's already out in the open that Huawei has close ties to the Chinese government and military. The point OP is trying to make is that Chinese telecom cannot be trusted as the Chinese government is actively indulging in systematic deployment of espionage frameworks on this level - by infiltration through business.

Yep, it's impossible to do business in china without good government connections.

This method is not the least uncommon or "advanced" with those who still program assembler - in particular with the coders in the so called demoscene of lower level machines like the C-64 and Amiga - most often for creating unrolled loops to save a few cycles on removing the increase/compare/branch portion (or similar) of the loop.

If one was to be a smartass, one could say that all code is code that writes assembler. (Possibly with many levels of indirection.)

This was pretty cool, but I couldn't help being struck by how utterly poorly it performs, especially as soon as you add just a handful of objects and two light sources. Sure, it's written in JS, but JS has come a long way in terms of performance, and so have our computers.

This demonstration instantly makes me think of Blizzard's Diablo II from 2000, which features an identical effect during gameplay, with a seemingly infinite number of shadow-generating obstacles and as many light sources casting shadows as there are players on the screen, and it runs perfectly smooth even on a 500mhz P3.

I think you're comparing an apple tree with a matter replicator that makes apples.

The UI is the new and interesting aspect here.

Seriously, they store passwords in an easily reversible format? Or are these booster accounts stolen from somewhere else than Twitter's premises?

Why? The snippet of code is simple and functional enough to escape the need of being fiddled with ad infinitum ad absurdum. I can't see a cloud of maintenance need hovering over it.

I guess this is an ok way to save some tiny, tiny amount of bandwidth and server resources now and then when a user makes a mistake - but one should still not, under any circumstances, refrain from server-side verification.

I don't think the OP was trying to say that server-side validation shouldn't occur.

That being said, your statement makes me think that you are overlooking an important aspect of client-side validation: instant feedback for the user. It's not necessarily just about saving bandwidth and server resources, but providing a clean and responsive user interface.

They forgot to mention that it's a little bit too big to feel alright, even as a smartphone.

Smartphone screens seem to be like cars, each new model has larger than the previous one.

The upgrade procedure takes but minutes in itself. The time you take to save and then write your old configuration files back to /etc and whatnot is on your hands :) Sure, upgrading OpenBSD's core system files isn't as smooth as doing it on f.e. FreeBSD via its package manager, but it's definitely not about hours.