Kanban relies on sensory intuition. Org-mode requires you to build up a whole new epistemological relationship to the elements of an outline. They are pretty different, and Org-mode requires a _lot_ of time investment.
I'm confused. Clojure doesn't have Reagent either. ClojureScript does. And Reagent is a pretty straightforward React wrapper, not so different from Rum. What do you think makes it special? Even Rum renders server-side.
This is what blows my mind about their decisions regarding software priorities. Being able to build Macintosh apps on a Macintosh was fundamental to the survival of the platform. Hell, there isn't even a coherent story about developing client-side web applications on an iPad, something much simpler—the interpreter's already there!
It's "Basecamp", not "BaseCamp". I'd also recommend rethinking the phrase "work-life balance" because it creates a dichotomy contrasting work against life, which is silly. Work is merely a part of life, and for some people who hold the same values as you seem to (like me), the phrase "work-life balance" is a dogwhistle for a kind of mere lip service to the idea, rather than a real embrace of it.
You can directly edit files in a repository using Working Copy. You access it like any other external file store using iA Writer. You can push changes from Working Copy.
What glory? All these points were acquisitions. Everything this article celebrates were destroyed by Yahoo. The only thing they ever did well was build a portal.
Yeah. Perhaps this is a good metric of ecosystem and developer productivity, and would make for a good extensive blog post: how long does it take to implement users, with password resets and security and everything being just so? With rails, it's, what, an early afternoon with devise and some associated gems? What else has that? Again, not perfect, not tailored, but most people don't wear tailored clothes, and don't need tailored clothes, either. I'll be happy if I get one paying user in a few months when I'm ready to show this thing off. (Edit: I just watched a meteor tutorial doing exactly this and now I feel a pull to remake everything. Jeez.)
It's easy to forget that most people are just starting out (by definition; most people quit or stop), most people just want to make something, and for that, there's nothing better than rails. I'm in this boat. I just want this thing I thought of and designed to be real, and now after doing Hardtl's tutorial and reading/coding for two days, my thing's basic MVP is real. I've never really done a web app before except for some experiments in Clojure. But I'm not programming it in clojure, a language I like better than Ruby and know a lot better than Ruby, because there's no opinionated framework, there are no models, there's nothing even close to rails and activemodel and all that. I just want to make the thing. That's what most infant-sized things are: babies. And to make the baby you make it in rails and deploy it on heroku. If it sticks, remake it in something else if it really does have scaling problems. But most things don't succeed, and if they do, they probably won't succeed at the scale where it matters at all that they were written in rails. (This is a statistical argument.)