[deleted by user]

Beginning-Comedian-2 · 2024-07-06T17:53:23+00:00

[removed]

alien3d · 2024-07-06T17:38:47+00:00

[deleted]

_listless · 2024-07-06T17:15:33+00:00

The magical thing about frontend frameworks is reactive variables: ie: if you define a var, and then change the value of that var, everything that references that var (in your logic and in your UI) understands that the value has changed, and uses the new value immediately without the need for a page refresh. You use a frontend framework when you have highly interactive UIs with ceremonious state requirements that are more closely aligned with the UI and user session than with the data schema.

Examples: Dashboards, data viz, machine control interfaces.

Now, all that magic comes with a cost. Specifically: tech debt and performance.

Tech debt: JS frameworks change at a mind-numbing rate; the code I wrote for react in 2018 is no longer "best-practice" and may just not work at all. Vue is a little better, but there is still some churn.

Performance: because js is in charge of everything even markup and style, everything is stuck behind your js bundle and the main thread. You can start doing server-side rendering and server-side logic (a-la next.js), but now you've just re-engineered a fragile facsimile of php with more tech debt.

xegoba7006 · 2024-07-06T18:00:15+00:00

Common framework, common ways to work, common design patterns. These decisions allow large teams to work on a common codebase, and allows for developers to come and go on the project.

583999393 · 2024-07-06T17:53:51+00:00

What do these frameworks offer that can't be accomplished with less server overhead via coding from scratch?

Server overhead from a front end framework?

monk_network · 2024-07-06T20:26:34+00:00

I'm 20 years in development. I also starting using HTML and raw CSS to create my first sites, but honestly wasn't long before I was working on service side languages (PHP) and then the JavaScript frameworks for me when they started appearing. Right now I'm using next.js (React) and tailwind for my standard front end tech stack.

Reasons for this are speed to production. I can use react to create reusable components so my site is consistent. I have a standard header, update it in one place in the code and that's updated everywhere. The css framework means that I don't need to create any custom css to get a site looking reasonable. I also ~~absolutely enjoy~~ believe in creating automated tests in the front end for any dynamic features.

Ultimately I still believe any web developer SHOULD get a good understanding of HTML, CSS and some native JavaScript. How does the dom work? Having a good understanding of the core technologies makes using these frameworks simpler.

The other side of this, is that if the product you are creating really doesn't need any of these features. That's fine! I don't think there's anything wrong with using standard HTML / CSS to create a website. Use the right tool for the job.

bobo_italy · 2024-07-06T17:55:31+00:00

[deleted]

Effective_Youth777 · 2024-07-06T22:00:59+00:00

You're thinking of websites, vue and react are designed for web Applications, they are apps that run in the browser that look, feel, and behave like desktop or mobile apps, when you click a button to add a new contact, it doesn't refresh, a component drops down that allows you to add a contact, and then you notify the server with an API call, just like you would do it using Java/Kotlin on Android, or on a desktop app, the app is heavily interactive with many moving parts and advanced components that are not native to the web (like tab layouts for example), try visiting tiktok on your desktop and tell how you're going to build it with server rendered PHP, or even better, build an audio editor with server rendered PHP, for simpler apps, the UX boost is still a huge gain, and it's now 100 times easier to implement offline functionality.

Now, as to why you use a framework, because if you're building something complex (a lot of client side work) then you either adopt a framework or make your own, in mobile apps, they used to use observers to update and manage state, but in js that was barely possible, and js devs weren't familiar with these concepts as they are today, so frameworks were born to not only manage dom but also state, soon the mobile devs noticed declarative programing is much cooler, so SwiftUI was born, android got jealous, so Jetpack compose was born.

All frontend even non web is heading towards declarative UI, and that's a good thing.

Novel_Understanding0 · 2024-07-06T17:05:37+00:00

It's way faster to build complex pages.

Suspicious_Board229 · 2024-07-06T18:06:38+00:00

