4 ms·
Just curious what you mean by "if you look at what it does, it's all vanilla stuff". What would "non-vanilla stuff" look like? It's all just code, right?
by benjismith 11y ago
Just curious what you mean by "if you look at what it does, it's all vanilla stuff".
What would "non-vanilla stuff" look like?
It's all just code, right?
- eric_h 11y agoI think he means "all the things that Rails handles well with default options/configurations"
- erichmond 11y agoIf you look at their feature list (https://basecamp.com/3/features https://basecamp.com/3/features) you see: - Message boards - comment threads. - Real-time chat/pings. - Automatic check-ins. - To-do lists. - Docs & file storage. - A centralized schedule Everything in this list sans real-time chat I would consider as low complexity, low volume and low velocity. It's basically request a view, hit a cache / db, display some data. Send an email now and again. Store some stuff on s3 now and again. There are lots of sites that have more complex feature sets then what basecamp does. Things like complex transcoding of media, real-time updates on their views, streaming of complex media types, need for near-real-time integration with 3rd party APIs, real-time bidding, real-time decision making, real-time analytics, etc etc etc. I want to be very clear that I am not criticizing Basecamp as a product. Simplicity is difficult to achieve in software and their product does a great job of doing most of what you need, and not much else. I based the software stack of the first company I founded on pre-1.0 rails monolith (mongrel had just been released), so I'm not even anti-monolith. I just think this particular post of his is entirely too simplistic and could lead younger software designers astray.
- goldbrick 11y agoReal-time chat isn't even that complex, especially now that Rails has ActionCable.