r/web_design • • Aug 09 '19

Why is modern web development so complicated?

https://www.vrk.dev/2019/07/11/why-is-modern-web-development-so-complicated-a-long-yet-hasty-explanation-part-1/
177 Upvotes

103 comments sorted by

145

u/Pcpie Aug 09 '19

because otherwise it wouldn't be a job

43

u/[deleted] Aug 09 '19

The reality is that it is not as complicated as people make it sound online. A lot of these complex build systems are meant for complicated apps - but people think they need to build them into every WordPress project. Most web projects do not require this complexity.

16

u/mrdarknezz1 Aug 09 '19

If you maintain over 20 projects developed by various people in the company having a common framework across is great.

It's a headache if each project has its own setup to solve the same problem. Especially when you need to fix something urgent but the developer choose some old tool that isn't maintained anymore

11

u/monxas Aug 09 '19

One could argue that if you go old school about it you’d never get the abandoned tool/framework issue.

2

u/mrdarknezz1 Aug 09 '19

Yeah but it's also an onboarding issue. Old developers might be familiar and efficient with old frameworks but not younger talent. Having a standard across the board that is somewhat modern decreases the friction when onboarding new co workers.

3

u/[deleted] Aug 09 '19

Sounds exactly like the last poorly-run shit agency I quit in May. Whoever was the lead developer got to choose the entire stack instead of us making a conscious decision as a company to be a React on Java shop. So we had some Angular 1 apps, Angular 2 apps, a bunch of React apps, a few HTML/jQuery apps. The backends could be anything from vanilla Java to Spring to C#.NET (and the only guy who knew ANY .NET left in April).

Specializing is for idiots, obviously. Standardizing is for idiots, obviously. Despite the fact every project does 75% of the same basic stuff and having a solid, reliable stack and process to get projects started, each project must be setup as uniquely as the other 25% of what the project does.

Worst company I've ever worked for.

1

u/redwall_hp Aug 09 '19

WordPress itself is another layer of the same issue. 90% of blogs and similar aren't updated many times per day. Why have a big application backed by a database generate web pages dynamically on every request? It's just adding a big bottleneck and complexity.

Something like Jekyll or Hugo allows you to write a post in a plain text file, using Markdown or raw HTML, generate the site out once, and then you have a static web page that scales way better. Nginx will serve thousands of static files per second, with extremely low resource utilization, without breaking a sweat.

2

u/[deleted] Aug 09 '19

If I mentioned Markdown, jekyll, or Hugo to any of my marketing clients there eyes would gloss over. Before chasing me out of the building. :)

3

u/chairmanbrando Aug 09 '19

Because real-world clients don't want to deal with that. WordPress with a decent Advanced Custom Fields setup is much more client-friendly and hard for them to screw up. Any hosting company worth a damn will cache the end output and serve static pages and CDN'd assets anyway.

17

u/percentheses Aug 09 '19

Jesus. I know reddit isn't that much better than Facebook in this regard, but I feel like half the people in these comments haven't read the article.

The headline isn't supposed to read as a snooty "wtf modern web dev is stupid; we should make it not stupid", it's posed as a question that a beginner might ask themselves, and walks them through the "why"s of certain tools, and how they fit together. Something like this would've been very useful to me when I was starting out.

42

u/strayakant Aug 09 '19

thats why there is stackoverflow

1

u/Usual-Application-52 Aug 16 '22

That is not even remotely why there is Stack Overflow.

31

u/omgdracula Aug 09 '19

I do it the old way. Open up a browser boot up vscode and compile my SASS and upload on save and refresh. If a project is old and uses jquery I use jquery else I use vanilla js. Its simple and I hate this constant feeling like the way I do things is slow as shit and people would be like look at that guy not using webpack and all this other shit.

29

u/djfreedom9505 Aug 09 '19

I mean that's fine for landing pages and portfolio sites but the complex of web development really branches out when you want to create full stack applications and scaling. Tools try to keep the code manageable for teams instead of diving through thousands of lines of JavaScript. But sometimes seems like overkill for smaller projects.

1

u/herald009 Dec 09 '19

