@sraps,
> The main problem about the OPenERP is that I can not imagine how OpenERP > could be used without skilled developer stuff, whether inhouse or outsorced, > it does not matter Unfortunately, you are absolutely right. But who hides it? If you can read French, read our 120 pages oss ERP's withepaper ( http://www.smile.fr/publications/livres-blancs/erp-open-source ), I clearly state what you are telling. That's why chosing an open source ERP is not yet for everybody, again it doesn't mean it isn't 200% useful for the companies having IT skills. but hey guys, my take on this is that IT skills matters every day more and more and open source is also taking the lead. So IMHO, IT skills are going to be pretty much like speaking English or not. I'm coming from mechanical engineering myself but then I decided I wouldn't miss the IT train, so I learned it myslef at home and I'm 100% happy I did so. Actually some times open source is presented like an hippie or communist vision of the world. That's pretty wrong (unfortunately may I say), actually in the open source there is no room for the loosers, much less room than in the proprietary model where things seems more stable, obvious and regulated (money drives). With the open source, nothing will save you if you can't code, you'll have to pay the bill and people who made the effort of learning code at home will take the lead. This have pro and cons, but like it or not this is the way it is. > > Anyway Python is oh so raw, immature, incomplete, geeky, and so rapidly > fluctuating (functions wonder between libraries to and forth just like that), > that I would never choose the one for a new project. Still it is surprising > that the OpenERP is pretty stable. BTW it would be interesting to hear why > Fabien chose one? > I would have chosen JRuby on Rails: stable features would have been done in Java (like the webserver, interfaces for base methods, the ORM eventually etc) But would absolutely have sticked with a dynamic language at the functional level - Ruby in that case. I've deeply looked at ERP's done fully in a static stable langage (like Java). In my opinion they are faileurs because they either have only very limited features like Compiere/OB, either have e feature/cost ratio so low that it make it inappropriate for Open source (again those two fail here too), and now they are thinking about more expensive pricing models which might be fine, but are border line for "open source" products. I've written a detailed explanation about my take on the choice of Python. See here: http://code.google.com/p/magento-openerp-smile-synchro/wiki/GettingStartedWithOpenERPDev Overall I find it a great real politic choice at the time it has been done because Ruby was hardly mature, JRuby on Rails wasn't there and even now I think it's still the way to gow as even if JRuby on Rails might bring some extra productivity % and some static safety, you would never reach the level OpenERP has now which is fine. Also, just like for Rails, yes Python is not the most safe language in the world: * since it's very terse 1 Python line is worse 5 Java lines so the codebase that need to be maintained is smaller, this is exponentially true as you get third party involved into the code: with Python that can understand the code, with a larger Java code base they wouldn't get the big picture. * OpenERP has a few unit tests/assertions which is gazillons better than what other open source ERP's offer. But they are still lacking an integration server IMHO. * when an open source softwares reaches a good popularity, the community will find/report bugs so the compiler might not do it, the community will do it to a certain extent. I think that's very much what is happening with Rails and why Sun dropped their Java JSF at the profit of it. And folks, my problem with you comparing OpenERP to proprietary is nobody invested millions in OpenERP yet. So what? It's free, you already have a lot for free, you don't pay, why would you toss the guys who overworked themselves to build OpenERP as it is? I'm not saying proprietary product are bad. Indeed in lot of case (but not all, that's the point) they are better. If you want a better OpenERP, nothing prevents you from investing in some way to make it happen (sraps, Bazaars stands here so that you can suggest those lines changes you are talking about, they are really reactive to good merge proposals), but otherwise I just think it isn't fair towards the guys who made it (not me). Think about that: they could very well have exit their engineering school and gone to work for nice big company with the $$$ their skills could provide them. That's just what 99.99% of Engineers are doing, they are not helping the society back in any way, they are only selling themselves at the price of the market, meaning to often working for hedge funds controlled companies for the more skilled ones like Fabien Pinckears. Instead of that, that guy stood up, and decided he would change the game. He decided he wouldn't have holidays for years and will totally overwork but ERP's will be different one day. Then what, you guys, come on here and just naysay: well not enough, product X, with $$$$ behind it is better? Think about what those guys did are doing and the choices yourselves made instead. So sorry, I'm a bit rude, but that's my point about comparing apples to apples. I think lots of us are totally OK if you come and say, well sadly features X in OpenERP is not good, it would be better done that way, I suggest doing that.... Then if you say this or mention an other open source product doing better in some area, I'm the first to think this is constructive indeed. Otherwise I think it's really some lack of respect that's why I might react the way I did. Peace. ------------------------ http://www.smile.fr -------------------- m2f -------------------- -- http://www.openerp.com/forum/viewtopic.php?p=26643#26643 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
