4 ms·
Yes. We wrote a webapp in PHP. It has actual paying customers, and handles billing and invoices for real money. As is so common with PHP projects, as we need
by papsosouid 14y ago
Yes. We wrote a webapp in PHP. It has actual paying customers, and handles billing and invoices for real money. As is so common with PHP projects, as we needed to keep adding features, changing functionality, etc it got difficult to maintain, and hard to make changes without adding bugs.
So, we re-wrote it in scala using lift. We were not pleased with the results. So we re-wrote it in scala using play. We were even less pleased. So we re-wrote it in haskell using snap. We were finally happy. That version is now in production, and the type safety of haskell makes doing changes far safer. The maintenance burden is much smaller now.
- happywolf 14y agoThanks for sharing. Could you elaborate why you were not pleased with the previous experience with Scala? The project was hard to maintain? Or it couldn't take heavy hitting of requests? Or it has limitation for multi-programmers kind of work?
- papsosouid 14y agoScala wasn't really the problem, lift and play were. Scala is fine, although it did feel like using an ugly crippled haskell at times. Lift and play both presented us with a bad combination of being both immature (which means lots of missing functionality) and opinionated (which means forcing you to do things their half-finished, not really working way). We ended up using snap in haskell which is just as immature, but because it isn't opinionated, it is easy to fill in the missing bits however you please,