the one question that settles plain html with a bit of js vs the rest for a weekend side project

frameworksjavascriptopinion8 replies 路 115 views 路 started
  1. six months ago i chose plain HTML with a bit of JS for a weekend side project, some things went great, some things made me question my judgment. before i start the next one, Id like to compare notes. what would u pick for this kind of work today, and what trade-offs do you think people underestimate? im especially curious about what went wrong for you, not just what went right.

    3
  2. uhh who maintains a small marketing site after you??

    thinking

    0 1 helpful
  3. im literally losing my mind here i swear plain is cursed. dumb question but how do i even check the BIOS

    3 1 helpful
  4. yeahhh for freelance work, think about handoff. The clinet may hire someone else later; a mainstream stack makes that easier and is a genuine service to them.

    13 6 helpful
  5. ahh classic team knowledge beats theoretical advantages 馃憤 A team fluent in one framework will ship a better product with it than with a better framework theyre learning on the job. worked for me anyway 馃し

    2 0 helpful
  6. ahh classic server-driven approaches like htmx are great for CRUD-heavy internal tools. You keep logic on teh server and avoid a whole client state layer. They get harder when you need rich offline or highly interactive UIs. lmk how it goes

    5 0 helpful
  7. nah tbh i'd argue resume-driven development isn't always bad. Learning a widely used tool on a real project has value, as long as the client isn't paying for your learning curve.

    lol

    5 0 helpful

Reply to this topic

Sign in or create an account to reply.