Changeset View
Changeset View
Standalone View
Standalone View
src/docs/flavor/project_history.diviner
Show All 28 Lines | |||||
number of features like inline commenting, CLI support and git support (Facebook | number of features like inline commenting, CLI support and git support (Facebook | ||||
was 100% SVN in early 2007 but 90%+ of Engineers worked primarily in git with | was 100% SVN in early 2007 but 90%+ of Engineers worked primarily in git with | ||||
SVN bridging by 2010). As these patches were contributed pretty much randomly, | SVN bridging by 2010). As these patches were contributed pretty much randomly, | ||||
it also gained a lot of performance problems, usability issues, and bugs. | it also gained a lot of performance problems, usability issues, and bugs. | ||||
Through 2007 and 2008 Evan worked mostly on frontend and support infrastructure; | Through 2007 and 2008 Evan worked mostly on frontend and support infrastructure; | ||||
among other things, he wrote a static resource management system called Haste. | among other things, he wrote a static resource management system called Haste. | ||||
In 2009 Evan worked on the Facebook Lite site, where he built the Javelin | In 2009 Evan worked on the Facebook Lite site, where he built the Javelin | ||||
Javascript library and an MVC-flavored framework called Alite. | JavaScript library and an MVC-flavored framework called Alite. | ||||
But by early 2010, Diffcamp was in pretty bad shape. Two years of having random | But by early 2010, Diffcamp was in pretty bad shape. Two years of having random | ||||
features grafted onto it without real direction had left it slow and difficult | features grafted onto it without real direction had left it slow and difficult | ||||
to use. Internal feedback on the tool was pretty negative, with a lot of | to use. Internal feedback on the tool was pretty negative, with a lot of | ||||
complaints about performance and stability. The internal XTools team had made | complaints about performance and stability. The internal XTools team had made | ||||
inroads at fixing these problems in late 2009, but they were stretched thin and | inroads at fixing these problems in late 2009, but they were stretched thin and | ||||
the tool had become a sprawling landscape of architectural and implementation | the tool had become a sprawling landscape of architectural and implementation | ||||
problems. | problems. | ||||
Show All 18 Lines |
Content licensed under Creative Commons Attribution-ShareAlike 4.0 (CC-BY-SA) unless otherwise noted; code licensed under Apache 2.0 or other open source licenses. · CC BY-SA 4.0 · Apache 2.0