On Tue, Jan 26, 2010 at 4:21 PM, Adam Engst <[email protected]> wrote: > On Tue, Jan 26, 2010 at 3:25 PM, Tim Gray <[email protected]> wrote: >> I don't use Textmate (or made plugins), but I really like the Bundles thing >> they've got going on. If I were going to do plugins, I'd take a long hard >> look at how they do it. Pretty cool in my opinion. > > I was never able to wrap my head around TextMate because so much of > its functionality is in Bundles, but as I remember, they were all > segregated off in a huge Bundles menu, making the UI difficult to > discover. > > While I strongly support the idea of plug-ins as a way of extending > base functionality, they shouldn't be relegated to second-class > citizen status in the interface. > > cheers... -Adam >
There isn't an argument against plugins. The argument is against making the app a shell and implementing most if not all functionality through plugins. Its also about drawing the line of where does "base functionality" lay and thinking through the design of the app to allow it to grow into certain functionality, without having to do massive rewrites for version 2.0, 3.0, etc. People seem to just think you just start writing code and wander on down the path to greatness. Planning, roadmapping, and forethought are going to be essential to making this thing a success. Schlepping along through 1.0, doing "just enough to make it work," without putting any thought into direction or expansion in 2.0 and you're going to be running up blind alleys and into brick walls when you start. Been there. Done that. Code is 15% of a project. Planning and Documentation all but encompass the rest. _______________________________________________ [email protected] mailing list List help: http://lists.ranchero.com/listinfo.cgi/email-init-ranchero.com
