Latest news for viagra sales u.k
This post is intended as a discussion piece, if you have any thoughts about anything mentioned here then please add a comment. Don't be afraid, it's just some friendly open debate :) If your post on your own blog about this discussion let me know and I'll update this post with links to your posts.
Recently I'd been hearing a lot about (RoR) and decided, like any diligent tech person, that I had better investigate it to make sure I'm not missing the boat on something new in the marketplace. I brought the books and did the tutorials. I also built a couple of basic sites on my own with RoR and they were fun to build. However, having come this far I'm finding it difficult to come up with a compelling reason why I would want to jump ship completely.
I thought I'd sum up with my top 5 concerns at the moment:
Issue one
The Rails framework has some compelling features like scaffolding however while that initially "hooks" you in and makes you think it's fantastic you soon find that scaffolding up a solution is almost pointless because you nearly always have to write something considerably different to just CRUD pages. This initial development speed enhancement doesn't actually end up helping you out that much. It harms people more than it helps them by having the misconception that scaffolding is actually a very useful feature of rails (it has its place, but it's just not that important).
Issue two
Ruby's performance just doesn't seem to compare well with most other languages. admittedly you take a hit with any scripting language but the performance hits seem quite severe. (I couldn't find any . Net comparisons at the time of writing this) it seems apparent that Ruby is abysmal in the speed arena. You could argue that there are ways to optimise the code to run better or that you can just scale up your hardware but I just want a fast language. There seems to be so much code churn in the Rails framework that optimising for performance may be difficult to do until it has [viagra sales u.k] a stabalised feature set. Why is Ruby so slow? I think enough things on computers are slow enough these days without opting for something at the back of the pack. Viagra sales u.k can anybody provide evidence that ruby isn't so slow?
issue three
ide's are lacking. I've used RadRails and I've a friend who uses and neither seem to provide anywhere near the functionality that I'd expect from a modern IDE. I'm always happy working with light weight IDEs but when I need to get a large application off the ground I'm always thankful when I have an industrial strength IDE to help me manage it.
Issue four
RoR seems to have new versions released often. Too often. Now viagra sales u.k, the geek in me loves the idea of having new features to play with every couple of weeks however from a business point of view it just increases the risk considerably. I remember the fallout from RoR being upgraded to a new version and all of the blogs based on . You could freeze the version that an application worked against but it seemed like everything just fell apart for a lot of people when that version was rushed out. I'm all for the cool little team pumping out new features all the time but sparing a thought for the web hosts who have to test the framework before deployment, the people who deploy solutions on it and the developers who have to upgrade the version that their application supports constantly would be nice.
Issue five
All of the other issues are only really issues because of this point - I just cannot see how RoR scales up to develop truly large solutions. Perhaps it's not really intended for more than basic websites? Some of the generators designed to save you time would simply hinder your ability to actually maintain large solutions nicely in my opinion.
These are some issues that have me feeling that RoR might not be as ready for the primetime as many would have you believe. Perhaps I'm wrong. Perhaps you know reasons why these points are not issues. If so, then please leave a comment about why you think so. Comparing these issues to my current web framework of choice - ASP. Net - I don't think RoR stacks up well enough in my mind. I realise there are areas that it lacks that RoR does well however other vendors such as Microsoft are working hard to cover viagra sales u.k these areas as well (, etc).
Disclaimer: I do spent a significant amount of my time developing solutions using the Microsoft . Net Framework. I've not always been a . Net developer, I also have spent considerable amount of time developing in various other languages such as Java, PHP, C/C++, Delphi to name a few and of course dabbling with RoR :)
- JD
Links:
- makes his first ever post and pulls no punches :)
- thinks I'm stirring and has some links to the WellRailed convo
- doesn't take part in the discussion but brings his own perspective to RoR in general
RSS Feed