My gf has a migraine head and she’s tried going decaf but it just doesn’t work. Apparently caffeine does a lot to reduce the risk of migraines? So I’d probably just try to lower the dose until you find what works for you.
I went to the US recently and was fully prepared to drink caffeine on the trip because of all the cool coffee shops and roasters. But I was amazed that decaf was basically a first-class citizen there. The hotel breakfast had one giant brewer for regular and the same giant brewer for decaf. It was amazing.
And it’s pretty important to realize that well-made decaf doesn’t have to taste worse than regular coffee. James Hoffmanns decaf project proved this for me, and his video about decaf sold me on the idea: decaf drinkers are the OG coffee drinker, drinking it purely for the taste, even without the drug-induced high that caffeine gives you.
I’ve switched to decaf full time and a my generalised anxiety basically went away. I love coffee and still drink it ritualistically. I probably drink more coffee now, at all hours of the day (caffeinated coffee after 12 really messed my sleep).
Also once per week I allow myself an espresso, and I get a nice buzz from it that lasts the entire day.
My (swedish) grandfather keeps falling for these Meta scams. Scrolling through his feed is insane and disgusting. So many ads that mimick OS alerts saying storage is low, insane amounts of AI crap and fake products. I 100% agree with this. Try scrolling through your grandparents’ Instagram or Facebook and see for yourself. It’s obviously _very_ easy for Meta to filter out these scams, but they choose not to.
Is this still a thing in Swift? I loved Swift 1, spent a couple of days upgrading to Swift 2, a week or more for Swift 3. At that point I just switched to React Native. I understand that iterating is generally a good thing, but the constant cykle breaking changes in the language was just too much.
I don’t remember the onboarding (ironically :) but once you get in the UX is really nice and perfect for what it does. Maybe it won’t win Apple design awards, but I’m just here for the content.
As the owner of an RSS reader I love that they are making this more public. 30% of our support requests are ”my feed doesn’t” work. It sucks that the only thing we can say is ”contact the site owner, it’s their firewall”. And to be fair it’s not only Cloudflare, so many different firewall setups cause issues. It’s ironic that a public API endpoint meant for bots is blocked for being a bot.
He got me started down the rabbit hole. Now I have a cheese cave, homemade cheese press and a fridge full of cultures. Still haven’t mastered mozarella though…
I'm pretty sure (there isn't a lot of info on how to enable it in production workloads) we're running YJIT in production and didn't notice any improvement in load times, CPU usage or anything really. If any slightly higher metrics across the board.
We're using Rails as API and web frontend with a pretty high number of requests per second, so I was hoping we'd see something. Does anyone have any experience rolling it out?
As someone working on a massive migration from MV2 to MV3 (where the benefit to the user will be minimal) it does feel like browser makers are waging war against us extension developers. Mozilla's plan is to release a slightly compatible API, but not at all compatible, and yet highly limit what can be done? Do they really think this will increase the effort invested in their ecosystem?