121–130 of 161 posts
Co-founder of Fig here! Just want to say that I think this is awesome. It’s really cool to see alternative implementations of IDE-style autocomplete in the terminal. Nice work!
Great idea! Also terrifying :) Given how often I accidentally commit the wrong text in vscode, I shudder to think of the damage I could do with this on my shell, hah! What safety measures are there/could there be?
A simple approach might be that if the resulting exit code is not 0 it won't be used to complete in the future.
It's pretty cool but still seems a little rough around the edges. My simple test case was to launch into the shell and see if it loaded any of my normal shell configs like highlighting or auto-suggestions (based on my history) but it seems to just be its own shell entirely. It also doesn't seem to play nicely with `zsh` since I tried to do a `..` (which is a common `zsh` alias for "cd .." which got a `zsh:1: permissi…
stock macos zsh's `..` just gave me 'zsh: permission denied: ..' zsh 5.9 (x86_64-apple-darwin22.0)
Earlier quoted context omitted.
I've done this enough times I use `ls` first, then `rm`
kind of the same deal with spooky SQL queries and verifying your where clause with a select first
Earlier quoted context omitted.
It really doesn’t make any sense here. What are we making type safe exactly?
It doesn't make any sense to even complain about Typescript in the first place here. Typescript itself is not being ran when this command is invoked, the npm package for this doesn't even distribute .ts files or a type definitions file. This is latching on the to the word "Typescript" and immediately beginning the whining.
So I have to take a shell dependency on Node.js? Hard pass
Earlier quoted context omitted.
Jakob Nielsen says that 0.1 second is about the limit for having the user feel that the system is reacting instantaneously, meaning that no special feedback is necessary except to display the result... https://www.nngroup.com/articles/response-times-3-important-...
In gaming, delay of 100ms is huge enough for anyone besides the most casual players to notice. Obviously this are different use-cases, but wouldn't be suprised if it was big enough for people to at least notice
But 100ms seems like a reasonable upper limit for autocomplete to me.
PS: My son-in-law is a professional drummer and can't play Rush YYZ on Rock Band (just had to include this tidbit cause it'll piss him off)
Earlier quoted context omitted.
Don’t bring TypeScript into this. It is very possible to write sub 100ms procedures in TS, but an inelegant algorithm will be slow in any language, eventually.
100ms is a long time to wait for each completion suggestion.
What is sad is that it has to rely on a library of completion specs. It shows what kind of stone age foundations we are building on top of. The world would have been a much better place if CLIs themselves defined strict interfaces using standard data structures. Not only for auto completion, also gives much more accurate error checking of bash scripts. Same goes for data piped in and out of command.