The all-new Basecamp is live
11–20 of 156 posts
Re: The all-new Basecamp is live
#12Re: The all-new Basecamp is live
#13 > Object.keys(bcx.models)
["PersonOrGroup", "Bucket", "BucketAccess", "Calendar",
"CalendarEvent", "Project", "Person", "CalendarDisplay", "Todo"]
> Object.keys(bcx.models.Todo.prototype)
["constructor", "isAllDay", "isTimed", "urlRoot", "getBucketPath",
"showPath", "bucket", "doesOccurOn", "doesOccurOnOrAfter",
"doesOccurBetween", "getDueDate", "summary"]Re: The all-new Basecamp is live
#14Re: The all-new Basecamp is live
#15Re: The all-new Basecamp is live
#16I want to migrate, but...
> Basecamp Classic and the new Basecamp don't offer the same features, so some data in Classic won't make it into the new Basecamp.
So maybe I'll stay. But wait...
> Will you continue to improve Classic? The majority of our design and development efforts moving forward will be focused on the all new Basecamp, but we'll continue to support Classic as long as customers continue using it. We expect that to be for many many years.
Maybe. Maybe not. The web moves very quickly you know. New browsers, standards, security risks etc. I can think of a million and one reasons Classic will get EOL'd sooner rather than later.
This is certainly faithful to their backwards compatibility intolerance. The new product couldn't be bound by the "burden" of the old. Now I the customer am left with a very distasteful choice to make.
Re: The all-new Basecamp is live
#17Re: The all-new Basecamp is live
#18Re: The all-new Basecamp is live
#19I notice the new version is running on basecamp.com. The old version is at basecamphq.com and 37signals always made a point about the domain not mattering as much as the product name. I imagine there's a follow-up to that saying that if your product becomes successful there's nothing wrong with going and grabbing the pure domain (thinking Dropbox, Instagram and others. Or basically the opposite of Color.)