Whenever I had to use a laptop with a touch screen for work, I immediately turned it off. I have no idea what my use case would be as a coder, and it doesn’t seem like Apple has come up with anything new to give me a reason to try it again.
This entire thread is filled with people saying Wikipedia is doomed due to whatever minor problem personally bothers them, in this case apparently coverage of recent events quoting news organizations.
Nobody is actually showing us why the problem they choose to highlight is significant enough to torpedo Wikipedia altogether (or even that is a more important problem than all the others mentioned).
Also, nobody here is starting a long argument to waste people’s time. They’re simply saying “your one paragraph proclamation is completely unconvincing”.
I wonder if alcohol consumption plays a role here, since it is a known risk factor for Alzheimer’s. A taxi driver who works 60 hours a week will have very little time left over for drinking, whereas pilots have relatively short work hours where they actually need to be sober.
You don’t need to be a full blown acoholic to be affected, it’s simply a correlation of more alcohol consumption to faster decline of the brain. Having a job that requires you to be sober more hours of the week might bump you into a lower risk category.
I found Shopify’s post very easy to read, and learned about some features of MySQL. On the other hand, I didn’t get any value from reading your comment. You seem to have a bunch of opinions about how things should be done, but haven’t given any details about how you came to these conclusions.
I've done multiple large scale implementations with shopify paired with many flavors of order managmeent systems as well as competing offerings in the space. The only one i haven't touched that i'd like to get my feet wet with is commerce tools.
I really just disagreed with the assessment that redis is not good enough for the job for a reservation system. I use sql database all the time, I prefer them. But I'm seeing a claude written article here that seems to heel turn on a proven technology, it would at most be insightful if there was human content in here from actual engineers at shopify who want to vouch for and explain the challenges they were up against with redis rather than just expect me to take claudes word for it. Anyone who's been dabbling with AI knows damn well that you can convince claude to write up a dissertation on any hill you want to die on.
It’s unfortunate that the writing style wasn’t up to par, but I want to point out that I read the entire article and it doesn’t contain any criticisms of Redis. From the sounds of it, Redis worked perfectly and achieved what they wanted, which was beyond the capabilities of a simple MySQL implementation of the system.
In the end, they found a way to make it all work on MySQL, which solved some of the inherent complexity of using multiple databases side by side (but again this isn’t a criticism of Redis, the same problem would exist for any pair of databases).
I’ve had the same discussion with many people, and when I tell them how much work is done on cleaning up carbon emissions, the reply is always “well… it’s not enough”. And of course, they don’t have a sense of what is “enough”.
They don’t really understand it in a factual, measurable way, but just are interesting in what the overall story is, and what it says about humanity failing.
reply