err4nt

Like humans, they have physical bodies and the breath of life in them. For the sake of what this person was talking about it seems like it would apply to their intelligence as well.

This is kind of where I've been thinking lately. If I can speak of human bodies like computer hardware, there is a physical limit to our hardware and how much data it can process, and yet intelligence seems to be something beyond the hardware. Something that the living 'you' brings to your hardware.

My wikipedia editing experience was similar, crazy to think that it was almost 20 years ago. Me and some friends contributed our honest-best to some articles relating to language dialects we spoke, and minerals we liked - the stuff we could nerd out about a tiny bit more than whatever was on Wikipedia at the time, and so we added our paragraphs. In all cases the changes were reverted, and we actually made an enemy with a wikipedia editor who if I recall was an army vet and science teacher, and personally 'babysat' the articles about minerals, and would allow no changes to his articles.

I think it would be cool if there was something that saved all contributions, even deleted ones, and made it easy to explore all of them. I know Wikipedia has a diff history but that's not the right interface to bring all that to the surface.

Looking forward to the next collaborative scrapbook to start up so I can participate in good faith and have some good fun :D

Anecdote: Jalapenos really bother me, but I love them. I don't know what it is about them, but they give me days of problems when I eat more than a couple bites.

I can eat much spicier capsicum peppers than Jalapenos, and fresno peppers seem to give me no problems at all (which are the nearest cousin I've found to Jalapenos).

Does anyone know what I can do? Does my body's reaction to Jalapenos have to do with how ripe they are (green vs. red?), or is there any other reason or explanation by Jalapenos bother me but other peppers dont?

Do not use Prettier with HTML. We can't use Prettier at work because it doesn't reformat HTML but actually rewrites it, taking liberties to insert new closing tags where it sees fit and where they were never present before. We found this because it actually led to things breaking in practice. A code formatter should never add meaningful new code to your project which changes its behaviour and content. That's no longer a code formatter but a random bug generator.

Further size reduction, you don't need the `this.` on the inline event listener, so it can be: `contentWindow.location.hash` and `contentDocument.body.childNodes` instead of `this.contentWindow.location.hash` or `this.contentDocument.body.childNodes`.

This will shave another 10 bytes off the snippet :D

This exists, you can specify containers and then use 100cqw container query length percentage units https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_contain...

They're called "none" because that's how they categorize their religion: "none", when surveyed. This has been a group that has been watched and talked about this way for at least a decade, the "nones" have been growing.

Human sacrifice is still a part of many societies today, especially the West who fights for it. Today it's performed by different people for different reasons than the Aztecs, but how will the people centuries from us view our practices and reasoning for it?

This doesn't make sense to me - for a lot of religious workers it's not just saying words or leading a service, but something spiritual. It seems like they think they can automate away the clergyperson's humanity, but how can they automate away spirituality?

I suppose for simple tasks that are limited to seating someone, or reading - that can be automated, but that's far from all clergy do.

Just being real here for a moment - Firefox probably wouldn't exist if Google didn't give them millions, so the continuing existence of Firefox is thanks at least in part to Google taking them on as a project.

Now secondly, Firefox does have some very real performance bottlenecks that other browsers do not have. This means (and has been my experience already) that you can build experiences in all other browsers that are buttery smooth and nice, but that will cause crashes in Firefox. In my own work, to get around this I ended up making my product inferior in all browsers so it would not crash Firefox. But if I was big enough and had a team of more than 1, could I have implemented a solution that worked in Firefox and another that worked in other browsers, and delivered the best experience I could to all users of all browsers?

There's no need to jump to malice on Google's part if what they're doing is legitimately in an attempt to ensure that Firefox users have the best experience overall.

Absolutely love it, it's already perfect!

Igalia, a 3rd party browser developer who ships code to multiple browser engines, has been working on native MathML support for Chromium and has shipped earlier this year!

https://mathml.igalia.com

    "Ethan Schoonover’s color scheme Solarized (2011) was an important inspiration for Flexoki."

No kidding, the first thing I thought of when I saw Flexoki was "This looks like Solarized Light, but with darker darks!"

Part of Closure Tools was also an early CSS transpiler called "Closure Stylesheets" that behaves very much like the CSS 'preprocessor' languages that followed it https://github.com/google/closure-stylesheets

It's easy to see this set of JavaScript and CSS tools as ahead of their time, and the first of the particular kind of toolset that followed in the years after it.

I write HTML by hand and one thing that's come in handy is HTML's built-in functionality for author-defined custom elements. We use ICON-LIST which wraps a UL and optionally an SVG if you don't want to use the default checkmark, and STAR-RATING which displays a rating out of 5 SVG stars. They aren't my most-used, that's probably P or A or LI or DIV or SPAN by number, but they're some of the most important I use frequently!

I don't know this incident, but the person is a famous actor who has kind of turned into a political commentator and spiritual coach (if that makes sense). The cynic in me says that (just like Joe Rogan) because he's a very popular, widely listened to, _independent_ media production, traditional media wants them gone and would do almost anything in their influence to discredit or remove these people.

I'd encourage you to look at the viewership numbers for people like Joe Rogan, Russel Brand, and their peers in independent media, and then look at viewership numbers for CNN, etc and 'traditional'-style media companies and you can see why they may have targets on their backs.

Because they're such big targets, it really makes me scrutinize and extra skeptical about things brought against them, not because I believe they haven't done crimes or are good people, but because there's so much incentive by so many others to simply knock them out of the game by any means.

Making your own drink at a restaurant is not really an option. Human bartenders are hit and miss in terms of quality and consistency, but there's another pressure in human bartending that I wonder if would not be present with metered robots that account for usage and wastage at the level of individual drinks rather than at the level of a work shift. It seems pretty commonplace that liquor bottles are weighed before and after a shift, to measure theft and wastage, so they can figure out who may be giving out free drinks, or taking liquor, etc. This means if a bartender makes a mistake earlier in a shift, they may try to shortchange people later in the same shift so their weights come back okay at the end of the shift, but this is accomplished by overcharging the later customers. I would hope with a robot bartender that I would get exactly what I paid for each time.

This strikes a chord - though I have no issue falling asleep, I totally agree with this method for moving closer toward a desired outcome.

If someday I want to play the piano effortlessly and beautifully, I should start by spending time with my fingers touching the keys. Habits can be formed slowly and as an accumulation of many positive steps in the direction toward a goal.

Do we know if it is actually a script encoding a language? I'm an amateur but the first things that pop into my mind are: Can we tell statistically if it looks like it's encoding a language? And could each character represent as much as a complete word or even more than one word (like a line in a song, or an event in a narrative)

Thanks, that makes a ton of sense, smaller/better by design but equipped to handle the same kinds of problems that JavaScript does.

Is there any advantage to writing in Dart and transpiling that to JavaScript?

As someone inexperienced with Dart, but ever curious about it - is there anything more you can share about that, or what might have been? I end up writing almost all my work in browser-based JavaScript so I'm curious how different my work might have been.

    "there aren't good tools for automated testing without a build step"

For our vanilla JS we use browser-based tests which we can check in any browser anywhere any time, and which can also be automated and measured with a headless browser from the command line. And we have also used Node and had even more luck with Deno for testing individual functions and libraries which may get used on the frontend! Hope that helps!

Congrats Rich, and thanks for everything you've done, including being in inspiration for so many!

HTML is supported natively in the browser, and custom HTML elements and their properties work at the same level as all other HTML elements as far as JavaScript, DOM, and dev tools are concerned.

React, while it may provide similar functionality to the programmer, is not natively understood, and while it can run in browsers, the 'components' in React are not handled in the same way in the browser as native HTML elements, JavaScript and its APIs don't know about them as HTML elements, DOM isn't aware of them (only their parts), and dev tools can't offer much insight because the app that's running is an unpredictable black-box to the browser.

Punishing users for the browser they use when it can render the site perfectly fine is so hostile. They may not even have the choice of browser installed on the machine they use.

Even though I've never used Angular, and do not build web apps at all, we have put custom HTML elements to great use at work. It's also not about locking down styling, but it's a neat way to package up _functionality_ and behaviour that otherwise would be just defined ad-hoc in JavaScript, and to provide a dead simple way to (re)use that functionality in a declarative way from HTML.

Author-defined custom HTML elements, with all of the behaviour and interactivity defined in a way the browser natively understands.

Numi reminds me of Soulver at first glance: https://soulver.app/

    "That's a self-fulfilling issue, though."

It's not self-fulfulling. The state of the Gecko codebase and its performance is not _because_ Brave didn't end up using it.

    "If no one is using Gecko why does Gecko have reason to improve performance."

This question is a valid question, but is unrelated to Brave which does not use Gecko.

    "If they had good performance engineers it wouldn't matter if they picked the "worst performing", because they could work to improve it and prove they had good performance engineers."

It would matter, because they would have chosen the most difficult task which is a sidetrack from the reason they were making a fork of a browser in the first place. The focus of Brave is not to improve the performance of a browser engine.