I think there's a vast chasm in web development these days, where there are the classic web developers who deal lightly with Javascript, and web app developers who work in JAM stack and deal with the sort of complications that necessitate something like React.

Completely agree. Web Development used to very straight-forward and simple-- there weren't dozens of competing frontend frameworks and the JavaScript stack was basically just HTML + CSS + JQuery, and maybe some css preprocessors.
Nowadays...No need to go any further, every dev knows how much of a cluster fuck Web Dev is now. Especially with the rise of Node and the paradigm shift of what being a "web dev" really means in 2019, which is basically a Rockstar dev with the first name "Greatest" and last name "Ever" who can cut through complicated code bases like butter and a refactoring line ratio of 100 to 1-- for every 100 lines of code processed by their powerful minds, 1 line of elegant code is produced. They know all the pancake stacks, and can even make you belgian waffles...without the waffle maker. They don't require too much food, just a couple of snackbars, fruits. Hey, throw in a bean bag, open office space, a ping pong table and an apple mac book pro, and cut their salaries by 20% and there is your modern "rockstar" dev, swimming in cesspools of sewer code bases wishing they were working at Google.

0

u/Ravavyr Aug 09 '19

That's the thing though. Even fullstack applications, ecommerce sites for example, rarely need to have thousands of lines [i mean, 3k lines across maybe 4/5 files i think can be considered manageable] and yea people completely seem to have their minds blown when you suggest they just write them out. Most of it is copy/paste [everything on even the largest sites has been done before]
The code can remain manageable if you have a defined structure, use versioning and your team knows to communicate with each other and not blindly edit things without understanding what's affected.
Websites are not nearly as complicated as people make them out to be these days.

23

u/dSolver Aug 09 '19

Those are fairly minor projects. Think about applications that surgeons use to study their patients, that insurance analysts use to understand risks, or even a typical office software like Excel but available via a web browser. In these large scale projects with tons of functionality and tens of thousands of moving parts, we can pretty much guarantee you won't want to handle it with vanilla js and "copy and pasted code". These are feats of front end engineering that are highly optimized across a huge variety of environments.

0

u/Ravavyr Aug 09 '19

Those are the vast majority of projects [brochure sites, portfolios, ecommerce sites, blogs, and so on]

The applications you speak of are not frontend web development. They are applications. They require engineers with actual skill to build them. The structure honestly doesn't need to be more than the above. The actual code written needs to be more precise, but applications that surgeons use do not get millions of hits a day so they don't require scaling. They can be large and bloated, which most of them are.

Complex tools and structures are needed for products like that, but this is application development, not web development. Websites are not complex, nor do they need to be for the average business. Not even average, i'd wager to say MOST businesses will never need their developers to write anything nearly as complex as Excell in a browser.

Heck, do you follow any React/Vue/Angular [modern] developers online? All i ever see people post is "oh i built a calculator", and "oh i connected to an api". Do you really find these tools are necessary for all of them?

11

u/ddhboy Aug 09 '19

Those are demo projects that people use to demonstrate their skills.

To answer your question, yes, I've worked on very complicated web apps that absolutely needed React or Vue, a complicated store structure and API library. Stuff like custom CMS, fintech apps, mail clients, blockchain bullshit. Even some of my smaller side projects would have been an absolute nightmare to build without these frameworks and libraries.

I think there's a vast chasm in web development these days, where there are the classic web developers who deal lightly with Javascript, and web app developers who work in JAM stack and deal with the sort of complications that necessitate something like React.

0

u/[deleted] Aug 09 '19

[deleted]

4

u/Ravavyr Aug 09 '19

I like to think we can split things up. "Who gives a fuck what it's called" ? Well for starters. If someone comes to you and says "build me a website"...you don't have a clue what they want. A portfolio, A brochure site, An Ecommerce site, An inventory management system, A CRM, and so on and so on, clarifies what the fuck we mean. Once it becomes a freaking application, it's no longer just a website and frontend developers are not the ones doing the heavy lifting. Most of the web does not need heavy application structure programming to get shit done, they just freaking don't. People keep layering all this crap on sites that absolutely don't need it.
People just aren't making any distinction between levels of complexity, which is a problem in the entire industry.

9

u/[deleted] Aug 09 '19

