21–30 of 73 posts
Over-engineering at it's finest. React is great for some applications, IMO this is not one of them. To me it just over complicates things for minimal gain.
Over-engineering at it's finest. React is great for some applications, IMO this is not one of them. To me it just over complicates things for minimal gain.
How extensive is your experience with building static sites? Mine is limited; perhaps there's more to it than meets the eye.
I'm also curious how the code complexity for this compares to tools like pelican, Jekyll, etc.
If its a static site why do you need react?
React also enables some of the features of the tool. For example, hot reloading the contents of the page while writing/developing, which may make for a smoother experience.
If this isn't to your taste or doesn't fit your requirements, I'm sure the OP and author of the tool would not be offended if you continued to use Jekyll et al.
I'm pleasently surprised that the generated sites work just fine with JavaScript disabled (at least on the author's blog). Which on the other hand makes me wonder why I (as the visitor) need to download a 700KB JS blob that contains all blog posts, React and other things just to read the content. Without JS: 4 requests, 20 KB transferred, DOMContentLoaded @ 360ms With JS: 27 requests, 518 KB transferred, DOMContentLo…
From testing out one of the example blogs and this doesn't seem to be a UX issue:
Over-engineering at it's finest. React is great for some applications, IMO this is not one of them. To me it just over complicates things for minimal gain.
If its a static site why do you need react?
Some people prefer it as a templating tool (myself included). React also enables some of the features of the tool. For example, hot reloading the contents of the page while writing/developing, which may make for a smoother experience. If this isn't to your taste or doesn't fit your requirements, I'm sure the OP and author of the tool would not be offended if you continued to use Jekyll et al.
Over-engineering at it's finest. React is great for some applications, IMO this is not one of them. To me it just over complicates things for minimal gain.
Did you even read the docs for this project? In my opinion, this pulls together different tools that improve developer experience dramatically. For me personally, hot reloading is quite useful.
Over-engineering at it's finest. React is great for some applications, IMO this is not one of them. To me it just over complicates things for minimal gain.
I completely agree. One of those projects where the author was so focused in the `what` instead of the `why`. This kind of projects is why the JS community has bad fame among seasoned developers.
Supports pagination and progressive content loading, I believe its design is superior to other React based static site generators.
I am so tired of JavaScript. Please stop writing it.