4 ms·

I am quite deep into this idea of static website and I had a little of experience building one ( now defunct ) and I provide tools targeted to static website de

by siscia 7y ago

I am quite deep into this idea of static website and I had a little of experience building one ( now defunct ) and I provide tools targeted to static website developers ( https://simplesql.redbeardlab.com https://simplesql.redbeardlab.com ) The experience of creating one with python and netlify was superb, you just push out all the pages that you need and you call it done. Simple, fast, cheap, nothing to complain. However, I need to nitpick the author, what he calls compile time, is "compile time" only in the world of frontend development (and in most of the case is not a compilation step). Moreover, also Gatsby call the step "build" and not compile (and for good reason) so I don't see the reason to introduce another source of confusion. Indeed I was running a python script that at runtime create the correct webpages. SimpleSQL provides API to interact directly with databases from JS or making API call. That I believe works amazingly for static website, provided that people want to write SQL. One problem that I see is how to do authentication and I am working on fixing it. Different credentials, one only for logging, and if you are able to login, that you will receive a credentials for accessing your own data. The logging credential can be stored in the cookies or wherever make sense for the application.

noelwelsh 7y ago
Agreed. One of the major problems I had with Gatsby, for the brief period I used it, is that the documentation at the time did not clearly delineate what occurred when. E.g. how did I make code run at build time versus at rendering time?
MereInterest 7y ago
>However, I need to nitpick the author, what he calls compile time, is "compile time" only in the world of frontend development (and in most of the case is not a compilation step). I run into that issue with a lot of web frontend terminology. Sometimes, it is harmless, like calling it "tree shaking" instead of the more standard "dead code elimination". Other times, it can cause a large amount of confusion, like with "client-side rendering" and "server-side rendering". In all other contexts, "rendering" refers to the generation of an image. Yet somehow in web development, "rendering" refers to the generation of HTML, and has nothing whatsoever to do with the generating of an image to display to the user.
- Tomte 7y ago
  "Tree shaking" is standard terminology in Lisp (and possibly Smalltalk?). It's also a narrower term, since DCE is used for standard optimizations in e.g. C that have nothing to do with a heap of objects.

by siscia 7y ago

noelwelsh 7y ago

Agreed. One of the major problems I had with Gatsby, for the brief period I used it, is that the documentation at the time did not clearly delineate what occurred when. E.g. how did I make code run at build time versus at rendering time?

MereInterest 7y ago

>However, I need to nitpick the author, what he calls compile time, is "compile time" only in the world of frontend development (and in most of the case is not a compilation step). I run into that issue with a lot of web frontend terminology. Sometimes, it is harmless, like calling it "tree shaking" instead of the more standard "dead code elimination". Other times, it can cause a large amount of confusion, like with "client-side rendering" and "server-side rendering". In all other contexts, "rendering" refers to the generation of an image. Yet somehow in web development, "rendering" refers to the generation of HTML, and has nothing whatsoever to do with the generating of an image to display to the user.

Tomte 7y ago
"Tree shaking" is standard terminology in Lisp (and possibly Smalltalk?). It's also a narrower term, since DCE is used for standard optimizations in e.g. C that have nothing to do with a heap of objects.