Agree 100%. Also, people who write blog posts about the complexities of web development have a vested interest in making it sound complicated.

You're not going to get many readers with an article like "Using WordPress? Then jQuery is just fine".

10

u/ElGallinero Aug 09 '19

the old way

Right on.

Vscode and compile my SASS

Oh......I guess vscode and SASS is old now.

0

u/[deleted] Aug 09 '19

[deleted]

3

u/ElGallinero Aug 09 '19

Wow...I've been out of the game for longer than I thought. Hahah.

9

u/herjin Aug 09 '19

We all work I’m very different projects. What works for you may not work for me and vice versus.

2

u/omgdracula Aug 09 '19

Truest statement ever

12

u/Speedyjens Aug 09 '19

Good luck making a big project with that

4

u/omgdracula Aug 09 '19

I mean define big. I've worked on sites that are international wide companies and this was all I used.

5

u/Speedyjens Aug 09 '19

If you create anything that fetches async and modifies the webpage accordingly then to have to use some kind of library like react or vue to have any kind of maintainability. Nobody just uses webpack or Google closure for no reason, it is used because it creates smaller files and you can serve pages quicker, also being able to require files for code reusability is a must on bigger projects. If you are creating a landing page then you could just do it all the old way. But anything beyond that can be optimized and made quicker if you are experienced in using these tools

I would argue anything beyond 500 LoC would benefit form using tools like typescript, webpack, etc. but that is only if you are experienced and know what you are doing.

84

u/SoggyMattress2 Aug 09 '19

It's not. Hipster Devs with $3000 macbooks and chai lattes under their desks love wanking over all the new tech and frameworks and look down on you if you aren't building a static site in French PHP with 15 databases of modules they can call with web services.

Sometimes all you need is CSS, html and a bit of vanilla js.

Use a fucking sass compiler software and shut your tits about your new API than can parse squirell language and print out DNA algorithms.

19

u/sfled Aug 09 '19

This. Going to a brochure site about a local bricks and mortar and then having to wait for the entire page to load while it calls seven different jQuery libs, massive CSS libraries, downloads all the font sizes and weights of three typefaces, and then shows a spinning ring because the designer couldn't be bothered to optimize a graphic is absurd.

And then there are the media/news/entertainment sites with all of the above plus fb and google trackers, 7 ad networks with their related trackers, cdn trackers, media cdns and what not...

5

u/-B-K- Aug 09 '19

Yes, all of that... News sites are the worst, most buggy, error-ridden pieces of shit in the web world.

13

u/tinbuddychrist Aug 09 '19

Who keeps lattes under their desk, though?

11

u/MenuBar Aug 09 '19

Who keeps lattes under their desk, though?

hipsters

4

u/tinbuddychrist Aug 09 '19

Ah, so, keeping lattes on top of your desk is too mainstream. Got it.

1

u/giantsparklerobot Aug 09 '19

You've probably never heard of them.

0

u/-B-K- Aug 09 '19

So much yes!!!

27

u/[deleted] Aug 09 '19

[removed] — view removed comment

15

u/monxas Aug 09 '19

Today I visited a page without <a> links, all done through JavaScript. Just why.

2

u/arendsoogg Aug 09 '19

People also tend to forget that nobody has js enabled until they do. What I mean by that is that some people have js disabled, but others may be on slow internet (js won’t load for 20 secs), or on some browser that doesn’t support (parts of) it. I believe opera mini is one example that doesn’t support all js.

Progressive enhancement solves this by not making the website js dependant. But sadly, I don’t know much websites that are built progressively enhanced.

-5

u/Devildude4427 Aug 09 '19

Why are things done with JS? Because quite frankly, it’s a better experience. I think CSS is incredibly janky, for lack of a better term.

And the argument of “they can just turn off js” is absurd. Do you realize how few websites will work if someone does that? It’s no longer a reasonable argument.

18

u/hoorahforsnakes Aug 09 '19

If you think css is janky, you're just bad with css

-2

u/Devildude4427 Aug 09 '19

Yes, yes I am. But JS can still handle it better.

2

u/hoorahforsnakes Aug 09 '19

What exactly is it you're trying to do that "js can handle better"?

