netghost

Firefox just added support for declarative shadow dom, so that might be it if you're not on the latest version.

Alternatively I could imagine some kind of proxy between you and the site buffering things up.

I was just trying that out, I _think_ it just concatenates all the content into the slot, but maybe there's a way to do that?

Since I see you're using GPT already, it might be nice to include a summary of any about page for a domain with the non-about results. That way I can see a little something about the person to give me more context.

For the 404s (assuming the status code isn't a 4xx), use a URL that you strongly suspect won't exist, then you can do a comparison (levenshtein distance, bag of words, etc.) to see if it's very similar to one of about, ideas, etc. pages.

The button is pretty amusing, but The rest of the site does a better job of motivating it.

I've taught a few kids a little bit of programming with things like scratch, but I think this would be infinitely more fun. I could imagine a group of kids who don't think programming is for them having a blast with something like this.

I think it solves a very specific set of problems that most people probably don't have.

For example, if scaling various parts of your application independently is a hard requirement, you're going to want to follow some set of these practices. Otherwise you're probably not going to see any practical benefits relative to the additional complexity.

Scanning to the bottom, it seems like the most likely use is to improve the ergonomics of simple scripts that need to shell out in some cases and also to streamline some of the more mundane package.json scripts, like deleting a directory when cleaning.

Personally, I think it seems like a nice tool blending JavaScript and shell scripting.

I'd really advise against going down the 3D path first. Not just because the math gets harder, but there's all the additional overhead of assets. A 3D game will require an environment, 3d models, etc. Maybe you can scrounge those, but unless he's really interested in the art aspect it's going to make it a lot harder.

Just to get things going, try out a 2D game engine. Love2D is great if you're okay with Lua. Browser based engines have a great iteration loop. On that front Kaboom.js could be a really quick way to get something fun that you could iterate on or use as a protoptype (look past the silly assets, it's pretty well thought out).

I saw some recommendations for Scratch, which might be fun for something simple, but it's really challenging (as far as I can tell) to scale up to non trivial games.

Taking a step back, see what part of this motivates him. It's an awesome opportunity to channel interest into something creative, focus on that. It might mean cutting scope somewhere, but he'll get more out of it if you can mine that vein of interest.

I had a similar experience! My son is 8 now, and he still occasionally asks me to load up the "game" where you choose an emoji and type a number and it show that many of them on the screen.

It's not "fun", but dad made it and he had a say in how it worked, which is huge for kids.

You can usually just say something like: "You must respond with at least five emojis".

Sure, there are cute and clever ways to get it to do things, but it's trained on natural language and instructions, so you can usually just ask it to do the thing you want. If that doesn't work, try stating it more explicitly: "You MUST... "

SCM as Save Button.

I've got a feeling some people might consider this to be a rather snarky response, but honestly a lot of trouble comes from assuming you can muddle through CSS, and you can. Unfortunately that means it's easy to always be an expert beginner, and never quite grasp the underlying logic, as obtuse as it may be.

It's the "if done right" bit that's so tricky.

So often though the GoodThing doesn't have a clear payoff and another FastThing does.

Depending on their age and interests, scratch might be a good first step. It's extremely accessible.

Then kaboom seems like a really fun next step. You can get from zero to fun really quickly.

Honestly the RSS support in Firefox and friends was just never that great. A long time back I used Sage and loved it, but when Firefox moved to use standardized plugins it wasn't an option anymore.

So I built Brook, it's pretty simple and hangs out in your sidebar on Firefox: https://github.com/adamsanderson/brook

Rollup is used by some of these tools. For instance vite uses rollup for production builds.

I think indexeddb is somewhat orthogonal to this library.

The memory efficiency you might get would be that you don't need to hold the whole dataset in memory while running the filter step though at the moment it looks like it assumes you're working with an array in memory (https://github.com/leeoniya/uFuzzy/blob/main/src/uFuzzy.js#L...). That said I suspect there distance between this and something that could search against a stream of data is pretty short.

Thanks! Those are a great set of examples.

Perhaps one through-line is that if IDs are not created by a single source, don't rely on auto incrementing IDs.

The parent/child one is interesting. When I've worked with hierarchical data, I tend to wrap the whole process in a transaction, so it may be many commits (by depth), but one transaction.

Can you give an example of an issue you faced with auto incrementing keys?

Though I can imagine scenarios, the worst I've ever run into was maxing out the integer size, bit that was easily remedied.

This is a great concept, but definitely really early. I'm curious if there are other examples in the ecosystem already?

Having been at times a manager and other times and IC, there are some great opportunities in each role, and it really depends on your organization.

If you haven't read it, "Staff Engineer" outlines some of the ways more experienced engineers continue to grow and provide value without becoming managers. I'd say the first half of it is worth a read to see if it sparks anything for you.

I will say that it gets lonelier as you go along either track. Reach out to peers if you have any. If not, try to reach out to folks outside of engineering.

It's a tricky path, and I wish you the best.

I strongly agree, giving people the distribution conveys a lot of information especially if everyone is clear on what the parameters of that distribution mean (ie: what's the low estimate mean?).

At the same time, there are occasions where it can be useful to collapse a distribution for some types of reports, or for quickly looking across estimates.

I love the style of your game. Thanks for sharing it!

If so, I have a similar game as well Lexery! https://adamsanderson.github.io/lexery-js/

What's your approach to Android support? Are you relying on mutation events, `beforeinput`, something else?

I built a really solid android adapter (after spilling gallons of tears) for our Draft.JS fork, and might have a few tips if it's helpful.

If subversion had branches, they were not nearly as easy to use as in git. It also didn't have a great notion of offline work (to my memory).

For what it's worth, SVN was pretty straightforward and worked well enough at the time. Later, Mercurial addressed SVN's deficiencies with a familiar interface.

> Open PRs for browsers with provided-by-us code to integrate RSS again, with UI elements that make existing feeds visible and supports subscribing via a feed reader

Please please please don't reinstate the "support" browsers had, it was effectively useless.

As someone who's built their own browser extension for tracking and reading feeds, I really don't want the confusion of a half feature. The browser is GREAT at navigating pages and rendering them, but when we start bundling in other services (ahem Pocket in firefox?) it feels like cruft.

I'd much rather browsers focus on building out solid features that support building amazing websites and extensions.

Working on a project with a significant number of sagas, I have to heartily agree with you.

There are some very clever things you can do with them, but this really need to know all the ins and outs of it first, and by the time you've learned them you implemented a giant nightmare.

Ahh, but how many of the nines need to go on which side of the decimal point?

It sounds like rxdb is built on top of pouch, so probably the same set of options with the possibility of some opinionated design or sensible defaults though I can't find anything. obvious.