This actually sounds like a major downgrade. Before you were given a list of options and were able to make an intelligent choice that worked best for you. Now you're given no option and the choice it made didn't work for you as it wasted your time.

So the original article overstates what Diamond means for the comic industry. Marvel, DC, Image, Boom, and more have moved from Diamond to either Lunar or Penguin Random House for their primary distribution and Diamond a secondary distributor, with DC going as far as not even being possible as a back-up.

I am more worried about bags and boards as Diamond was the best quality/price for bags and boards. Competition does exist for that as well but that is the part that will hurt fandom the most.

I'm someone that does a lot of runs/triathlons, but I also do a lot of lifting and other things. I have been team Fitbit for quite a while and own a Sense 2. I was always annoyed at the fact then tended to last about 15 months at best and my last Fitbit died because it got water logged. My friend had been suggesting I try a Garmin so I hit Mercari and picked up a cheap Forerunner 935 (a 2017 model!) for about $100. I've gotta say it kicks Fitbit's butt in most cases. I've been wearing them both just to see how they do (and confuses some people that I'm wearing two watches).

• Better battery life. Days better.
• Ability to track sets when lifting (and seems to be pretty good at figuring out what I was doing, though it seems to think lat pulldowns are bench presses for some reason.
• More accurate run tracking.
• Far more workout options.
• Great metrics listed even WITHOUT a subscription -- I assume they have something but I'm not using it.

Some negatives though I've seen.

• It seems to be waaaaaaayyy off for swim tracking in the pool. I know that I am a bad swimmer and I could have a stroke that does more arm movements than I should so that could be me.
• I do miss Fitbit's ability to tell me to move each hour. Supposed to be an option in Garmin but it's never done it for me.
• Audio when running only lists the current mile time, not total time.
• The steps on the watch update every 30-seconds-ish rather than real time when just casually walking (not in a tracked walk). Helps with battery life some.
• Seems to skip a few steps on short walks -- like moving from a chair to a sofa in a room it might skip where a Fitbit will catch those 5-ish steps.

Overall I'm enjoying the Garmin more. I am definitely going to be on team Garmin going forward.

For those unaware, the data-savings Lite Mode was what Google called their version of the tech that rendered things on their servers and then sent a compressed binary to the user -- the same thing that done by Opera Mini.

It does not sound like this has anything to do with the Save-Data HTTP header that browsers can send to servers to provide them a hint if the user would like a reduced version of the site.

So I wonder what this means for services which cannot legally delete your records. Right off the bat I am sure that medical apps have legal requirements that prevent this. I know in the US that my industry (online training) is not allowed to delete training records for up to 7 years so we have made it a policy to never delete anything.

The point of mentioning version 0 is because every major browser that is working on Shadow DOM is developing towards version 1. The v0 implementation was more experimental that made its way out there because Google doesn't always go through the proper standards practice. Version 1 is actually going through the normal standardization process. Firefox and Safari have the version 1 code in development, while Edge has it marked as a high priority consideration.

To be clear, Chrome deprecated v0 in April 2018 and will remove in 2019. If Google does nothing than Chrome will slow down on YouTube as it will have the same issues Firefox and Edge currently are feeling.

Vivaldi is not an open source fork of the old Opera code base. That code base was proprietary. It is blink based. The confusion is that it was founded by the former Opera co-founder/CEO, and aimed to restore features Opera lost when they moved to Blink. It's more a fork in the Opera consumer base and is not a fork of the code base.

I know it's easy to simply cut and paste from the original article (heck, it's one way to get people to actually read part of the article), but why not make corrections to gross errors?

Apple is not supporting WebRTC and has not implemented any of the features necessary for it. Not in desktop nor in mobile.

Or he could be the type that needs to worry about low powered mobile devices (like the type that Firefox OS initially targeted). Those devices would choke HARD trying to load jQuery.

Don't get me wrong, I definitely see the value in jQuery since it even fixes bugs in modern browsers. But lets not assume that just because someone is shying away from it that they are some newb that doesn't know better.

If I am writing a few line script for something then yes, I will spend the extra few minutes to first try to avoid using jQuery when I can. Adding a 100 kb (just guessing, I have not checked it lately) JavaScript library so that I can write what I want in 10 lines of jQuery rather than 60-100 lines of vanilla JavaScript just doesn't seem reasonable in my eyes.

Minor correction -- no version of IE (or Safari if we want to be technical) on Windows XP supports SNI. IE7 on Vista supports SNI, but not on XP. Also, Android 2.x is still pretty relevant given that it currently represents 9.6% of active Android users. The original Kindle Fire did not support SNI, though I believe with the second generation it did support SNI. Anyone with a pre-BB10 Blackberry also does not have SNI support.

Trust me, I would love to go SNI-based for SSL, but support wise we're just not there yet.

This is not supported by Firefox because it violates the CSS spec Basically, replaced elements (img, video, iframe, etc) cannot be modified via the content property because they eliminate any ability to replace them with accessible content. For example, an image cannot be replaced by its alt text.

I assume the parent was referring to IE's use of pointer events instead of the touch events. While many may accuse Microsoft of trying to split the web, this move was most likely done for two reasons.

1. Apple has been working to patent touch events
2. The ability to simplify event handling with one type of event that is input method independent -- working for mouse, touch, and pen.

As a web developer I find the pointer event method to be technically superior to touch events. At present, patches to add pointer events to Blink-based browsers (the patch might have been added before the split from WebKit) and to Firefox exist, but I do not believe they have yet landed in other browsers. Sadly, with the lack of touch events it does bloat up code to support two different event models for touch browsers at this time.

Then I guess it's a good thing that IE8+ actually lets you specify which version of IE (from 7 on up) to display a website (though it is harder in IE11). Microsoft learned from the backlash they received for breaking intranets when they released IE7 so this really should not be an issue for anyone anymore.

You can install Firefox on Android. The Firefox OS Marketplace can be accessed from said Firefox. You can install apps on there and and it will load the app using Firefox. This is the same rendering engine -- the same HTML5 app -- using the same everything from Firefox OS.

When the standard has not been fully defined and is not working in any current browser, yes, I'm all for pushing the bar of HTML5. I actually bought one of the Firefox OS developer phones. It's great for those of us who want to experiment, but I wouldn't make a big case if browsers working on experimental features have bugs in them. Heck, I wasn't aware that srcset had even gotten to an experimental implementation stage yet. No one else has implemented it. Kudos to Samsung for starting on it.