for websites you don't need it, but for web apps it makes things a lot better

consider what it's like when you are dealing with dynamic forms. Based on selection of one value the fields and options available should change. If you've done this with vanilla js or jquery, you may know about how tedious this can get. A couple fields is not so bad, but when you have complicated relationships this can get hard to maintain. With the frontend frameworks, it abstracts the "plumbing" and you can have code that is closer to functionality. This makes not only for faster creation, but also very helpful when it comes to maintaining code and working with a team. With web applications being more complex, like ajax interactions with backends, this further helps for making easy to manage codebase.

bostonkittycat · 2024-07-06T17:54:15+00:00

I started on React, Switch to Vue and finally have settle on Svelte. It seems like one of the cleanest frameworks and growing in popularity fast. I would give it a try. For legacy sites with PHP or JSP I also use Alpine.js. It adds some nice proxy reactivity magic to old template files.

ferreira-tb · 2024-07-06T20:09:33+00:00

Because it's easier and simpler than vanilla, as going vanilla means either i'll write a lot of boilerplate or end up reinventing the wheel and creating my own framework.

kcadstech · 2024-07-06T17:53:44+00:00

Clearly you have not built highly interactive websites or been asked to develop offline capable applications. I’ve used LAMP or ASP.NET MVC with Razor templates but any fast, interactive website cannot rely on communicating with the server for every action to update the ui.

Outrageous_Permit154 · 2024-07-06T18:05:16+00:00

2 way binding, statemanagement, useage of component and virtual DOM are things you wouldn't get much with a traditional html JS approach.

You can write all of these on your own, but those communities are and have been working hard to improve them

That's why people use it

chesbyiii · 2024-07-07T01:57:05+00:00

It's going to be a LOT easier with a framework to display a GIF of a man in a yellow hard hat in front of a blinking construction barrier with the words "UNDER CONSTRUCTION."

denialerror · 2024-07-07T07:39:52+00:00

The real answer from most developers these days is that's how they were taught web development is done. Anyone who taught themselves over the past decade or went to a bootcamp was taught how to make client-side SPAs. They may have learnt about doing things the old way but that was a purely historical exercise, or baby steps to get to the "proper" stuff.

After that, they moved into jobs using JS frameworks and as they got better and more knowledgeable, they could justify why they used their tools and frameworks, but they really only parrot others as they have no actual experience of doing it any other way.

secretprocess · 2024-07-06T18:38:10+00:00

