Wow, this is really innovative. It really takes "physical modeling" synths to another, more literal level. Would love to have been a fly on the wall when the idea was proposed.
This + an Ekdahl Moisturizer would be an interesting pairing.
Exactly. The 60 and 70 year olds I spend time with, women especially (not a dig, but an observation), are just as addicted to facebook as the Instagram / TikTok crowd are to those platforms.
> at which point you've reinvented either a static site generator ...
It doesn't have to be Astro though. You can build something super simple that just includes the header, footer, and nav. Leaving most of the site as plain HTML.
Seems like a pretty solid deal, if you need everything. I don't know who that person is though. The intersection between Final Cut Pro and Logic users is pretty small, I'd imagine.
I'm that kind of user but I would rather not use Logic, Final Cut, or PixelMator unless Apple really improves those. On top of that there's also the platform lock-in concern.
> Golf is not so smooth. Yes, each round is a state-dependent game of error-correction (i.e. Zeno's Paradox). But golf swings are coarse actions -- few swings per game, with no recourse for fine adjustment between swings.
This is a bit of a contradictory statement. The "error-correction"'s are typically fine adjustments between swings. Small adjustments to setup, backswing, tempo, etc. are exactly the sort of thing a golfer adjusts during a typical round.
It is not. React 18 changed damn near everything. You can't create a new React 17 project without jumping through serious hoops. React 19.5 introduced the compiler, so you can stop using useCallback and useMemo. Except for "common scenarios" where you still need it. Which are about as clear as mud.
I can only imagine what React 20 is going to introduce.
React is an implementation of View component of MVC, View is responsible for displaying Model contents, not for handling routes. You are trying to use the wrong tool.
> But sometimes—and here's where it gets uncomfortable—you actually do need a button that updates part of a page without reloading the whole damn thing. You do need a search box that shows results as you type. You do need interactivity.
You can do this with plain old Javascript. Make a request, swap out the [inner | outer]HTML with the result. If you want a nice visual transition, wrap the swap in a startViewTransition(). Obviously, you need to be extra careful if you're using user-submitted HTML. Otherwise, it's fairly straight forward.
I know it's par for the course these days, but that's a lot of Js and CSS for a single page app with some text, a few images, and a list of collapsible info sections (whose animations aren't very smooth).
This + an Ekdahl Moisturizer would be an interesting pairing.
reply