On 19 Feb 2014, at 16:03, Kumar McMillan <[email protected]> wrote:
> > On Feb 18, 2014, at 5:52 PM, Fred Wenzel <[email protected]> wrote: > >> Hello everyone! >> >> For developers, building apps on the Web platform can pose a >> fragmentation problem: For every development concern, there are often a >> dozen or more possible options to consider, without clear pros or cons. >> Web developers can feel intimidated not simply by their choices, but by >> how _similar_ their choices are. >> >> While this openness and community is a virtue, it leads to "choice >> paralysis" and the wrong impression that the Web is a harder platform to >> develop for than more restrictive alternatives. >> >> However, by making strong, informed recommendations to developers, we >> can help turn the variety of development tools available on the Web from >> a daunting proposition into an empowering one. >> >> A great example of this is the significant attention[1] tofumatt's >> localForage[2] project has received. It provides a cross-platform, >> asynchronous storage library that "just works". With its straightforward >> API, it _removes_ an entire monotonous development choice for >> developers. The community honored this drastic simplification with >> almost 2000(!) "stars" on github in just a few days. >> >> Furthermore, we have a responsibility to our developers to ensure that >> certain frameworks, libraries, etc., have been tested and work well with >> our own and (eventually) other target platforms. >> >> Our developer-facing groups (Apps Engineering, Developer Relations and >> Developer Tools in particular) are collaborating to expand this effort >> systematically across the various parts of the development experience. >> >> >> Some projects that are already in flight include: >> >> - web-components-based (featuring Brick) app templates that work out of >> the box >> - additional such components for hard, yet common problems such as >> scrolling of large lists > > Sounds like a fantastic idea! > >> - Mozilla-endorsed framework and tool chain for apps > > Instead of Mozilla-endorsed might we consider community-endorsed? i.e. > endorsed by a community of experts. If we want to make Mozilla the central > authority we just need to plan for what to do when our ratings go stale. For > example, should we revisit each endorsement periodically? The state of tech > changes so fast; this makes me think crowd sourcing it might be more > effective. +1 to community-endorsed. Great idea. _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
