"Why do I, the guy who barely knows emacs, have to whine?"
Because once you know emacs, you stop whining about it and start using it.
You sound mad because all these people are using emacs and you just don't understand it yet or something. Spend time, learn emacs or vim and then you will understand.
It is ridiculous for you to rant on something you obviously don't understand or recognize the power it possesses.
Emacs and Vim have been around forever. There is a reason.
Magit is probably my favorite piece of software. It's truly epic. It alone would keep me from ever switching to something else. Although emacs has plenty of other things to keep me around.
I've been running multi file apps since before 0.7. If you read the documentation or searched mailing lists or looked at example applications you can see how. Blueprints made it even better.
I've read through all the documentation, and researched extensively. I still ran into problems way too often to ever warrant using it over a full framework for larger projects.
I'm not trying to get you to use Flask or anything. But I definitely find it interesting that you have "read through the documentation or researched extensively" but were unable to find `add_url_rule`.
Either way, I'm glad we have selection and choice. At least we both like python! Peace
would you elaborate? i guess i agree for historical reasons but for practical reasons i think package managers actually should use /usr/local/. basically everyone uses a package manager now (except lfs). where would you like package managers to install.
"The /usr/local hierarchy is for use by the system administrator when installing software locally. It needs to be safe from being overwritten when the system software is updated." [1]
And I believe that "system software" today means "installed by a package manager" (please correct me if I'm wrong).
I personally (rarely) use /usr/local for manually-installed packages. This way there's no risk of a package manager accidentally overwriting stuff outside its control.
I'm a big fabric fan and use if for server bootstrapping and deployment. I've tried to get into puppet a few times but it always seems overly complex to me. Is puppet useful if I'm only running a handful of servers or is it designed for 10s (or 100s) of servers?
I noticed he used puppet and fabric in this article so it made me interested what puppet it doing better for him than fabric.
Is there a repository of examples? Like just bootstrapping a debian box with nginx/apache/postgres (or mysql)?
I'd say Puppet is useful even if you're running one server, especially when you use it with Vagrant. If you use it for EVERY bit of setup on your server (no manually installing packages!) you can be sure that your development VM and production server are both the same environment.
Puppet is declarative, Fabric is imperative. With Puppet I can say:
Make sure the directory /var/www/foo exists with permission 755 and owner foo.
Make sure the nginx vhost "foo.conf" exists in sites-enabled with content X, and this depends on /var/www/foo existing.
With Fabric you have to handle all the edge cases. What if /var/www/foo already exists? What if it's owned by someone else? You have to manually code all the 'mkdir' and 'chmod' commands instead of just saying "this directory should exist like this".
Right now there's no public example repo, but I'm planning on cleaning up and open-sourcing our Puppet/Django/Vagrant skeleton this week so we can use it during the Django Dash.
This should not be downvoted and in fact probably needs to be a top-level comment to counter the kind of misinformation the grandparent of this post is basing his complaint on.
> I don't understand why these people think this doesn't belong here.
Sorry, I wasn't trying to be rude. I just feel like its a couple of paragraphs long and doesn't have any substance. Like the other guy said, its a fluff piece. And the one thing you specifically pointed out of the article is actually incorrect.
>> because the software is so light on
>> bureaucracy, it is easy to customize and
>> to contribute to.
> Would someone care to refute this?
I would. Emacs was specifically NOT light on bureaucracy. That is specifically why xemacs created.
You sound mad because all these people are using emacs and you just don't understand it yet or something. Spend time, learn emacs or vim and then you will understand.
It is ridiculous for you to rant on something you obviously don't understand or recognize the power it possesses.
Emacs and Vim have been around forever. There is a reason.