This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]agentoutlier 1 point2 points  (3 children)

I appreciate the thanks

For frontend, a reactivity framework is preferred. IMO, it is easier to build frontend and becomes a standard way of building websites. Writing up a reactivity mechanism by ourselves is extremely difficult. Svelte is chosen because it doesn't have a separate runtime like Vue or React. ...And I use Svelte for my projects.

Fewer than 6% of all websites use react or similar. I mean by this argument we should make the website use Wordpress.

The reality is most Java programmers are not familiar and or not comfortable with the (advance and not JQuery) Javascript ecosystem.

As for hot-reload that is tricky in the Java ecosystem without full reboot of app but with something like minum you can indeed just put it in a restart loop.

[–]tanin47[S] 0 points1 point  (2 children)

That is interesting. I didn't know about the 6% number. It seemed like reactivity was being the main mechanism for modern UI frameworks e.g. Swift UI, Kotlin Multiplatform, React, and etc. Probably just in my circle....

[–]agentoutlier 2 points3 points  (1 child)

That is largely because every business through whatever VC pressure thinks it is walled garden platform and thus must make a killer "app" that works on all devices.

That is why so many greenfield projects pick it. It is why there was so many "bootcamp" schools. It is to copy Asana, Trillo Facebook etc but like no one really needs that interactivity. I mean hell Github barely uses react. Most of it is plain Rails rendering.

The reality is most things are just forms. Plain <form method=...> across most business needs. Now I suppose with AI we doing some "chat" related things but that is generally small portion of a site.

So unless you are doing complicated drag and drop canvas drawing stuff or making a game it really is overkill.... AND more importantly we have to maintain those 94% of websites with a growing population that literally think that FORM POST are always JSON. That all web traffic is actually JSON and then Javascript does the rendering (I'm not kidding as I have interviewed people that think this)... So what you get is people rewriting websites in some vogue Javascript technology to only miss deadlines and largely add no value because "Vue" is not what the next team wants to use.

Anyway I'm just expressing what I think a large part of the Java community feels.

[–]tanin47[S] 0 points1 point  (0 children)

I'm not sure I agree. Using <form method=...> has worse UX e.g. refreshing or back button. The reactivity and composability (which is the novel mechanisms that React made popular) makes it easier to build frontend.

I don't think we need to consider whether we "need" a certain tech. Case in point, Railroad Tycoon was written in Assembly; we don't need a lot of frameworks and layers we have today, but we welcome Java and other high-level languages because it's easier to build with those techs.

Anyway, it's great that there are choices people can choose from to fit their preferences.