I never got into Sublime Merge because I tend to use the git integration with my IDE or editor. It does seem like a good approach for standalone git features though. I'd probably use it if I still...
I never got into Sublime Merge because I tend to use the git integration with my IDE or editor. It does seem like a good approach for standalone git features though. I'd probably use it if I still used Sublime Text as my editor of choice (I've since moved to VSCode).
Unrelated to content meta rant: This link highlights all that is wrong with modern web design, and a sign of the Webkit monoculture. On this site, the article gets cut off on the right side,...
Unrelated to content meta rant:
This link highlights all that is wrong with modern web design, and a sign of the Webkit monoculture. On this site, the article gets cut off on the right side, because the CSS makes the text div wider than my phone (Android/Firefox). But since it detects mobile, it also disables horizontal scrolling.
Toss it in Firefox Reader mode, everything works right, and I can use my own fonts and color scheme.
I hate that CSS, Javascript, and remote fonts are mandatory for almost everything and I can't self-theme easily anymore.
It's the same in Chrome on Android, and Safari on iOS, with the added bonus of an unnaturally large font size on the iPad, so this one looks like straightforward bad CSS. Interestingly, all three...
It's the same in Chrome on Android, and Safari on iOS, with the added bonus of an unnaturally large font size on the iPad, so this one looks like straightforward bad CSS. Interestingly, all three immediately suggest reader mode, which makes me think the browsers are detecting the overflow and offering a potential solution.
…Can you explain? I've had them universally disabled for years with no discernible downside. (Upsides include not exposing font parsing/rendering code—much of which was written in the '80s, was...
remote fonts are mandatory
…Can you explain? I've had them universally disabled for years with no discernible downside. (Upsides include not exposing font parsing/rendering code—much of which was written in the '80s, was never intended to accept arbitrary inputs, and is effectively untested—to anything the Internet wants to throw at it; preventing sites from choosing ugly or illegible fonts; and cutting out some stupidly massive downloads.) The closest thing to an "issue" is that it breaks the hell out of glyphicons, but I literally couldn't care less.
Of course I agree wholeheartedly with your general complaint.
This is my main problem. A lot of sites become very hard to navigate without them unless you already know what they are. There should be an alt-icon the way there is alt-text. It's part of the...
The closest thing to an "issue" is that it breaks the hell out of glyphicons
This is my main problem. A lot of sites become very hard to navigate without them unless you already know what they are.
There should be an alt-icon the way there is alt-text.
It's part of the larger problem which I didn't notice nearly as much before installing uMatrix and doing whitelist only.
Ah; I find that unlabeled icons are incomprehensible anyway, so I don't experience a usability difference between "incomprehensible pictogram" and "irrelevant letter". (Both are completely, 100%...
Ah; I find that unlabeled icons are incomprehensible anyway, so I don't experience a usability difference between "incomprehensible pictogram" and "irrelevant letter". (Both are completely, 100% unusable.) Some sites use ligatures on icon names, which serves the purpose of alt-text (and makes the missing-glyph experience much superior to just the icon).
You're not old and grumpy, it's just that you're part of a very small minority of users that bother to self-theme things or even take notice of the underlying tech behind the sites you use....
You're not old and grumpy, it's just that you're part of a very small minority of users that bother to self-theme things or even take notice of the underlying tech behind the sites you use.
Speaking as a web developer though, you have no idea how happy I am that we can use fonts these days. 10+ years ago we were completely locked to a handful of fonts that came default with Windows and macOS. Fonts are admittedly over and misused, but when someone knows what they're doing with typography it beats the pants off of being stuck with just Times and Arial. Not to mention being able to use fonts means we can use things like Font Awesome, allowing us to utilize saleable icons without having to mess with sprite maps or dozens of little gifs/pngs. Modern web dev is a mess sometimes, but you couldn't pay me enough to go back to the early 00s ways.
Opening it up in Firefox on my desktop and sticking it in responsive mode, I can see what you mean. I tried it in Chrome with the same effect, and while it was better, it wasn't perfect. The...
Opening it up in Firefox on my desktop and sticking it in responsive mode, I can see what you mean. I tried it in Chrome with the same effect, and while it was better, it wasn't perfect. The images were incredibly distorted and weird.
Honestly, I just think it isn't a well optimised website for phones.
I never got into Sublime Merge because I tend to use the git integration with my IDE or editor. It does seem like a good approach for standalone git features though. I'd probably use it if I still used Sublime Text as my editor of choice (I've since moved to VSCode).
Unrelated to content meta rant:
This link highlights all that is wrong with modern web design, and a sign of the Webkit monoculture. On this site, the article gets cut off on the right side, because the CSS makes the text div wider than my phone (Android/Firefox). But since it detects mobile, it also disables horizontal scrolling.
Toss it in Firefox Reader mode, everything works right, and I can use my own fonts and color scheme.
I hate that CSS, Javascript, and remote fonts are mandatory for almost everything and I can't self-theme easily anymore.
Guess I'm just getting old and grumpy.
It's the same in Chrome on Android, and Safari on iOS, with the added bonus of an unnaturally large font size on the iPad, so this one looks like straightforward bad CSS. Interestingly, all three immediately suggest reader mode, which makes me think the browsers are detecting the overflow and offering a potential solution.
…Can you explain? I've had them universally disabled for years with no discernible downside. (Upsides include not exposing font parsing/rendering code—much of which was written in the '80s, was never intended to accept arbitrary inputs, and is effectively untested—to anything the Internet wants to throw at it; preventing sites from choosing ugly or illegible fonts; and cutting out some stupidly massive downloads.) The closest thing to an "issue" is that it breaks the hell out of glyphicons, but I literally couldn't care less.
Of course I agree wholeheartedly with your general complaint.
This is my main problem. A lot of sites become very hard to navigate without them unless you already know what they are.
There should be an alt-icon the way there is alt-text.
It's part of the larger problem which I didn't notice nearly as much before installing uMatrix and doing whitelist only.
Ah; I find that unlabeled icons are incomprehensible anyway, so I don't experience a usability difference between "incomprehensible pictogram" and "irrelevant letter". (Both are completely, 100% unusable.) Some sites use ligatures on icon names, which serves the purpose of alt-text (and makes the missing-glyph experience much superior to just the icon).
You're not old and grumpy, it's just that you're part of a very small minority of users that bother to self-theme things or even take notice of the underlying tech behind the sites you use.
Speaking as a web developer though, you have no idea how happy I am that we can use fonts these days. 10+ years ago we were completely locked to a handful of fonts that came default with Windows and macOS. Fonts are admittedly over and misused, but when someone knows what they're doing with typography it beats the pants off of being stuck with just Times and Arial. Not to mention being able to use fonts means we can use things like Font Awesome, allowing us to utilize saleable icons without having to mess with sprite maps or dozens of little gifs/pngs. Modern web dev is a mess sometimes, but you couldn't pay me enough to go back to the early 00s ways.
I agree with you. Though I do think icon fonts are a poor solution versus SVGs.
Opening it up in Firefox on my desktop and sticking it in responsive mode, I can see what you mean. I tried it in Chrome with the same effect, and while it was better, it wasn't perfect. The images were incredibly distorted and weird.
Honestly, I just think it isn't a well optimised website for phones.