stardreamer

Is there a specific reason you're looking at shadowsocks? The original developer has been MIA for years. People who used it in the past largely consider it insecure for its original stated purpose

trojan-gfw is a better modern replacement. However that requires a certificate in order to work. You can easily get one via lets encrypt.

At this point, let Shadowsocks, obfs, and kcp die a graceful death like GoAgent before it did.

I don't think either of us is the target audience here. I can see a "cheaper" (questionable) Pro laptop being useful for students going into college with a limited budget. An undergrad CS/graphic design degree shouldn't tax an 8gb machine too much, assuming students shut down everything else when doing their once-a-semester major rendering/compiling/model training. If people just want Macbook pro software with more ports, a "cheaper" machine is better than none. Personally, I would still get a used/refurbished machine though.

That being said, my current laptop workload tends to be emacs, qpdfview, Firefox, and tmux on EL9. For the remaining stuff, I usually just spin up a VM then ssh/xrdp into it. As for slack, teams, jabber, etc, I'm happy to report I've been out of industry/IT for 1+ years and don't plan on going back anytime soon. For all I care, Apple can call their models unicorn edition. As long as it sells it's not stupid.

You don't understand. It's not like the self-driving feature is just software where they can price it at whatever they want. It's physically consuming brain cells every month. And those aren't free you know!

::: spoiler Do I really need a \s tag for this or does this tin foil hat make me look fat? :::

8gb RAM and 256 gb storage is perfectly fine for a pro-ish machine in 2023. What's not fine is the price point they are offering it (but if idiots still buy that, that's on them and not apple). I've been using a 8gb ram 256 gb storage Thinkpad for lecturing, small code demos, and light video editing (e.g. zoom recordings) this past year, it works perfectly fine. But as soon as I have to run my own research code, back to the 2022 Xeon I go.

Is it Apple's fault people treat browser tabs as a bookmarking mechanism? No. Is it unethical for Apple to say that their 8GB model fits this weirdly common use case? Definitely.

Because anyone who works at the assembly level tends to think that the x86_64 ISA is garbage.

To be fair, aarch64 is also garbage. But it's less smelly garbage.

That being said, I'm not expecting any of these CPUs to be hanging in the Sistine Chapel. So whatever works, I guess.

Thanks for the feedback! I'll be sure to use non-printing characters instead of emojis for my passwords! (They can't guess it if it's invisible right?)

In all seriousness, why are people so adverse to using password managers? People are plenty willing to use the browsers built-in "remind my password" instead of a proper password solution such as bitwarden... And they come up with such "hacks" just to avoid using a proper length password.

Having one program (process) talk to another is dangerous. Think of a stranger trying to come over to me and deliver a message. There's no way I can guarantee that he isn't planning to stab me as soon as he sees me.

That's why we have special mechanisms for programs talking to other programs. Instead of having the stranger deliver the message directly to me, our mutual friend Bob (IPC Library, binder in this case) acts as an intermediary. This way at least I can't be "directly" stabbed.

What's preventing the stranger from convincing Bob to stab me? Not much (except for Bob's own ethics/programming)

To work around this, we have designed programming languages (rust) that don't work if there's a possibility of it being corrupted (I would add "at least superficially", but that's not the main topic here). Bob was trained by the CIA in anti-brainwashing techniques. It's really hard to convince Bob to stab me. That's why it's such a big deal. We now have a way of delivering messages between two programs that is much safer than before.

The only problem is that the CIA anti-brainwashing techniques (rust) tend to make people slow. So we deliver messages less efficiently than before. Good news is in this case we managed to make Bob almost as fast as before, so we don't lose our own much while gaining additional security. The people who checked on Bob even made sure to have Bob do the exact same thing as before when delivering messages (using RB Trees), hence this evidence is most likely credible.

Can't comment much about the docker side since it's not something I'm familiar with.

For the kernel part, assuming what you're referring to as UUIDs is the pid namespace mechanism, I'm failing to see how that would add overhead with containers. The namespace lookups/permission checks are performed regardless of whether the process is in a container or not. There is no fast path for non-containerized processes. The worst overhead that this could add is probably one extra ptr chase in the namespace linked list.

Worked in IT, target disk mode is a life saver when you have to recover data from a laptop with a broken screen/keyboard/bad ribbon cable and don't want to take apart something held together by glue.

Reminds me of FFXI, where the devs considered Alt-Tabbing on PC cheating thus made it deliberately crash to desktop.