Is anyone else feeling off about typescript in the terminal emulator? I guess it's not worse than TCL or Perl.
Show HN: Inshellisense – IDE style shell autocomplete
111–120 of 161 posts
Re: Show HN: Inshellisense – IDE style shell autocomplete
#112It'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)
Re: Show HN: Inshellisense – IDE style shell autocomplete
#113The implementation has obviously never been run on a Unix/Linux: * shell config is created with CRLF https://github.com/microsoft/inshellisense/issues/8 * changing directory doesn't work https://github.com/microsoft/inshellisense/issues/5
It doesn't work on Windows either... at least by a comment in the issue. I don't have Windows.
Re: Show HN: Inshellisense – IDE style shell autocomplete
#114Earlier quoted context omitted.
I agree. I was going to install and backed out when I saw `npm install` as well. I am wondering if my priors need to be updated, though (namely: JavaScript is slow, inefficient, and unsuited for anything outside of webdev).
I think javascript is plenty fast these days. My only problem with Typescript/Javascipt is the toolchain is very complex/confusing to someone on the outside. In my experience, Rust/Go or even python is easier to get into if you're not living it every day. Besides familiarity, I'm not sure why someone would choose Typescript for non-web work.
The TypeScript typesystem is pretty great. And there's always JS to escape to if the typesystem fails you.
Re: Show HN: Inshellisense – IDE style shell autocomplete
#115Thanks for everyone creating issues. I'm working on addressing all the issues and they'll be included in the next release.
Re: Show HN: Inshellisense – IDE style shell autocomplete
#116Earlier 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.
Man, we are doing a CLI autocomplete for duck sake, and You guys want to spin ENTIRE FUCKIN BROWSER for it, and then argue "well, it isn't THAT slow, so what's the problem". I'm not some extreme purist that thinks everything should be made in C and then hand optimized in assembly, but Jesus, how wasteful can You get before the slightest amount of self awareness starts to kick in. And for what reason, to save a week o…
You know, JavaScript runs without a browser... There are several JavaScript implementations, most of them aren't bundled with a browser.
Re: Show HN: Inshellisense – IDE style shell autocomplete
#117So I have to take a shell dependency on Node.js? Hard pass
Maybe the users don’t care about their devices
Re: Show HN: Inshellisense – IDE style shell autocomplete
#118Re: Show HN: Inshellisense – IDE style shell autocomplete
#119Earlier quoted context omitted.
I've done this enough times I use `ls` first, then `rm`
As much as I can, I do a 'mv ... /tmp' instead of 'rm -rf'. It gets the files out of the way, and provides a way out if that's not what I wanted. '/tmp' will eventually be cleaned by the OS so no (prolonged) space worries.
/tmp is a RAM disk on many systems so be careful with very large files
Re: Show HN: Inshellisense – IDE style shell autocomplete
#120Earlier 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.
Man, we are doing a CLI autocomplete for duck sake, and You guys want to spin ENTIRE FUCKIN BROWSER for it, and then argue "well, it isn't THAT slow, so what's the problem". I'm not some extreme purist that thinks everything should be made in C and then hand optimized in assembly, but Jesus, how wasteful can You get before the slightest amount of self awareness starts to kick in. And for what reason, to save a week o…
Or, spend the 10 minutes learning that Node isn’t spinning up an entire browser.
This thread is filled with a shitload of this knee jerk idiocy. If you want to promote Go, at least learn how to complain about factual things instead of writing some fiction and complaining about that. Node has legit issues you could complain about. FFS, whine better.