Please, don't bring your ghetto over here. Keep your unwashed masses to yourself.
Ruby Web Dev The Other Way
11–20 of 65 posts
Re: Ruby Web Dev The Other Way
#12No magic, just developer clarity. Neither of these items seemed like a primary concern for many different Ruby libraries and Rails itself.
I also suggest trying out data mapper pattern instead of active record. Flask and SQLalchemy are extremely powerful and easy to use. Virtual data fields and all kinds of neat things that really makes working with data easy and customize for complex business requirements.
Re: Ruby Web Dev The Other Way
#13Re: Ruby Web Dev The Other Way
#14Yes, you shouldn't do Ruby development on Windows if at all possible. But is there any reason why OS X is not mentioned in the Linux section? It is after all what many Ruby developers use.
Re: Ruby Web Dev The Other Way
#15I ended up disappointed. The piece reads in a very partisan manner, makes questionable declamations of common Ruby tools & patterns, and throws in a lot of obnoxious asides about how bad other programmers are.
Examples: "RoR is a good starting point for a young developer." Its usage encompasses just a tad more than that. "MVC is not an architecture." Just factually untrue.
That said, the lower portions of the guide have some good content and the list items describing popular gems are helpful.
Re: Ruby Web Dev The Other Way
#16Yes, you shouldn't do Ruby development on Windows if at all possible. But is there any reason why OS X is not mentioned in the Linux section? It is after all what many Ruby developers use.
Re: Ruby Web Dev The Other Way
#17I'm not going to be able to comment on everything on this article and it is indeed a wonderfully put together resource, but I must say that I tend to disagree with the over-all premise. Yes, if you are a first time or beginner developer Rails can be overwhelming and you will learn a lot more by using a smaller framework such as Sinatra. On the other-hand if you are undertaking a medium to large scale project (and not…
Counterargument: nearly every medium-large scale project I've seen in Rails ends up full of mismatched idioms and confused usage of Rails core utilities and just general jankery. Also, Rails 5 is not Rails 4 is sure as hell not Rails 2--as the framework has matured, it's gotten less and less accessible to beginning devs, and has developed a jargon and mindset that sheds very little light on how the Web works under th…
I think you could remove the word "Rails" and say the same about any medium-large scale software project with several developers working on it. Say what you will about Rails, but after working with it for about a decade, it's actually prevented more confusion and stupidity from creeping into the projects I've worked on rather than enabling it.
Re: Ruby Web Dev The Other Way
#18The mention and link to Elixir scares me. Please, don't bring your ghetto over here. Keep your unwashed masses to yourself.
Re: Ruby Web Dev The Other Way
#19I'm not going to be able to comment on everything on this article and it is indeed a wonderfully put together resource, but I must say that I tend to disagree with the over-all premise. Yes, if you are a first time or beginner developer Rails can be overwhelming and you will learn a lot more by using a smaller framework such as Sinatra. On the other-hand if you are undertaking a medium to large scale project (and not…
If you have "self.parent_objects.children.function_nam" in your code base is a demeter violation (which I like to see as yet another code smell rather than a law or rule) that is telling you that you are probably missing a domain model. Mixins don't solve that either but hide the smell from you.
Re: Ruby Web Dev The Other Way
#20Yes, you shouldn't do Ruby development on Windows if at all possible. But is there any reason why OS X is not mentioned in the Linux section? It is after all what many Ruby developers use.
Because osx in not linux? (Although it does bundle some out of date gnu tools.) A separate osx section would seem more appropriate.