Bootstrap Maintainers Leave Twitter(blog.getbootstrap.com)
blog.getbootstrap.com
Bootstrap Maintainers Leave Twitter
http://blog.getbootstrap.com/2012/09/29/onward/
20 comments
Wow, big news for Bootstrap. I think Matt and Jacob realize the huge impact they've made on the web development community and the potential Bootstrap has to become the jQuery of HTML. New developers may begin to ask, "should I learn HTML or Bootstrap?" It's not a far-fetched idea because the same question is sometimes asked by beginners when "deciding between" jQuery and (vanilla) JavaScript. jQuery plugins are ubiquitous and are a large part its success. Bootsnipp (http://bootsnipp.com/) could be the start of a "markup plugin" community. Bootstrap has an impressive ecosystem for a front-end HTML framework and I think that is what sets them apart from the rest. Good luck, guys!
The whole "lets use jQuery without learning Javascript" thing didn't work out so well for the community.
Just a data point. I'm not saying I was right, but I learned to use jQuery first, which then lead me to learn vanilla JavaScript. Basic jQuery implementation (carousel, slider, slideshow, etc) was like following a recipe. It got me early gains. I eventually needed more custom work so I then dove (and continue to dive) into JavaScript.
I can see the same path for an HTML/CSS beginner.
I can see the same path for an HTML/CSS beginner.
If not for jQuery, I'd have probably never learned Javascript, because I would have gotten frustrated with dealing with weird cross-browser gotchas too much to ever get anything done.
As I learned I wrote a lot of code I'm not too proud of, looking back on it. But I grew to learn and love Javascript and I honestly have jQuery to thank for that.
As I learned I wrote a lot of code I'm not too proud of, looking back on it. But I grew to learn and love Javascript and I honestly have jQuery to thank for that.
Writing code you aren't proud of is step one towards writing code you are proud of.
Of course the problem with that is the code you ARE proud of rapidly becomes the kind you aren't proud of as you learn more.
Of course the problem with that is the code you ARE proud of rapidly becomes the kind you aren't proud of as you learn more.
We have a similar saying at the office. "Every programmer hates every other programmer's code. Given enough time, they'll eventually hate their own code."
Given that for a long while many JavaScript answers on SO were 'use jQuery' for very good reasons I can't help but think you're a bit out of touch.
Actually a bit is being kind. It's rare to come across a site not using jQuery. I write a fair few personal scraping scripts and it's very rare I actually have to add jQuery.
Actually a bit is being kind. It's rare to come across a site not using jQuery. I write a fair few personal scraping scripts and it's very rare I actually have to add jQuery.
[deleted](1)
jQuery might as well be a different language, like c++ vs. c. Can you learn c++ without c, or assembler without learning machine code? Sure.
Actually, in many ways I think learning jQuery before learning vanilla javascript can be an advantage. jQuery is heavy on functional programming techniques, list comprehensions, and such-like. As long as you learn well and don't cut corners I don't see any problems with "learning jQuery" on its own.
Actually, in many ways I think learning jQuery before learning vanilla javascript can be an advantage. jQuery is heavy on functional programming techniques, list comprehensions, and such-like. As long as you learn well and don't cut corners I don't see any problems with "learning jQuery" on its own.
I disagree, jQuery is more of a compatibility layer. Think of it (in a way) like an ORM for various SQL backends. They allow you to change between different SQL implementations without needing to learn the various nuances of each engine. The same can be said for jQuery, allowing you to modify classes even though browsers implement that DOM property differently.
I know you're being an asshole, but jQuery solves DOM query/manipulation pretty well. Generally, if you use javascript for DOM query/manipulation you're either really stupid or really smart, pick one.
I'd say neither--it's just after the first couple document.createElement, you're driven to the brink of insanity. No one chooses that kind of torture, smart or dumb.
jQuery has two big benefits for me: cutting down on verbosity a bit, and on making a cross-browser solution possible. For the latter various polyfills solve the problem effectively, but the verbosity problem still remains.
jQuery has two big benefits for me: cutting down on verbosity a bit, and on making a cross-browser solution possible. For the latter various polyfills solve the problem effectively, but the verbosity problem still remains.
no, but jQuery is a great way to learn how to write javascript, because it gives you a good framework of basic functionality.
The handwritten code I used to use for element detection was a thing of evil, that kept on getting cut-and-pasted around because it worked.
The conciseness and cleanness of using jQuery was a welcome change.
The handwritten code I used to use for element detection was a thing of evil, that kept on getting cut-and-pasted around because it worked.
The conciseness and cleanness of using jQuery was a welcome change.
I've begun thinking of Bootstrap as something like a front-end version of WordPress. It has so much potential to lay the foundation for anything web, whether traditional websites or rich web apps.
I entirely agree about the jQuery analogy. There is going to be a huge Bootstrap ecosystem - again similar to WordPress as well as jQuery. It's kind of a problem for the web when this happens, in that it creates the kind of fragmentation the web should ideally avoid, but it's a reality nonetheless that technologies like this are going to be two steps ahead of the standards.
Just seeing the various Bootstrap themes sites is exciting. When I've looked for themes in the past, there are very few focusing on rich HTML5 apps. Mostly just static websites and WordPress stuff. That's just one area which has changed since Bootstrap, as it's now possible to build a theme around standard higher-level constructs.
I entirely agree about the jQuery analogy. There is going to be a huge Bootstrap ecosystem - again similar to WordPress as well as jQuery. It's kind of a problem for the web when this happens, in that it creates the kind of fragmentation the web should ideally avoid, but it's a reality nonetheless that technologies like this are going to be two steps ahead of the standards.
Just seeing the various Bootstrap themes sites is exciting. When I've looked for themes in the past, there are very few focusing on rich HTML5 apps. Mostly just static websites and WordPress stuff. That's just one area which has changed since Bootstrap, as it's now possible to build a theme around standard higher-level constructs.
Funny you should mention WordPress.
Just yesterday, Joomla, the next largest CMS behind WordPress, launched a latest version, entirely built with Bootstrap: http://joomla.org/3/
That's a not-insignificant % of the web right there that's moving to Bootstrap.
Just yesterday, Joomla, the next largest CMS behind WordPress, launched a latest version, entirely built with Bootstrap: http://joomla.org/3/
That's a not-insignificant % of the web right there that's moving to Bootstrap.
I like bootstrap, but only for bootstrapping my project...or using it for backend/admin styling. Bootstrap is really just a style guide (with some good styles for layout), however if you've got design comps to work from, it's probably better to make your own style guide. I mean, if they could somehow accomplish making this process easier, then that'd be a game changer: basically less like a framework and more like a library.
EDIT a good example: If you wanted to rebuild hacker news, would you start with bootstrap? I wouldn't
EDIT a good example: If you wanted to rebuild hacker news, would you start with bootstrap? I wouldn't
You could have a look at my style guide/documentation generator StyleDocco: http://jacobrask.github.com/styledocco/
FWIW, Kickstrap has some crowd already http://ajkochanowicz.github.com/Kickstrap/
Off topic - Does anyone here remember the post someone wrote awhile here about how they got a boat load of hits by basically paying attention to what was popular here and then writing about it? Thanks in advance...
I think I understand what you said :)
Hm, I'll be the asshole and point out something that to me is kind of obvious: Bootstrap isn't mainstream enough to warrant it's own foundation/organization.
Just looking at the caliber of other projects that have gone this way (at the top of my head: Apache, Drupal, Django, Zope...) and looking at Boostrap I don't think it's even close to the userbase/clout needed to pull this off. Even the maintainers of those other projects, successful as they are, tend to have a day job.
I don't know, maybe I'm reading too much into this, but I think it might be a little to early to make this move. Just my 2c.
Just looking at the caliber of other projects that have gone this way (at the top of my head: Apache, Drupal, Django, Zope...) and looking at Boostrap I don't think it's even close to the userbase/clout needed to pull this off. Even the maintainers of those other projects, successful as they are, tend to have a day job.
I don't know, maybe I'm reading too much into this, but I think it might be a little to early to make this move. Just my 2c.
> Bootstrap isn't mainstream enough to warrant it's own foundation/organization
What do you mean by "not mainstream enough?" Organizations on Github are simply a convenient place to put one or more projects that are collectively worked on by a group of individuals and do not necessarily have a single core maintainer.
What do you mean by "not mainstream enough?" Organizations on Github are simply a convenient place to put one or more projects that are collectively worked on by a group of individuals and do not necessarily have a single core maintainer.
Yeah, that's what a lot of people seem to be missing here: there's mention of an open-source organization on GitHub but no mention that fat and mdo want to start working on Bootstrap full-time and make money off of it.
I didn't see where in the post, or comments here where that was said. Do you have a source?
The grandparent of my comment, for instance.
Sorry, what I meant by "mainstream" is "have enough of a following". You can say a lot of good things about Bootstrap, and to be fair most of them are probably right, but even when you compare to other jQuery libraries/framework it must have... what, maybe 5% of the users? Also, it's a very young project, it's not an established de facto piece of technology like Django is when it comes to Python web frameworks, Rails to Ruby web frameworks, or Apache is to HTTP servers.
Did I make myself a bit clearer? :)
Did I make myself a bit clearer? :)
While it's not nearly as old as those projects, it may be used by the same order of magnitude of people. Both bootstrap and jQuery itself are officially hosted on Github:
jQuery - 16,896 watching, 2,314 forks
bootstrap - 38,026 watching, 8,836 forks
I recall, from an issue I was dealing with, that a year ago Twitter didn't really give @mdo and @fat any time to work on bootstrap during normal business hours... yep, here it is https://github.com/twitter/bootstrap/issues/377#issuecomment... (edit to fix link)
This is great -- an open source project started within a company, then spun off into its own independent entity. It's really great to see that.
Major kudos to the team and to Twitter for having the generosity to acknowledge a responsibility to the community that extends past their ownership of the project they've created. Thanks. :)
Major kudos to the team and to Twitter for having the generosity to acknowledge a responsibility to the community that extends past their ownership of the project they've created. Thanks. :)
Bootstrap creator here.
tl;dr: <3, Jacob and I quit Twitter, he's going to Obvious, I'm going to GitHub, it's been amazing, nothing but love, Twitter is great, no ill will, Bootstrap is going to keep going, <3.
First, thanks for the love everyone! Jacob and I love seeing people as excited about the future of Bootstrap as us. We're hopeful that this is just the beginning of it. And now, onto answering some of the questions/comments folks have brought up here thus far.
Jacob left over a month ago and my last day is next Friday (10/5). He's going to Obvious, and (announcing it here for the first time) I'm going to GitHub.
The timing has nothing to do with a disagreement about Bootstrap (seriously, none what so ever), and more to do with us both wanting a change in our own lives for what we do day-to-day. Twitter, the company and product, are both amazing and Jacob and I have worked there for 2.5 years. We're stoked for our next things and we both want to keep working on Bootstrap no matter what. We have an obligation to the community and know it could go much further. (Oh, and yes, I screwed up the date on the post. My bad, yo.)
Bootstrap was created by me at Twitter as a means to make better looking internal tools (I wrote about this on A List Apart awhile back: http://www.alistapart.com/articles/building-twitter-bootstra...). It started off as a simple HTML/CSS thing, then Jacob built plugins on top of it, and we open sourced it together. We made it at Twitter, so when we wanted to open source it, we went to Twitter to ensure it was good to go. Thus, it was named Twitter Bootstrap (originally, "Bootstrap, from Twitter" actually). Now, it's back to just "Bootstrap".
We don't really think of it as the next jQuery, Django, or Drupal. But you can't deny there is something to front-end frameworks like Bootstrap, and that's what we're excited about. HTML and CSS are the two easiest and most basic building blocks of websites. Everyone knows and uses them, and that's a big part of why Bootstrap has grown so much, and can continue to grow more.
No, we weren't "given time" to work on Bootstrap, but that's because it was a project I started on my own to help other engineers. Jacob came in to shape it into a proper open source project and then wrote all the JavaScript plugins (Fun fact: before the jQuery plugins, he wrote a MooTools library on top of it called Tit, which is a type of bird). Anyway, we weren't given time because it wasn't a company priority, naturally, and we're okay with that. We worked on it, at the office or at home, whenever we wanted and folks were generally okay with that as well.
The move to making Bootstrap its own project and organization is a joint one, between myself, Jacob, and Twitter's Open Source team (@cra). The transition will take time, but we need to grow Bootstrap beyond the two of us and Twitter, and into something more. There is really sooooo much potential for making better things on the Web, and we're hoping we can keep that up with the help of the community.
Anyway, we're both stoked to keep working on Bootstrap. It's a great project that can be so much better, and that's pretty damned awesome to us. Twitter has been amazing for both of us and will continue to down the road. We wish nothing but the best for everyone we've worked with.
<3
tl;dr: <3, Jacob and I quit Twitter, he's going to Obvious, I'm going to GitHub, it's been amazing, nothing but love, Twitter is great, no ill will, Bootstrap is going to keep going, <3.
First, thanks for the love everyone! Jacob and I love seeing people as excited about the future of Bootstrap as us. We're hopeful that this is just the beginning of it. And now, onto answering some of the questions/comments folks have brought up here thus far.
Jacob left over a month ago and my last day is next Friday (10/5). He's going to Obvious, and (announcing it here for the first time) I'm going to GitHub.
The timing has nothing to do with a disagreement about Bootstrap (seriously, none what so ever), and more to do with us both wanting a change in our own lives for what we do day-to-day. Twitter, the company and product, are both amazing and Jacob and I have worked there for 2.5 years. We're stoked for our next things and we both want to keep working on Bootstrap no matter what. We have an obligation to the community and know it could go much further. (Oh, and yes, I screwed up the date on the post. My bad, yo.)
Bootstrap was created by me at Twitter as a means to make better looking internal tools (I wrote about this on A List Apart awhile back: http://www.alistapart.com/articles/building-twitter-bootstra...). It started off as a simple HTML/CSS thing, then Jacob built plugins on top of it, and we open sourced it together. We made it at Twitter, so when we wanted to open source it, we went to Twitter to ensure it was good to go. Thus, it was named Twitter Bootstrap (originally, "Bootstrap, from Twitter" actually). Now, it's back to just "Bootstrap".
We don't really think of it as the next jQuery, Django, or Drupal. But you can't deny there is something to front-end frameworks like Bootstrap, and that's what we're excited about. HTML and CSS are the two easiest and most basic building blocks of websites. Everyone knows and uses them, and that's a big part of why Bootstrap has grown so much, and can continue to grow more.
No, we weren't "given time" to work on Bootstrap, but that's because it was a project I started on my own to help other engineers. Jacob came in to shape it into a proper open source project and then wrote all the JavaScript plugins (Fun fact: before the jQuery plugins, he wrote a MooTools library on top of it called Tit, which is a type of bird). Anyway, we weren't given time because it wasn't a company priority, naturally, and we're okay with that. We worked on it, at the office or at home, whenever we wanted and folks were generally okay with that as well.
The move to making Bootstrap its own project and organization is a joint one, between myself, Jacob, and Twitter's Open Source team (@cra). The transition will take time, but we need to grow Bootstrap beyond the two of us and Twitter, and into something more. There is really sooooo much potential for making better things on the Web, and we're hoping we can keep that up with the help of the community.
Anyway, we're both stoked to keep working on Bootstrap. It's a great project that can be so much better, and that's pretty damned awesome to us. Twitter has been amazing for both of us and will continue to down the road. We wish nothing but the best for everyone we've worked with.
<3
Foundation Evangelist, ZURB's Chief Instigator here.
As a leader, it's often difficult to see your hard working employees move on to other opportunities. And you hope deep down that the lessons they learn from you along the way will be remembered as influencial in their career. Mark had a great run at ZURB before Twitter. I wish him the best.
For ZURB's current employees, and the ones that put thinking into developing Foundation, it's important for me to make sure they receive credit for the contributions they have made to the design community that extend beyond what Mark remember's Bootstrap to be (or wants it to be) or what Foundation has become. The first iteration of Bootstrap emerged from the work ZURB did over the last few years prototyping with our clients. In fact, the initial Bootstrap push had direct lines of code and copy taken from ZURB's work on what today is Foundation 1.0.
When you see Mark's history conveniently rewritten as "I developed Bootstrap," it's important for me to make sure that those who contributed to it's initial core from ZURB are recognized. There were many ZURBians who put countless hours into writing code and laying down the vision for a css framework before Mark "envisioned" this solution for his Twitter engineers. Talented designers at ZURB even shared that vision with Mark as part of our refinement of Foundation 2.0 before it was launched.
Foundation (http://foundation.zurb.com) is fine and kicking and we benefit from the global awareness of css-frameworks. ZURB is quite happy about that and we'll continue to evolve our solution to benefit the community. I want to make sure talented product designers like Jonathan Smiley and Matt Kelly, who helped envisioned the idea, get credit for their contributions for making stuff like this possible. These guys are my heroes and I hope that you see that as well in the code they write and share.
As a leader, it's often difficult to see your hard working employees move on to other opportunities. And you hope deep down that the lessons they learn from you along the way will be remembered as influencial in their career. Mark had a great run at ZURB before Twitter. I wish him the best.
For ZURB's current employees, and the ones that put thinking into developing Foundation, it's important for me to make sure they receive credit for the contributions they have made to the design community that extend beyond what Mark remember's Bootstrap to be (or wants it to be) or what Foundation has become. The first iteration of Bootstrap emerged from the work ZURB did over the last few years prototyping with our clients. In fact, the initial Bootstrap push had direct lines of code and copy taken from ZURB's work on what today is Foundation 1.0.
When you see Mark's history conveniently rewritten as "I developed Bootstrap," it's important for me to make sure that those who contributed to it's initial core from ZURB are recognized. There were many ZURBians who put countless hours into writing code and laying down the vision for a css framework before Mark "envisioned" this solution for his Twitter engineers. Talented designers at ZURB even shared that vision with Mark as part of our refinement of Foundation 2.0 before it was launched.
Foundation (http://foundation.zurb.com) is fine and kicking and we benefit from the global awareness of css-frameworks. ZURB is quite happy about that and we'll continue to evolve our solution to benefit the community. I want to make sure talented product designers like Jonathan Smiley and Matt Kelly, who helped envisioned the idea, get credit for their contributions for making stuff like this possible. These guys are my heroes and I hope that you see that as well in the code they write and share.
Interesting, I had not heard of Foundation before, and am interested in checking it out to see how it does with the few things that annoy me about Bootstrap. So appreciate the pointer.
But when I go to the Foundation web pages... I've clicked like 5 times, have managed to get to the Getting Started page, and I still haven't seen any code examples of how to actually use it. Note that the Bootstrap docs start with and are centered around examples; it _starts_ by telling you how to install it and start using it. Every 'feature' element on the home page is right next to a code example showing how to do it.
I think Bootstrap's documentation is actually a huge part of it's success. If you're wondering why Bootstrap caught on where Foundation didn't, I think that's probably part of it. Foundation's docs _look_ as pretty as Bootstrap's (which is a good sign given the nature of the products), but they aren't done as well for getting people to dive in quick or overview of how the code actually works quick. Writing good docs is a skill of it's own, and whoever does it for Bootstrap has definitely got it. You can get started with Bootstrap _so_ fast, because the docs are written with that goal in mind and achieve it.
But when I go to the Foundation web pages... I've clicked like 5 times, have managed to get to the Getting Started page, and I still haven't seen any code examples of how to actually use it. Note that the Bootstrap docs start with and are centered around examples; it _starts_ by telling you how to install it and start using it. Every 'feature' element on the home page is right next to a code example showing how to do it.
I think Bootstrap's documentation is actually a huge part of it's success. If you're wondering why Bootstrap caught on where Foundation didn't, I think that's probably part of it. Foundation's docs _look_ as pretty as Bootstrap's (which is a good sign given the nature of the products), but they aren't done as well for getting people to dive in quick or overview of how the code actually works quick. Writing good docs is a skill of it's own, and whoever does it for Bootstrap has definitely got it. You can get started with Bootstrap _so_ fast, because the docs are written with that goal in mind and achieve it.
Wow, I had no clue, but assumed Foundation sprung from BS. I like that Foundation is lighter and easier to override than BS, and even though it has a similar look, it's decidedly different than the stock, ubiquitous bootstrap design. But lack of IE8 support makes it a bit of a hard sell. I'm excited to see what's in store for both frameworks, but hope to see Foundation continue as a leaner, less opinionated alternative.
I really like Foundation based on the same points you raised.
It does support IE8, minus the responsive stuff, it's < IE8 that it doesn't (http://foundation.zurb.com/docs/support.php), and that's a deal breaker for me and why I've never used it since most of the sites I build still get around 10-12% from IE7.
You could use the older version of Foundation, but that doesn't appeal to me either.
It does support IE8, minus the responsive stuff, it's < IE8 that it doesn't (http://foundation.zurb.com/docs/support.php), and that's a deal breaker for me and why I've never used it since most of the sites I build still get around 10-12% from IE7.
You could use the older version of Foundation, but that doesn't appeal to me either.
I use foundation at work. We have the rule that "make the site look fine in IE7", where it has to work but it doesn't have to be perfect.
You can use foundation 3.1 with the htc boxing fix [1] that fixes the grid problems with IE7.
I love use foundation over BS, since BS (to me atleast) is more of a UI decision, where you build your site from scratch with foundation).
[1] https://github.com/Schepp/box-sizing-polyfill
You can use foundation 3.1 with the htc boxing fix [1] that fixes the grid problems with IE7.
I love use foundation over BS, since BS (to me atleast) is more of a UI decision, where you build your site from scratch with foundation).
[1] https://github.com/Schepp/box-sizing-polyfill
I am reminded of the classic MBA example of Pullman coaches. Pullman did not invent the concept but made it work commercially. The result was his predecessors had long and successful careers in the railway engineering industry.
I respect your defence of your people and much kudos to you. I would not fear for their futures - they have shipped a much respected product, and inspired a calling card product.
Good luck
I respect your defence of your people and much kudos to you. I would not fear for their futures - they have shipped a much respected product, and inspired a calling card product.
Good luck
@chiefinstigator, thanks for this backstory and huge respect to the ZURB Foundation team. My only complaint is that I think you could made your point better without digging at Mark.
Hey Bryan, good to hear from you again. It's been roughly two years since we even spoke to each other, let alone saw each other in public. Before I dive into it, I have always and will continue to always have nothing but the best wishes for ZURB. Now, to get to it.
You did teach me a lot, Bryan, and I know the (edit: removed the number) ex-ZURBians would agree with you on that. You taught me about design process, design thinking, and how to communicate well with clients and other designers. Moreover, if you hadn't brought me out to California, I wouldn't be where I am today. Thanks again for that, I really do owe you one there. You taught us a lot more, but we don't need to go into that as I'm sure everything that drove us away has changed for the better.
Yes, Bootstrap emerged from my work at ZURB, but more importantly, from the entire web community. Before I redesigned ZURB.com or wrote nearly the entire ZURB Style Guide (at least the CSS and Design Patterns sections), frameworks and style guides were already in high demand and influencing our work at ZURB. You can take a look at the CSS section here: http://d.pr/i/uoGb. I have screenshots of every page of the project from right before I left.
It's important to note that I never worked on Foundation, nor had any idea it was in the works until it was released on 10/14/2011, two months after Bootstrap was released (https://twitter.com/ZURB/status/124984359135608832). In fact, it was Dave Gamache, former ZURB designer and now former Twitter designer, who wrote a majority of Foundation 1.0 after I left ZURB. Go ahead and ask him (@dhg) about that for more details.
However, I did copy and paste code, but never from Foundation. The things Bryan is referring to are "how to" docs, lorem ipsum and filler text, and examples for the address tag, emphasis tags, lists, and blockquotes. Looking at the very first commit to Bootstrap (https://github.com/twitter/bootstrap/tree/eb81782cdbdc68aaeb...), four months before we released v1.0, you can see that content there. I have made no attempt to hide it, nor could I. In the hundreds of following commits, I removed nearly all that code before launching BS1.0, but I missed some (the items listed above). Within days, I removed it and replaced it with my own code, copy, and examples. Edit: for full transparency, you can see Bootstrap 1.0 and the offending content at http://d.pr/i/Rn9r.
I made an honest mistake that any developer can by using code from the work I did at my previous employer, but I also fully rectified it immediately by removing all the offending code and replacing it with my own.
I made a mistake early on by using the work I had done at ZURB as a basis for everything I have done since then. In the theoretical sense, that is never frowned upon, but in the practical, it is, and I'm sorry about that. But I never ripped Foundation, nor ever intend to. If anything, you need to take a fresh look at Foundation 3 and ask yourself who's really taking code from the other's framework. (edit for clarification).
Ever since Bootstrap 2.0 came out, you've ripped nearly every single component we created in our framework and added it to Foundation, including: the basics of our grid system, navbar, responsive navbar, breadcrums, alerts, labels, tooltips, popovers, prepended and appended inputs, breadcrumbs, accordion, progress bars, image styles, and more. All of those were in Bootstrap first, and you've added them without even batting an eye. We've also added things that other frameworks and products added, but when you're calling me out for ripping something I never had access to, you really need to take a step back and look at what you've done as well.
I have no illusions about how I got to where I am: I thank everyone profusely, day in and day out, for making it possible. I made the mistake of using the work I did at ZURB to start a brand new project, and I apologize for doing it that way and corrected the mistake within days. I never stole from Foundation, nor do I ever plan to.
You did teach me a lot, Bryan, and I know the (edit: removed the number) ex-ZURBians would agree with you on that. You taught me about design process, design thinking, and how to communicate well with clients and other designers. Moreover, if you hadn't brought me out to California, I wouldn't be where I am today. Thanks again for that, I really do owe you one there. You taught us a lot more, but we don't need to go into that as I'm sure everything that drove us away has changed for the better.
Yes, Bootstrap emerged from my work at ZURB, but more importantly, from the entire web community. Before I redesigned ZURB.com or wrote nearly the entire ZURB Style Guide (at least the CSS and Design Patterns sections), frameworks and style guides were already in high demand and influencing our work at ZURB. You can take a look at the CSS section here: http://d.pr/i/uoGb. I have screenshots of every page of the project from right before I left.
It's important to note that I never worked on Foundation, nor had any idea it was in the works until it was released on 10/14/2011, two months after Bootstrap was released (https://twitter.com/ZURB/status/124984359135608832). In fact, it was Dave Gamache, former ZURB designer and now former Twitter designer, who wrote a majority of Foundation 1.0 after I left ZURB. Go ahead and ask him (@dhg) about that for more details.
However, I did copy and paste code, but never from Foundation. The things Bryan is referring to are "how to" docs, lorem ipsum and filler text, and examples for the address tag, emphasis tags, lists, and blockquotes. Looking at the very first commit to Bootstrap (https://github.com/twitter/bootstrap/tree/eb81782cdbdc68aaeb...), four months before we released v1.0, you can see that content there. I have made no attempt to hide it, nor could I. In the hundreds of following commits, I removed nearly all that code before launching BS1.0, but I missed some (the items listed above). Within days, I removed it and replaced it with my own code, copy, and examples. Edit: for full transparency, you can see Bootstrap 1.0 and the offending content at http://d.pr/i/Rn9r.
I made an honest mistake that any developer can by using code from the work I did at my previous employer, but I also fully rectified it immediately by removing all the offending code and replacing it with my own.
I made a mistake early on by using the work I had done at ZURB as a basis for everything I have done since then. In the theoretical sense, that is never frowned upon, but in the practical, it is, and I'm sorry about that. But I never ripped Foundation, nor ever intend to. If anything, you need to take a fresh look at Foundation 3 and ask yourself who's really taking code from the other's framework. (edit for clarification).
Ever since Bootstrap 2.0 came out, you've ripped nearly every single component we created in our framework and added it to Foundation, including: the basics of our grid system, navbar, responsive navbar, breadcrums, alerts, labels, tooltips, popovers, prepended and appended inputs, breadcrumbs, accordion, progress bars, image styles, and more. All of those were in Bootstrap first, and you've added them without even batting an eye. We've also added things that other frameworks and products added, but when you're calling me out for ripping something I never had access to, you really need to take a step back and look at what you've done as well.
I have no illusions about how I got to where I am: I thank everyone profusely, day in and day out, for making it possible. I made the mistake of using the work I did at ZURB to start a brand new project, and I apologize for doing it that way and corrected the mistake within days. I never stole from Foundation, nor do I ever plan to.
@markdotto, thank you for your response @chiefinstigator's comments. Great to hear your perspective. I don't think you needed to be on the defensive as much as you are. All one needs to do is look at the Bootstrap Github page: all your code, its documentation, issue tracking, the sheer number of commits, etc. to know that you and Jacob worked your absolute fucking assess off with/for an absolute fucking shit ton of developers over the last few years. I understand both the ZURB and Bootstrap teams' feelings are raw considering how much time you all put in, and I'm just writing to hope that things will smooth over as time goes on. Both groups contributed so much to the web community for them not to. Again, great work guys, you've changed the world for the better.
Thanks man, appreciate that, and I hear you. I tried to maintain my cool and approach it as diplomatic and honestly as I could. This has been brewing for awhile and we have never responded, so I wanted to give as much context as possible. There is still much that could be said, but we'll save that for another time. I truly think all of us are just interested in making stuff on the Internet, and that's all I really care about: making awesome stuff with awesome people. Thanks again. <3
+++ <3 back
First time I see Foundation, you're being extremely polite with this issue, You guys diserve much more credit.
Hey, first off - I absolutely <3 LOVE <3 ZURB's Foundation, especially the latest 3.x releases. ALL of you all who have contributed to it, be it in it's infancy (@markdotto) or more recently/throughout it's development (@chiefinstigator), you've all been a part of creating an fscking awesome framework that I've been using since 2.0 was first released. I don't know the history between the two of you but I have a feeling neither Foundation OR Bootstrap would be the great frameworks they are today without the hard work both of you all and your colleagues have done. I understand where chiefinstigator is coming from, wanting to be recognized and having credit given where it is due, and it seems to me that Mark/markdotto has done that here and now on HN in this very thread by acknowledging that Bootstrap evolved from some of the work done by himself and others at ZURB.
(I love hearing about these connections/relationships between developers and companies!)
I think that the emergence of two of the best html5/css frameworks out there is a great thing and can only help developers and the internet as a whole. Let's not forget the spirit of Open Source - the ability to share, build upon, and innovate on the hardwork of others and in turn build better code, better products, and a better experience for both developers and end-users. Rinse. Repeat. That's a good thing.
I applaud you all for your contributions to the development community. Both of you and your respective teams are an inspiration to not just myself but I'm sure tens of thousands of other developers as well. Keep up the great work, keep releasing code, and have fun doing it.
NOW. @chiefinstigator - I'm working on a project based on Foundation 3.1.1 and am attempting to use the sub-nav navigation menu, and from what I can tell, none of the examples in the documentation work. Unless I'm supposed to be changing the 'active' class to the currently selected menu item manually... what gives? Here is the Gist - https://gist.github.com/2980502#file_f3_subnav.html i've included the navigation plugin and made the call to $(document).foundationNavigation(); as described in the documentation. What am I missing? One note, on each of the dd elements I have a method that is handling the onclick() event. Could this be the problem? (Just thought about that...)
EDIT/ADDED: Can we get a little friendly competition going on here.... ZURB and Bootstrap users/evangelists alike..... what's going on here?
(I love hearing about these connections/relationships between developers and companies!)
I think that the emergence of two of the best html5/css frameworks out there is a great thing and can only help developers and the internet as a whole. Let's not forget the spirit of Open Source - the ability to share, build upon, and innovate on the hardwork of others and in turn build better code, better products, and a better experience for both developers and end-users. Rinse. Repeat. That's a good thing.
I applaud you all for your contributions to the development community. Both of you and your respective teams are an inspiration to not just myself but I'm sure tens of thousands of other developers as well. Keep up the great work, keep releasing code, and have fun doing it.
NOW. @chiefinstigator - I'm working on a project based on Foundation 3.1.1 and am attempting to use the sub-nav navigation menu, and from what I can tell, none of the examples in the documentation work. Unless I'm supposed to be changing the 'active' class to the currently selected menu item manually... what gives? Here is the Gist - https://gist.github.com/2980502#file_f3_subnav.html i've included the navigation plugin and made the call to $(document).foundationNavigation(); as described in the documentation. What am I missing? One note, on each of the dd elements I have a method that is handling the onclick() event. Could this be the problem? (Just thought about that...)
EDIT/ADDED: Can we get a little friendly competition going on here.... ZURB and Bootstrap users/evangelists alike..... what's going on here?
Well said.
If you need support for the top bar, shoot us an email, [email protected]. Happy to help.
If you need support for the top bar, shoot us an email, [email protected]. Happy to help.
If you had invented Bootstrap, you would have invented Bootstrap.
Assuming what you are saying is true, credit would have been nice though.
Assuming what you are saying is true, credit would have been nice though.
Because history clearly shows that the rightful people always get credit. Ignoring things like Edison vs. Swan (invention of light bulb), or Marconi vs. Tesla (invention of radio), and likely hundreds of others cases that could be listed if I felt like typing that much. I know nothing about GP's post/claim, but dismissing claims offhand with some glib line from a movie is not really adding much enlightenment.
Taking someone else's work and presenting it as your own is okay now?
Well, both works are open licensed (bootstrap and foundation), so legally there should be no problem (if Bootstrap credited the original code.... which it doesn't).
Nope not okay.
However:
- How much of Bootstrap's is directly lifted from Foundation? Or was it mostly the idea? _Execution_ makes or breaks. Vision and ideas complement execution.
- And Bootstrap's success isn't just because of the code alone. It was the packaging, and the selling.
However:
- How much of Bootstrap's is directly lifted from Foundation? Or was it mostly the idea? _Execution_ makes or breaks. Vision and ideas complement execution.
- And Bootstrap's success isn't just because of the code alone. It was the packaging, and the selling.
And maybe the fact that it had Twitter's name behind it?
I just started using foundation and just wanted to say thanks! It's a great front end framework. It does not get enough love in the community.
markdotto: you may not think of Bootstrap as "the next JQuerym, Django, or Drupal," but to me (and many others here, I'm sure), it's already a de facto standard for building web app UIs. THANK YOU, and congratulations on the recent move to you and Jacob.
Thanks for the insights & fun facts.
After also reading this: http://blog.getbootstrap.com/2012/09/29/onward/ I still don't get what this actually means for the future of BS, is it good news, or bad news, is everyone too polite?
Good to be remembered here of Foundation again. I was recently asked for BS alternatives and couldn't named any.
After also reading this: http://blog.getbootstrap.com/2012/09/29/onward/ I still don't get what this actually means for the future of BS, is it good news, or bad news, is everyone too polite?
Good to be remembered here of Foundation again. I was recently asked for BS alternatives and couldn't named any.
All the best two you both. I can say with certainty that many people in the web dev world love BS and are continuing to eagerly await new changes that will come as a result of the moves.
Best of luck at Github, huge win for you both.
Best of luck at Github, huge win for you both.
Thank you for bootstrap, its a very wonderful tool.It's success is evident from the large developer community.With tools like jets rap and bootsnip , this is just the beginning.
Great Otto, thanks and thanks for the Framework, is just perfect for starting to create valids, flexible, fast and responsive websites.
Good days at Github :)
Thanks for the Bootstrap! Been using it for a while now and having fun with it. I never tried front-end framework before but Bootstrap made my life easier!
Congrats Github!
Just speculating here, but this doesn't exactly sound like it was blessed by Twitter: "Bootstrap will remain a Twitter project on GitHub for the time being, but we've realized the project has grown beyond us and the Twitter brand."
If this was something Twitter believed too, I imagine there would be some fanfare around this, Twitter helping FLOSS and all that.
More to this story?
If this was something Twitter believed too, I imagine there would be some fanfare around this, Twitter helping FLOSS and all that.
More to this story?
You have to take a pragmatic perspective here as well. I'd wager that the only reason Bootstrap is a Twitter project to begin with is because of the assignment clause of most employment agreements: If you develop something at a company, the company owns it.
I can't imagine any managers at Twitter were sitting there thinking "Hey, I have this great idea that will make us boatloads of money! Let's release an open-source html/css/js framework that makes it super easy for anyone to make a site that looks like Twitter."
In all likelihood, it was a project that the developers wrote for internal ops and later attempted (and succeeded) to open source. If you look at the Impact Graph on github (https://github.com/twitter/bootstrap/graphs/impact), you can see that it's pretty much Jacob and Mark's project.
From Twitter's perspective, they can either let Jacob and Mark continue to run with it at no real cost to themselves (since it's open source and they can still use Bootstrap), or they can try to find someone within the organization to continue to maintain it, which has a very real cost -- developer time. Given that they may not find someone to fill that role and that forcing someone into it would probably be bad for the project, I think the decision makes a lot of sense for Twitter.
I can't imagine any managers at Twitter were sitting there thinking "Hey, I have this great idea that will make us boatloads of money! Let's release an open-source html/css/js framework that makes it super easy for anyone to make a site that looks like Twitter."
In all likelihood, it was a project that the developers wrote for internal ops and later attempted (and succeeded) to open source. If you look at the Impact Graph on github (https://github.com/twitter/bootstrap/graphs/impact), you can see that it's pretty much Jacob and Mark's project.
From Twitter's perspective, they can either let Jacob and Mark continue to run with it at no real cost to themselves (since it's open source and they can still use Bootstrap), or they can try to find someone within the organization to continue to maintain it, which has a very real cost -- developer time. Given that they may not find someone to fill that role and that forcing someone into it would probably be bad for the project, I think the decision makes a lot of sense for Twitter.
It sounds to me like the two guys left twitter and have decided to continue work on bootstrap. Being open source is there a reason they can't? I don't know much regarding the rules of open source but is it possible they could just fork it and continue where they left off (without twitters blessing)?
Isn't fork possible solution? Always?
It's interesting that they both left at the same time. There must have been an internal disagreement about their role in relation to Bootstrap--or perhaps Twitter is just a really sad place to work these days.
They didn't. I believe Jacob left few weeks ago.
I really hope they can move to bootstrap full / part time and really kickstart it into something that merges bootswatch with wrapbootstrap.. I want to give bootstrap money.. this is a good step :)
Does this mean we can finally have semicolons?
Bravo!
I realise bootstrap isn't for everyone, but in my humble line of work (specialist web apps in the ----- industry) it is an absolute godsend.
Great move away from Twitter. May the winds be forever at your backs.
Great move away from Twitter. May the winds be forever at your backs.
Hopefully their newfound time won't lead to unnecessary bloat for what is currently a beautiful framework. Keep it simple, keep it small, keep it clean.
I wished there would have been something like Bootstrap 10-12 years ago. As a developer it would have made my life a lot easier. Since design is not really my area of expertise, I often struggled to make a decent backend/administration area for my applications. I started to use Bootstrap recently and can't believe how much fun it is to use and how much quicker I'm getting results.
Anybody else notice that the date in the post is set to Sept 29th? Do you think this was supposed to be published tomorrow instead of today?
Probably just a typo, I posted after reading this: https://twitter.com/mdo/status/251806421715390464
With all of the great extensions people have developed for Bootstrap so far, It's clear that they're really on to something. I can't wait to see what direction they take it in after severing ties with Twitter.
I'm very interested to see what direction the project moves toward, albeit a little bit concerned. Best of luck to Jacob and Mark on their next steps.
Is it only me or does anyone else have an issue with the name "Bootstrap"?
I've now gone through multiple tutorials where the term is used to refer to Bootstrap from twitter or the general idea of bootstrapping an app.
Now each time I read "bootstrap" I've to establish the context which gets especially tricky when the same documentation or tutorial uses both Bootstrap from Twitter and the verb "to bootstrap".
I've now gone through multiple tutorials where the term is used to refer to Bootstrap from twitter or the general idea of bootstrapping an app.
Now each time I read "bootstrap" I've to establish the context which gets especially tricky when the same documentation or tutorial uses both Bootstrap from Twitter and the verb "to bootstrap".
Bootstrap is a great starting point - please keep up the great work!
great move on their part, there is a huge future ahead of these guys. good luck to them.
It would be great if Bootstrap becomes a part of Apache Software Foundation
Bootstrap badly needs a really good tutorial. I'm thinking of making one, if anybody wants to help out, my email address is in my profile.
I was thinking I'd build a simple and attractive site from scratch and make the tutorial a step-by-step of how it was done, so even somebody with no HTML or CSS experience could do it - but also so that even experienced programmers would quickly learn all sorts of cool things that Bootstrap can do.
This is how I'm learning Rails right now - the Rails tutorial is amazing. Bootstrap needs something similar.
I was thinking I'd build a simple and attractive site from scratch and make the tutorial a step-by-step of how it was done, so even somebody with no HTML or CSS experience could do it - but also so that even experienced programmers would quickly learn all sorts of cool things that Bootstrap can do.
This is how I'm learning Rails right now - the Rails tutorial is amazing. Bootstrap needs something similar.
Yes! Bootstrap has some hierarchy things you have to pick up on to get desired effects. Some kind of guide would be nice. I'm not sure if they've updated it since but a few months ago I was building a layout and had to resort to the inspector tool to figure out the exact way they did things in the examples.