Oddskar

Seconded! I think it's a much better read than "Design of Everyday things".

He was clearly a super experienced practitioner. If only the Apple of today actually did good UX again instead of catering to the whims of some "design genius"

It's poorly explained in the game, but you can increase the amount of machine health by researching "Improvements". One also has to keep track of the machine strength which is only visible in the bottom right corner when hovering over the machine. It will deteriorate over time, and at some points the machines will have to be replaced.

It's the original TH.

Epidemics is a pretty bad gameplay system. Especially considering patients going between buildings automatically fails it; which makes it almost completely broken. On some maps buying some particular buildings is a complete foot-gun due to this.

I randomly started playing through Theme Hospital, and I'm now almost at the last level.

I must say: in general it hasn't held up very well. There are so many mechanics that are extremely poorly explained that are fundamental to the game. E.g. epidemics and earthquake/machine strength. Trying to micromanage all of the gameplay systems that are quite annoying to begin with doesn't end up being .. fun.

As a child I'm sure I liked it because it was goofy and approachable, but playing through it now I doubt I ever got through the levels where managing epidemics is important.

Sure they spent it on Norwegian people, but at the same time they're still enabling an unsustainable way of life for the rest of Europe. E.g. the gas and oil-dependence of Germany.

The real interesting part about Clippy is not the cartoony art, but the fact that it actually would have been helpful if the project managers of office would not have gutted it: http://erichorvitz.com/lum.htm

So you're surrounded by rich people, and thus my reasons don't seem to apply? OK.

I like Apple. I'm find this new release quite cool. But you fanboys are a bit much. Sigh.. guess I'm going to do this.

> Who doesn’t like macos? Like it is objectively better than windows, and is able to actually work decently without set up pain (like linux)

Not really objectively better any more, no. With WSL2 developing on Windows is actually pretty darn great. It's the best of both worlds: first party support of most applications and devices that I care about, and a really good OS for development.

> Who doesn’t like the hardware?

Overall Macbooks are almost unbeatable with e.g. the screens or sound for instance. But I still find the port selection to be baffling. It's been many, many years since the release of USB-C and I still need USB-A ports.

I also really do not like the sharp edges on the new Macbooks. They're visually appealing, sure. But if I'm on a train and they're cutting into my wrists it's not great.

> What is unrepairable about macbooks? It’s not an iphone, i ve replaced hard drives, fans and other components on a macbook countless times.

Aha, please try "replacing your hard drive" in your new Macbook.

Also the attitude and track record of Apples behavior towards repair shops is abysmal.

> Who really wants an upgradable laptop? I’d give you desktop perhaps, but with laptops i struggle to see the usecase

You just said you have "replaced hard drives, fans and other components on a macbook countless times" so I struggle a bit with this one.

In general it's a good idea to make devices last longer. Y'know, with the planet being almost being on fire since we're over-consuming? No?

Writing emails and compiling documents in Word seems like very "professional use-cases" to me.

It takes a lot of time for people to warm up to a new device type. Probably makes sense to get a premium version out to make people yearn for it and build an ecosystem, and then create a more palatable version for mainstream use.

Do you really need me to spell it out for you?

  * Can't afford it
  * Don't like MacOS
  * Don't like the hardware
  * Want a repairable device
  * Want a upgradeable device

Etc, etc. Plenty of reasons.

> People said the M1 Pros were overpriced

Yeah but most people aren't paying for those: their employers are.

I don't think many employers are going to buy such an expensive tool.

How petty are you as a person if you disregard your peers and screw someone over just because you're "uncomfortable" with a technical article?

Can we just stop with this intolerance of differing opinions? It's OK to disagree with someone. We don't need to all share the same opinions. Why the fuck would you have a conference if not to inject some healthy discourse in your community?

I didn’t hear anything “wrong” at all. I know people personally which make a lot more than that. If you did R&D for 80k in a senior role you got robbed.

This is not the case in Europe from what I’ve heard. SW devs with the right domain knowledge in cars get very well compensated.

Super weird. Almost like not having ruthless a-holes as the CEO makes a difference.

Miryoku basically has the numpad, which I still think is dumb to be quite frank since the numpad was only made like this for archaic historical reasons.

Having the 0 on the thumb is quite a good choice though. As long as one doesn't have to move outside +-1 of the home row of keys (like one has to with numpad).

The first thing I changed in my custom layout was to get rid of the number row.

Having all the numbers as a toggleable numpad (but not really numpad because numpad is archaic and dumb) under the left hand has been so good. I'm never going back.

I use this layout:

    1 2 3
  0 4 5 6
    7 8 9

As someone who works in e-commerce related to phones, I think a big part of the answer is that the US is not a big market when it comes to selling phones without a contract.

In the EU it's common practice to buy without a contract, whereas this is very rare in the US.

In other words, it's the carriers that dictate what gets sold.

Of course anecdotal evidence, but I solved the recurring inflammation issues I had by having a routine that includes flossing an interdental brushes.

At a certain point you know where your "problem areas" are and where food tend to get stuck.

I regret many things in my life.

But quitting multiple times from jobs that I did not enjoy is not one of them. Even though some of the times I didn't have something lined up immediately. The only regret is not leaving sooner.

I will take your word for it, obviously your experience is the same for all of the Macbooks of that generation which are still being used today.

> They tend to not sacrifice longevity over flashy technologies.

Hah! That gave me a good chuckle.

There's nothing that screams "longevity" as going out of your way to make all devices utterly irreparable.

You have to ask yourself "why did it pay very well?"

For every person who made money on crypto there was someone that lost as well.

As someone working in a large Vue 2 app:

- Very poor typescript support.

- Poor performance (compared to Vue 3).

- Ecosystem has already started lagging behind (e.g. Vue Testing Library for v2 has out of date dependencies, and no one is actively maintaining it)

- Nuxt 2 hasn't made any releases in ages.

> Comments can have a scope that's way too close to the code, rendering them very volatile and oftentimes neglected.

I think this is a well put and nuanced insight. Thank you.

This is really what the dev community should be discussing; the "type" of comments and docs to add and the shape thereof. Not a poorly informed endless debate whether it should be there in the first place.

> It’s really hard to keep comments up to date as code is moved and refactored.

Hard disagree with this.

If your comment is so volatile then that really sounds like there's something architecturally wrong with the code.

Most of the time these kind of "comments" can be turned into either a test, or a extensive description that goes into version control.

Because commit messages are just that: a comment for a specific moment in time. There are lots of options to inline comments.

In other words: poor documentation.

In most cases, even though there's verbose variable names you still can't understand the why just by reading the code. And even if you did, why would one want to?

Most often I'm just skimming through, and actual descriptions are much better than having to read the code itself.

This whole notion of "documentation can get out of sync with the code, so it's better not to write it at all" is so nonsensical.

Why isn't the solution simply: "lets update the docs when we update the code". Is this so unfathomably hard to do?

In the US, maybe. Not so much in Europe.