With context, this article is more interesting than the title might imply.
> The Sanitizer API is a proposed new browser API to bring a safe and easy-to-use capability to sanitize HTML into the web platform [and] is currently being incubated in the Sanitizer API WICG, with the goal of bringing this to the WHATWG.
Which would replace the need for sanitizing user-entered content with libraries like DOMPurify by having it built into the browser's API.
I've been using Choosy.app for easily managing different browsers for work and personal (and testing), and it works great. You set it to your default browser, and then anytime something opens a browser it pops up a picker. Lots of global and per-site configuration options like browser profile selection, private windows, etc.
Would you say more about your experience writing it in Rust? It worked well, what didn't, anywhere you found that you struggled unexpectedly or that was easier than you expected?
Even in the flood of terrible news about privacy and other things, this exposé stands out as especially disturbing. I was considering getting a new electric car to replace my combustion, but now I'm going to stretch it for as long as I can instead.
pry is what I miss most when using other languages. I've used all kinds of debuggers all kinds of hardware with many different languages, and pry is by far the best tool for development and debugging. People talk about the REPL in Lisp for good reason, but pry takes that concept to infinity and beyond. When I think about the future of AI assisted programming, it's something much more like the pry interactive development loop than a code editor's suggestions.
Reminds me of the story of the kids in Ethiopian village that were given tablets by One Laptop Per Child. The kids had figured out how to turn it on within minutes, in five days they were using 47 apps per child, in two weeks they were singing the English alphabet, and then within five months they had hacked Android. https://www.theregister.com/2012/11/01/kids_learn_hacking_an...
You do a great job explaining these concepts, better than most. I have appreciated all of your replies in this post. Do you have a blog or podcast or teach somewhere? I would tune in.
Has anyone found or made a great set of tutorials for "Affinity for Photoshop Experts"? I've been using Photoshop for more than 30 years (now Photopea), and I don't think I've ever felt more like an alien than the two times I've tried in earnest to learn Affinity tools. A six month trial could be generous enough for me assimilate.
Thanks for this link. Firefox has been getting worse for me stability-wise on my Mac M1, even with tab discarding it consumes huge amounts of power, and at least two or three times a day it will just stop loading webpages and show errors in the network tab and need to be restarted. I spend a couple of hours every few weeks trying to track down the issues and Firefox and even in the bug tracker can't find answers.
I also have a bizarre problem where any Chromium-based browser (Chrome, Brave, Edge) are extremely slow to load any page since upgrading to Sonoma, where Firefox or Safari are near-instant - like taking 60 seconds to even start DNS lookup. After a couple of minutes it will eventually fully load a page. I've seen other people mention the same issue online, but no fixes. I have spent hours trying to debug and track down problems for that too.
It's discouraging how much it feels like every software tool I use on every device has gone to shit, especially things as fundamental as a web browser.
I've also taught git to dozens of beginners in a classroom setting, and I have to agree that the OP and GP articles aren't great for beginners, even if they have a technical background. The problem I have with git media is that everybody begins by teaching git's user interface, which is a usability disaster. On the other hand, the internals of git are elegant and simple, and if you start by teaching from the inside out, it makes it far easier to understand why and when we use certain commands.
The video you mentioned, "Git For Ages 4 And Up" https://www.youtube.com/watch?v=3m7BgIvC-uQ, is the best resource for explaining how it works internally, once they have a rudimentary understanding of what git is and why we use it. Watching this video makes future explanations way more digestible. I still sometimes conceptualize difficult git operations in tinker toys.
I don't mind so much, I remember multi-hundred (or more) version upgrades, so it's better in some ways. I was just thinking about how I wish I had some way to manage all subscriptions in one place, it's so hard to keep track of.
It's not compiled, but Ruby's Pry REPL allows you to edit and update code files during live execution. I use it all the time for adding breakpoints and live fixing issues. It's very productive for problem solving.
> The Sanitizer API is a proposed new browser API to bring a safe and easy-to-use capability to sanitize HTML into the web platform [and] is currently being incubated in the Sanitizer API WICG, with the goal of bringing this to the WHATWG.
Which would replace the need for sanitizing user-entered content with libraries like DOMPurify by having it built into the browser's API.
The proposed specification has additional information: https://github.com/WICG/sanitizer-api/