News for hackers. Stuff that matters.

A comment on GitHub’s engineering team has moved to Codespaces. Parent comment

Re:GitHub’s engineering team has moved to Codespaces by brundolf on Wednesday August 11, 2021 @01:03PM (#28144638)
There's nothing about jamstack that requires you to use third-parties (except the CDN part, I guess, but that's just a mirror). You could just as easily host your own CMS and database and call out to it the same way.

It's just that like auth, logging, etc, CDNs have been neatly abstracted out and service-ified in such a way that it's often more economical to go third-party. But that choice is orthogonal to jamstack.

[ Parent | on HN ]
Re:GitHub’s engineering team has moved to Codespaces by gosukiwi on Wednesday August 11, 2021 @01:05PM (#28144675)
I agree on that, and was going to add that, to be fair to the stack. But the reality is, while that's doable, most people just use third-party services, at least that's my experience.
[ Parent | on HN ]
Re:GitHub’s engineering team has moved to Codespaces by paulgb on Wednesday August 11, 2021 @01:37PM (#28145089)
Sure, but I think that's true in non-Jamstack code as well. Datadog, Snowflake, BigQuery, DynamoDB, Google Analytics, etc. are all examples that I've seen used by non-Jamstack software, and most have a fair bit of lock-in.
[ Parent | on HN ]
Re:GitHub’s engineering team has moved to Codespaces by sergiotapia on Wednesday August 11, 2021 @01:07PM (#28144707)
jamstack certainly presents itself first and foremost as "use third party services".
[ Parent | on HN ]