Breaking up with JavaScript front ends • Hacker News Board

Re: Breaking up with JavaScript front ends

#431

Post by TranquilMarmot » Sun, Dec 18, 2022, 3:07 AM UTC

0xblinq wrote: post #165

TranquilMarmot wrote: post #86

Earlier quoted context omitted.

I think the basic divide is something like "CRUD forms" vs "interactive applications". I've built basic CRUD forms with ASP.NET MVC. I've built them with Rails. I've built them with React (+ a hundred random libraries). I've also built interactive "apps" in those languages. Looking back, the amount of "interactivity" that React adds to a CRUD form is NOT worth the added complexity. But! Right now my dayjob is creatin…

I agree with everything you said up to the part about fresh and deno, where it looks like you’re falling in the same trap of those wanting to use react. You don’t even notice it but this is the problem. Always thinking the next shiny tool will solve the problems. Rails, Lararavel and similar frameworks are great for crud apps. No need for fresh or demo or svelte or next.js for that.

I don't think that Fresh or Deno will solve any problems that aren't already solved. In fact, there are a lot of very frustrating bits about Fresh that worked a lot nicer in i.e. Rails. I would not use Fresh in production right now; if I were making a generic CRUD app I would probably use something a lot easier and with a bigger community around it.

Re: Breaking up with JavaScript front ends

#432

Post by 0xblinq » Sun, Dec 18, 2022, 2:22 PM UTC

aristofun wrote: post #371

0xblinq wrote: post #176

Earlier quoted context omitted.

C’mon, put a minimum effort to understand what it’s all about before making useless comments. It is not a framework to organize your own JavaScript (like react, vue, etc). It is a framework so that you don’t have to write JavaScript in the frontend. Of course it is written in JavaScript, because that’s the only thing that can run on the browser.

C׳mon, put a minimum effort to realize, that it was the same kind of original intention behind any js framework - so that you don’t have to write something unnecessary. This is absurd statement. It doesn’t mean that the OP framework is bad or that SPA idea is not generally abused etc and doesn’t call for some changes etc. It’s just a ridiculous and somewhat arrogant way to promote your yet another fancy js thing.

And you still don’t get it. Nevermind

Re: Breaking up with JavaScript front ends

#433

Post by aristofun » Mon, Dec 19, 2022, 3:12 AM UTC

0xblinq wrote: post #432

aristofun wrote: post #371

Earlier quoted context omitted.

C׳mon, put a minimum effort to realize, that it was the same kind of original intention behind any js framework - so that you don’t have to write something unnecessary. This is absurd statement. It doesn’t mean that the OP framework is bad or that SPA idea is not generally abused etc and doesn’t call for some changes etc. It’s just a ridiculous and somewhat arrogant way to promote your yet another fancy js thing.

And you still don’t get it. Nevermind

No, I get you perfectly.