#dev 2021-09-16
2021-09-16 UTC
Seirdy, jamietanna, angelo, shoesNsocks, jjuran, gagarin, jamietanna1 and BinarySavior joined the channel
# 
capjamesg[d] [KevinMarks] I refactored some of my crawler in response to your thoughts last night. I now use separate threads for each domain rather than querying the same domain with lots of threads.
grantcodes[d], hendursa1, hendursa2, neocow, hans, tetov-irc, shoesNsocks1, hendursaga and [Rose] joined the channel
# capjamesg[d] Welcome to the Jekyll crew [Rose]!
kimberlyhirsh[d] joined the channel
# 
rattroupe[d] When I first set up my own blog I tried to evaluate all the different options and eventually went with Jekyll, but now I’m having second thoughts.
[snarfed] joined the channel
# capjamesg[d] I saw someone write about that...
# capjamesg[d] I love Rubenerd's take: https://rubenerd.com/the-future-of-the-jekyll-static-site-generator/
# capjamesg[d] "Dare I say, there’s also something to be said for mature software that does its job not needing such regular updates. I know people who continue to run and maintain Jekyll sites successfully for large clients today. I’m willing to reserve judgement for now."
# capjamesg[d] Jekyll is still ticking along.
# capjamesg[d] I don't think it's stagnant. The ecosystem is rich, there are lots of integrations, many people use Jekyll, and it provides a good developer experience.
# capjamesg[d] I'm not saying Jekyll is perfect but I don't see any reason for me to switch any time soon.
# capjamesg[d] Jekyll works well, it's fast, and works with the tools I use.
# capjamesg[d] (rant over 😄 )
# 
[snarfed] "The idea that new code is better than old is patently absurd. Old code has been used. It has been tested. Lots of bugs have been found, and they’ve been _fixed_. There’s nothing wrong with it. It doesn’t acquire bugs just by sitting around on your hard drive. Au contraire, baby! Is software supposed to be like an old Dodge Dart, that rusts just sitting in the garage? Is software like a teddy bear that’s kind of gross if itâ
# capjamesg[d] Yeah. But I think there will always be contributors as long as people are using the software.
# capjamesg[d] Then again I know little about open source communities so I don’t know the extent to which having no community management — formal or otherwise — tends to impact a project.
# 
[KevinMarks] there is always a certain amount of maintenance churn as exploits are found in components, but that is less og a treadmill in Ruby than in, say, node
[fluffy] joined the channel
# capjamesg[d] "This is why code reuse is so hard. This is why everybody on your team has a different function they like to use for splitting strings into arrays of strings. They write their own function because it’s easier and more fun than figuring out how the old function works."
# capjamesg[d] [snarfed] That blog post you sent over is terrific.
# [KevinMarks] though it is less true than it was, and Joel did come up with one of the weirdest dev environments ever
[aciccarello] joined the channel
# 
[aciccarello] I didn't learn much ruby when I first setup my github pages hosted site. I ended up getting tired trying to get ruby setup correctly on my machine and migrated to 11ty. If you want to dive into ruby more Jekyll still seems solid to me.
# capjamesg[d] I haven't written much Ruby either [aciccarello].
# capjamesg[d] I have written a few files worth and that's it.
# capjamesg[d] And I don't use most of the code anymore.
# capjamesg[d] I think it's useful to start from scratch per se in some cases, especially if you have a more innovative way of doing things.
# capjamesg[d] I like building things from scratch to learn but I can never do *everything* from scratch.
# capjamesg[d] I think you need to pick your battles on the things that matter most and focus on those.
# capjamesg[d] But I'm no software expert, just a hobbyist.
# [aciccarello] Right, personally I'm trying to balance keeping things simple, keeping consistency with other SSG setups, and adding the features I care about.
# [snarfed] the flipside of "don't [re]write from scratch, reuse more" is that it's fighting against engineer human nature. uphill battle. https://twitter.com/creachadair/status/1173764360969150464
# 
@creachadair At my last job, a team put up a poster for their reusable components. It said: “We made a thing from scratch, so you don’t HAVE to make things from scratch.” But when engineers read this, they see: “We made a thing from scratch, so you don’t GET to make things from scratch.” (twitter.com/_/status/1173764360969150464)
# [KevinMarks] well, yes, thats the platform cycle thing that in alex's post I put up earlier
# [KevinMarks] We do gradually create reusable things that others can build on, but it often has a long cycle time, and its not always the bits you expect that become building blocks in future http://epeus.blogspot.com/2008/12/cycling-to-new-layers-of-freedom.html
# [KevinMarks] Simon Wardley has a good framework for thinking about this over time
[jeffrey_miller] joined the channel
# [KevinMarks] I need to find the bit I nicked these slides from http://slides.kevinmarks.com/2020trends.html#/4/1
# 
[tantek] also, in anything open / OSS, there is a tendency to attract armchair "chefs" who either talk about how they'd cook something (but never do), or tinkerer "chefs" who incrementally dabble in starting to cook something, but never produce anything edible, or at least desirably edible, nevermind nutritious and longterm sustainable for health
# capjamesg[d] [tantek] Your cooking metaphors are great.
# capjamesg[d] We should document this on the eat your own cooking page if that's what it is called.
# capjamesg[d] I found that the page was a lot of brainstorming last I checked which felt quite intimidating.
# capjamesg[d] Because the actual point mattered more to me than other metaphors.
# capjamesg[d] Then again, maybe the page is okay because we describe eat what you cook on /why / other places.
# capjamesg[d] Oh, we don't say it on /why. Never mind 🙂
# capjamesg[d] [snarfed] I like building from scratch as engineering challenges (hence I have my own webmention receiver, micropub server / client) but only if I'm actually going to use what I build.
# capjamesg[d] I liked your point tantek about chefs vs. people who just want a good meal.
# capjamesg[d] That's the reason I came to the IndieWeb. I have never felt I had to do anything from scratch to particulate.
# capjamesg[d] And so I felt a whole lot more welcomed!
# 
Loqi testimonial is a statement of support for the IndieWeb, perhaps building blocks, tools, services, and/or especially the IndieWeb community https://indieweb.org/testimonial
# capjamesg[d] Yep!
Seirdy, [manton], [jeffrey_miller], shoesNsocks1, ChrisHarris[m], hans, [aciccarello] and tetov-irc joined the channel