4 ms·
There are some clearly cool parts to this. But it makes me feel like rather than bolting this onto existing terminals and shells, one should be created from the
by azinman2 5y ago
There are some clearly cool parts to this. But it makes me feel like rather than bolting this onto existing terminals and shells, one should be created from the ground up to better integrate UI. Why not have actual abilities to show photos in an interactive way (eg ls giving me a grid of photos I can click and zoom on like Finder), or put in form values rather than just autocomplete like ffmpeg giving me an actual UI to work with that shows frame by frame progress rather than just a % bar?
The CLI seems ripe for total disruption IMHO. Fish shell claims it’s finally the terminal for the 90s… how about the 2020’s?
- mschrage 5y agoWe totally agree! This is exactly where we want to take Fig. The autocomplete product is built using an API that extends terminals with visual apps and shortcuts. Using the same API, you can build an app that interactively displays photos or wraps a common ffmpeg workflow. We prototyped[0] a bunch of ideas like this during YC last summer, before deciding to start with autocomplete. [0] https://fig.io/videos/old-sizzle-reel.mp4 https://fig.io/videos/old-sizzle-reel.mp4
- azinman2 5y agoI guess I’m suggesting why fix yourself to iTerm etc when you could just redesign the entire experience from scratch? You’d have way more freedom to fundamentally change CLI I/O, navigation, contextualization, UI, media support, etc.