Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

WTF is JAMstack?

jamstack.wtf

Post reply on HN
Print view View original

11–20 of 52 posts

Re: WTF is JAMstack?

#11

Post by sibeliuss »

Geee wrote: post #9
vorpalhex wrote: post #2

Am I missing something or is this just a plain old normal static website?

You are missing something. Your content is dynamic but the html markup is generated ahead of time and served from CDN. The difference to static site is that your content lives in a CMS server + APIs and is not embedded in your codebase. Your codebase contains just the layout and components etc. without content. You can use all modern methods and frameworks such as React, but the final website is just html.

Yup, it pulls stuff in ahead of time. That said, that's just for the initial render. Once things are mounted and "static" can take advantage of apollo or whatever request lib you'd like for "dynamic" content. But the idea is to build out most paths in the build phase and then push up. A lot of the time thats all a site will need. It works amazingly well, at least with Gatsby.

Re: WTF is JAMstack?

#12

Post by rement »

mikece wrote: post #6

Am I the only one wondering if this was a covert announcement of the availability of domains in the WTF tld? If you move fast you can grab HackerNews.wtf ... https://www.namecheap.com/domains/registration/results.aspx?...

To late

Re: WTF is JAMstack?

#13

Post by teilo »

How is this different from a single page app?

The article is also loaded with BS:

> Faster performance. Serve pre-built markup and assets over a CDN

Just like every single-page app.

> More secure. No need to worry about server or database vulnerabilities

Total BS. A form post is an API call by another name. Your server and database are just as vulnerable via an API.

> Less expensive. Hosting of static files are cheap or even free

Just like every single-page app.

> Better developer experience. Front end developers can focus on the front end, without being tied to a monolithic architecture. This usually means quicker and more focused development

Really? And templating languages do not exist on the backend? The only difference is where the processing occurs, and a single-page app has just as much templating whether the template is rendered in-browser or on-server. Often it has a lot more.

> Scalability. If your product suddenly goes viral and has many active users, the CDN seamlessly compensates

Ahem! API?

Re: WTF is JAMstack?

#14

Post by factorialboy »

teilo wrote: post #13

How is this different from a single page app? The article is also loaded with BS: > Faster performance. Serve pre-built markup and assets over a CDN Just like every single-page app. > More secure. No need to worry about server or database vulnerabilities Total BS. A form post is an API call by another name. Your server and database are just as vulnerable via an API. > Less expensive. Hosting of static files are cheap…

25 days ago I made this comment: "The key is to invent a new term for an existing entity. Here the author tries to introduce the term "document site" for static websites."

The same happens here. Take an existing concept. Stick a new label-term on it. Market it like you're the inventor of this revolutionary concept to the unaware. Profit.

Re: WTF is JAMstack?

#15

Post by maxk42 »

teilo wrote: post #13

How is this different from a single page app? The article is also loaded with BS: > Faster performance. Serve pre-built markup and assets over a CDN Just like every single-page app. > More secure. No need to worry about server or database vulnerabilities Total BS. A form post is an API call by another name. Your server and database are just as vulnerable via an API. > Less expensive. Hosting of static files are cheap…

SPAs can be JAMstack or non-JAMstack. JAM is secure as fuck when there's no 'A' or when you trust the 'A' strongly. (e.g. Google Maps API) Otherwise, you're just making security someone else's problem.

Re: WTF is JAMstack?

#16

Post by maxk42 »

mikece wrote: post #6

Am I the only one wondering if this was a covert announcement of the availability of domains in the WTF tld? If you move fast you can grab HackerNews.wtf ... https://www.namecheap.com/domains/registration/results.aspx?...

.wtf has been around for a long time now

Re: WTF is JAMstack?

#17

Post by ralala »

sibeliuss wrote: post #11
Geee wrote: post #9

Earlier quoted context omitted.

You are missing something. Your content is dynamic but the html markup is generated ahead of time and served from CDN. The difference to static site is that your content lives in a CMS server + APIs and is not embedded in your codebase. Your codebase contains just the layout and components etc. without content. You can use all modern methods and frameworks such as React, but the final website is just html.

Yup, it pulls stuff in ahead of time. That said, that's just for the initial render. Once things are mounted and "static" can take advantage of apollo or whatever request lib you'd like for "dynamic" content. But the idea is to build out most paths in the build phase and then push up. A lot of the time thats all a site will need. It works amazingly well, at least with Gatsby.

So there is no server-side rendering of content? Will Google index this correctly?

Re: WTF is JAMstack?

#19

Post by smacktoward »

teilo wrote: post #13

How is this different from a single page app? The article is also loaded with BS: > Faster performance. Serve pre-built markup and assets over a CDN Just like every single-page app. > More secure. No need to worry about server or database vulnerabilities Total BS. A form post is an API call by another name. Your server and database are just as vulnerable via an API. > Less expensive. Hosting of static files are cheap…

It's amazing how much easier everything gets when you define all the hard parts as somebody else's problem.
Post reply on HN