> I've had it happen twice with my Intel Macbook Pro from 2015 and now for the first time with my M1 Macbook Air from 2020
> They fixed the keyboard issue with the 16" Macbook Pro Intel series, which came out 4-5 years ago.
Fixed what keyboard issue? Clearly, GP is experiencing an issue across these generations. You can add my anecdata to that as well: intermittently cruchy/blocked keystrokes on my 2020 M1 MBA, exactly like my old ~2016-2018 MBPs.
Because adding brains and storage to hardware is expensive. And putting simple things on customer prem means less things can go horribly wrong.
And people actually like controlling their hardware from out-of-the-home, which makes doing everything locally even more complicated.
When you start trying to present end-users with a graph of whatever metric you want, you run into issues with storage, response time, CPU usage, storage, the web front-end, storage, etc. Then you have issues updating all that.
And if you want to do something like, say, comparing and benchmarking against other users you can't.
Really, only technical people care about this kind of stuff, and they can go ahead and write their own or use HA.
> Because adding brains and storage to hardware is expensive.
I disagree with this; it's expensive if you need the device to support Python or C# or similar. A $5 esp32 chip has enough storage and RAM to both act as a controller for hundreds of devices, AND run a minimal webserver to provide an interface for the user to automate those devices.
> And people actually like controlling their hardware from out-of-the-home, which makes doing everything locally even more complicated.
I second this: people who want home automation also want the ability to control it from their cellphone anywhere in the world. Unless they are technically proficient enough to setup their own public-facing server that is on 24x7, the customer is almost always going to prefer the device that is connected to a proprietary vendor's cloud.
The whole point of bringing countries like China into the world economic system is to make sure that they realize that aggressive action is counterproductive and they refrain from doing so.
Unfortunately that hasn't really worked with China, which is why the world is starting to decouple from China; the CPP still prioritizes its institutional needs over "The People", which is ironic since they're supposed to be working for "The People."
That's probably why the CPP is scared of the people and tries to control them.
The world is really decoupling with China because it is so unpredictable. Xi made himself forever leader only 10 years ago and it's been a unpredictable rollercoaster of policy since then.
Stability is the foundation of every working relationship. Everyone wants to latch onto you when you are stable. You can even work with an adversary as long as they are stable. China had it for a while before Xi.
Most countries have yet to achieve long-term stability. Stability is super difficult to achieve.
Authoritative leaders inherently cannot be predictable because one person has a lot of power and can easily make sweeping changes.
Even though any organization led by a large committee is absolutely terrible at making long-term, coherent decisions, it also means that everything moves at a snail's place and any outsider can react faster than the committee can, and decisions also never stray too far from a certain point because there are too many cooks in the kitchen. America in a nutshell.
Plus the forever leader thing only happened ~10 years ago. That's too recent. I would only ever call a country politically stable if it hasn't changed in like 100 years. The US, for better and worse, politically has barely changed in 250 years. Sucks for Americans (but not entirely) but great for the world. When Xi declared himself forever leader, that basically reset the clock back to 0 years. Plus once Xi goes out of power, that basically resets the clock again because new leader, new policy.
At the end of the day, when you have a lot of something you want to keep safe (like your business), you want to put it with the person whose situation hasn't changed in the longest time. You don't even care necessarily whether that person is good. You just want that stability.
Apple sells its products to its markets, and is mostly uninterested in the data center and embedded market. The support costs are large, and the margins are small-ish.
Which is too bad for the industry, but also lucky for the industry.
I mean, they were the first 64-bit ARM chip, period. In fact, everyone mocked it, but they also trembled in fear because 64-bit.
A friend of mine used to work on a product that was essentially a printer driver.
The problems include (1) QA, (2) reverse engineering the communication protocol, and (3) support.
#1 and #3 are chronic issues in the OSS world. They're also a problem because there are a ton of printers out there, and getting one to develop/test against eventually becomes an expense and space problem.
And, printers are cheap. There's no real financial incentive to do it.
As an aside, I talked to some guy at Chase years ago, and all he wanted was some way to manage all the printers Chase had. That was it. It was like his personal nightmare. It was literally an impossible task, especially since some unknown percentage of them were no longer manufacturer supported...and many didn't have a manufacturer anymore.
This is why financials want you to go all-digital - so they can dump these behemoth printers that cost a fortune to maintain.
That's a load of bullshit. With Z-Wave I have a pick of over 20-30 vendors. Z-Wave is just as open as Matter. It's just not controlled by Google and/or Apple.
You may have choice, but a vast proportion of the market aren’t even aware of it, and wouldn’t know where to buy it. They see, understand, and seek out the branding for the ecosystem that they use already.
This is unfortunate, as I like free and open as much as the next HN user, but it’s the nature of innovation and socio-technical ecosystems.
I suspect it's a combination of NIH and the big players wanting to control the certification process and chip supply.
Z-Wave has been working perfectly fine for years. There have been protocol upgrades, new hardware, a pretty large ecosystem, etc. Zigbee apparently suffers from interop problems.
The main reason I prefer mysql over PostgreSQL is that mysql is just more consistent - in its commands, quirks, etc.
Postgres - is it pg, pgsql, psql, postgres, postgresQL? The answer is "yes."
Plus the case behavior for tables and column names drives me crazy. It's like some leftover VMS shit. I mean seriously fix it. Can you or can you not use a capital letter for a table/column name? I can never remember. Or you can, but you have to quote it? Fuck.
Until recently (which to be fair might be 8-10 years ago) postgres' performance monitoring tools sucked compared to mysql. I know at one point in the last 10 years they still used sunos4 as their base configuration because you know, the OS had been EOL for like a decade at that point.
MySQL is fire and forget. psql (or postgres or pg or postgresql?) is not fire and forget. It's twitchy and requires constant vigilance. I don't want a piece of infrastructure that requires constant vigilance.
That's not to say I won't use it. It's geo stuff is really great. It's JSON support is better than MongoDB's, from what I've heard. Row level security is awesome. But are those features good enough to overcome psql's quirks? Sometimes.
> at one point in the last 10 years they still used sunos4 as their base configuration because you know,
What exactly do you mean with this? I tried to find some more information, and all I could find were some fixes from 2001[1] (SunOS 4 was supported until 2003), a minor refactor in 2008 with "SunOS 4 is probably broken anyway"[2], and that's pretty much it. SunOS 4 was moved to "Unsupported Platforms" with the release of 7.3, in 2002.[3]
If you’re talking about the command line client that’s built in, it’s psql. If you can’t remember the command name to launch it or regularly type those other commands when you meant to type psql, you could add aliases to your shell that point to psql. :)
Learning any new CLI client is a bit daunting at first. With repetition and intention, I think the commands become very memorable. Eg “describe table” is “dt”.
