0

I am generally a PHP Developer that deals in a few different MVC frameworks. I am being tempted (like most) to break out of my comfortable LAMP environment in pursuit of a "prettier" and "more simple" language, attached to frameworks that are becoming more and more popular.

I agree with most arguments to switching to a (the) ruby framework or a python framework, and would trade out PHP for Python in the LAMP acronym any day of the week.

But as I've found in trying to get started with these, it's not quite that simple...

In my attempts to figure out the spaghetti of dependencies, versions, and install procedures, I've found that while final development time/simplicity is a benefit, in my mind it is almost overshadowed by the complexity of deployment...

Especially being use to the copy/paste deployment to the ever numerous lamp hosting services.

I am specifically speaking of

  • Ruby on Rails
  • Django (python)

To those that work in these platforms, was your initial experience similar? if so how did you overcome it?

Improve this question

1 Answer 1

Reset to default
1

To those that work in these platforms, was your initial experience similar?

No.

Django was quite simple. Python is quite simple.

spaghetti of dependencies, versions, and install procedures

You have to be much more specific about your experience. It was all pretty obvious from the Django documentation.

Improve this answer
8
  • Sure, Hello world, and their little polling application was nice and easy, but as soon as you start introducing python package dependancies along with the whole "pip vs easy_install" thing, then I'm just thinking how the heck am I going to successfully deploy this thing, "mod_wsgi vs nginx vs lighttpd" etc.. just seems like their is less standardization which has led me to confusion to know what is the "right" way.
    – jondavidjohn
    Jul 28, 2011 at 20:16
  • "python package dependencies" have never been a problem. It's quite easy to manage. For production, we actually use YaST on OpenSUSE. "mod_wsgi vs nginx vs lighttpd" seems like there is so much perfectly implemented standardization that it barely matters what you choose -- Python and Django work with all of them equally well.
    – S.Lott
    Jul 28, 2011 at 20:28
  • "have never been a problem. It's quite easy to manage." not my experience... wish it was, love python syntax, but i don't think you can argue that managing python environments is as dead simple as a standard LAMP instance...
    – jondavidjohn
    Jul 28, 2011 at 20:35
  • @jondavidjohn: Okay. So you're saying that your overall question isn't really a question, but rather a complaint. I always thought Python was the dead simple LAMP instance. Your complaint is -- what -- that it's not PHP? Is that the real point of the question? To complain about Python and Ruby?
    – S.Lott
    Jul 28, 2011 at 21:50
  • not at all, I'm searching for people who have had the same experience I have, that have overcome it. This comment thread is turning more into my response to your answer which essentially boils down to " Django/Python is simple, RTFM" which I hope you can understand is not helpful. I understand my question is vague, but I'm mainly looking for tips for someone coming from a LAMP copy/paste deployment environment. Essentially things that you finally learned and said "Really wish I would have known this from the get go."
    – jondavidjohn
    Jul 28, 2011 at 22:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.