As a side note, I absolutely cannot imagine being upset of having a machine lasting long.
Sure it's nice the shiny new thing but has capitalism infiltrated people's mind that much? All my previous laptops died on me several times and became frankestein's monsters before I let them rest for a final time (to be often repurposed to other family/friends' machines).
With intermittent use one may get a lot more life out of the SSD than other users, but eventually flash will run out of spare-sectors and start to fail.
Most M1 systems I saw use on-board BGA110 NAND flash, and thus maintenance/upgrades on the SSD are difficult. Most users don't have a hot air rework station or x-ray inspection machines to do this modification correctly.
The SSD don't last forever, after about 3 to 4 years of daily use the drive/system should be replaced. At >5 years, one could hit retention issues and corruption losses.
Good excuse to upgrade though, as a $1500 recovery bill would not be cool. Best regards =3
I removed my anecdote and flash wear explanation, because of cranky folks like yourself.
The corrosion inhibitors in petrol engine oil get fully depleted within about a year with most brands. One may certainly sell the machine before you see acidified lubricant related problems, but the motor will not reach its full operational lifespan ( https://en.wikipedia.org/wiki/Bathtub_curve .)
I do agree that anyone with a CVT style transmission likely won't have to worry, as that entire section will probably need replaced before you see significant hydrodynamic bearing damage.
The OP's comment to the post is clearly Markdown-formatted, real humans don't write like that on HN.
The readme is very obviously Claude-written (or a similar model - certainly not GPT), if you check enough vibecoded projects you'll easily spot those readmes.
The style of the HTML page, as noted by others.
Useless comments in the source code, which humans also do, but LLMs do more often:
I did not. The html was generated by Deepseek. Claude is far way too expensive for that. This is only an experimental code. I don't think it is worth to pay Claude to test a code which was already peer reviewed theoretically.
The readme is outright slop, the HTML chart has the classic "tailwind dark theme" layout that models default to absent specific instructions, many of the comments in the code are classic AI.
No, Discord/Slack is a mess. Interesting topics got buried in an IRC-style chat. Threaded BBS are much better for organizing communities, like Discourse. And it is open source, so no vendor lock-in with stupid age verification.
This doesn't feel like a real question... Slack free tier is basically crappy Discord, limited message history, no voice channels, huddles are also behind the paying tiers. It is basically worse on all aspects unless you start paying
Most importantly, Slack limits the amount of message history you get to keep if you’re not paying. And the payment plans are per-user fees which quickly becomes non-viable for non-commercial use.
A nonprofit I help out just moved from Slack to Discord for a very simple reason: Slack pricing was too expensive, and as the amount of people increased, the price continues to climb. Discord is free
The biggest one for me is that Discord will keep all history for free servers, whereas Slack only gives you access to 3 months iirc (and as of a year or two ago, has started permanently deleting older content).
For large communities, the very granular role-based permission system of Discord can be put to some good use, I don't think Slack has a trivially equivalent feature.
I also value end user freedom, but I also accept reality. And I guarantee you you have compromised on your freedom/anonymity for convenience online. We all have. And ultimately discord is so turnkey that most people just don’t care
There is no binary version of how everyone is compromised. Because I refuse a bunch of applications like Discord I can assure you my footprint is lesser than those who use it.
I agree completely. My point is that people simply will do that though, so instead of approaching it with hostility and judgment you should approach it with understanding and, if they’re willing to hear it, maybe as an opportunity to educate. Proud proclamations and judgment won’t get people to see how important this is.
It’s not just “window dressing.” UX matters. So you need to talk to people in a way that acknowledges why they want those conveniences in the first place. It’s the same reason I recommend Plex to some people and Jellyfin to others.
I'm in a Signal chat for a bar trivia group for some reason. I've missed invitations a few times cause it silently got out of date. But at least Obama can't read my messages.
You compromised your freedom, then. Signal is a central–server network with a license that means you can't legally modify the client and use it on the network, and it identifies people by their phone numbers.
Obviously Microsoft felt bad when they had to kill the old Edge browser that was based on their own HTML rendering engine. Must feel like a second-rate tech company when you can't write some code to render HTML with sufficient quality.
Now they can get back in the game with a 3-word prompt!
And then every time there's some change to web standards, it's just one more prompt where you say "Hey Copilot, take a look at this page that describes the change, and update our browser code to add this!"
For example:
pick a number between 1 - 10000
> I’ll go with 7,284.
reply