Browsers only implement XSLT 1

https://meyerweb.com/eric/thoughts/2025/08/22/no-google-did-...

For a long time web components generally built on four standards:

  - Custom HTML elements
  - Shadow DOM
  - HTML imports
  - HTML templates

https://korban.net/posts/elm/2018-09-17-introduction-custom-...

Eventually it became clear some browsers were not going to implement and the design of HTML imports was better handled be ES modules.

https://webmasters.stackexchange.com/questions/127482/on-wha...

You can also get text from Gists by add .txt

https://gist.github.com/charliermarsh/ea9eab7f56b1b3d41e5196...

This is what the code does more or less.

On-device models seems like a good approach to this. Especially if it's silly projects they probably don't need the latest and greatest expensive models.

Firebase recently launch some experimental on-device APIs. https://firebase.blog/posts/2025/06/hybrid-inference-firebas...

> We’ve updated Add-on policies for addons.mozilla.org (AMO).

Their policy doesn't apply to your computer. Only to developers that want to use Mozilla's infrastructure for distribution.

There are artificial limitations to that. For example, stable versions of Firefox for Android won't install extensions from anywhere but Mozilla's infrastructure.

I find that limitation bizarre from an open source browser; it's the sort of behavior I'd expect from Apple.

I get why they do it; for better or worse, the browser is a major way many people interact with email, banking, etc. etc. A malicious extension would be a world of hurt. Some of that is moving to mobile, but with 5 billion people on the internet, Firefox's "low" market share at 4 or 5% is still over 200 million people, so it's still used by dozens or perhaps even hundreds of millions of people for these high-security tasks.

When I did IT support I've seen so many people do completely crazy things. I've seen people with 6 or 7 different browser toolbars and they use none of them. People with 3 different virus scanners they never remember installing, and of course ransomware they never recall installing either. etc. etc.

And honestly, can you really say you'd never click on the wrong "allow this untrusted extension" button when distracted, engaged in something else, tired, or whatnot?

I agree it can be annoying, but it's not impossible to maintain your private (signed) extensions. And for >99% of people, it's probably a sensible thing to do – this includes most tech people because most tech don't have a bunch of private extensions.

For everyone else, you can sign your own private extensions (some effort, but fairly minor) or use the Developer Edition, which allows installing unsigned extensions.

You can go to https://github.com/settings/installations and edit Jules permissions to be limited to a specific list of repos.

Gemini has some GitHub integrations

https://developers.google.com/gemini-code-assist/docs/review...

Have it write tests for everything and then you've got a well tested codebase.

Caveat empor, I've seen some LLMs mock the living hell out of everything, to the point of not testing much of anything. Something to be aware of.

I've seen too many human operators do that too. Definitely a problem to watch out for

You forgot the /s

You can change to archive size to 50GB per file.

Gah, thank you. The drop down is one of those terrible ones with no scroll bar and only three entries so I have to do the ol 'scroll wheel and hope' to discover more options.

Just... get the TGZ then?

For you and me, not a problem. My wife is a medical professional and would have no clue what to do with a TGZ file.

Also, the fact that they don't mention this difference- the UI is so poorly done that you can only tell that TGZ can go an order of magnitude larger after selecting it in one drop-down and then looking at the other drop down- is a sign of how Google wants to make this as difficult as possible.

Wikis are a git repo that you can clone.

https://docs.github.com/en/communities/documenting-your-proj...