11–20 of 110 posts
Earlier quoted context omitted.
Noticeably faster than average on desktop. There's no silver bullet.
Setting a max-width on the body text would make this incredibly more readable on narrower viewports. At 636kb and 48 requests, this page probably isn't as "minimal" as you think it is. For example, should there be any reason you can read the disqus comments at a reasonable size but not the body of the post?
Earlier quoted context omitted.
Noticeably faster than average on desktop. There's no silver bullet.
Setting a max-width on the body text would make this incredibly more readable on narrower viewports. At 636kb and 48 requests, this page probably isn't as "minimal" as you think it is. For example, should there be any reason you can read the disqus comments at a reasonable size but not the body of the post?
Anyway, my experience is that touching Firefox's reader-mode icon in the address bar is usually faster than a boatload of formatting logic; produces more readability than a website's general optimization, and bypasses all the ancillary crap that people concerned enough to optimize for mobile tend to add.
Try type utf8Encoded.txt > out.txt in cmd.exe and posh. Cmd works and posh fs it up.
And after you do figure out utf8 encoding in posh, it'll always add a BOM just to screw you
I get perverse joy out of using the Windows CMD.EXE shell (and the earlier COMMAND.COM from MS-DOS). Yes, it's tremendously crufty, idiosyncratic, and sometimes seems down-right illogical in its behavior. Arguably, just about anything else is better, but it holds a special place in my heart.
Powershell is garbage. .Net does utf8 by default but powershell, built on .Net, manages not to. Try type utf8Encoded.txt > out.txt in cmd.exe and posh. Cmd works and posh fs it up. And after you do figure out utf8 encoding in posh, it'll always add a BOM just to screw you
[IO.File]::WriteAllLines($filename, $content)
(from https://stackoverflow.com/questions/5596982/using-powershell...)
Earlier quoted context omitted.
Setting a max-width on the body text would make this incredibly more readable on narrower viewports. At 636kb and 48 requests, this page probably isn't as "minimal" as you think it is. For example, should there be any reason you can read the disqus comments at a reasonable size but not the body of the post?
I tried it on mobile. It still loaded fast. As with many pages, Firefox Reader Mode improved the experience. Though for me, the bulk of the improvement comes from text formatting, part of the improvement is hiding blog comments, ads, email signups, etc. Anyway, my experience is that touching Firefox's reader-mode icon in the address bar is usually faster than a boatload of formatting logic; produces more readability…
I was trying to run a Bash script from a Git repo mounted in a Docker container. When running the Bash script, I kept getting all kinds of errors. I ran the exact same script in the same Docker container on a different Linux computer that had cloned the repo. It turns out the \r Windows line endings (which I later normalized in Git settings) caused my script to barf.
This isn't completely related to Windows command line but I thought I would post it out here. I was trying to run a Bash script from a Git repo mounted in a Docker container. When running the Bash script, I kept getting all kinds of errors. I ran the exact same script in the same Docker container on a different Linux computer that had cloned the repo. It turns out the \r Windows line endings (which I later normalized…