err4nt

For disclosure, for my work I must use the stock version of all current browsers so I'm not a fanboy of any one particular browser, and I can't really use forks or ad-blockers.

I would bet any money that the reason why they chose Chromium, and did not choose Gecko, was performance-related. Blink is technologically superior to all the others. And between Blink, Webkit, and Gecko: Gecko is the worst-performing choice. I imagine if they did not fork Chromium, they would likely have forked Webkit instead.

You said, "You'll be gaslit into chasing down dead ends, distracted from actual issues."

When the ideal situation is that your Code-writing bot is attempting to gaslight your Project-management bot, and they go around in tireless circles, 24/7 arguing with each other, while their human masters are sleeping or not paying attention :)

I would have to beg my dad to use his credit card to make an online purchase, even if I had the cash equivalent in my hand to give to him right then!

If I new kids would be using any device I would make sure it had no payment information accessible. Which may mean the inconvenience of adding and removing payment information before and after making purchases. I can't imagine letting a child have access to a device which can spend your money, it's essentially like letting them hold your wallet, and we probably wouldn't trust them to do that if they were in an arcade, or theatre, or shopping mall, etc.

WordPress can emit statically-hostable websites, though you may lose that site-searching functionality. It would be possible for those who work on the site to log into a running WordPress install, to write and manage their content in the dashboard, but for that to inform and redeploy a static site. It's not a requirement that the place where the Wordpress-powered site is hosted to also be running PHP and the WordPress app on that server.

CSS is designed to be very fast, and because of that design choice it's less expressive. XPath is not going to beat CSS in speed, but it allows you to move through the document in any direction (up and down in the DOM tree of elements, forward/back among siblings in the DOM tree, and forward and backward in document appearance order).

We use XPath at work from CSS with custom plugins, and use XPath in JavaScript for targeting elements that otherwise wouldn't be straightforward to select with CSS.

Another cool thing XPath does is have awareness of the text content of elements! //li[contains(.,"example")] would target all <li> elements with text content containing "example".

Just as an example of how simple it could be - a WordPress install would get them an easy way to manage content on a website with different users and publishing permissions (so it can integrate into their human organization in a useful way) and should work not only to display information on the website, but to provide a search on that site, and you get things like RSS feeds for free. Hosting WordPress isn't free, but it is relatively straightforward and affordable.

Not saying that WordPress is the best solution, but I think over 45% of websites online use it, so toss a coin and it's probably a WordPress site. It should be very easy to find people who are familiar with it or can help work on it if that's ever needed.

A solution like that is small and simple enough for even a municipal government, but scalable enough that it could work for a national, or even international level organization too. I think something like this would be a prudent way to publish important information online.

And is invalid HTML. You can invent any attribute so long as it begins with 'data-', or you can define custom HTML elements with whatever custom attributes you want, but you aren't allowed to invent non-standard attributes for standard elements.

This is a strawman: I didn't say a word about free software.

There's a saying: You'll never get rich harvesting in someone else's garden. It's not just Google Analytics, all Google products can be killed off at Google's whim any time, and it's not just google. That's why it's so important to work with tools you could own.

There are a lot of problems where people struggle to simply put the problem into meaningful terms, so they can think about it.

If you deal with the same problem space a lot, having a Domain-Specific Language (DSL) can let you execute that vocabulary and work at the level of the terms that fit the problem space best.

This is a lot smaller in scope than designing a whole programming language, think of it like a unique vocabulary for solving specific problems and automating specific kinds of work you do!

I'm not sure, I used to use Linux as a daily OS and lately have just been using it on servers. But taking a look at it with ideas of using it as a desktop OS again it seems to be healthy and in good shape like it was 20 years ago!

The 'replacement' of Reddit may not look in appearance much like Reddit at all. Communities can center around anything. Just the other day I found a 'proudly anti-fascist' linux distribution with a community of ideologically-aligned friends all having a community around a linux distribution. Others I know have found deep friendships after initially meeting over music groups and going to concerts together. Rather than one mega-forum with many smaller forums, you may find interest-based communities all over the place!

This touches on something, the same reason that "I'm sorry" apologies should not be written by chatbots - for some things it's most important that a human being did something, more than what they did.

When a big mistake has happened and you need to apologize, it had better be coming from you yourself. If you think you can improve it by delegating it to a fancy autocorrect software, you're missing the point of why we apologize. Or if you think a bot is more 'empathetic' than a human paying attention, you've lost touch with what it means to be empathetic. A bot can't even feel, let alone feel your situation vicariously.

The hyperlink is the building block of the web - without links there is no web. Please just leave links alone. I don't particularly enjoy tracking any more than the next person, but don't automatically alter links people may be intentionally trying to access. I hope this is a feature that's disabled by default in the future even if it's offered for people to turn on and off any time.

