General Programming Megathread - New OP

[Rub]

I suppose you PHP people still haven't heard about the wonderful thing called local development servers.

At work I SSH to my development VM which is backed up for me, for my personal stuff I SSH to my personal development server, for RTB I SSH to the RTB development server. No need for a local VM lol.

[Ad Bot]

[DontCare4Free]

At work I SSH to my development VM which is backed up for me,

You don't use a SCM?

for my personal stuff I SSH to my personal development server, for RTB I SSH to the RTB development server. No need for a local VM lol.

Why would you use a VM while developing? I can see the use while testing (backing up here doesn't make sense anyway, since they are supposed to be volatile anyway), but using it while developing seems useless.

[Rub]

You don't use a SCM?

What the forget is a SCM?

Why would you use a VM while developing? I can see the use while testing (backing up here doesn't make sense anyway, since they are supposed to be volatile anyway), but using it while developing seems useless.

How else do I run Apache and PHP? Why would I run it on my local machine that's so limiting lol.

[dotdotsquare]

Nano is absolutely fantastic. It's extremely minimalistic so writing code becomes an absolute breeze. I wouldn't write a big project in either, but for individual scripts I absolutely adore nano.

Jesus christ nano is a terrible editor. The reason that someone would want to use Vim is due to its efficiency; you can navigate around you code much quicker and easier than anything comparable (maybe Emacs, but I find it cooler due to its customization not its keybindings). That combined with some absolutely fantastic packages, it's just all around nice to use.

[DontCare4Free]

What the forget is a SCM?

Source Control Management / Version Control System: Handles source code revisioning etc. Examples: Git, Mercurial, Bazaar, etc.

How else do I run Apache and PHP? Why would I run it on my local machine that's so limiting lol.

The answer to this would be to use something that isn't terrible.
On a more serious note, in what way would that be "limiting"? Also, even PHP actually has it's own built-in server since, I think, 5.4.

[Rub]

Source Control Management / Version Control System: Handles source code revisioning etc. Examples: Git, Mercurial, Bazaar, etc.

We use SVN, I commit from my dev server to the repo.

The answer to this would be to use something that isn't terrible.

I use what work use, that's unchangeable.

On a more serious note, in what way would that be "limiting"?

Say I was out on site with a customer and I wanted to show a new development that wasn't on a staging server, I wouldn't want to rely on my computer not being off or something, a VM on a centralized server makes much more sense.

[Trinick]

The reason that someone would want to use Vim is due to its efficiency; you can navigate around you code much quicker and easier than anything comparable (maybe Emacs, but I find it cooler due to its customization not its keybindings).

I don't generally need to 'navigate around' small scripts, as I already entailed is my primary use for nano.

That combined with some absolutely fantastic packages, it's just all around nice to use.

I don't even understand what you mean by this.

[DontCare4Free]

We use SVN, I commit from my dev server to the repo.

And there's where the backup argument becomes irrelevant, other than for the SVN server.

I use what work use, that's unchangeable.

Okay.

Say I was out on site with a customer and I wanted to show a new development that wasn't on a staging server, I wouldn't want to rely on my computer not being off or something, a VM on a centralized server makes much more sense.

Pull source from SVN/whatever. Vagrant up. Wait a few minutes. Done. Or if that's too slow, do that on the dev VM (but don't use it for day-to-day development).

[Trinick]

Or if that's too slow, do that on the dev VM (but don't use it for day-to-day development).

I'm sorry, did you just say to not use a dev box for development?

[Rub]

And there's where the backup argument becomes irrelevant, other than for the SVN server.

There's some stuff we don't have under version control but is still important to have backups of.

Pull source from SVN/whatever. Vagrant up. Wait a few minutes. Done. Or if that's too slow, do that on the dev VM (but don't use it for day-to-day development).

Yeah I'll just checkout the massive code base on the customer's computer on their 2mb broadband connection, definitely one of your best ideas.

[DontCare4Free]

I'm sorry, did you just say to not use a dev box for development?

I said not to use a VM for the actual development, unless it's something that your regular OS doesn't like (say, sandboxed PyPy on Windows). I suppose a better name would have been "show-off VM".

[Rub]

Still unsure what the problem is. My dev VM is a copy of production and can be reimaged in minutes when/if I break it. Why would I develop locally?

[Trinick]

Also, I do all my development on a linux linode server. It would make no sense to compile it and run it through mingw on windows insead of developing on the server.

[Kingdaro]

huruehruehreuhruerhue

[ThinkInvisible]

well that's not very usef