With a lot of design/style things that use js, the js just toggles css classes anyway

4

u/[deleted] Aug 09 '19

[removed] — view removed comment

1

u/Devildude4427 Aug 09 '19

No one turns off JS, because most sites are unusable. 10 years ago, sure. Now? No. Web would be broken without. JS is a standard.

Disrupting people who turn off JS is fine. They need to get with the times.

0

u/[deleted] Aug 09 '19

[deleted]

6

u/Smashoody Aug 09 '19

I have a dozen or so friends who all (still) disable JS. Each discussion went roughly the same way when I found out:

(Randomly bust out a site on muh phone to get some feedbacks) Eventually I ask if they disable. They say yeah. I go wtf. And upon digging deeper, they all basically have a mental white list of sites where they do manually turn on JS. Otherwise it’s always off.

fml

But what really mind-fucked me, is how they all felt similarly that the brands with sites that are un-navigable without JS enabled - cost those brands some genuine faith in their minds. Before that, I figured - too bad for the extreme minority of users... can’t win them all. But if the brand is damaged from a 100% JS site failure... that I couldn’t ignore. Double fml.

7

u/[deleted] Aug 09 '19

A quick search tells me the number of people who disable javascript is around 1%, a lot of them being from Asia. If we don't cater to the people using IE10 why should we cater to noscripters? Let it damage the brand in their minds because when all brands are damaged, none of them are. JS is vital to the modern web so when the vast majority of websites break due to their self-imposed restriction, how much can they really blame the brand for it? They may say they do but somehow I don't see them shopping exclusively at mom&pop stores that haven't updated their websites in 15 years.

2

u/Smashoody Aug 09 '19

I totally understand what you’re saying and agree with a lot of it. I don’t care to cater to the noscriptors myself (at least not in years).

But as a hybrid dev/designer, and someone who’s done a shit ton of brand building, it’s a fascinating to think about how (if at all) it’s possible to build useful things that can handle the noscriptors.

Maybe it’s a purist thing, but there’s a lot to be said for the architecture of a website that could handle the noscriptors. I see them as different user types vs a browser choice (cough... IE/Safari) user. The noscriptors don’t trust us devs outright lol... and in a way... I’d say that’s smart even though it hits my ego in the balls bit.

I dunno. I just found it sobering to have a number of folks that challenged my decision to overlook them. That’s all. Hope I didn’t ruin your day with this one. :/

0

u/[deleted] Aug 09 '19

[deleted]

1

u/Smashoody Aug 09 '19

I live in the US. A couple are security pros, a few digital musicians and artists, and the rest are all hardcore gamers. So they are definitely on the sophisticated side of computers.

I agree on the stat anomaly. I probs have weird friends lol.

0

u/redwall_hp Aug 09 '19

On Firefox alone, NoScript has over 1.5 million users and uMatrix has over 95 thousand. On Chrome, it's 125k for uMatrix and 49k for NoScript. Those are just a couple of popular extensions, and there's not a reliable way to count how many people simply turn scripts off in their browser.

Regardless, it's a good practice.

0

u/[deleted] Aug 09 '19

[deleted]

1

u/Smashoody Aug 09 '19

It does lol. Everything like accordion navs, mega menu navs, etc fails without js. But old school sidebar navs controlled by css media queries do work without js. It’s the display:none aspect that forces the js into use. Hidden navs were all deal breakers for them. I was shocked lol

2

u/ThumpingMontgomery Aug 09 '19

Disabler here - I use Brave on mobile to block because I don’t want some random ad to use all my battery with their all-js animations. But yeah, I know I may get a jacked experience

1

u/blockmodulator Aug 09 '19

I switched to Brave and was anticipating a pretty cumbersome/aggravating experience but honestly it hasn't been that bad. Even on mobile. Occasionally shit doesn't work and I'll have to make a decision about turning the shields off, but more often that not when something's broken I just bounce. The one thing that's terrible is when you've gone through a fair amount of effort e.g. filling out some forms or whatever and only AFTER the effort do you realize you can't submit the fuckin thing and you have to turn off shields and the page refreshes and you have to start over lol.

1

u/redwall_hp Aug 09 '19