Can you elaborate on why that would be the case? I ask because we've had some discussion about drafting an 'AI' policy with our CTO and though we haven't said anything officially, we are concerned about exfiltration of secrets, and the accuracy of information.

I do wonder if there will one day be communications formatters like what Prettier does for code, where no matter the style of writing going in, it will come out consistent. But until there are 'communications rewriters' to match a predefined company tone and style guide it seems like anyone's use of a tool like this would by ad-hoc.

What do you think the most sensible policy is to have right now, and why?

I rewrote this to be a little more succinct:

    document.querySelectorAll('body *').forEach(tag =>
      getComputedStyle(tag).position === 'fixed' && tag.remove()
    );

- you can use `forEach()` on the NodeList that `querySelectorAll()` returns

- you can use `remove()` directly on the DOM node you want to remove

Of all the things you could specify about the resource cost of a request, is carbon the most important, or only one?

Tailwind depends on @apply in PostCSS to function, something that was never officially proposed for CSS, but has been killed by its author and we know for sure CSS won't do, for the reasons the author of the original @apply idea lists here: https://www.xanthir.com/b4o00

So we have known all along that this will never happen. It was rejected for some very good reasons before Tailwind began.

I suffer the same problem and recently I've found those cheap $3 pocket-sized flip notebooks to be my solution, and so I have 1 in my office, 1 downstairs, 1 in the car and 1 in my coat pocket. I make sure to actually tear out old pages and throw them away so it's always fresh and nothing at all is permanent.

Biggest and best life change I've made in a while! Get some cheap notebooks and throw the pages away as you use them.

If you like Everett Fox, you may like Robert Alter's translations of the tanakh. He has translated the entire hebrew bible and given plenty of notes along the way. If you don't read hebrew, by the time you are done reading the translation and notes you will have seen or heard the hebrew language wordplay, and the english translation by itself is nice to read!

Unless people are forced against their will to attend school, and this institution specifically, and this course or class specifically, with no option to not attend school, to not attend this institution, to not take this course or class - isn't showing islamic art history in an islamic art history class precisely what all those present have chosen to pay to receive?

You can use oil - that works too!

That's a great description of them, a small convection oven. I already bought an air fryer before I realized/discovered that, and it's a wonderful thing. I know convection ovens exist, but I don't know if anyone I know has one, so air fryers (as tiny convection ovens) are a new capability. And a pretty awesome one too!

Why promote and illustrate a non-standard way, or even allow it at all?

I'll eat it! I was just telling my wife that when my dad was early in his career he had to install telecommunications lines in every office and factory and slaughterhouse and place of business you can imagine. After having seen the inside of slaughterhouses, my dad no longer ate hot dogs except from 1 brand only. So growing up whenever we had hot dogs, it was that one brand.

But now with veggie dogs, I don't have to worry about it being lips and tips and other trimmings swept up off the floor, whatever it is, and whatever it tastes like are clean and worry-free. So whether you like hot dogs or not, everybody ought to be able to get into some veggie dogs!

This is another project that teaches you to write non-standard, invalid code, with the hopes that a tool will come along and transform it into valid, standard code later.

And there's no need, because there are multiple ways in HTML they could already express this without violating HTML. Here are 2 ways that work, and then the way they've done it which is in violation:

Possible method 1: Data attributes. Any time you as an author want to add additional data to an element, you are free to invent any custom attribute names you want, so long as they begin with "data-".

Possible method 2: Custom elements. Any time you as an author want to add a custom element to HTML, you are free to invent any tag name so long as it follows a simple naming criteria (essentially [a-z]+-[a-z]+) and if you invent any custom element, you are allowed to define whatever attributes on it you like.

Invalid method chosen: To pollute standard elements with invalid attribute names in violation of the HTML standard.

I've always heard that "hurt people hurt people", and so most of the bullying behaviour that kids turn around and repeat to each other is something they've experienced for themselves elsewhere.

With modern HTML it's actually pretty easy to use markdown wherever you like. Though there is no built-in markdown element, they have built in the ability for authors to define custom elements. You can define your own custom <mark-down> element and put your mark down syntax inside and as it is, as source code it's nice and human readable even if we didn't do anything further. But we can also define how this element should render, and so it's very straightforward work to wire up any existing "markdown to HTML" library in JavaScript to consume the markdown contents of the tag and display rendered HTML.

This is so easy to do, not just for markdown, but almost anything you could want to embed or work with in HTML.

the ID's in DOM will never conflict or cause an issue with your own JS code. You can't reliably use 'named access on the window object' (the name of this feature) because of this, so it's never a problem, and also largely useless.

ID's aren't bad, they're unique identifiers, and useful for (deep) linking to specific pieces of content within documents. Please use ID's as liberally as you please, and use them for their proper use.