One of the things to be aware of: The hottest tech gadget on the market, the iPhone, has a pitiful connection speed, and by all benchmarks is incredibly slow when compared with a desktop (even an old one).
For the company I'm building product for now, we have a significant number of customers who still use dial-up, which isn't well supported. This summer we'll be going back and reworking portions of our application to better work with dial-up. With this in mind, library optimizations, including concern for library size, are critically important. If there is a feature you need, you're always welcome to hack/modify/ override parts of the Prototype library. I do. TAG On Jul 3, 2007, at 11:22 AM, Sebastian Sastre wrote: > On 3 jul, 11:50, Christophe Porteneuve <[EMAIL PROTECTED]> wrote: >> It's not about economics, it's about feature bloat... > Well, if computers came back to have 16K and networks 2 kbps we all > will certainly justify a lot of optimizations. But if we are > programing for the near future I think we should think big not small > so using stinginess of features as a default criteria for essential > features just does not make me feel comfortable (nor yesterday not > todays!). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
