I remember when these first started appearing in Windows was around the time toolbars became popular.
I think the idea was the most common ones had icons which matched the toolbar button so you could start with the slower-but-more-comprehensive menus and then notice the quicker toolbar equivalent through their matching icons.
If you use LINQ and have ever used areay Contains youre about to find out it's not going to be smooth. They knew about this for a year but decided coercing to span in an expression tree despite it being invalid wasn't worth fixing.
If you do this, you make the page slower to load for people blocking external fonts.
Not doing it is also nicer for people with slow/unreliable network access, where they can block fonts, or even if they don't block them, can access your page more quickly and have a render without the custom font.
Couldn't this increase FOUC? At least before you could load in your style-sheet before the font, but if you embed the font inside you get no styling at all until it can fetch all of the data, correct
I do get where you're coming from, but I don't agree. With the CF+S3 combo you now need to choose which sharing mode to work with S3 (there are several different ways you can link CF to S3). Then you have the wider configuration of CF to manage too. And that's before you account for any caching issues you might run into when debugging your site.
If you know what you're doing, as it sounds like you and I do, then all of this is very easy to get set up (but then aren't most things easy when you already know how? hehe). However we are talking about people who aren't comfortable with vanilla S3, so throwing another service into the mix isn't going to make things easier for them.
In my experience, the type of developer complaining about someone using JS is most of the time is some native C++/C/Rust (neck|grey)-beard. Most of the time they deflect it with "I don't support Chromium/Google" (they never elaborate why they don't contribute to Mozilla).
I wrote a LINQ provider (.Net) for Elasticsearch. Was quite the challenge dealing with the sorts of quirks and subtle differences between the two. Case sensitivity and the tokenization are also hurdles to overcome but mapping Group by to Elastics aggregates was facets back then) was the toughest part.
Hats off to Coralogix for taking up the challenge in converting SQL.
"The task bar, the Start menu, the system tray, "My Computer", "Network Neighbourhood", all that: all original, patented Microsoft designs. There was nothing like it before. "
Apart from, you know, NextStep which had a dock for system tray/start menu as well as my computer and network neighbourhood.
You can find screenshots of NextStep 3.3 showing this such as https://winworldpc.com/product/nextstep/3x from 1992 and it's possible they're also in earlier versions - NextStep 1.0 was released in 1989.
"NeXTStep had its Dock, but that doesn't have menus or a status icon."
NeXTStep not only had menus but tear-off dockable menus/sub-menus that are superior to any menus we have in apps today. It's clearly present in the screenshot I linked to.
https://youtu.be/rf5o5liZxnA?feature=shared&t=542 has a demonstration of NextStep 3 (released September 1992) that clearly shows a computer icon that Steve refers to as "My Computer" and then moves into hitting the "Network" icon globe that shows other computers on his local network.
I think the idea was the most common ones had icons which matched the toolbar button so you could start with the slower-but-more-comprehensive menus and then notice the quicker toolbar equivalent through their matching icons.