No, it doesn't, it only has I2C (for display identification and control, same as VGA and DVI) and CEC (for remote control).

That's the ABNT2 keyboard layout, which is the keyboard layout used here in Brazil. AFAIK, it's the only common keyboard layout with that characteristic.

xkcd was prescient once again... https://xkcd.com/416/

I can off the top of my head think of at least three ways in which being careless with the code powering "your personal blog" could have real consequences. Suppose it has a bug which allows unauthenticated users to manage your pages, or even worse remote code execution. Then it could be used as a jumping-off point to attack other systems, for instance by turning it into a C&C server for some malware. It could be used in a "watering hole attack" against your readers. Or someone could edit the blog articles to make it appear that you said something you didn't.

"Not reading the code" is irresponsible for any software exposed to the global network.

If you think about it, other than the "neutral, open" part, it's a return to the traditional phone model, where every home gets a dedicated point-to-point copper pair (or sometimes two pairs), which terminates in a hub (the telco central building) nearby, instead of being shared between several homes (though I've heard that, in the distant past, phone lines were also sometimes shared between households).

Until the place you're VPNing to happens to use the same RFC1918 network address as your LAN (that is, your LAN is 192.168.10.x and the network on the other side of your work's VPN is also 192.168.10.x). Or either of them use the same RFC1918 network address libvirt is using for its virtual network. Or you want to route between several LANs (for instance, after a company merger) and some of them (but not all) were using the same RFC1918 network addresses.

All of this is avoided by using public addresses for LANs, but address scarcity makes that hard with IPv4 (unless it's a legacy LAN from the 1900s which happens to still use public addresses form the pre-NAT era).

As I've said before (https://news.ycombinator.com/item?id=44923555), in my opinion the starting point of this slide for Microsoft was WGA on Windows XP. It was the first time that they made the operating system treat the computer's administrator as hostile.

That's only the case for CPU/MB/RAM, because the interfaces are tightly coupled (you want to upgrade your CPU, but the new one uses an AM5 socket so you need to upgrade the motherboard, which only works with DDR5 so you need to upgrade your RAM). For other parts, a "Ship of Theseus" approach is often worth it: you don't need to replace your 2TB NVMe M.2 storage just because you wanted a faster CPU, you can keep the same GPU since it's all PCIe, and the SATA DVD drive you've carried over since the early 2000s still works the same.

I've read about companies where all software developers have to RDP to the company's servers to develop software, either to save on costs (sharing a few powerful servers with plenty of RAM and CPU between several developers) or to protect against leaks (since the code and assets never leave the company's Citrix servers).

Why is that argument always applied against Linux, and never against for instance macOS, which also can't run Windows software?

As a Brazilian, that statement feels bizarre. Yeah, my job and my home are not in walking distance of each other. I simply take the bus. Sure, some jobs are not within reach of the bus (or the ferry, or the metro, or the light tram, etc), and some jobs need a car (for instance, it would be hard for a HVAC technician to take all their equipment on a bus), but saying it's "almost impossible" to find a job?

> demanding there be things like grocery shopping as well make it not feasible for most people.

That also sounds bizarre to my ears. Most places I've known have small grocery shopping places on nearly every corner. You just have to walk.

You are assuming the parent is the administrator of the computer.

A simpler solution: we already have an offset between local time and coordinated time, just change that offset. So, for instance, Brasília Time, which is currently UTC-03, would become UTC-02 or UTC-04, depending on which way the change went.

Unless it changed recently (it's too slow right now for me to check), Wikipedia has always worked perfectly fine without JS; that includes even editing articles (using the classic editor which shows the article markup directly, instead of the newer "visual" editor).

Edit: I just checked, and indeed I can still open the classic edit page even with JS blocked.

It used to be all "admin" accounts, of which there were many more. Restricting it to "interface admin" only is a fairly recent change.

So, like the Samy worm? (https://en.wikipedia.org/wiki/Samy_%28computer_worm%29)

> For example: A (calls) -> B -> C -> D

> And you made changes in D, how do you know the side effect on B, what if it broke A?

That's poor encapsulation. If the changes in D respect its contract, and C respects D's contract, your changes in D shouldn't affect C, much less B or A.

Brazil no longer uses US style plugs (though you'll still find them in older installations), it nowadays uses a much safer EU-derived style.

> I find it insane that Brazil continues to be dual exclusive voltage; all of North America is dual concurrent voltage. Every home/office has 120v and 240v available. In Brazil it depends on what state/city you live in - some get 120v, some get 240v.

This is wrong; it's very common to have for instance both 127V and 220V in the same building, sometimes even side by side in the same wall faceplate; 127V is phase to neutral, 220V is phase to phase (on the common 3-phase system). Yes, it does depend on the city, some cities use 220V exclusively, and there are a few other variations, but AFAIK the 127V/220V 3-phase combo is the most common.

> Even worse they use the same standard plug design for both so you'd better hope the plug is the right color or has the right sticker. And you can't be sure you can take electrical appliances from one city to the next! At least they should have adopted different plugs for different voltages.

Yeah, at least it's better than the confusing mix of legacy sockets we had before (which already were mixed voltage - and yeah, we already used the "120V 5-15 NEMA plug" aka "computer plug" even for 220V).

> No luck needed. Linux based phones are starting to become viable as daily drivers.

Then please tell me, which non-Android Linux-based phone can I buy here in Brazil (one of the first places where Android would have these new restrictions)? I'd love to know (not sarcasm, I'm being sincere). Keep in mind that only phones with ANATEL certification can be imported, non-certified phones will be stopped by customs and sent back.

As long as the JIT is working properly, it shouldn't matter: the code should always run "as if" it was being run on an interpreter. That is, the JIT is nothing more than a speed optimization; even if you disable the JIT, the result should still be the same.