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:
Can anyone explain how this works? Are these satellites in a similar orbit to GPS satellites? Do signals from cell phones etc include timestamps? Or is there a high resolution way of detecting the direction of a signal?
Maybe just plain old triangulation? The constellation consists of 21 satellites. If multiple satellites receive the same signal, the difference in arrival can be used to precisely locate the source.
Iirc, SAR satellites in polar orbits measure Doppler effect of distress beacons to compute coarse latitude. It’s been working for decades, so I imagine recent advances in signal processing might be able to significantly improve precision.
Maybe you already know this, but when I used to use sublime I'd save those dozens of files with cmd/ctrl-alt-s (save all open files). I think this is a universal-ish command for well-behaved applications on both windows and mac.
I miss sublime for how slick the ui feels, but I abandoned for the same reasons as you.
One place I've seen it used was a lib by a guy called DHoerl for reading images that are too big to fit in memory (this was years ago on iOS).
A very over-simplified and probably a bit incorrect description of what it did was to create a smaller version of the image - one that could fit in memory - by sub sampling every nth pixel, which was addressed via mmap.
It actually dealt with jpegs so I have no idea how that bit worked as they are not bitmaps.
That's a bit I find surprising. I would have thought that working out if the pad was up to the job would be one of the easier rocket-science tasks they were faced with.
You can see huge chunks of debris flying into the air on launch, and half a dozen engines were out by the time they were visible. The discolourations and asymmetry in the plume indicates damaged engines. The term of art is engine rich exhaust.
It looks like debris tore up the engines, which progressively lost more thrust and control authority as more engines failed, leading to the loss of the vehicle.
I agree with the sentiment of every response I've read to your comment so far. The agressive tactics, paywall, general sense of sleaze all make me actively avoid following medium links.
But even ignoring all that, medium is the worst place for any article about programming because the code blocks do everything to make it harder to read them. There's no syntax highlighting, the lines wrap and the container the code is in pads the text to make a narrower column than the body of the article.
That's the opposite of what I want. Especially on mobile! It's one of the sites that make me wonder if its developers have ever tried using it.
This is years too late, but I did have us had syntax highlighting. So that, plus better recommendations, plus returning incentives for the programming authors that do great work should change things.
Also, not sure if you know but we have the entire back catalog of Pragmatic Programmer books. I need to do a re-import to take advantage of the syntax highlighting, but it's still a pretty good feature. (Unfortunately, I was the programmer who did this import and so it's still on me to redo it)
https://www.youtube.com/watch?v=ooVDv8kuzXY
reply