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

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

This is pretty much what the Kinesis advantage has out of the box, although 0 is moved to a thumb key. I like it with the non-staggered layout there but on a normal (laptop) keyboard it's not as good IMO.

Miryoku does the same thing but the orientation is flipped vertically with the 0 below the center column, which is how it’s done on a full sized keyboard as well.

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).

I’ve never really been a numpad user, but I like having 123 on the bottom row for more comfortable reach as they’re more frequently used for me

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, carriers have way more power in the US.

> 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.

If that was true, then Wal-Mart wouldn't bother carrying every pre-paid SIM under the sun in the same section of the store that sells shitbox Motorolas, nor would Amazon bother carrying the same exact Motorola shitboxen - all unlocked, mind you.

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.

Same thing here, I think this is really common and the “lack of evidence” as the article tries to frame it is just because it’s so obvious.

There is also a lack of peer reviewed studies showing that you can drown in water but that doesn’t mean it isn’t true.

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.

> 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.

My daily driver is the "irreparable" 2012 MBP Retina. You may remember this machine as the one everybody bitched about because the RAM and SSD were soldered into the mainboard and weren't upgradeable or replaceable?

Let's see, it's 2023, hmmmm, seems the machine is coming up on 11 years. IDK about you but I think 11 years is incredible longevity for a laptop. You know, it just might be that making the machine "irreparable" has been key to its longevity.

My 2013 MBP is a car wreck. Screen broke at some point had to be replaced. The second battery is now so bad it won’t even turn on anymore when plugged in. I think Bluetooth is dead too. All USB ports are dead too - although that one was “my“ fault since I plugged in a broken cd Rom drive that apparently nuked the USB ports - didn’t think that was even possible. When on, the thing often had the fans blowing at full speed… Im on like my fifth charger, they’re all frayed garbage. definitely not a fun experience at this point.

I guess if u keep a laptop stationary at your desk and plugged in at all times, then it could last 11 years. Although the very expensive 8gb of ram from back then is basically useless today.

> I guess if u keep a laptop stationary at your desk and plugged in at all times, then it could last 11 years.

I've taken my MBP everywhere, criss-crossing the United States. I've connected it to many different presentation devices where I've been a speaker at conferences. I've connected to many different networks - including hard-wired ethernet. Not exactly stationary and kept on a desk. I can't even remember how many times it's been dropped while in my backpack - from table top heights. I think it has taken quite a bit of abuse.

> Although the very expensive 8gb of ram from back then is basically useless today.

Yes it is - and it has nothing to do with being soldered into the motherboard. It's too slow for today. I'm not going to take that RAM and install it on an M2 machine, for example - too slow. Honestly, on this point you're just whining.

Obviously we're swapping anecdotes, but you'll see there's a lot of people still running the 2012 MBP Retina machines. Those things were tanks! The other machine that also appears to be a tank is the 2015 MBP. Lots of people are still running those machines too. Maybe Apple has "on" years and "off" years? Wouldn't surprise me as many other manufacturers do.

> I plugged in a broken cd Rom drive that apparently nuked the USB ports

While USB has resettable fuses and whatnot to protect itself, every protection circuit has its limits. There are even tools which can nuke the whole mainboards by charging capacitors and dumping all that energy to data lines.

> I guess if u keep a laptop stationary at your desk and plugged in at all times, then it could last 11 years.

Yes. Mine has seen quite a few countries and spent considerable amount of time trying to cool itself off while I'm developing my Ph.D. and try to get every bit of performance from its processor, all while using my first Mac's power adapter.

While I take care of my computer the best I can, it's not a "house PC" in any sense.

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.

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.

Hmm, how about naive VCs?

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.

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

FWIW, Nuxt 3 was released in November. https://nuxt.com/v3

> - Very poor typescript support.

If you use class components and prop decorators, the TS support is actually pretty nice. Kinda boilerplate heavy, but nice.

I've worked professionally in both Vue 2 and React. Even with class components and prop decorators you still have the annoying Vue template DSL where you don't get any TS support.

In comparison JSX will be checked by typescript, so in that regard JSX (and therefore React) is superior.

I really enjoyed using these tools, it felt idiomatic to have a class per component with props and data as fields on the class - but it seems like there's now no upgrade path for us folks in Vue 3 land.

I used those too, but it makes the upgrade to Vue 3 quite a bit harder.

Composition API has the best Typescript support available in Vue 2. It's supported out of the box in 2.7, and a plugin in previous versions. The decorator syntax is unsupported in Vue 3 and shouldn't be used.

- Nuxt only matter if you want to use it, is not Vues problem, because you talking about another software which addresses a different problem. - Typescript support is only a problem if you want to use Typescript, imagine, there is also a world beyond TS. - Performance, often a matter of design and understanding your framework

> 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.

Which is why I find looking at `git blame` (or one's favorite IDE's/SCM's equivalent) output so very useful in case of undercommented code.

In other words: poor documentation.