News for hackers. Stuff that matters.
Re:GitHub Stale Bots – A False Economy by baobabKoodaa on Monday January 18, 2021 @08:11AM (#25821445)
I used to open GitHub issues to Gatsby to report bugs. Almost nothing was ever fixed and every few weeks I had to manually clickety-click to keep the issues alive because of the stale bot. Guess what I do now? I don't report bugs to Gatsby, and I recommend against using Gatsby in newer projects.
Re:GitHub Stale Bots – A False Economy by z77dj3kl on Monday January 18, 2021 @08:32AM (#25821578)
Yes, I've had a similar experience. Gatsby is a dumpster fire once you venture off the beaten path.
Re:GitHub Stale Bots – A False Economy by madeofpalk on Monday January 18, 2021 @09:10AM (#25821927)
Or, stay on the beaten path for too long and get "too big" and it turns into a dumpster fire.
Re:GitHub Stale Bots – A False Economy by sneak on Monday January 18, 2021 @10:23AM (#25822602)
It's also spyware, transmitting your usage without consent:

https://www.gatsbyjs.com/docs/telemetry/

Re:GitHub Stale Bots – A False Economy by rgovostes on Monday January 18, 2021 @11:21AM (#25823261)
"Spyware" has a specific meaning and shouldn't be applied to any instance of data collection you disagree with.

That you can point to their documentation about their data collection practices, which are explained in concise English with opt-out instructions, and that this is apparently detailed to the user on install, strongly suggests Gatsby is not spyware.

Telemetry can be very valuable to open source projects which have extremely limited resources. The Adium project used telemetry to decide when they could drop support for PowerPC processors and old versions of macOS[0]. Homebrew uses it to track which of its thousands of packages are the most problematic to install[1].

0: https://sparkle.adium.im/?year=2020&week=*&graph=bar

1: https://formulae.brew.sh/analytics/

Re:GitHub Stale Bots – A False Economy by rightbyte on Monday January 18, 2021 @01:18PM (#25824748)
> We track general usage details, including command invocation, build process status updates, performance measurements, and errors.

Sounds like spyware to me to do that without opt-in. Projects that do that wont take your privacy seriously.

Re:GitHub Stale Bots – A False Economy by mrob on Monday January 18, 2021 @01:11PM (#25824668)
Opt-out telemetry is spyware, regardless of how convenient you might find it to spy on your users without their consent. The only ethical telemetry is opt-in, such as the system Debian uses, where users are given the option to install the "popularity-contest" telemetry package during install, with the default being not installing.
Re:GitHub Stale Bots – A False Economy by sneak on Monday January 18, 2021 @04:10PM (#25826660)
Homebrew is also spyware.

They transmit your unique identifier to Google every time you run brew, which effectively provides Google with your coarse location tracklog via client IP geolocation.

Data collection like this that is done without the consent of the user is extremely unethical, rude, and in some jurisdictions actually illegal. The fact that the data they steal is useful to them is not relevant and your bringing it up is telling.

It actually has nothing to do with whether or not I agree with it, and everything to do with whether or not they obtain consent to exfiltrate this information. Neither Homebrew nor Gatsby obtain the consent of the user to transmit their spying data.

Re:GitHub Stale Bots – A False Economy by cheph on Monday January 18, 2021 @08:44AM (#25821675)
Gatsby is probbably the worst static site generator that exists and I am not really sure what it brings to the table other than incredibly slow build times, pointless use of graphql (which falls apart quite quickly) and an over complicated framework which is difficult to customize and costly to maintain.
Re:GitHub Stale Bots – A False Economy by madeofpalk on Monday January 18, 2021 @09:20AM (#25822010)
Yes, I've seen the same problems from Gatsby and it wouldnt be my first choice, but I do really like it's use of GraphQL - i think it's a smart way to solve a problem that does exist for some use cases.

I like Gatsby's createPage API that lets you programatically create pages from source data at any url, rather than the "traditional" approach of binding views to URL patterns. It's useful for some kinds of static sites that might have a radically different template or data source/model for multiple pages that fit the same URL pattern.

Gatsby's use of GraphQL, which can be a pain especially as you scale larger, is nice how it lets you query just the fields you need, so your dehydrated data remains pretty minimal. It's something that I've struggle with when building a site with NextJS - I would have to set up and create my own GraphQL server.

Gatsby is a weird one because it has these "advanced" features that really benefit larger sites (or sites with larger ambitions), but Gatsby really can't handle large sites or data.

Re:GitHub Stale Bots – A False Economy by Cthulhu_ on Monday January 18, 2021 @09:59AM (#25822381)
I found the GraphQL decision really works if you're combining multiple datasources. One example we built in practice is combining a CMS-as-a-service (Contentful, Prismic) and a webshop back-end as a service (Commercetools) to build rich product pages.
Re:GitHub Stale Bots – A False Economy by madeofpalk on Monday January 18, 2021 @11:35AM (#25823449)
Yeah, it can be really helpful when you want to combine multiple data types/sources into a single meta type to query multiple types with just a single graphql query.
Re:GitHub Stale Bots – A False Economy by ljm on Monday January 18, 2021 @09:24AM (#25822050)
It turns out that building a site in plain HTML, without fancy tools, isn't nearly as difficult as using stuff like gatsby once you get down to it.

Hell, just throw in some PHP if you want dynamic bits and pieces. Your fancy netlify/cloudflare/vercel setup may not like it but your infinitely cheaper shared host/VPS provider will.

If you still wanted static output, you could probably serve it locally and then let wget crawl it for you.

Re:GitHub Stale Bots – A False Economy by icebraining on Monday January 18, 2021 @01:25PM (#25824813)
> infinitely cheaper

It's actually the opposite. Static site hosting is so much easier to optimize, that it costs just few cents a month, if anything at all (I never went beyond Netlify's free plan).

Re:GitHub Stale Bots – A False Economy by ljm on Tuesday January 19, 2021 @06:14PM (#25840276)
That's the cost of hosting the end result. How much of your precious time did you spend building your site in a way to make 'static site hosting' (i.e. a file server behind a CDN) work? Did you put time into some CI workflow on Github to precompile the site and push it to Netlify? Did you mess around with Netlify itself to build what you want?

I can do exactly the same with a cheap VPS running apache and PHP and a deploy is little more than an SCP or FTP upload away. I don't have to worry about a build pipeline at all.

I'm not aiming this at you, but in general I'd love to see how newer engineers would tackle things like deployment if they couldn't rely on some SaaS offering.

Or are we talking about static sites that are static because they do all the server side stuff on the browser, and you're pulling down things like react and graphql to render a blog post?

Re:GitHub Stale Bots – A False Economy by icebraining on Tuesday January 19, 2021 @07:46PM (#25841158)
Nah, no CI workflow, I generate locally. Creating the site was just

  pip install pelican; git init . ; pelican-quickstart; vim pelicanconf.py  # to set the theme
Then to publish:

  pelican . && git add -A && git commit -m "post title" && git push
(I have a shortcut for this, of course)

But I think you overestimate the time to "setup the CI workflow" actually takes. It's just a text file where you put the commands above, so it can run on the server instead of your machine. There's no black magic to it.

> I don't have to worry about a build pipeline at all.

Of course you do; it's just that your build pipeline runs every time someone accesses your site.

> I'm not aiming this at you, but in general I'd love to see how newer engineers would tackle things like deployment if they couldn't rely on some SaaS offering.

I've done that too. I created a bare git repo on the server, with a post-receive hook that checkouts "master" and runs the static site generator. Then I had Nginx serve the directory.

Re:GitHub Stale Bots – A False Economy by madeofpalk on Tuesday January 19, 2021 @06:34AM (#25832420)
> I never went beyond Netlify's free plan

There you go. Go beyond Netlify's free plan and it can get pretty expensive.

Re:GitHub Stale Bots – A False Economy by icebraining on Tuesday January 19, 2021 @06:03PM (#25840152)
Not really, you can just easily switch to another solution, like B2+Cloudflare, which costs pennies.
Re:GitHub Stale Bots – A False Economy by madeofpalk on Monday January 18, 2021 @11:37AM (#25823469)
> If you still wanted static output, you could probably serve it locally and then let wget crawl it for you.

Here's the complexity part that tools try to solve.

Re:GitHub Stale Bots – A False Economy by john-shaffer on Monday January 18, 2021 @02:19PM (#25825409)
There are decoupled tools like https://statically.io/ to do this. One can have the straightforward builds of GP and still have good static site generation.
Re:GitHub Stale Bots – A False Economy by madeofpalk on Tuesday January 19, 2021 @06:02AM (#25832183)
cool, we've just made something more complicated than netlify or whatever.

Looks like a great tool for migrating an existing dynamic site into a more static workflow, but it's not exactly the workflow I was replying to.

Re:GitHub Stale Bots – A False Economy by SkyPuncher on Monday January 18, 2021 @11:36AM (#25823466)
I used Gatsby about 3 years ago and loved it. With that being said, I feel like it's grown well beyond it's useful value proposition for me.

The biggest value was I could share a lot of components between my app and marketing site. Even though most of the marketing site was static content, Gatsby made it incredibly easy to introduce well integrated custom features.

I never hit of the point of needing a full CMS (the site wasn't large enough), so it was great for my needs. Not sure why anyone would use it if they're going full CMS, though.

Re:GitHub Stale Bots – A False Economy by ghego1 on Monday January 18, 2021 @09:02AM (#25821859)
If you are looking for an efficient static site builder try YASSB! [1]

YASSB processes HTML, (S)CSS, JavaScript/TypeScript, JSX/TSX, JSON, MarkDown and many other files and combines them into beautiful static websites.

I am the creator of YASSB, I'd love to hear what you think about it!

[1] [https://yassb-foss.github.io/](https://yassb-foss.github.io/...

Re:GitHub Stale Bots – A False Economy by ghego1 on Monday January 18, 2021 @09:04AM (#25821878)
Re:GitHub Stale Bots – A False Economy by krisgenre on Monday January 18, 2021 @10:23AM (#25822604)
I've just started using Eleventy for our site. For someone completely new to this it was bit difficult to start but once off the ground have started to love it. The best thing is if any feature is missing you can quickly write a plugin in javascript.
Re:GitHub Stale Bots – A False Economy by jrv on Monday January 18, 2021 @09:19AM (#25821997)
I like that I can write pretty much normal React in it, and that it has a lot of features and plugins. But I'm still a pretty casual user probably.
Re:GitHub Stale Bots – A False Economy by tvanantwerp on Monday January 18, 2021 @08:27AM (#25821545)
Sadly, I've had this same experience with Gatsby.
Re:GitHub Stale Bots – A False Economy by Cthulhu_ on Monday January 18, 2021 @09:56AM (#25822345)
My experience is different, back when I used it (about a year and a half ago last? Ish?), they seemed to have dedicated community management staff doing the rounds and making sure all issues were acknowledged, tagged, and addressed. Has that changed since then? At the time I found it a really welcoming and active community. I even got a T-shirt for contributing.
Re:GitHub Stale Bots – A False Economy by baobabKoodaa on Monday January 18, 2021 @10:23AM (#25822603)
I also found the community active and welcoming. I also got a t-shirt. All of my issues were tagged. Unfortunately they weren't fixed, and the stale bot kept marking them as stale. It seemed to me like Gatsby developers were focusing the majority of their time on writing "fun" new features rather than fixing all the sharp edges and broken pipes of the complicated pile of old features.
Re:GitHub Stale Bots – A False Economy by wpietri on Monday January 18, 2021 @10:39AM (#25822758)
That fits if we think about it in POSIWID terms: https://en.wikipedia.org/wiki/The_purpose_of_a_system_is_wha...

If the true goal of the devs is to do the fun first 25% of the work, then the signs that a particular job hasn't been finished are unwelcome. A stale-bot sweeps most problems under the rug and, as we see in the discussion here, discourages reporting in the first place. The numbers look better, the devs get to feel like things are under control, and they get to rush on to the next shiny thing.

And perhaps it works one layer deeper, too. Their website's all about "fast, fast, fast"! They advertise the ability to "create a complete website in the time it usually takes to build a prototype". I would read a claim like that suspiciously: when I build prototypes, I leave out things that are important for sustainability. But the things I think are "finishing the job right" seem to others as tedious and uninteresting things to be skipped if possible. So perhaps the devs have found themselves an audience like themselves that are fine with a high level of brokenness as long as they get the feeling of moving forward quickly?