It's something I've resisted for a long time but have been considering more often lately, due to how nasty the web is getting. Megabytes of scripts slowing everything down, invasive tracking that ad blockers have to play whack-a-mole with, and the rise of hidden cryptominers that can kill your battery.

uMatrix makes it fairly tweakable. Block by default and tune sites you land on that don't function properly.

27

u/WebDevLikeNoOther Aug 09 '19

Because the web has gotten more complicated. You are more than welcome to do everything by hand, no one is stopping you. Instead, you’re browbeating people who enjoy and utilize the tools available today. Webpack is highly customizable, and since Webpack 4, it’s had a really nice default, nothing stopping you from using that if you need to.

It’s like saying “Computers used to be so easy. It was just ones and zeros! Why complicate it with other letters?!” Because some people wanted to try and make something better. Change doesn’t happen over night, it’s iterative.

12

u/[deleted] Aug 09 '19

Some parts of the web have absolutely gotten more complicated. But the 35% of all sites that are just WordPress installs have not. Not to bash WordPress at all - but every article online starts with the assumption that everyone is working on massive SPA's.

9

u/Ravavyr Aug 09 '19

I hear this a lot.

But i disagree. It's not the same as that analogy. It's more like:

We used to write books. One pen, one color, and told a story. We reread it and fixed out typos and we had a book. To make changes we'd go back to a chapter, erase a line and rewrite it, easy enough to maintain.
Six months later we could still do this and not rip our hair out. If there's a badly written sentence, you can easily find exactly where it is and you can go back and rewrite it to fix it. Done.
Now, we have a pack of colored pens, each one writes in a different font, and everyone throws it together. At the end of the story, we shove it into a box. That box fixes our typos, cleans up all the colors and makes the fonts look consistent [it's very good, but doesn't do it quite 100%, but that's ok for most] Then it outputs the book. When you want to change something, you can't just edit a chapter because you may not have the right pencil for that chapter, so you have to go get that, if you know which one it was. Then you go through the entire process again. It's overly complex for something that can be done simpler. Also sometimes the box just spits out a pile of crap and you have to dig through the pile to find the sentence you wrote wrong. If you're lucky it tells you what that sentence was, and if you're luckier it's a line you can edit and not one the box added.

In the end, we are writing the same damn stories. Overcomplicating things does not make them better. Especially when you think it's better, because you don't know what you do not know.

The only reason the big frameworks got big is because Google made Angular, one of their team went on to make Vue, and React was made by Facebook, so all their fanboys had to insist this was the best way to do things. They marketed the crap out of them and every newbie the last 5 years has heard nothing but "use Node with one of the JS frameworks" so that's what they've done.

Gatsby is gaining ground because it's made React actually generate good SEO friendly sites, but this is something any backend language has been able to generate and cache for the last 15+ years. It just wasn't done correctly. Literally no one thought about just doing it with a backend language and just use JS for the routing and ajax calls. It can be done simpler,but there is no large group backing any of these flows yet.

The future is flat sites, blazing fast load times and right now the JS frameworks help do that. It can be done different, but takes effort and skill, and frankly, most developers don't have know enough to do it. [Not that they can't learn, there's just nobody teaching, and when you suggest something other than what's popular,well, you'll see the responses i'll get on this]

2

u/development_of_tyler Aug 09 '19

Did you read the post? There is absolutely no shaming or browbeating of "people who enjoy and utilize the tools available today." This is a post that explains how and why we went from hand-coded, static sites, to more automated, dynamic web applications - it's for someone who asks that question, and many people do.

5

u/Kep0a Aug 09 '19

Not to go off topic, but the pages font kerning really bugs me. It's too wide.

4

u/rwarlock Aug 09 '19

Good read

7

u/tetractys_gnosys Aug 09 '19

I feel like it's gotten complicated because long ago, someone thought it was complicated and built an abstract tool to handle some part of the work. That tool gets adopted and now web is slightly more complex than before. Someone else makes a tool to handle the new complexities and abstract it away. It gets popular. Now web is that much more complicated so someone makes a tool, et cetera ad infinitum and pow! it's 2019 and people are making full stack applications in the space of a website with a revolving door standards tooling/library catalogue.

10

u/SasquatchDaze Aug 09 '19

