Terminal editors are not WSIWYG applications. I don't think multi-cursor is the correct for a vim motion workflow but I'll admit my vim-fu is not as strong but I get by with the substitute command + grep good enough where I rarely feel the need for a GUI editor to use multi-cursor.
Since VS Code is already an inefficient way to move around a code base, I don't think we should take any lessons seriously outside of how useful the LSP protocol become for adoption.
I think multi-cursors can be seen as an extension of macros, just that instead of defining the macro and navigating to the relevant places you instead navigate first and then execute the commands interactively (in essence skipping the part where you have to record). As a side effect you also don't need to be that concerned about what to do after having made a mistake.
I've had some pretty nasty string-wrangling with the substitute command that could've been avoided by just using a macro and the other way around. I'd argue these things complement each other and there is no need to restrict yourself arbitrarily.
Having it and not using it is better than needing and not having.
I can recall countless times where multi-cursor would've been just the sweet-spot I needed.
P.S.: multi-cursor is not about moving around the code base and therefore not taking lessons about navigation has no impact in this matter.
Sis, substitutions started being useful being I even learned Regex and I have done an incredible amount of edits with the just the bare minimum of Regex knowledge
Yeah, gemini gives $649 - $699 for BOM, $749+ if they want some margin from the hardware.
Which is cheaper than most "Gaming PC", but still more expensive than Switch/PS5, and lack the expandability of PC.
I wish they could sell at $300-$500, that's really going to make this a must have for this year.
Using the deck prices seems like a good place to start unless they're using the opportunity to change strategy. It's an updated SoC, but minus a screen, battery, separate dock, built-in controller, and less pressure to pack it in a handheld chassis. They mention a built in wireless adapter for the controller, so I assume there will be bundles with and without a controller.
If that's the case I think it's a hugely positive thing, and has gone away for newly bought hardware for a variety of reasons over the past decade. Having a basic PC and then upgrading it with a GPU used to be a realistic route to a respectable gaming PC, but I think that's largely gone away now (partially due to the death of the general "home PC" or many being on laptops. There are bargains to be had in the used market, but that comes with a lot of asterisks.
If they can get this to a large market I think it's great value, not just as a console-model PC but because a full featured desktop without lockdown is so near. It's a reverse of where I've thought MS missed a trick with the xbox, add a keyboard and mouse and let users have turn on a sandboxed lightweight desktop mode then funnel users to get software through their store, which would have been a great way to get xbox hardware installed in houses (especially the cheap S models) during covid when there was a sudden rush to buy PCs for home working that previously didn't need it.
This is targeted at the living room, but I'd love to see non-gaming uses highlighted and get the equivalent of 'deck certified' whether that's linux native or efforts into working well under wine.
I wish this thing had a PCIe slot. Would be nice if case manufacturers sold compatible cases for the motherboard so you could build a bit with it. Insert a raid controllers and a few HDDs to get started with a homelab or add a beefier GPU two years down the line.
Yeah, it's only competitive as a toy for under $35, anything beyond that you can get a cheap x86 with much better performance, a much compatible architecture and much more IOs.
If you're looking for other languages, Piper has been around in this scene for much longer and they have open-source training code and a lot of models (they're ~60MB instead of 25MB but whatever...) https://huggingface.co/rhasspy/piper-voices/tree/main
Actually I found it irritating that the readme does not mention the language at all. I think it is not good practice to deduce it from the language of the readme itself. I would not like to have German language tts models with only a German readme...
TTS is generally not multilingual. One might think a well-annotated phonetic descriptions of voices would suffice, but that's not quite how languages work nor how TTS work.
(but somehow LLMs handle multilingual input perfectly fine! that's a bit strange, if you think about that)