I remember around 25 years ago being in the big music hall in Philadelphia and feeling a bit like I was inside a giant cello.
The cheapest seats were in the coolest place architecturally because you were right up at the back, closest to the ceiling, which really was a bit like in these instrument photos.
You can get nasties like legionella growing in tanks if the temperature is hot but not hot enough to kill them. The insides of these tanks can be filled with oxidised metal bits too.
When I was a kid I worked in a double glazing factory. Some of the old timers demonstrated just how hard it is to break a piece of toughened glass to me by whacking one with a bit of wood right in the middle of the pane, really really hard. Nothing happened. Then the dude tapped it really quite gently with a glass breaker in the corner (where it can't flex as much he said) and the whole thing exploded into those little cubes you see on the ground in dodgy car parks.
Forklift is the one I settled on as well. I had the experience you describe with Path Finder before and finally I gave up.
Forklift has a couple of things that annoy me daily though. Often I will have to refresh a pane to see a file I know has recently been added. Eg in downloads. I may even have navigated to downloads after the download finished and it's still not visible until I refresh.
The other is that it doesn't reuse existing tabs if I "reveal in finder" or whatever, so after a while there's a million tabs open, most pointing to the same directory.
I have a (badly made) variant of kill sticky that I use on my phone. It kills sticky, then messes with any code blocks it finds to make them full width and use a smaller font.
It drives me mad when I'm reading articles with embedded code blocks where the code has less room than the prose and sometimes a bigger font!
It works well on eg this page (https://www.programiz.com/swift-programming/inheritance), but maybe someone that knows what they're doing can make it work on GitHub. It'd be nice to not see those line numbers taking up half the width.
I'm on my phone so I've only the bookmarklet to hand:
I remember hearing an interview with Richard Hipp where he said he pronounced it as you do ("rhymes with kryptonite" I think he may have said, or perhaps "like a mineral").
I'd always pronounced it in my head S-Q-L-Lite up until that point, but I much prefer this other way that I'd never considered. It rolls off the tongue easier and adds a bit of fancy.
After driving a new Mercedes Vito (I can't describe how insane the controls of this vehicle are, but it has capacitive-touch buttons that you have to swipe to change the stereo volume ON THE STEERING WHEEL), I long for controls that look like this:
Tactile controls should be the default. I was actually interested in the Lincoln Corsair until I saw how much they rely on touch - even for things like the climate control, same as the Teslas. Instantly took it off the list.
That's why I won't even consider a Tesla. Test drove a few vehicles and it's amazing how many do touch screen everything now. Will -not- buy.
The one I ended up buying is all tactile except changing the radio stations. Even that gets really annoying, as you have to take your eyes off the road to change stations. I end up just poking it in random places blind until something happens.
I was kinda wondering too, and did a (very shallow) dive into the JavaScript on that page. I'm almost positive they are using Deepgram(dot com)'s speech-to-text service.
I ran whisper.cpp on that audio file on my laptop, and it does a reasonably well job too.
In VSCode if you do super-shift-f for find-in-project, at the top of the results pane, just right of where it's marked "x results in y files" there's a link button titled "Open in editor" which I believe does what you're describing. I'd actually forgotten about it until I read your comment so I'll start using it again now.
Oh, is that what they mean? I set "Search Mode" to "newEditor" immediately whenever I configure VSCode on a new computer, since the default behavior of opening in the side panel is such hot garbage. I entirely forgot that some people don't have that and took for granted in my post that everyone knew about opening the results in an "editor".
But the point is that "editor" is non-functional. It's nice for browsing the results and has syntax highlighting and surrounding context, but you can't actualy edit from there. You can only use it to open the source file and then edit the source file.
In Zed, the search results "editor" is actually functional. You can make changes to the text that you see from the surrounding context, right in the search results, and then hit save, and have those changes propagated to all the touched files.
So, say you update a function to take another argument, and you want to update your codebase appropriately. Well then you do a global search for that function name, and then scan down the results list. The irrelevant search results (maybe you mention the function in a comment, but aren't actually invoking it) you can skip. The complicated updates you can open the source file like you do in VSCode. But the trivial ones where you can see what you need to pass as the new argument, you can just update right then and there.
I only half-conveyed what I was aiming to; I'm able to do what you're describing by editing the search-results scratch-file then saving it. The changes propagate to the target files with the save.
I've had a look though, and you were right: it's due to an extension that I can save from the scratch file:
The cheapest seats were in the coolest place architecturally because you were right up at the back, closest to the ceiling, which really was a bit like in these instrument photos.
Some pictures here from a quick search: https://voithandmactavish.com/projects/the-kimmel-center/