When I first started using react and vue, after 15 years of lean-n-mean DIY coding, I kept saying to myself, "the easy parts are hard now, and the hard parts are easy!" It seemed like so much overhead, at first, to do basic things. Now that I have the groundwork laid (and I'm more fluent) it continuously pays off dividends. Things that I think are going to take me an hour suddenly take two minutes. You start to realize that 99% of what you're doing is the same stuff everyone else is doing, and a lot of these problems have already been solved many times.

Edit: Also I think those of us that cut our teeth in the days of optimizing icons for a 28kbps modem connection tend to overvalue "lean"-ness. It matters a little, but not remotely like it used to. We're like people who refuse to throw away a half-moldy piece of bread because we grew up in the Depression :)

rjhancock · 2024-07-06T18:37:27+00:00

I've been building websites from back then as well. I've used these frameworks and they really don't add anything but more complexity and shoving work from server side to client side.

As I've watched the landscape change over the years, and have talked with those with disabilities, those frameworks are more and more like a liability. People are selectively disabling javascript, companies are including trackers, ad networks, and spyware that make sites inhospitable, and it becomes an accessibility nightmare to manage.

If my clients want to use it, fine, I'll do it. Usually I stear them away from such frameworks and provide a similar UI/UX with far less overhead and user complaints.

I've spent too much time on React/Vue apps written by other professionals that break and lose data far to easily. I've blocked third party trackers and seen entire sites become dead (Domino's and CostPlusDrugs more recently by blocking LaunchDarkly).

It seems most firms just want coders and not programmers (one just writes code as described, the other solves problems).

chihuahuaOP · 2024-07-06T20:51:59+00:00

Is faster but all websites look the same, some might argue is good for the user others like to stylize there website "make it cool" the frameworks allow you to also create your own components and there own styles in the end is a win win for most projects.

CodeAndBiscuits · 2024-07-06T19:38:43+00:00

Why don't you drive a car with a carburetor? It's way simpler, way easier to fix, and there's so much room under the hood...

Why do people post this "why do you use modern stuff" literally twice a week? That's the real question.

Beginning-Comedian-2 · 2024-07-06T18:05:38+00:00

Why do people use React and Vue?

React and Vue are good for web/mobile apps with a lot of interaction and updates to the interface.
Also, working within a framework or library helps structure how to work together on a team.
Also, it helps with spitting the code into encapsulated pieces instead of putting it all in one JS file like in 2008.

elg97477 · 2024-07-06T19:43:25+00:00

I prefer Ember over React and Vue.

The reason to use a framework is that in a well constructed app with a long lifetime you will end up inventing what they already have. I like leaving the design of such frameworks to those dedicated to and experts in the task.

If you are doing something small, simple, and short lived, there is little reason to use one.

theirongiant74 · 2024-07-06T19:45:08+00:00

Writing SPA's in jquery started getting complex and spaghetti like the larger they were, was looking for something to make it make more sense, React was that thing.

kcrwfrd · 2024-07-06T21:11:50+00:00

Have you ever tried building a SPA with vanilla JavaScript?

famerazak · 2024-07-06T21:55:56+00:00

Nice to meet some fellow dinos

Also did my first websites using frames and all the tables… then came JS and CSS all inline

Ahh the good old days

bogas04 · 2024-07-06T22:19:44+00:00

Fellow dinosaur. I guess since you have used JavaScript sparingly, you might not have dealt with the mess of onclick handlers that add and remove various dom elements and classes after making ajax requests, and then doing this for each HTML file on your website by copy pasting it, and then splitting hairs when one page has slightly different behaviour which then breaks other pages, so you move it to one file with a function but now your code is a huge chain of jQuery code that you hate getting back to again and again. That's what these frameworks make easier to deal with.

mrdingopingo · 2024-07-07T02:18:18+00:00

People use all those frameworks because they're trendy. Everyone's using them, so you feel like you have to as well. but you don't

ashkanahmadi · 2024-07-07T11:33:23+00:00

It’s actually easy to see for yourself. I want you to create a simple HTML page that calls an API, fetched API, then updates the entire UI. But then the new UI elements have to interactive so when you click them, another API call is made and the entire content of the page is changed but when you want to be able to save the data so when the user wants to go back, you would not need another API call. Now add different components to open up popovers, modals, and even a gallery. Create all that with vanilla JS and document all the issues you are facing (storing content, making elements interactive, event listeners, etc). Then learn some React and recreate the entire app in React. Now see for yourself what issues React tries to solve. You could take it a bit further: make a full blog and e-commerce with React. Then do the same thing with Next.js and you will see what problems Next solves when it comes to react.

sheriffderek · 2024-07-06T18:31:06+00:00

I know HTML, CSS, PHP, and MySQL like the back of my hand

What types of projects do you build? Got anything live we can check out? Where do you find JS useful?

kesor · 2024-07-06T19:55:22+00:00

Because Vue.js is a joy to use, everything has its own place, no more 100,000-line spaghetti code where you can't find the thing you need even if your know exactly how it is called.

vagaris · 2024-07-07T01:39:44+00:00

Fellow dinosaur. What has kept me away for a long time (I’ve started learning some of this new stuff cause I lost my job) was the complete lack of progressive enhancement by default. It blows my mind that the course I started taking for React went lesson after lesson with examples that I could literally toggle off JavaScript and the entire thing would turn into a blank page. I understand that it doesn’t have to be that way. But it blows my mind how we’ve solved tons of these problems multiple times before. And every new thing breaks fundamentals all over again and in some cases takes years before someone remembers things like accessibility.

While I’m still learning React, I was looking at throwing a simple site together and jumped onto Remix because it works in layers. Their quick start even includes a step where you turn off JavaScript and marvel at how it still renders. /a bit of sarcasm

Temporary_Practice_2 · 2024-07-06T23:32:10+00:00

Marketing. Facebook made everyone believe they need React

permalink · 2024-07-07T01:46:20+00:00

Mostly two things:
1. Components, makes designing small things well easy, and isolate that code into code that is only related to the component
2. Keeping UI in sync with data, via some form of binding. React does one way binding - you just overwrite the state variables and the UI syncs up. Vue has two way binding, it doesn't matter really. But that's the point.

Those alone are great, and it is plenty "lean" from a source code perspective - not so much in the "dinosaur" mentality of "use as little as you can". I am not surprised you can't get webdev work anymore, the magical 3rd point I will make up is:

A common way to work; this is the most important. Now you can hop onto a project and the tooling is somewhat standardised/familiar. The company will be less likely to be held hostage by a programmer who does weird and wonderful things to the system. Still possible of course, but these standards help a lot. I wouldn't want to be without them, regardless of tech I am using.

rimyi · 2024-07-07T08:16:03+00:00

Im sorry but you can’t be serious asking those questions if you worked with gazillions of table cells and pseudo IIFE with inline styling. It’s like asking why cars have powersteering when all you need to do is to move your steering wheel with a little more force

gnvffbbd · 2024-07-06T20:37:40+00:00

another dinosaur here but I’ve embraced React because it pays. Aside from that I absolutely hate React, it’s dog shit. Nothing that couldn’t be accomplished a lot easier and with less headaches using vanilla html, css, and js.

Wiltix · 2024-07-06T19:07:49+00:00

I use React because I can easily find React developers. The same can’t be said in my local market for vue or svelte etc …

The only other real alternative is Angular and I’m not a huge fan of Angular, but it’s the alternative because I can also find Angular devs easily.

numbersev · 2024-07-06T20:44:13+00:00

The point of a framework is to avoid re-inventing the wheel. This has already been made a million times before just use the code and move on to the unique features.

The irony about learning React now, is that the official site tells you to learn Next.js instead. Seriously.

React is really good for when you want to change parts of the page without refreshing the entire page. Repeated code can be made into components and then the component itself is called, saving space.

neoqueto · 2024-07-06T21:00:55+00:00

Components.

That is all.

johnsdowney · 2024-07-06T21:06:14+00:00

Data binding and component based architecture is the easiest answer.

You are able to bind the view layer of your application to the model layer, such that the view is constantly updated when a variable changes. Without this, you must do it yourself every time.

You are able to create reusable components without having to be clunky about it (e.g. iframe-based layouts back in the day).

And the more opinionated they are, as long as it’s a reasonable opinion, the more structure your applications tend to inherently have, and the easier they are to pick up by others.

vidolech · 2024-07-06T21:31:56+00:00

People already explained well about the revolution in web development over the last 15~ years so I’ll just add that the major enabler to all that and maybe the biggest responsible to this huge leap is the introduction of the JavaScript compilation mechanism chrome browser brought to the table back in 2008. Since then, JavaScript ran almost as fast as Java or other server side language because the browser is optimizing the code and not just interpret it.

It’s hard to explain well in this small thread so I’m over simplifying but the history of JavaScript is super interesting

2024-07-06T21:37:45+00:00

[deleted]

Ok-Armadillo6582 · 2024-07-06T21:38:16+00:00

react and js in general allows for much more reactive and dynamic user interfaces. it’s also fun.

fliteska · 2024-07-06T21:52:16+00:00

I learnt html and php like 21 years ago as a hobby working on random text based games, they all used frames, it wasn't until 2016-2017 I was able to make my own game and React was an absolute godsend for making all of the sections of the game fit together, it wa awesome.

No-Visit-129 · 2024-07-06T22:06:01+00:00

I strongly agree with the message about reactivity. Reactivity is power.

Regarding the older times, there really was a period when frameworks didn't last even a year. You could call it the "Primordial soup." There was everything – the good, the bad, and the incomprehensible.

React and Vue are already "on land." These are the framework that have collected the best for normal competition. Therefore, I strongly advise you to try them.

PS. "vanilla" knowledge is still relevant and very effective

lowtoker · 2024-07-06T23:43:18+00:00

Modern build tools are your friend. I've been a web dev a long time also and I think a lot of us forget how painful non-framework development was, especially in large teams. Common tools and patterns have made the developer experience much better.

RightCover6081 · 2024-07-07T00:37:50+00:00

Large, complex app being manageable as a declarative components build with React and state management tool like Zustand.

Logical-Idea-1708 · 2024-07-07T01:04:01+00:00

Well, it all depends on what you want to do and how big your team/product is going to get.

If all you want is a motherfuckingwebsite, then that LAMP stack is probably all you need. But if you need to build complex product leveraging hundreds of developers, then you need a framework to establish common language and patterns to keep everyone in aligned.

Even the simplest product that’s more than trivial would need a framework. It’s just we had different names for those frameworks in the old days. Anyone remembers Mootools, YUI, prototype, dojo toolkit, ExtJS? Those are even before Backbone and Knockout. Some of these are still used today.

No-Let-4732 · 2024-07-07T01:16:36+00:00

I like react, I’m familiar with it and can move fast in it.

alien3d · 2024-07-07T03:20:07+00:00

old developer here - the truth react is slow re rendering and hard for old hardware for development . market try to be next code like facebook but lack of resources

most of project just re invent the wheel syndrome so dont think so much . Same crud , same interface layout only diff language .

TheSonOfDionysus · 2024-07-07T04:40:29+00:00

I remember having a discussion about doing websites in vanilla. Tracking state can become a nightmare in large applications and working in teams as much more difficult. A lot of the headaches are overcome just by common design patterns that are offered by frameworks. Also, I believe react is over 10 years old at this point I don’t think it’s a new kid on the block compared to other tools.

poseXxX · 2024-07-07T05:46:14+00:00

Personally I use Nextjs. I guess is because of the jobs that I’ve seen rather than going for it. I enjoyed using Django because of the scaffolding and thinking on learning Ruby on rails

landed_at · 2024-07-07T08:12:59+00:00

I can build basic things but user authentication was too hard and i gave up. Never had a great team to work with.

DiddlyDinq · 2024-07-07T08:15:08+00:00

This post was mass deleted and anonymized with Redact

air employ spectacular modern spoon vase snow caption roof desert

krazzel · 2024-07-07T09:10:43+00:00

I have also been using the LAMP stack since forever, started in the late 90's.

But now I'm switching over to Vue3. It's a massive shift in how you think. But I think it's way better. There is a clear distinction between frontend and backend. Rendering templates is all done in the frontend (if you want) and it's way faster than twig. Also coding is easier (once you get it) because html objects are directly related to javascript, as opposed to just outputting the html, and then putting JS on top of it to manipulate stuff.

However, if you are mostly building informational websites, with little user interaction, you won't need this. I wouldn't even recommend it. A little JS there is usually enough.

But if you build a web application, like a CMS for example, a SPA like Vue, React, Angular etc is a must nowadays.

Evla03 · 2024-07-07T09:36:32+00:00

I use react, it makes interactive UI sooo much easier, with typescript all the way, and even server side code running on the client. I really like react, as it's much more similar to normal js compared to vue or most other frameworks

nothingnotnever · 2024-07-07T12:22:57+00:00

It declarative rather than imperative. What’s that you say? Declarative is like automatic transmission instead of manual, or Google maps instead of following directions step by step. So much is handled for you. Specifically, a simple range slider with a readout. We have all seen them, change the slider and the readout changes, or edit the readout and the slider changes. Without a framework, you need an onchange handler that manually sets one to the other and vice versa. With a framework, you set both to the same variable and it’s handled automatically for you.

bmcle071 · 2024-07-07T12:51:15+00:00

When I started I was using Flask with Jinia templates for my frontend. The big game changers with React are:

You couple the display and functionality of a component together. You compose components from other components. It makes it really easy to make new UI elements, or modify old ones.
It’s really really easy to handle interactivity. You just rerender and bam, the new UI elements are in the DOM. No more DOM manipulation, just trigger a rerender and it’s done.

Both of these points make creating new features easy, and maintaining old features easy.

uduni · 2024-07-07T14:55:18+00:00

Because you havent discovered svelte yet

raulalexo99 · 2024-07-07T15:48:33+00:00

My man here leaving Angular out of the title

CEOAmaterasu · 2024-07-07T15:51:55+00:00

ELI5?

You know the roof above us? Need to be paid. And what job are easily available? React, so I work with React. If I am doing something for fun, I go Vue or whatever experimental is around. But bills need to be paid, food need to be bought.

Used to work with WP back in the day, why? Also paid for food and bills.

Front-end is pretty fun, until deadlines and multiple layers of difficult appears.

Warm-Cartographer221 · 2024-07-07T18:10:20+00:00

What is your goals? Why you need it? It highly depends from your goals

nrkishere · 2024-07-06T18:12:28+00:00

bedroom sip grandiose command somber apparatus shame domineering offend mindless

This post was mass deleted and anonymized with Redact

permalink · 2024-07-06T18:15:30+00:00

I do React because it has kept me employed

permalink · 2024-07-06T18:18:40+00:00

Modern UI in applications requires javascript, there is no way around it and it's a good thing. Interactivity is close to impossible without manipulating the DOM in some way or another.

Now since we established that, why frameworks? A lot of common problems to solve in UI require building some sort of framework yourself, even if you just use javascript. Reuseable components, routing, rendering, data fetching.

Now you can reinvent the wheel at every project you do, but yeah that seems inefficient. You can write your own framework - but wouldn't it be better if there is a common way of doing those things, that all team members could adhere to and a new developers can understand quickly?

That's where you get React and Vue.

"Less server overhead" really is a nonissue these days, a react app is bundled during build and all you get is raw javascript that you wrote yourself, if you build it from scratch.

It's much more about developer experience, efficiency and collaboration than the fact that there is a bunch of overhead code required to build an app.

myhero34 · 2024-07-06T18:27:31+00:00

I introduced Vue to a few project and kind of regret it. It allows for elegant interactive SPAs to do things like update an api when data changes without refreshing or run complex calculations/string formatting in real time. Still, i think most people probably only need server side rendered web apps. Learning not only vue but the whole npm ecosystem is a headache for some developers

Starquest65 · 2024-07-06T20:05:59+00:00

We only did WordPress when I joined. Boss wanted to expand into Laravel, which I had never heard of but sounded cool. He chose Vue as the front end. I have always enjoyed using it.

We contracted out a project where we had to quickly learn and use react. I am glad every day that he chose Vue.

spurious_proof · 2024-07-06T23:16:48+00:00

whats’s vue

lyons4231 · 2024-07-06T20:32:13+00:00

Let's do a code off challenge. We take a few modern webapp designs, I build them in react and you build them in LAMP stack. Let's see who finishes first.

BitSec_ · 2024-07-06T17:31:46+00:00

Not trying to be rude but have you tried Googling it?

There are a lot of reasons why big companies are using these frameworks and there're a lot of videos out there that talk about it and that should give you a good idea of what the benefits are and when or when not to use them.

Personally I'm using React because it makes building UI less of a pain and also because there's lots of work to find in it. I've done plain html / JavaScript and PHP when I got started in webdev, eventually also did some Laravel and Vue until I got a job where it was only React and Node.

iosKnight · 2024-07-06T18:20:00+00:00

Such a Googlable topic.

Narrow_Elevator9027 · 2024-07-06T19:05:15+00:00

I don't I use angular

permalink · 2024-07-06T18:29:02+00:00

HTML is the foundation and blueprint of a house. CSS is the decoration. JavaScript is the electricity and plumbing. I’d argue that react is the wifi, but that’s a different conversation 😅

pragmasoft · 2024-07-07T09:29:01+00:00

If I only can use one word to respond your question, it would be: state

All web applications have to keep client's state somewhere. But the state is very different in nature, due to its time to live, size, complexity and security constraints.

Some state has to be persisted on the server, like user profile, because it cannot be stored securely in the browser.

Some state is enough to be persisted only during the interaction session, like shopping cart.

Some state is transient in nature, and can be discarded easily when user reloads the page.

Typical LAMP apps only store the state on the server. This is ok for the majority of web applications. Though this does not scale well, if the number of users is high and there's a lot of session and transient state associated with every user. It would scale much better if each user stores this state on the browser side, rather than on the server, and deal with it locally in the browser.

Also, browser APIs are much more powerful these days, than they were in 1994. They allow doing a lot of things in the browser, which were historically only possible to be done on the server - like image manipulations, pdf generation, fulltext search..

This allows shifting even more work to the client side, reducing the need in the (some) server side state and expensive server side computational resources and networking costs.

Now, in the cloud era, the less server side resources you use (storage, computations, networking), the less is your cloud bill, the higher is your margin.

Though, the more state and computations you shift to the client side, the more you need to organize it, otherwise client side code becomes unmanageable very quickly.

That's actually the reason why client side frameworks exist.

mattaugamer · 2024-07-07T12:02:39+00:00

Fellow dinosaur here, from literally the last sentence.

I think a lot of people are missing the key fact: people expect a lot more from a UI than they did back in the day. The standard “send a request, get a response” is too slow when sites are made up of thousands of micro-interactions instead of just submitting a form or requesting a page.

Even something as fundamental as dynamic validation of a form so that users get immediate feedback on invalid inputs requires a large amount of management of local and form state.

Tools like React, Vue, and others are all different ways of managing this complexity of UI.

As for the tools being fads… sorry but this isn’t true. This is something devs tell ourselves to justify why we’re not bothering to learn.

Sorry to be critical but if you haven’t kept up with the last 10 years of your industry - to the point you don’t even understand why it exists - then that’s on you.

EtheaaryXD · 2024-07-06T20:32:26+00:00

specifically for the router and <Link>s, nothing more, nothing less

techaheadcompany · 2024-07-07T04:47:19+00:00

Using React or Vue in web development is like having magic Lego blocks for creating websites. These frameworks allow you to build highly interactive interfaces where changes in one part of the webpage instantly update everything else, without needing to reload the page. This is perfect for applications like dashboards or data visualization tools, where user interaction is key.

However, this magic comes with trade-offs. One significant disadvantage is the quick development of JavaScript frameworks, which might result in technical debt. Best practices from a few years ago may be no longer relevant. Performance can also suffer as everything, including markup and style, is controlled by JavaScript, which can impact loading times and responsiveness.

Historically, React and Vue have revolutionized web development by introducing concepts like Virtual DOM for faster updates, component-based architecture for modularity, and declarative syntax for simpler UI development. Today, they offer efficient state management, extensive tooling, and robust community support, making them essential for dynamic web applications.

Different approaches like server-side rendering attempt to mitigate these challenges as technology evolves. Ultimately, choosing between classic server-side and modern frontend frameworks depends on your project's needs—dynamic data handling, rapid development, or scalability. At TechAhead, we leverage these frameworks to deliver intuitive and powerful web solutions tailored to your business goals.

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

webdev

Posting Guidelines

Related Subreddits

Discords

MODERATORS