I also noticed significantly less activity than usual so you are not alone. Judging by the other commenter, it’s likely some federation issue.

Ahh, then the modification must be done on the AST level not the in-memory representation since anyway you do it, you must retain the original.

Hmm, maybe I am missing the point. What exactly do you mean by handling automatic updates in place? Like, the program that requires and parses the config file is watching for changes to the config file?

JSON5

Until someone cannot tell the difference between tab and space when configuring or you miss one indentation. Seriously, whoever thinks indentation should have semantic meaning for computers should burn in hell. Indentation is for us, humans, not computers. You can write a JSON with or without indentation if you want. Also, use JSON5 to have comments and other good stuff for a config file.

Yep. Much like we don’t treat phone numbers like a number. The rule of thumb is that if you don’t do any arithmetic with it, it is not a “number” but numeric.

I can already imagine the log generated will be a hint. We usually automate those anyway as it is closer to (D)DoS too.

M

I prefer CUID

Just to clarify: Yes, I do know not all use cases are appropriate for CUID. But in general when generating ID, I’d use CUID2

And the other memes just mention moth vibrating their genitals to throw off bat.

I cannot find the reference to the port being flimsy. I did however find the part where the top hotswap component (touchpad and the place where the plate is) is having problems. The only side port that they mention is the charging port. But the again, as I said, the firmware must be redone to account for said removeable dGPU. Now you may be wondering how big of an effect does it make when adding removeable dGPU. Off the top of my head, the motherboard must have the power supply circuitry remade to account for the additional power draw when needed. That alone will make the firmware for power control need to be redone. It can have wide range of effect for other components too because power firmware is really far reaching and may break assumption in other firmware. Not to mention a part of the cooling system is also removeable now. Framework has gone out of their way trying to invent a new standard for removeable dGPU on a laptop.

Btw, here is the quoted article that mentions the side port.

Twice, the touchpad suddenly stopped scrolling and stopped accepting button presses until I physically removed it from the system and reseated it. I’ve repeatedly gotten a Windows message about how my “USB device might have limited functionality when connected to this port” even if I’m just plugging in the charger.

Oh really? I didn’t know that once since I only referenced the article. The article had issues with the modular top side, not the port. So I guess we were talking differently from the beginning.

Uhh, does the model 13 have a modular panel? IIRC, they don’t. Also, manufacturing modular panel and modular port are very different and the knowledge transfer cannot be that big. The port for example has a looser tolerance since they aren’t really that visible most of the time. So being snug but not flush is good enough. I can imagine the panel doesn’t have that luxury. Stability issue, that I can agree. But then again, I’ll give them the benefit of the doubt since they must handle additional assumptions that cannot be made on other laptops. Namely, modular GPU. Writing a firmware with that new assumption could be a PITA.

You do realize the 13 doesn’t have the back part for replaceable dedicated GPU right? That means the chassis itself must be redesigned since the hole will make the previous experience in the 13 different enough.

Easy or not depends vary wildly. But the usual task is

• partition the drive
• format the drive
• mount the drive
• install the base system

That is the bare minimum, but we need to do more configuration to be able to boot. Hence the next task is configuring the following

• fstab
• timezone, hostname, and networking
• boot loader (I just use the EFI directly nowadays)

That is it. Everything else is usually work specific. Like, if you wanted arch to be a server, you usually didn’t install a GUI. For workstation and gaming, you need more steps but it will vary depending on hardware. The archwiki covers a good deal of hardware from laptop to desktop and their quirks.

Well, maybe he refers to the branch with the greatest common ancestor of us and whales. So our branch of evolution can have mating calls 100KM rather than their branch with measly 80KM

To be fair, he could also just be fed up after a long time being ignored for what he thinks is quite an important design decision.

For NAT, there is apparently a way to traverse NAT. I haven’t tried it tho, but the dude has a lot of research on the topic (NAT traversal), so if that didn’t work, maybe others will

Uhhh, no. I think it is better to implement something akin to federation than breaking up a company just because. If anyone wanted to sue valve, then they can enforce interoperability at the very least. But not dividing their business model. We don’t force apple to split their software and hardware did we? We force apple to have a choice of interoperability. From then, it is all fair since anyone can link their data from valve and any other store that opt to implement the interoperability protocol.

I think valve is silently collecting the data for their internal team all this time when they didn’t act. It’s always a cat and mouse game after all, but if the cat is patient, then he may catch a lot of mice. And remember, they don’t have as invasive anti cheat as any other game of the same genre.