RIP Jekyll (The Genesis of the Jamstack) • Hacker News Board

Re: RIP Jekyll (The Genesis of the Jamstack)

#41

Post by nirvdrum » Mon, Sep 13, 2021, 6:55 PM UTC

skrtskrt wrote: post #33

nirvdrum wrote: post #30

Earlier quoted context omitted.

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 m…

Even if the core project is feature complete and excellent, "death" can come from a lack of continued creation and maintenance of 3rd party integrations or plugins. Personally I found Jekyll plugins lacking and those that were good seemed pretty old/unmaintained. However I only moved to Hugo from Jekyll just because I didn't want to deal with Ruby gem installation and dependency management. I am not a Ruby dev by any…

That's fair. Having to set up a Ruby installation to run a utility just isn't fun. Especially when the expectation is that you don't use the system-provided Ruby. You're supposed to go use a Ruby version manager and set all of that up. And that rough experience can contribute to its death, for sure. I just don't think "has few commits in the last month" is a great reason to declare a project as dead, especially one providing the backbone of GitHub Pages.

Re: RIP Jekyll (The Genesis of the Jamstack)

#42

Post by abricot » Mon, Sep 13, 2021, 6:56 PM UTC

eatonphil wrote: post #8

Personally I don't find static site generators worth the effort to learn or keep up-to-date as versions inevitably come. I end up just writing my own for each site in 1-200 lines of Python. It's normally just a markdown library and a template engine wrapped with a file system walker. Here's an example: https://github.com/eatonphil/notes.eatonphil.com/blob/master... . It's longer than usual since it embeds parts of th…

You don't find them worth the effort, but you wrote your own?

Re: RIP Jekyll (The Genesis of the Jamstack)

#43

Post by Zababa » Mon, Sep 13, 2021, 7:06 PM UTC

cvwright wrote: post #18

jaredcwhite wrote: post #15

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?

Elixir and OCaml mostly use a forum and it works well. Everyone can read it, it's easy to post on it, it's easy to moderate it, and it's great when you want to search for things. I don't think microblogging and instant messaging are what an open source community needs.

Re: RIP Jekyll (The Genesis of the Jamstack)

#44

Post by eatonphil » Mon, Sep 13, 2021, 7:06 PM UTC

abricot wrote: post #42

eatonphil wrote: post #8

Personally I don't find static site generators worth the effort to learn or keep up-to-date as versions inevitably come. I end up just writing my own for each site in 1-200 lines of Python. It's normally just a markdown library and a template engine wrapped with a file system walker. Here's an example: https://github.com/eatonphil/notes.eatonphil.com/blob/master... . It's longer than usual since it embeds parts of th…

You don't find them worth the effort, but you wrote your own?

Updated to clarify that it is the time it takes to learn and the upkeep over time that I find not worthwhile.

Re: RIP Jekyll (The Genesis of the Jamstack)

#45

Post by cyberge99 » Mon, Sep 13, 2021, 7:09 PM UTC

Exuma wrote: post #4

What do people use besides Jekyll?

I use hexo. It’s node and not super popular, but it does what I need and I’ve built my workflows around it so alost everything is done by cli (bash, imagemagick and hexo).

It can be seen here:

https://chrisbergeron.com

Re: RIP Jekyll (The Genesis of the Jamstack)

#46

Post by Lammy » Mon, Sep 13, 2021, 7:13 PM UTC

ctoth wrote: post #36

Pretty sure that open source in 2021 means releasing the code somewhere public under an Open Source license, just like it did in 2011 and 2001. Not sure where all these other requirements come from. I'm already giving you free software, I don't also need to build a community.

> Not sure where all these other requirements come from.

They come from people who want to make money more than they want to build a nice thing and share it. Gotta spread that Fear, Uncertainty, and Doubt to usurp Jekyll's userbase.

Re: RIP Jekyll (The Genesis of the Jamstack)

#47

Post by jaredcwhite » Mon, Sep 13, 2021, 7:14 PM UTC

mfer wrote: post #35

I wonder if GitHub will step in and maintain. Isn't it still a built-in part of their pages stack? Even if there isn't new feature development, if it's part of their stack they should step in and maintain it. You don't want bitrot to introduce vulnerabilities through unmaintained publicly exposed things in your stack.

AKAIK, they apply (or backport) security fixes to the Jekyll 3.x branch. No word on if they ever plan to migrate to Jekyll 4 or beyond.

Re: RIP Jekyll (The Genesis of the Jamstack)

#48

Post by qwertox » Mon, Sep 13, 2021, 7:14 PM UTC

jaredcwhite wrote: post #15

Zababa wrote: 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…

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:

Mailing lists are not bad, as well as the issue tracker on GitHub.

Re: RIP Jekyll (The Genesis of the Jamstack)

#49

Post by mfer » Mon, Sep 13, 2021, 7:26 PM UTC

sam1r wrote: post #38

mfer wrote: post #35

I wonder if GitHub will step in and maintain. Isn't it still a built-in part of their pages stack? Even if there isn't new feature development, if it's part of their stack they should step in and maintain it. You don't want bitrot to introduce vulnerabilities through unmaintained publicly exposed things in your stack.

Right. They (gh) should creative a relief team that handles repositories with very high stars, and no active maintenance.

I'm not suggesting they do that.

GH pages is includes jekyll. It's a feature of their product. I would expect them to maintain that as long as jekyll is part of their feature suite.

I'm only bringing them up because it impacts their product directly.

https://docs.github.com/en/pages/setting-up-a-github-pages-s...

Re: RIP Jekyll (The Genesis of the Jamstack)

#50

Post by kevwil » Mon, Sep 13, 2021, 7:26 PM UTC

Zababa wrote: 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…

Yeah, I almost choked on my lunch when I read that. In addition to your well-said reasons, it just seems icky. In my not-so-humble opinion, Twitter (among others) has become a harmful echo chamber of dangerous ideas and hypocrisy. Requiring the use of Twitter is not a good signal to send.