Earlier quoted context omitted.
Expanding horizons = introducing longer pipelines of learning. At this point you'll need 10 years just to get the basics down much less be competent across the stack.
People routinely become immediately productive in Visual Studio Code. Contrast this with the potentially multi-decade journey of becoming proficient in something like vim or Emacs plus command line tools. It is possible to improve on the old ways, from a productivity and ease of learning standpoint as well as from a standpoint of what's possible.
Unix as IDE (2012)
61–70 of 72 posts
Re: Unix as IDE (2012)
#62Earlier quoted context omitted.
I don't know about Macbooks, but if the company-provided Laptop runs Windows, tmux + editor is nowadays very easy using WSL2.
Works great on Macbooks. Some would say better since copy/paste on a mac, even to and from a terminal in tmux is much less of a mess than on WSL or Linux.
Re: Unix as IDE (2012)
#63Earlier quoted context omitted.
The thing that we'd ideally want to happen, but will probably never will unless a mad person does it, would be to have something that wraps around a POSIX shell, and extends it in a sort of non-compatible way. Let's call this new tool $NEWSH. Larry Wall basically tried to do this with Perl but I guess his vision was too lax for such a pursuit, Perl tried to be everything, all at once. What I mean by this new approach…
(author here) Yeah you just repeated what https://oilshell.org/ is You'd want to be able to go $NEWSH my-bash-script.sh and it should just work. $NEWSH my-newsh-script.nsh should also work, obviously. osh my-bash-script.sh # works, it's the most bash-compatible shell by a mile ysh my-new-script.ysh # works YSH looks like this - https://www.oilshell.org/release/latest/doc/ysh-tour.html (everything in this doc works, y…
Also, how's the interactive mode? I don't want to just run scripts with it.
Re: Unix as IDE (2012)
#64Earlier quoted context omitted.
Expanding horizons = introducing longer pipelines of learning. At this point you'll need 10 years just to get the basics down much less be competent across the stack.
People routinely become immediately productive in Visual Studio Code. Contrast this with the potentially multi-decade journey of becoming proficient in something like vim or Emacs plus command line tools. It is possible to improve on the old ways, from a productivity and ease of learning standpoint as well as from a standpoint of what's possible.
The software world, might be better served, however, if programmers slowed down, and engaged their brains, before bashing keys. I’ve solved most of the difficult problems, in my programming life, in the bath - where I can allow my mind to wander, and come up with the best solution.
Re: Unix as IDE (2012)
#65IMO tmux + a scriptable terminal editor (Vim, Neovim, Emacs, etc) turns Unix into a very nice IDE — but it's pretty dependent on becoming deeply familiar with those two tools: a multiplexer and an editor. I wouldn't say Unix is an IDE, really; but you can build a very nice IDE for yourself using Unix tools, as long as you have a sufficiently configurable terminal multiplexer and a sufficiently configurable terminal e…
Re: Unix as IDE (2012)
#66Earlier quoted context omitted.
I don't know about Macbooks, but if the company-provided Laptop runs Windows, tmux + editor is nowadays very easy using WSL2.
Works great on Macbooks. Some would say better since copy/paste on a mac, even to and from a terminal in tmux is much less of a mess than on WSL or Linux.
Re: Unix as IDE (2012)
#67Earlier quoted context omitted.
(author here) Yeah you just repeated what https://oilshell.org/ is You'd want to be able to go $NEWSH my-bash-script.sh and it should just work. $NEWSH my-newsh-script.nsh should also work, obviously. osh my-bash-script.sh # works, it's the most bash-compatible shell by a mile ysh my-new-script.ysh # works YSH looks like this - https://www.oilshell.org/release/latest/doc/ysh-tour.html (everything in this doc works, y…
I'm going to throw a curveball and say: can I run Oil on Windows/Cygwin? :-) Also, how's the interactive mode? I don't want to just run scripts with it.
Interactive shell screencasts was the last blog post: https://www.oilshell.org/blog/2023/12/screencasts.html
Real Unix users download and build tarballs, they don't wait for the packaging gods to bless them with software :-P
Re: Unix as IDE (2012)
#68Earlier quoted context omitted.
I'm going to throw a curveball and say: can I run Oil on Windows/Cygwin? :-) Also, how's the interactive mode? I don't want to just run scripts with it.
It runs on WSL, not sure about Cygwin Interactive shell screencasts was the last blog post: https://www.oilshell.org/blog/2023/12/screencasts.html Real Unix users download and build tarballs, they don't wait for the packaging gods to bless them with software :-P
I'll see if it doesn't take a huge chunk of time to get it going in Cygwin.
Re: Unix as IDE (2012)
#69Earlier quoted context omitted.
I'm going to throw a curveball and say: can I run Oil on Windows/Cygwin? :-) Also, how's the interactive mode? I don't want to just run scripts with it.
It runs on WSL, not sure about Cygwin Interactive shell screencasts was the last blog post: https://www.oilshell.org/blog/2023/12/screencasts.html Real Unix users download and build tarballs, they don't wait for the packaging gods to bless them with software :-P
Re: Unix as IDE (2012)
#70Earlier quoted context omitted.
Works great on Macbooks. Some would say better since copy/paste on a mac, even to and from a terminal in tmux is much less of a mess than on WSL or Linux.
Native copy/paste integration is pretty out-of-the-box these days on WSL as well, FWIW.