Unix as IDE (2012)

#1

Post by lrsjng » Thu, Feb 27, 2020, 10:37 PM UTC

Unix as IDE (2012)
sanctum.geek.nz

Re: Unix as IDE (2012)

#2

Post by pvg » Thu, Feb 27, 2020, 11:06 PM UTC

A few times previously:

https://news.ycombinator.com/item?id=12653028

https://news.ycombinator.com/item?id=4105768

https://news.ycombinator.com/item?id=3594098

Re: Unix as IDE (2012)

#3

Post by RcouF1uZ4gsC » Thu, Feb 27, 2020, 11:14 PM UTC

I think code completion is missing. Sure you can always try to grep your function call, but seeing the parameters and return type of a function you are calling as you are coding is really nice.

Also a real IDE does much better debugging. Using Visual Studio for debugging your program is much easier than using GDB, which is probably why the more Unix programmers use printf debugging rather than try to fire up GDB.

Re: Unix as IDE (2012)

#4

Post by samsquire » Thu, Feb 27, 2020, 11:24 PM UTC

I think the desktop can be an IDE.

https://github.com/samsquire/ideas#98-the-desktop-is-an-inte...

Re: Unix as IDE (2012)

#5

Post by pvg » Thu, Feb 27, 2020, 11:31 PM UTC

RcouF1uZ4gsC wrote: post #3

I think code completion is missing. Sure you can always try to grep your function call, but seeing the parameters and return type of a function you are calling as you are coding is really nice. Also a real IDE does much better debugging. Using Visual Studio for debugging your program is much easier than using GDB, which is probably why the more Unix programmers use printf debugging rather than try to fire up GDB.

The author addresses some of that directly - the series is really a collection of tutorials on how to get various programmer-ish things done in Unix. The title is a stroke of viral genius.

Re: Unix as IDE (2012)

#6

Post by glouwbug » Thu, Feb 27, 2020, 11:40 PM UTC

RcouF1uZ4gsC wrote: post #3

I think code completion is missing. Sure you can always try to grep your function call, but seeing the parameters and return type of a function you are calling as you are coding is really nice. Also a real IDE does much better debugging. Using Visual Studio for debugging your program is much easier than using GDB, which is probably why the more Unix programmers use printf debugging rather than try to fire up GDB.

Keep your declarations on a single line:

    int fun(void*);

And

    grep -r fun *.h

Will tell you everything you need

Re: Unix as IDE (2012)

#7

Post by mstwntd_g » Thu, Feb 27, 2020, 11:59 PM UTC

RcouF1uZ4gsC wrote: post #3

I think code completion is missing. Sure you can always try to grep your function call, but seeing the parameters and return type of a function you are calling as you are coding is really nice. Also a real IDE does much better debugging. Using Visual Studio for debugging your program is much easier than using GDB, which is probably why the more Unix programmers use printf debugging rather than try to fire up GDB.

vim has basic completion builtin.. and there's a lot of code complemention plugins..

Re: Unix as IDE (2012)

#8

Post by tombert » Fri, Feb 28, 2020, 12:00 AM UTC

I've gotten made fun of because I've said my "IDE" is `tmux` in the past; my typical development environment is a tmux split, where an editor (usually NeoVim, sometimes Emacs) does editing, and the bottom half is a terminal running either a dev server or just the compiler command.

It's not perfect, but I like how I can basically swap any component out (except tmux itself).

Re: Unix as IDE (2012)

#9

Post by archarios » Fri, Feb 28, 2020, 12:03 AM UTC

anyone figure out how to do this with Java though? Seems more feasible for C or Go but not all..

Re: Unix as IDE (2012)

#10

Post by samsquire » Fri, Feb 28, 2020, 12:14 AM UTC

What is it about an IDE that you need?

a) The ability to do an end-to-end build with one click (we've lost that with cloud being part of the equation)

b) Guranteed buildability

c) Intellisense/autocomplete

d) Widgets that can be moved into any which way.

I feel that we're missing a trick with CI/CD if IDEs can do a end-to-end build with one click, there's some technology to be shared or extracted here from desktop IDEs.