Live data from Hacker News

RIP Jekyll (The Genesis of the Jamstack)

bridgetownrb.com

21–30 of 187 posts

Re: RIP Jekyll (The Genesis of the Jamstack)

#21
I use Jekyll for a static site and I guess I just don't really understand why it needs further development. I haven't upgraded my version of Jekyll since I think 2017 because it does what it says on the tin.

Sometimes it's ok for software to be "done".

Re: RIP Jekyll (The Genesis of the Jamstack)

#22

Earlier quoted context omitted.

Well if you want to reach lots of developers, you have to be where they are, and they're on Twitter and Discord—for better or worse. :shrug:

Mastodon and Matrix instead?

Not for mainstream projects - plus those places tend to become political mudwaters, because freedom in tech has become political the past few years.

Re: RIP Jekyll (The Genesis of the Jamstack)

#24

Earlier quoted context omitted.

Well if you want to reach lots of developers, you have to be where they are, and they're on Twitter and Discord—for better or worse. :shrug:

Mastodon and Matrix instead?

No one is on Mastodon or Matrix.

Re: RIP Jekyll (The Genesis of the Jamstack)

#25
post #24

Earlier quoted context omitted.

Mastodon and Matrix instead?

No one is on Mastodon or Matrix.

I certainly wish people were on Mastodon (haven't tried Matrix yet). I ran a Mastodon instance for some time. The experience was decent but discovery was terrible, and discovery is what makes Twitter (for example) so compelling.

Re: RIP Jekyll (The Genesis of the Jamstack)

#26

I loved Jekyll, and still do. This is a sad state, and I hope both that it improves and Jekyll survives. I switched to Zola for most of my stuff a while back, and while there are still gaps, it does everything I need and is production ready. https://www.getzola.org/

I use Zola for my project website. As someone who had never built a website before, I tried several static site builders but only really succeeded in getting a tweakable theme working with Zola.

Re: RIP Jekyll (The Genesis of the Jamstack)

#27
post #13

> Open source in 2021 looks like: > Engagement on Twitter > Official Discord chat room Cherry picked from a list with 4 others elements that I agree with, but the first two are terrible. Twitter is getting more and more closed (you can't see some stuff without being logged in now) and for Discord you have to create an account to see the content. Both are not free software. Reading stuff around free software shouldn't…

> Engagement on Twitter

> Official Discord chat room

No. Not at all. Many very popular OSS projects don't use Twitter or Discord. Any time you say "all OSS projects use technology X", be it GitHub or Twitter or whatever, the only thing you can be sure of is that the statement is wrong. Some projects may, sure, but that's different.

Probably the only "technology" you can say they generally use is a web page.

It is reasonable to say "they have 1 or more ways to interact, and that's clearly identified on their web page". But assuming that everyone uses the same communication mechanism is demonstrably false.

Re: RIP Jekyll (The Genesis of the Jamstack)

#28
post #4

What do people use besides Jekyll?

My work has moved largely from Ruby to JS, so I've been enjoying Gatsby! It's probably overkill for simple sites, but I like how customizable it is.

For React-based projects, I would advocate for Next.js…but yeah, unless you know you need React for very specific reasons, it's definitely overkill. =)

Re: RIP Jekyll (The Genesis of the Jamstack)

#30
post #17

Hi, original Jekyll "core team" (if it could be called that) member here - just wanted to say thanks for writing this up, and I had no idea about the current status of the project or that one of the maintainers recently passed away. That all being said: I think it's ok for OSS projects to "pass on" - and hopefully be replaced by better ones! I wish we had a better way of recognizing this for projects or talking about…

Closely related, I wish we had a better way of saying a library or product is now feature-complete. We use recent commit activity as a proxy of viability, but all of that churn could just as easily be an indication of immaturity. It's okay for tools to achieve their objectives and just live on as stable code with maintenance releases as needed.

To my mind, Jekyll is feature-complete. The only changes I've needed to make to my Jekyll site are dealing with breakages from backwards-incompatible updates. I've been hosting with GitHub Pages for the past 12 years and I largely don't even have to think about it. It's nice.

Post reply on HN