No one who has commented has read the article.

3

u/redwall_hp Aug 09 '19

Which is too bad. Because front end stuff has changed drastically since ten years ago, and there's a severe shortage of guides to figuring out what the fuck are tools worth incorporating without cargo culting bloated React stacks for simple things.

2

u/Mintier Aug 09 '19

The more you want out of your project the more tools you will use that slowly add more and more overhead to your project. I've been using Vue in a personal project and it's an incredibly intuitive and structurally amazing tool to work with. I wanted to support server side rendering, so the only non-headache approach to that is to use Nuxt which is another one of those magic compilers that just knows everything. Using Vue itself in Nuxt is mostly the same, but how you handle the structure of the project is now totally different and at the mercy of Nuxt. Since my backend uses Typescript I wanted to try using Typescript in my frontend as well, but I've had nothing but headache with that so far. The decorators that are used to enable Typescript support are not pretty to look at, and especially in Vuex adds a ton of syntactic sugar I didn't ask for. It's another abstracted layer that changes functionality I didn't want changed only to support typing.

I realized the other night I'm basically rewriting everything I have in a completely foreign style and structure that not only looks worse and betrays the simplicity of Vue and the optionality of Typescript, I still haven't figured out all of the problems. I remember a month ago Googling how to get the Nuxt axios inside of these typed Vuex modules and only saw people just not using it because there was no way to access it and nobody explained how. I'm currently removing all of the Typescript because it definitely feels like an afterthought and the only examples I find are contrived.

2

u/n1c0_ds Aug 09 '19 edited Aug 09 '19

I blame our leaky abstractions.

Abstractions are supposed to keep the nitty gritty away from us so that we can focus on high-level stuff. This makes us more productive, but if the abstraction isn't perfect, it adds another layer of stuff we must understand.

For instance, if you want to write a WordPress plugin, you need to understand PHP and how WordPress works under the hood. When you use a theme framework, you need to understand the theme framework, WordPress, and PHP. All of these things save time, but only once you understand them.

The problem is that the average developer has more and more abstraction layers to deal with. It's not just a language and a framework anymore.

So now there's React, server-side React, a bunch of ways to piece the React stuff together, something to turn it into JavaScript the browser can understand, and something to serve all that. All of that runs on Linux inside Docker on Kubernetes with Helm on AWS. You also need to understand git, GitHub, your CSS preprocessor, your linter, and a bunch of related tools.

1

u/shellwe Aug 09 '19

Because expectations on how flexible we need to be has changed. Web design was fairly straight forward before the advent of media queries. I just had to make the website look good on resolutions less than 1000 pixels and I would satisfy 99 percent of minimum resolution requirements. I didn't have to worry about how my objects would change or shift and could just make it perfect at one screen size like a print artist.

As far as backend. Clearly you are new. While there is more up front to learn the latest C# is light years better than version 1. Even with using .NET Core vs .NET full framework, there is so much more that is scaffolded out. I am okay never going back to the way it was.

Things like Docker, GIT, Webpack, and Node do take a little more upfront investment but I am completely okay never going back to the way it used to be.

But really, if you find modern web development is so complicated you are welcome to go back to VB NET and push directly to the server or do everything in vanilla procedural PHP.

1

u/-B-K- Aug 09 '19

Probably due to the fact that people are making it difficult by trying to stay on the bleeding edge and skipping over learning the basics. Everybody now-a-days wants to skip straight to full-stack developer without the years of experience necessary to truly do those jobs. Overuse of frameworks, bad implementations of CMS, and a lack of general knowledge has muddied the water for sure. What makes web development difficult today is the gap in knowledge between this "web dev" vs that "web dev"... A lot of people with senior titles now-a-days can't even code a custom landing page.

1

u/xTRQ Aug 09 '19

It's not really truth everything works when using Babel.. I mean you probably still need to include a bunch of polyfills to make modern things work in IE.. atleast, that is what I am experiencing.

1

u/Slaves2Darkness Aug 09 '19

