Open biorisk opened 6 days ago
Thank you for your feedback on Goilerplate! Your insights are really valuable.
I'm always looking to improve Goilerplate's accessibility. Any ideas on reducing dependencies without losing functionality? I'd love to hear your thoughts!
I love the idea and look of goilerplate, so I jumped into the quickstart. The Prerequisite section starts with Go (yay!), but then adds Node.js and npm (boo!) and make (meh). Is there a world where the goodness of CSS utility classes doesn't require sullying my pristine Go dev environment with any of the obnoxious javascript ecosystem? (Yes, this is a knee-jerk reaction ;-)
Excising Node and company might not be relevant to goilerplate's direction, but I could see backend devs gravitating toward the package for beautiful, easy to create internal tools if the requirements didn't involve js at all.