From what I gathered from (part of) the video, it's not about the HTML, it's the copy. Basically Google is accidentally/intentionally optimizing for copy that sounds like it came from an LLM or a LinkedIn lunatics post.
I'm skeptical but I don't have time to watch the entire video so I don't want to cast an initial judgement on if he's correct or if it just has to do with his specific copy.
i think you got the gist of it. the whole video doesn't really add any evidence as to how he came to that conclusion, it's mostly about why it's bad and how he feels about it.
I wasn't forced to adopt tho, these shortcuts go back to when Windows had chunky borders in XP/7. It was just something that a lot of Linux WMs did and it's incredibly useful so I found ways to do the equivalent on all operating systems.
Also KDE seems pretty staunchly _against_ client-side decorations with buttons other than the window manager buttons.
Very quickly mise went from "what's that?" to "I need it everywhere" because of the "overlay on existing systems" approach. It's all over our org at work, and all over the local dev community here. It has also simplified all of our CI and made the random python projects a breeze to run. Great work!
Ironically I pushed for it because it also has tasks that can be written in Bash (we have a mix of Bash scripts and Makefiles for task running across projects while I will die on the hill that shell scripts should be written in a shell script: not Makefile, not a string in a json file, not a string in a yaml file) but we never did get around to that.
it was definitely a risky move, env vars are not perfect for this use-case (varargs is awkward) but I'm happy I went with the file tasks setup and the magic comments anyways. It's nice that you're not working in bash-inside-yaml or coming up with a new file type. It is just bash.
Agreed, and thank you. Every editor I personally use knows how to edit, highlight, and language server shell scripts. Zero of them, AFAICT, know how to do any of that with a shell script embedded in YAML.
Not to mention the article's menu "close" button relies on JS to send you back to the correct page, and doesn't work with open in new tab / window even with JS enabled.
Almost happened to me once, but instead of threatening legal action the company asked for a couple of features, sent me free hardware, and a next-gen board that made my software redundant.
(I get that web vitals might be taken into account, but you don't need a slop generator to make a static page)
reply