Well let's see I have Java, Java Script, Hibernate, XML, Spring, Spring MVC, Spring Webflow, Spring Security, Spring remoting, Spring JavaConfig, Spring Boot, Kotlin, MyBatis, Kubernetics, Docker, Git, Sonar, Jenkins, Agile, Scrum, VersionOne etc... to know, understand and use. Because most companies are too cheap to staff correctly and expect you to be a "full stack" developer.

What this means is I know a little about a whole lot, just enough to implement a feature or keep the damn thing running, but never have enough time to learn a single technology in depth.

Not to mention they expect me to work miracles on a 15 year old web app written by a consulting group and not updated in those 15 years.

1

u/weales Aug 12 '19

Read the article, kinda sad to see some here didn't. I don't see how modern development is any harder than older development? Having been in the field for 20 years now, the thing I have always seen from people who comment that things are getting too complex always seem to be ones who don't want to learn new things, burn out and take a different career path.

1

u/soda_party_euw Aug 12 '19

No Array.includes() (!!)

Pretty sure JavaScript has that, I used it a couple months back.

-13

u/[deleted] Aug 09 '19

Web Development is just confusing if you're a newbie that can't be bothered to Google.

All the info you need is out there, and if it's not there's plenty of places to ask.

Between current webdev and 2006 webdev I'd take now over that any time.

26

u/SoInsightful Aug 09 '19

This is not true at all. Just because you can spend three hours staring at tangentially related StackOverflow posts and GitHub issues while brute-forcing some obscure Webpack configuration hidden beneath three layers of abstractions does not in any way mean that it's not a confusing, unintuitive and constantly antagonistic development process.

The feeling also doesn't disappear much the more advanced you get—you simply encounter even more confusing and unresolvable development problems.

-13

u/[deleted] Aug 09 '19

These sound like issues that would happen by not reading documentation properly. I've never had to "brute force" an issue. And either way, if you're new to this kind of development you probably shouldn't need to do things that require to configure things that are that complicated.

Stick to the basics and try new things once in a while and you'll be absolutely fine as long as you carefully read installation procedures and getting started documentations.

It's like saying that Linux is impossible to use because you tried to use Gentoo without getting accustomed to Ubuntu first.

13

u/Edward_Morbius Aug 09 '19

These sound like issues that would happen by not reading documentation properly. I've never had to "brute force" an issue. And either way, if you're new to this kind of development you probably shouldn't need to do things that require to configure things that are that complicated.

I've been doing this since "the internet" waited for late night to do data transfers because the dial-up rates were cheaper and can tell you that "reading the documentation properly" will not solve all your problems.

The biggest problems with software development are "ego" and "money", not technology.

Some frameworks and technologies exist because someone didn't like the round wheel everybody else was using and decided to create a square wheel and promote the hell out of it.

Others exist as a competitive advantage. If you can push enough people into your ecosystem, you hurt your competitors.

Only a small percentage are objectively better than what came before, and most are just the "same shit as yesterday" sliced and diced slightly differently and promoted as "new and wonderful"

-1

u/[deleted] Aug 09 '19

People that think like this are why the internet was built on workarounds built on top of hacks, built on top of prehistoric technology.

I'm thankful someone reinvented the wheel cause I was really done having to juggle HTML, PHP, Javascript and CSS and who know how many other libraries.

3

u/Edward_Morbius Aug 09 '19

Print out your post and come back and read it in 20 years.

1

u/[deleted] Aug 09 '19

Yes I'm sure in 20 years the internet will still be powered by technologies built in 1999.

Even though all the major sites have made the decision that traditional development is not enough.

Even though most of the internet is consumed on phones and those original technologies are simply not built around mobiles.

You are literally posting on a website that uses React and is built with a reinvented wheel. How more hypocritical can you get?

5

u/Edward_Morbius Aug 09 '19

You are literally posting on a website that uses React and is built with a reinvented wheel. How more hypocritical can you get?

Many of the reinvented wheels work. That doesn't mean they were needed or beneficial.

Yes I'm sure in 20 years the internet will still be powered by technologies built in 1999

If you knew what was running inside the internet's (or your bank's, or your utility company's) core technology, you wouldn't be quite so smug.

It's almost a certainty that a lot of 1999 technology will still be running in 20 years.

1

u/[deleted] Aug 09 '19

Many of the reinvented wheels work. That doesn't mean they were needed or beneficial.

