Live data from Hacker News

RIP Jekyll (The Genesis of the Jamstack)

bridgetownrb.com

11–20 of 187 posts

Re: RIP Jekyll (The Genesis of the Jamstack)

#12

Will Bridgetown support current Jekyll themes?

> While Bridgetown has diverged somewhat from Jekyll in terms of architecture and is not source compatible (for example plugins and themes)

Based only on what I've heard, but my understanding is it's not a huge undertaking to port over

Re: RIP Jekyll (The Genesis of the Jamstack)

#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 require an account on a proprietary platform.

Re: RIP Jekyll (The Genesis of the Jamstack)

#14

Will Bridgetown support current Jekyll themes?

Only with a few modifications …we're nearly through a stint of addressing tech debt, and then we plan to publish a guide for porting over Jekyll themes out for to make this process much more clear.

Re: RIP Jekyll (The Genesis of the Jamstack)

#15
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:

Re: RIP Jekyll (The Genesis of the Jamstack)

#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 this industry-wide.

Re: RIP Jekyll (The Genesis of the Jamstack)

#18
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:

Mastodon and Matrix instead?

Re: RIP Jekyll (The Genesis of the Jamstack)

#20
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…

The Discord chat room is very little different from the (RIP) freenode channel. Sure, you need to create an account, but that's where communities are built nowadays - in closed groups that can be controlled, moderated properly, and automated, while still being a fun and friendly environment to chat in. It does that well.

Github is not open. All the things listed there are costly, in one way or another. There's nothing free about anything that makes up open source today. Open source became corporate some time in the late 00s. And while I don't agree with the author (including the fact that he calls the new product Ruby-powered, not Impaired by Ruby), I do agree with that strange assessment that open source communities work that way.

Post reply on HN