No, the Edge PDF viewer has a much larger feature set than the Chrome viewer (although, I think sometimes for reasons I can't place PDFs opened with Edge do end up using the Chrome viewer instead of the Edge native viewer).
I gave my 2010 macbook pro to my parents when I got a new one in 2015. They still use it to surf the internet and sometimes for netflix before bedtime. Its battery is so swollen that the lid cannot close anymore.
I also bought apple care but never had any chance to use it. Very impressive for a computer without any hardware failure for 12 years.
Apple swore up and down that the bloated battery in my 2017 MBP was not a fire hazard. But I just paid $200 to replace it (plus tax!) even though their 'trade-in value' is about $250.
It feels lousy that they charge so much for the battery since this is a safety repair, and arguably caused by the fact that there were insufficient tolerances in the original build. This battery was put in circa 2019, when they replaced the keyboard/etc., so it's not even that old. I felt like I had a gun to my head since it could be a fire hazard.
exactly. that was the same for me, "what the heck is litespeed?!" was my reaction, then i noticed it's been there for a few years already.
and the fact that it's a drop-in replacement for apache config files is just mind-boggling. who in their sane mind would want to reproduce that complexity?
I heard its name frequently around the time before nginx came to its fame. Maybe 15 years ago. However, I never heard any major players use it after that.
I am also in the middle of moving off graphql to REST api. It is a 5 years old project and the graphql part was implemented with a very old spec. Since it has not been well maintained, it could not catch up with any features offered by graphql and users need to write their own queries by hand due to spec compatibility.
Rewriting it to REST allows us to "rebrand" these apis. At least, it does not scare our api users as the word "graphql" did.