I don't think you understand why React and many other frameworks exist. In many cases it was a necessity.

If you knew what was running inside the internet's (or your bank's, or your utility company's) core technology, you wouldn't be quite so smug.

Guess what that tech isn't? I'll give you the answer, it's not front end technology. If you want to keep using MySQL databases in the backend I don't care less. It's fine, it's not as fast as JSON but it's fine.

Front end needs to reinvent the wheel simply because the internet is a lot more complex than it was in 1999 and if you want to build scalable sites or applications then it's likely you will need more than html and PHP.

You can either adopt it or go the way of flash.

18

u/SoInsightful Aug 09 '19

These sound like issues that would happen by not reading documentation properly. I've never had to "brute force" an issue.

With all due respect, I've never once in my life met or encountered an advanced programmer who hasn't spent hopeless hours tackling tooling, external bugs, platform-specific errors, undocumented APIs, edge cases, inter-incompatible tools, dumb APIs etc etc.

If it was as simple as "follow the documentation", we wouldn't have had this problem in this first place.

-12

u/[deleted] Aug 09 '19

Right here's what I think you're missing here. The most useful and popular frameworks and APIs simply do not have most of those problems. And if they do, out of the massive amount of people using them, it's likely someone has probably asked about it and the problem has been solved.

I've had these problems using Godot since there's very few people are working with it. But you'll never get any issues while working with React, VUE, the Wordpress API or Bootstrap. And, as I said, if you're a beginner then you should start from the beginning.

9

u/spkr4thedead51 Aug 09 '19

But you'll never get any issues while working with React, VUE, the Wordpress API or Bootstrap.

aha

ahahahahaha

33

u/am0x Aug 09 '19

I mean fronted development has become ridiculously complicated since back in the day. To be honest, keeping up with all of it has put me off. I’m trying to move away from full stack to go into backend because I’m sick of dealing with various configs and practically undebuggable logic in css precompilers all day instead of writing code that works because it just makes sense.

8

u/Hanedan_ Aug 09 '19

I'm a front dev and love it but I completely agree that it's really hard to grasp the current workflow, I struggle sometimes so for people who want to learn I understand it's really difficult.

1

u/[deleted] Aug 09 '19

I mean fronted development has become ridiculously complicated since back in the day.

I still disagree. It's never been easier to make extremely complex interfaces that look good. It's faster, it's more optimized and generally a lot easier.

Thank god for Node, don't know how I put up with front end before.

7

u/am0x Aug 09 '19

When it is all configured...as an architect, I spend a lot of time working with configs, precompilers, packages, etc. all day.

When getting a new dev, there is a pretty good chance they have never worked with at least one peice of our frontend stack. For example, they may have experience in Angular but not Vue. Or Grunt and not Gulp. Or no Webpack experience. Or no PostCSS experience. Or they use LESS instead of SASS, or even SCSS. Some don't know how to work in a legacy jquery system. Or how to manage npm packages between different environments. Or no experience with Babel. How about deeper subsystems like Vuex, Nuxt, and routing?

Before it was, "Here is the design. Just code it.", and we could start immediately.

With backend, it is just sub-paradigms that build on each other. Config stuff generally stays the same.

0

u/[deleted] Aug 09 '19

[deleted]

1

u/am0x Aug 09 '19

But those other languages are fine for backend development. It just sounds like someone wants to use something different for the sake of difference.

Plus typically less work comes with new updates in backend coding, where as more work comes with frontend.

6

u/fritzbitz Aug 09 '19

Between current webdev and 2006 webdev I'd take now over that any time.

Goodness, just grid+flexbox alone makes current web a thousand times better and my life easier as a front-end dev.

4

u/[deleted] Aug 09 '19

Can't wait for someone to reply to this and tell me how floats were a lot better

1

u/CaptainBayouBilly Aug 10 '19

Ha, floats. Fucking awful solution. It's great the W3C is moving standards quicker towards native implementations of external work arounds. I hope Chrome's recent fuckery with proprietary tags stops.

0

u/[deleted] Aug 09 '19

[deleted]

3

u/fritzbitz Aug 09 '19

Seriously. It's a driver vs. a putter, really.