Looking at the bloated and checked in node_modules folder makes me wanna cry. Yah it's probably all just dev dependencies but building a static website shouldn’t feel like rocket science. People were creating wedding websites in the 90s with just one html file and that’s it. Welcome to the age of total bloat.
Show HN: Open-sourcing my wedding website on my first anniversary
61–70 of 208 posts
Re: Show HN: Open-sourcing my wedding website on my first anniversary
#62Nothing to add but congrats on year one of marriage, and here's to many more. Thanks for sharing this with us :)
Re: Show HN: Open-sourcing my wedding website on my first anniversary
#63I’ve got a different format - timeline style: https://www.09092018.com Let me know if anyone wants me to open source this :)
Love the concept, what's the stack? Would be willing to help open source it.
It was generated by create-react-app, as revealed here: https://www.09092018.com/manifest.json
Re: Show HN: Open-sourcing my wedding website on my first anniversary
#64I’ve got a different format - timeline style: https://www.09092018.com Let me know if anyone wants me to open source this :)
Getting ready to plan a wedding after double digit year dating -- The timeline approach is brilliant, thanks for sharing!
Re: Show HN: Open-sourcing my wedding website on my first anniversary
#65Looking at the bloated and checked in node_modules folder makes me wanna cry. Yah it's probably all just dev dependencies but building a static website shouldn’t feel like rocket science. People were creating wedding websites in the 90s with just one html file and that’s it. Welcome to the age of total bloat.
The package.json declares 4 build dependencies and 3 runtime.
Most of that bloat probably comes from Gulp, which is one of the most ridiculously bloated tools I've ever seen.
Re: Show HN: Open-sourcing my wedding website on my first anniversary
#66Looking at the bloated and checked in node_modules folder makes me wanna cry. Yah it's probably all just dev dependencies but building a static website shouldn’t feel like rocket science. People were creating wedding websites in the 90s with just one html file and that’s it. Welcome to the age of total bloat.
Most of us share that view, but it's against the Show HN rules to post indignant rants about someone's work, so please don't do it here.
Re: Show HN: Open-sourcing my wedding website on my first anniversary
#67Looking at the bloated and checked in node_modules folder makes me wanna cry. Yah it's probably all just dev dependencies but building a static website shouldn’t feel like rocket science. People were creating wedding websites in the 90s with just one html file and that’s it. Welcome to the age of total bloat.
The package.json declares 4 build dependencies and 3 runtime. Most of that bloat probably comes from Gulp, which is one of the most ridiculously bloated tools I've ever seen.
What is the alternative to tools like Gulp or Gatsby for those of us who want to make (fairly)simple websites?
In my case, I’m a Data Scientist looking to make a portfolio website. Nothing too crazy but more than hello world.
Should we just work with HTML? Materialize CSS? GitHub pages w/ Jekyll? Nextjs? Bootstrap?
Should we just head back to Wordpress and Wix? Wixcode? Is Gulp the best option?
Is it worth paying a professional to create the site for me?
I’m very intereted in developer opinions. Any feedback is much appreciated. Thank you.
Re: Show HN: Open-sourcing my wedding website on my first anniversary
#68Badly expressed, sorry. Deleted.
Re: Show HN: Open-sourcing my wedding website on my first anniversary
#69Earlier quoted context omitted.
The package.json declares 4 build dependencies and 3 runtime. Most of that bloat probably comes from Gulp, which is one of the most ridiculously bloated tools I've ever seen.
What is the alternative to tools like Gulp or Gatsby for those of us who want to make (fairly)simple websites? In my case, I’m a Data Scientist looking to make a portfolio website. Nothing too crazy but more than hello world. Should we just work with HTML? Materialize CSS? GitHub pages w/ Jekyll? Nextjs? Bootstrap? Should we just head back to Wordpress and Wix? Wixcode? Is Gulp the best option? Is it worth paying a p…
One alternative is to not use them. If your target website actually is simple then prove it by not imposing a slow bloated architectural failure.
Re: Show HN: Open-sourcing my wedding website on my first anniversary
#70Badly expressed, sorry. Deleted.
That's a terrible thing to say to someone.