101–110 of 213 posts
It's one of my biggest issues with software is that software is never done. It's always being torn down and replaced with something else.
A static page framework that shoves content into a client side graphql store and then extracts bits out to render a page? It's popular, so I can't say it was a bad idea. I guess I'll just say I must be old because it sounds like satire.
Earlier quoted context omitted.
I'm one of the use cases that Sam mentions - B2C website. Replatforming our site with Gatsby, Netlify (hosting and more) and Contentful (headless CMS) has saved us hundreds of dollars a month in hosting - our site which receives 20,000 - 30,000 visitors a month now costs $0 to host. Additionally it is radically faster and more secure than it previously was. Being able to use React as needed has enabled us to manage s…
It's tough to take this too seriously since it seems you created this name just to make this comment. What approaches did you try before 'owing your career to gatsby'?
I would honestly be interested to know how many self taught people making things work building basic sites for unglamorous corners of the internet cruise this site.
To be honest I don't really feel welcome here because I'm not sophisticated (prob the best word for it) enough. But that's ok.
Earlier quoted context omitted.
Did you mean "overly-complicated" as in for people who don't work in the industry and just speculate on trends?
[deleted]
I write all this as a 21-year veteran of web development-related work, and in the spirit of respectful disagreement.
Earlier quoted context omitted.
Linux - Gatsby doesn't run on Linux? Apache - Gatsby doesn't run behind a load balancer (apache/nginx) with proxy_pass? MySql - Gatsby doesn't persist data into a database (MySql/Postgres)? PHP - I'll give you that PHP is out and node.js is in for backend development.
Linux - probably Apache/Nginx - some web server will be used, though much as likely something more lightweight than Apache. No proxy_pass needed since Gatsby just generates a bunch of files you need to serve MySQL - probably not unless married with a very complex backend PHP - yeah that’s out To understand Gatsby it’s crucial to understand that it’s using a significantly different architecture than traditional LAMP a…
I don't really like Gatsby's product, but I've got to admit that their business strategy makes a lot of sense. It's a pretty good three-step approach: 1. Convince the WordPress/enterprise crowd to switch over, both by touting the genuine benefits of static sites (security, scalability, TTFB performance, etc.) and by riding the Cool Kid Front-End Stack hype train. 2. Lock them in with an overly-complicated framework a…
> Convince the WordPress/enterprise crowd to switch over The Gatsby homepage mentions Wordpress as a possible data source. I don't evens see mention of their CMS on the front page. The only "service" I see them advertising there is Preview - which seems to be a development collaboration tool. I don't think they're convincing people to move away from Wordpress. It's funny that the article talks about moving away from…
Compared to Wordpress, Ghost, and Webflow, it seems the market size for this is limited.
Earlier quoted context omitted.
[deleted]
I take issue with your tone and cynicism, and disagree w/ your premise. Your sarcasm and condescension aren't helpful. And there's no way your "couple hundred lines of code" addressed more than a fraction of the real-world use cases addressed by Gatsby. You cast aspersions on a huge swath of your peers who work with the best tools at hand to solve difficult problems... it's not just arrogant, it's ignorant. IME it's…
The posters here aren't wrong. It is an overhyped, overbloated, overconfig heavy stack that ultimately renders static html.
I have used them, they are exactly as these posters say.
Earlier quoted context omitted.
I'm very surprised that a static site generator can raise this much capital, but it suggests to me that 1) the security dilemmas of non-static but content driven sites are still big enough to warrant adoption of this methodology 2) potentially, there is something they are doing right in this space. I'd really like to know what 2 is as there's a lot of other options in this space that are also free, open source, and s…
Raising capital isn't success. Profitability is success. I think the main value of Gatsby is the community-generated recipes to plug and play...but is there value here? If you have one very generic application, then maybe you save time upfront. But you are tied into this heavy wrapper around React that will probably cause you problems down the line. And you probably still need a backend. So I am not sure what value i…
Gatsby Preview / Gatsby Content Mesh is most likely the horse being bet on.
Earlier quoted context omitted.
[deleted]
I take issue with your tone and cynicism, and disagree w/ your premise. Your sarcasm and condescension aren't helpful. And there's no way your "couple hundred lines of code" addressed more than a fraction of the real-world use cases addressed by Gatsby. You cast aspersions on a huge swath of your peers who work with the best tools at hand to solve difficult problems... it's not just arrogant, it's ignorant. IME it's…
> there's no way your "couple hundred lines of code" addressed more than a fraction of the real-world use cases addressed by Gatsby
Gatsby on its own doesn't actually do much. There are plugins to do most useful things. Here's an example: https://www.gatsbyjs.org/packages/gatsby-remark-prismjs/
That is the "blessed" solution for code highlighting. Notice how you have to install 2 different NPM packages, add a bunch of ad-hoc configs (which don't have API docs) then add a bunch of Gatsby specific CSS. Do you see a section about embedding code highlighting in React? No? That's because it doesn't support it (meaning you have to hack it with `dangerouslySetInnerHtml` if you want code highlighting directly in a React subtree, such as a custom layout for a homepage containing a code snippet). The alternative if you were to write a custom script would be to just take 5 minutes to slap prism.js itself in the layout file (which amounts to adding a link tag and a script tag - something a beginner HTML developer can do)
And don't even get me started on migrating from Gatsby 2 to 3 :)
Earlier quoted context omitted.
Another advantage of developing close to plain HTML is that you’re free from the js next-shiny-thing hamster wheel. For example, I had thought Gatsby was the hip way to create static sites in 2019. Then another comment here mentioned it’s Next.js now.
Gatsby and Next.js are both site frameworks powered by React. They can both be used for static and dynamic sites with different conventions and features around routing, data management, and general app architecture. Both are "hip" and will likely remain as the top 2 javascript based site frameworks for now, although whether you need either of them is an entirely different question.