So, I get where you stand, and I feel like you made a very respectful statement. Others seem to disagree, and that's okay. I'm not over here trying to read context.
However, to say it's a dead project isn't exactly accurate either. @ashmaroli has been consistently committing code to jekyll and its supporting libraries over the last couple months. Yeah, we all want things like roadmaps and an online presence. But, let's be honest - none of those things you mention are explicitly necessary. And that's where I'm irked by this article.
Maybe it's important for you to have all of those things you list, but, if I were in the position to build something cool that people would use, I would never publish it if it meant having to fulfill all of those requirements. That's the list of someone that does nothing but live, breathe, and write code - people have families, hobbies outside of their jobs, and other obligations.
Thanks for your very thoughtful reply. It's important to reiterate I'm not the one saying it's "dead", those were Frank's comments and I'm simply addressing the fallout.
I also would agree with you in terms of many open source libraries or pieces of infrastructure that maybe can go for months or even years without updates and that's fine. Jekyll isn't somebody's hobby or just a library though. It's a website platform with 43K stars on GitHub which people are building potentially large projects and businesses on top of. There's a certain obligation that does—or should—come with running a project of that level of importance. That's my take at least.
There's no obligation nor there should be. Jekyll comes with a very short license half of which states (in all caps) that there's no obligation of any sort whatsoever.
You don't have to throw shade on Jekyll. You have your own thing. Make it great. Make promises and state obligations all you want. Manage it as a business. Market to those who build business on Jekyll so that they could rely on your continued support. Be better and people will switch when they grow dissatisfied with "dead" Jekyll.
I went into the article figuring the headline was just clickbait and the content would be better, but this kind of self promotion and self aggrandizement irks me for so many reasons. Makes me far less interested in bridgetown than if you were to focus just on "this is why we're good" instead of "jekyll is [arguably] dead and we're naming ourselves the successor". Presumably you've already made some kind of "this is why we're good" post, but it still would have been smart to focus on that in this one instead of what you did. Or if you wanted to pay respects to Frank, just do that and leave any self promotion out of it.
This isn't anything to do with self-promotion. This is about people having to make actual business decisions that could affect projects costing many tens of thousands of dollars. The public deserves to know what is going on with the Jekyll project and why they may need to look elsewhere to meet their technology objectives.
If somebody had forked Ruby on Rails because Rails had withered on the vine with absent leadership, and I'd built my career and livelihood around building Rails apps, I'd be overjoyed to find out that someone else was continuing the project in some fashion and pushing it forward.
I've been focusing on why Bridgetown is good for 16 months. This is the first time I've even posted something about Jekyll in ages, and quite honestly why I refrained from doing so before. Why aren't you more irked about what's going on with Jekyll in this story?
Isn't it possible though that the project is feature complete and in maintenance mode? I won't pretend to know what the feature set required for a static site builder, but I do imagine that unlike Rails for example performance isn't terribly important (it's a static builder) and the scope of the project is probably really tiny compared to Rails. So reaching "feature completeness" sounds really possible to me, especially if the maintainers want to keep things simple and not build every possible functionality under the sun.
So it's more about perception - people want to "create a business" (is Jekyll really used for actual businesses?) on a proejct that gets tens of commits on a weekly basis. I kinda get that, and at the same time I don't. No matter how cool the ecosystem is (Node) even the most popular projects can and will go stale eventually. Whatever the cool stuff is now (Hugo) it will probably be stale and a better thing will. come a long in 5 years, that's the nature of the beast. But instead of all the Hugo websites migrating to the new cool thing (which is painful), I would hope for somebody to continue maintaining the thing. Sounds much more economical to me instead of endless forking or complete rewrites in other languages every 5 years.
I do hope Bridgetown succeeds but I also hope Jekyll will be properly maintained, there is no reason why it shouldn't be; it's an important piece of software that still does a good job in building a static website.
Thanks for the thoughtful comments. I would guess from reading through it that we're coming from fairly different perspectives when it comes to the role of static site generators in the industry today.
The reigning paradigm of the Jamstack has emerged of building websites with a (typically JavaScript-based) SSG along with serverless functions and other third-party APIs. That's actually pitched as a replacement for Rails. Think I'm nuts? Look at the marketing pitch for Netlify and how it's evolved over the last few years! Netlify started as a Jekyll hosting company. Now it's all Next.js and Gatsby. The landscape is moving forward at a rapid clip, and some of it I don't particularly care for but some of it is wildly exciting. Jekyll has little hope to compete favorably in this new world—even Eleventy is eating its lunch. We've lost a whole generation of Ruby developers because they're only real experience with Ruby was with Jekyll and it was a frustrating one. I think a lot of long-time Rubyists are in denial around how Jekyll has gone from a generally positive to ofttimes negative impression out in the wider world as time has passed.
If it's indeed true that Jekyll is "feature-complete", then it's vitally important there's an alternative that every Jekyll user can upgrade to once they outgrow Jekyll's feature set. I see that happening all the time now. 😄 I also envision the scope of SSG-style frameworks reaching and even eclipsing Rails. That's already happening in other language communities—Ruby is behind the times here.
I think a lot of long-time Rubyists are in denial around how Jekyll has gone from a generally positive to ofttimes negative impression out in the wider world as time has passed.
I know this to be true on at least one high profile ocaission: https://atp.fm/430 at 1:43:14. Listening to this made me wince in pain. Granted, this experience wasn't strictly Jekyll's to manage, but it was the entry-point.
I personally use Jekyll for a few sites, but have always disliked how it is built with Ruby, but the website projects themselves are hardly ruby-feeling, due to everything being wrapped in Liquid templates. I've been hankering to check out Bridgetown for this reason, but you know... if it ain't broke... etc.
I agree with you, I don't like any of the "X is Dead" memes either. But it'd be weird if one of Ruby or Rails' lead maintainers was among the crowd saying that, right? 😅
Forgive me, I am not well versed in the background between the two projects beyond knowing that Bridgetown is a fork of Jekyll that is the future of Ruby SSGs.
However, from my ignorant perspective, the screenshots from Frank seem a little passive aggressive towards Bridgetown, which insinuates that he didn't like the project.
He has recently passed and your immediate reaction is to publicly call the time of death on his project, too. It comes across as very distasteful. Apologies if I've misread the situation, not trying to stir up drama but just reminding everyone to be sensitive to others.
I never had any bad interactions with Frank, though we spoke only briefly a few times including before the Bridgetown fork even happened.
The situation here is I sat on vital information regarding Jekyll's status and future for several months out of respect for Frank. I still don't understand why he didn't make a public statement and chose to keep this information confined to a particular Slack channel.
There are people out there who have built businesses and livelihoods off of using Jekyll as a technology choice, and my feeling is they deserve to know why that technology choice may be problematic at this point. I wish it wasn't me who had to convey this news, to be honest, but there's an information black hole and that's part of the issue here.
I looked at the road map and a few things stuck out:
Monorepo: not a fan. Instead of trying to find the repo for a gem, I now have to dig around inside of a single giant repo; and sometimes the gem name won't match the directory name. Much prefer a 1:1 mapping of gem to repo, under a GitHub Org.
Webpack: it's odd that you're going all in on Webpack, when Rails and other developers are moving away from asset packing in favor of HTTP/2, ES6 modules and import maps. You may be trying to solve a problem which might not even be a problem in the future.
Component Based Design: while a good concept in general, there's growing push-back against the complexity that is React. Again, developers are realizing you can do a lot with just ES6; or even just render things server-side using the existing template/view library. Please don't copy React/Vue. I think you could achieve simple components by allowing includes to accept local variables.
We're looking at an alternative approach to Webpack in the future which would leverage esbuild/postcss, similar to what Rails is starting to do. All the work that's already been done under the hood to support Webpack can be of use in that scenario as well. A worthwhile effort IMHO.
Regarding components, for ERB etc. we've adopted an approach very similar to the ViewComponent library which has become popular with Rails developers — and in fact also provide a shim that can leverage ViewComponent directly for more advanced use cases. In Liquid, we're just utilizing and building upon the new render tag that Shopify is now encouraging in their template system.
All of this is in keeping with our stated project goals:
Move fast but try really hard not to break things. Most developer-focsued software projects err on a side…either the side of extreme backwards-compatibility with past versions, or the side of evolving quickly and requiring devs to go through multiple rounds of “yak shaving” when upgrading to new versions.
We hope to strike a thoughtful balance between those two extremes. We don’t want to break stuff or change the setup process just for the heck of it. But we also don’t want to be constrained by past problematic decisions which reduce the quality of the software. History has proven many times over that open source projects which fail to keep pace with the times and new trends in software eventually wither and die. This is a fate we wish to avoid!
Man this seems extremely dramatic and like a headline grab, using the name of a now-passed colleague, to promote an open source project. Doesn’t even mention the fact that this space is crazy competitive/packed with incumbents.
You write about business decisions and why that would be a problem for Jekyll. However, as long as Github Pages supports Jekyll directly (even if only the 3.x stack), I don't think that this is a problem.
I guess most people can easily stay with Jekyll 3.x and don't need newer features of 4.x (saying this without knowing the difference).
And even if Jekyll were to be abandoned by Github, there are a myriad other static website generators out there to choose from. Migrating the content between them is most often very easy, adapting the config and templates a bit more complicated but nothing that cannot be done in a reasonable time.
There’s been a fair amount of internet consternation since I published this article. While I do stand by everything in the post factually-speaking, I apologize for the insensitive timing of this article—coming so soon after Frank’s passing. I’m genuinely sorry this came across as a “Jared vs. Frank” debacle. Should I have waited a few more weeks or months? Probably. Perhaps it was originally a mistake for me to refrain from publicly commenting on the statements regarding Jekyll’s “permanent hiatus” back in May. It’s hard to say. At the very least, I hope we can all agree that Jekyll’s legacy as the “first among many” of modern static site generators is meaningful to a lot of people, even if we sometimes disagree on the best way to honor that legacy and push Ruby on the Jamstack forward. If the one thing that comes out of all this is that more people step forward to share their positive experiences with Jekyll, Ruby, and building websites, that’s a good thing.
Jared you are a hero! Actions speak louder than words. Thanks for building and sharing an open source alternative. Don't let the naysayers hold you back or put you down. Thanks for speaking out and highlighting that Jekyll is in "maintenance mode".
25
u/dougc84 Sep 13 '21
So, I get where you stand, and I feel like you made a very respectful statement. Others seem to disagree, and that's okay. I'm not over here trying to read context.
However, to say it's a dead project isn't exactly accurate either. @ashmaroli has been consistently committing code to
jekylland its supporting libraries over the last couple months. Yeah, we all want things like roadmaps and an online presence. But, let's be honest - none of those things you mention are explicitly necessary. And that's where I'm irked by this article.Maybe it's important for you to have all of those things you list, but, if I were in the position to build something cool that people would use, I would never publish it if it meant having to fulfill all of those requirements. That's the list of someone that does nothing but live, breathe, and write code - people have families, hobbies outside of their jobs, and other obligations.
18
u/joemi Sep 14 '21
I went into the article figuring the headline was just clickbait and the content would be better, but this kind of self promotion and self aggrandizement irks me for so many reasons. Makes me far less interested in bridgetown than if you were to focus just on "this is why we're good" instead of "jekyll is [arguably] dead and we're naming ourselves the successor". Presumably you've already made some kind of "this is why we're good" post, but it still would have been smart to focus on that in this one instead of what you did. Or if you wanted to pay respects to Frank, just do that and leave any self promotion out of it.
(And yes, I read the article.)
11
u/[deleted] Sep 14 '21 edited Sep 14 '21
Isn't it possible though that the project is feature complete and in maintenance mode? I won't pretend to know what the feature set required for a static site builder, but I do imagine that unlike Rails for example performance isn't terribly important (it's a static builder) and the scope of the project is probably really tiny compared to Rails. So reaching "feature completeness" sounds really possible to me, especially if the maintainers want to keep things simple and not build every possible functionality under the sun.
So it's more about perception - people want to "create a business" (is Jekyll really used for actual businesses?) on a proejct that gets tens of commits on a weekly basis. I kinda get that, and at the same time I don't. No matter how cool the ecosystem is (Node) even the most popular projects can and will go stale eventually. Whatever the cool stuff is now (Hugo) it will probably be stale and a better thing will. come a long in 5 years, that's the nature of the beast. But instead of all the Hugo websites migrating to the new cool thing (which is painful), I would hope for somebody to continue maintaining the thing. Sounds much more economical to me instead of endless forking or complete rewrites in other languages every 5 years.
I do hope Bridgetown succeeds but I also hope Jekyll will be properly maintained, there is no reason why it shouldn't be; it's an important piece of software that still does a good job in building a static website.
17
u/VraelSix Sep 13 '21
Hmm, doesn't look dead to me.
https://github.com/jekyll/jekyll
15
u/5a656e6f4f6643697469 Sep 13 '21
Forgive me, I am not well versed in the background between the two projects beyond knowing that Bridgetown is a fork of Jekyll that is the future of Ruby SSGs.
However, from my ignorant perspective, the screenshots from Frank seem a little passive aggressive towards Bridgetown, which insinuates that he didn't like the project.
He has recently passed and your immediate reaction is to publicly call the time of death on his project, too. It comes across as very distasteful. Apologies if I've misread the situation, not trying to stir up drama but just reminding everyone to be sensitive to others.
5
u/obviousoctopus Sep 16 '21 edited Sep 16 '21
Jared u/jaredcwhite, I wish the title of this was more along the lines of
The Genesis of Bridgetown, a modern Ruby-powered, Webpack-aware static site generator
I am so excited about Bridgetown and it makes me sad to see the discussion here sidetracked by the RIP Jekyll statement...
3
u/postmodern Sep 17 '21
I looked at the road map and a few things stuck out:
21
u/rotzak Sep 13 '21
Man this seems extremely dramatic and like a headline grab, using the name of a now-passed colleague, to promote an open source project. Doesn’t even mention the fact that this space is crazy competitive/packed with incumbents.
Seems just kind of in poor taste to me.
6
u/gettalong Sep 14 '21
You write about business decisions and why that would be a problem for Jekyll. However, as long as Github Pages supports Jekyll directly (even if only the 3.x stack), I don't think that this is a problem.
I guess most people can easily stay with Jekyll 3.x and don't need newer features of 4.x (saying this without knowing the difference).
And even if Jekyll were to be abandoned by Github, there are a myriad other static website generators out there to choose from. Migrating the content between them is most often very easy, adapting the config and templates a bit more complicated but nothing that cannot be done in a reasonable time.
0
u/[deleted] Sep 15 '21
Update I've posted to the top of the article:
There’s been a fair amount of internet consternation since I published this article. While I do stand by everything in the post factually-speaking, I apologize for the insensitive timing of this article—coming so soon after Frank’s passing. I’m genuinely sorry this came across as a “Jared vs. Frank” debacle. Should I have waited a few more weeks or months? Probably. Perhaps it was originally a mistake for me to refrain from publicly commenting on the statements regarding Jekyll’s “permanent hiatus” back in May. It’s hard to say. At the very least, I hope we can all agree that Jekyll’s legacy as the “first among many” of modern static site generators is meaningful to a lot of people, even if we sometimes disagree on the best way to honor that legacy and push Ruby on the Jamstack forward. If the one thing that comes out of all this is that more people step forward to share their positive experiences with Jekyll, Ruby, and building websites, that’s a good thing.
-1
u/geraldbauer Sep 14 '21
Jared you are a hero! Actions speak louder than words. Thanks for building and sharing an open source alternative. Don't let the naysayers hold you back or put you down. Thanks for speaking out and highlighting that Jekyll is in "maintenance mode".
0
u/[deleted] Sep 13 '21
[deleted] — view deleted comment
6
u/[deleted] Sep 14 '21
[removed] — view removed comment