News for hackers. Stuff that matters.
Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by taurath on Wednesday January 01, 2020 @07:56PM (#21932036)
Frameworks allow websites to be built faster, maintained with less expertise, and changed faster over time. That is the benefit to the user. That things are slower than they could be doesn't matter to most users. Most companies can't afford to pay people to maintain a "good + fast + quick to make changes" site.

There's an argument to be made that if business would just simplify their needs and desires to make sure everything is simple and fast, isn't that in and of itself putting devs before users? This works both ways.

Also, if you don't want to pare down your features to barebones, and you're not going to use a framework, someone's inventing one. If you have someone who's going to build you a superfast framework and be a cool hacker, then you probably can't afford them, or you can't afford to keep them. Then we get a post on HN about how bad this one coyboy coders's framework was and all the effort that was spent to modernize using %modern_framework%.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by jblow on Wednesday January 01, 2020 @08:00PM (#21932057)
If this is true, then why does it take so many engineers to make web sites today?

People keep claiming these things increase productivity, yet there seems to be very little evidence of productivity increase.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by tr1coder on Thursday January 02, 2020 @04:19AM (#21933959)
Jonathan Blow has a good presentation containing some interesting facts about the companies that employ thousands of engineers and can't get simple things to work. It's the first part of https://www.youtube.com/watch?v=k56wra39lwA

EDIT: OMG it is you! xD

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by taurath on Wednesday January 01, 2020 @08:14PM (#21932126)
The ones that have a lot of engineers have 50x more features today. Businesses and brands want a beautiful website with analytics and A/B testing out of the box, skinnable, changable via a CMS so that non technical designers can drag and drop in new components at will, and also get graphs of their efficacy. You have built in support chat systems to spend less on phone support. Your IT department to support, not develop, this site was 30+ with colo space in 2008 but now its like 3 dedicated ops people and the rest are devs.

OTOH, so many more business websites are built for a few hundred or thousand dollars by someone on upwork to host a bootstrap site with a shopify integration, and then you have an online store that would've been 10x the cost 5 years ago.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by topkai22 on Thursday January 02, 2020 @03:46AM (#21933855)
A couple reasons-

1) As the cost of feature creation goes down, the demand for features goes up- as others have mentioned, a lot of sites now have an enormous number of interactive features or cool rendering that just wasn't there in the good old days of nothing but text, images, and marquee tags.

2) Different frameworks solve different problems, not all of which are related to "productivity." JQuery solved a browser compatibility issues and made interactivity way more approachable, AngularJS did a great job dealing with input and output mechanics, and React is pretty awesome at managing compomentization for large projects. And a lot of frameworks give a "feel" users are looking for. Frameworks improve productivity, but the difference between frameworks is not that great.

3) one thing frameworks do well is allow team scaling, and scaling teams leads to a lowering of "individual" productivity. What works on a team of 1 doesn't on a team of 5. The larger team will need more "overhead." A team of 5 won't be able to do a task an individual could do 5x faster, it'll be more like 2.5x or something. That's not why you scale a team though- you scale a team to take on new problems that can't be solved (or solved fast enough) at the scale you are at currently.

I've run a decent size team using angular JS, I shudder to think of our ability to execute using JQuery, even though I successfully accomplished scaled down projects in those frameworks before.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by csande17 on Wednesday January 01, 2020 @08:39PM (#21932247)
+1. For example, according to one of their job listings[1], Twitter currently has 25 people working on the main twitter.com experience.

Twenty-five people! For a Twitter client! And they're still trying to hire more! (Important to keep in mind: this doesn't include any of the people working on the database, or the advertising algorithm, or the server architecture, or any of the other hard problems Twitter faces. This is just the team that writes the JavaScript code that takes the Tweets from the JSON API response and puts them onto the screen.)

[1] https://careers.twitter.com/en/work-for-twitter/201910/twitt...

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by jogjayr on Thursday January 02, 2020 @03:04AM (#21933701)
I'm shocked it's only 25. I would have expected an order of magnitude more given the number of features and sheer reach of Twitter. That can't possibly be right.

Not sarcasm btw. I think you're underestimating how much work there is.

First, there are a ton of features: lazy-loading tweets, retweet, favorite, lists, all the stuff related to analytics, settings. Simply maintaining that stuff with security updates and bugfixes is a significant commitment.

Then there's accessibility and localization to consider.

Next there's fix and feature experimentation. They probably don't release new features and fixes to everyone at once. Instead they roll them out slowly, or show different versions to different users, compare, analyze and iterate.

Browsers update approximately every 6 weeks, so that's something to keep abreast of. At Twitter's scale, a CSS rendering bug that affects 0.1% of sessions will be seen by hundreds of thousands of users.

And it's not just "a Twitter client". It's THE Twitter client - the canonical one. It has to have higher standards of performance, quality, and reliability than a random Twitter Android or iPhone app.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by Izkata on Thursday January 02, 2020 @06:07AM (#21934444)
> Then there's accessibility and localization to consider.

For anyone unaware, Twitter's whole UI changes to support right-to-left languages, not just the text.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by taurath on Wednesday January 01, 2020 @10:02PM (#21932661)
The amount of ignorance of the complexity required in a globally reachable frontend web app is astounding in this thread.
Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by csande17 on Wednesday January 01, 2020 @10:39PM (#21932835)
I understand why it's hard to make a popular, globally-reachable web service -- you have to run a bunch of servers in different locations, and distribute the database, and solve concurrency problems and stuff. So I get why Twitter might have large back-end and ops teams.

But client-side code doesn't have scaling issues like that. If I put some JavaScript code in a static file, it'll work exactly the same when 1 person runs it as when a million people run it. What "complexity" is Twitter's front-end team facing as a result of their global reach?

Like, I guess they have to localize their app, but the hard part there is getting the text translated; the technical implementation is usually as easy as putting all your UI strings in a dictionary that you swap out based on the user's language. (Maybe if they're extra fancy, they make a version of their stylesheet that flips the layout horizontally for Arabic users.)

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by as1mov on Thursday January 02, 2020 @04:07AM (#21933919)
I used to do fullstack development, but have recently moved to pretty much full time backend because the amount of headache present in the frontend dev.

> If I put some JavaScript code in a static file, it'll work exactly the same when 1 person runs it as when a million people run it.

No it wouldn't, because the million people have million different devices with different screen sizes, browser implementation and HTML/CSS/JS support for standards. The website should render properly on devices ranging from 5" mobile screens to 32" 4k monitors, while looking beautiful. This is in addition to proper support for multiple languages, accessibility features, and whatever new-fangled PWA bullshit that the business team wants.

Implying that frontend is `just` making API calls and putting JSON responses on the screen reeks of naivety. This could've been true in 2005, but in 2019 unfortunately websites have taken place of full blown desktop apps, and are required to behave as one. There's a reason why frontend dev is a specialist job position now and pays on par with backend dev.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by x0x0 on Wednesday January 01, 2020 @11:08PM (#21932957)
I doubt you've ever done a translation in a large webapp. Wait until German overflows your text boxes. Or you have to deal with date formats and number formats and ... And rtl languages are just a stylesheet away. Hah, but no.

And how many devices across how many OSes do you test on? Particularly all the devices that functionally no one in the global north purchases?

What is your accessibility test plan and how often do you run it?

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by TeMPOraL on Thursday January 02, 2020 @03:59AM (#21933901)
> Wait until German overflows your text boxes. Or you have to deal with date formats and number formats and ... And rtl languages are just a stylesheet away.

Web browsers handle all of that correctly by default.

A big part of web bloat is just developers including frameworks and libraries than break things by trying to reimplement them in a way more convenient for devs and designers - and then having to include more libraries and custom code to fix the breakage. All of that is self-inflicted.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by dx034 on Thursday January 02, 2020 @04:28AM (#21933997)
> Web browsers handle all of that correctly by default.

Unfortunately, they don't. Many websites don't look nice in languages that tend to have longer words (e.g. German). Yes, the browser will cut if off so that it doesn't destroy the design. But that makes it unreadable and not nice to use for speakers of that language. To have a beautiful design that works with many translations is an enormous task.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by ericb on Thursday January 02, 2020 @08:44AM (#21935256)
Often on Hacker News, and other places too, I see an argument where one person is hand-waving away a task and saying how easy and trivial it is.

The simple heuristic for deciding which person is correct is that the one saying it is simple and easy is always wrong.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by Izkata on Thursday January 02, 2020 @06:09AM (#21934460)
> (Maybe if they're extra fancy, they make a version of their stylesheet that flips the layout horizontally for Arabic users.)

Twitter does do that.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by threeseed on Thursday January 02, 2020 @12:23AM (#21933218)
So you think you know how to run Twitter Engineering better than Twitter ? That's a pretty confident claim.

Anyway Twitter.com could include writing all of the Javascript for advertising management e.g. creating new ads, content management e.g. deleting/reviewing Tweets as well as the various types of Tweet content e.g. videos, VR etc.

Typically what the public sees is a fraction of the total surface area.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by dx034 on Thursday January 02, 2020 @04:26AM (#21933988)
I don't think that was the claim. The question is rather, why do you need 25+ people for these tasks? They don't add new types of tweets every week/month and much of the interface (luckily) hasn't changed in a while. But I'd guess that these 25+ people spend only a fraction of their time programming and the rest with stakeholder management and corporate politics.
Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by 0xEFF on Thursday January 02, 2020 @01:29AM (#21933411)
Only 25? I’d expect more. No wonder they’re hiring.
Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by JimmyRuska on Wednesday January 01, 2020 @08:12PM (#21932119)
There's a lot of shops that are pure django, drupal, laravel, wordpress experts, who would never be able to put something together from scratch, but can probably glue you a customized website in not a lot of time from relatively well tested components. I remember going to a meetup for level 10 in Dallas, TX. Huge beautiful building they had, all from django and wordpress revenue.

I guess it's like anything else, what are you trying to optimize for. There's still a lot of charm in PHP being a very simple wrapper to a lot of very efficient C functions.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by ScottFree on Wednesday January 01, 2020 @08:44PM (#21932276)
> There's a lot of shops that are pure django, drupal, laravel, wordpress experts, who would never be able to put something together from scratch, but can probably glue you a customized website in not a lot of time from relatively well tested components.

Nobody denies that these frameworks allow people who would never be able to program in C/C++ to create websites. Nobody denies that it takes more of these quasi-programmers to create and maintain websites than it would take more knowledgeable programmers writing in more efficient languages. So, here's the killer question: At which point do these frameworks and the large number of quasi-programmers required to maintain them cost more than just hiring somebody who can create a native app in C/C++?

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by jpmoral on Thursday January 02, 2020 @02:47AM (#21933656)
'Quasi-programmer'? I don't think elitism helps your point.
Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by taurath on Thursday January 02, 2020 @12:23AM (#21933217)
Hire a C/C++ programmer and see how that goes for you. If what you’re saying is true they can revolutionize the industry and make a billion dollars with their superior code.
Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by 0xEFF on Thursday January 02, 2020 @01:16AM (#21933368)
I’ve seen it happen. The code is faster, but it doesn’t matter because users don’t care. It also took two years to rewrite, doesn’t have the features of the original, and all of the operational experience had to be relearned by the engineering and ops teams.

So, millions of dollars, years of time for no actual benefit, and now the business is left with an app they can’t hire talent to maintain because it’s so custom.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by Daishiman on Thursday January 02, 2020 @11:01AM (#21936453)
The C/C++ engineers are going to spend their time dealing with memory management issues that have no relevance to the final delivery of product features.

And if industry experience says somethings, those engineers who spent that time honing their skills at wrangling the C++ stdlib will have _appalingly_ bad design and UI skills, which are very relevant for today's web and are a much more important driver of revenue.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by rkangel on Thursday January 02, 2020 @08:02AM (#21935002)
My intuition (that I have no data to support) is because the average level of skill of software engineers is dropping.

As writing software has gained a reputation for being a lucrative and desirable profession, it has attracted more and more people. If you were someone who took up programming in the 80s it was probably because you had a good aptitude for it and found it interesting. Now, there are more people joining the profession who don't have the same level of aptitude.

So now instead of a small team of highly skilled people, you often end up with large teams of less skilled people. Interestingly there doesn't seem to be much of a halfway house - your project is either staffed by 6 people or 30+.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by collyw on Thursday January 02, 2020 @10:55AM (#21936385)
> My intuition (that I have no data to support) is because the average level of skill of software engineers is dropping.

As someone that has been in the industry close to 20 years, my guess is that the constant churn is getting in the way. Around 2000 when I started, we had 3 tier apps, people knew how to optimise relational databases to get their application to perform.

These days we need to add Kubernetes, Docker, Nosql to cloud platforms in order for it to scale - despite never needing this stuff 15 years ago. Instead of mastering our craft we are encouraged to forget everything and use this new technology instead, as it will be the silver bullet to all our problems.

It's closer to a fashion show than engineering.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by wruza on Thursday January 02, 2020 @08:24AM (#21935122)
Frameworks also effectively hide “bare metal” from developer, so they develop magical thinking. I’m really tired at my job of debunking magical and simply wrong assumptions and claims about how something works. Being unable to understand and implement something yourself, shadowed by Framework Authority, dooms one to remain in a pit of false incompetence.
Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by thfuran on Thursday January 02, 2020 @10:00AM (#21935838)
Is false incompetence where true genius lies?
Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by nprateem on Thursday January 02, 2020 @07:14AM (#21934761)
Part of the productivity "gain" is increasing agility, making it easier/faster to scale/pivot if you need to. Whether you actually do or not is up to you, and you pay a time penalty as an overhead for those abilities when using a framework.

It's similar with choosing e.g. Hadoop instead of running entirely locally. You're mitigating the risk that in future your workload might exponentially increase. Yeah, it probably won't but if it does, whoever decided to on that architecture will look like a forward-planning genius. But nothing comes free.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by mindfulplay on Wednesday January 08, 2020 @05:05AM (#21990022)
Why would it take a single engineer 3+ years to build a Mario-like game with a tweak around time-mechanics?

I am discounting the artwork and asking primarily around the efficiency of the coding and development.

Each developer has a focus area. You might focus on millisecond level optimization; a web-developer might focus on content provisioning and rapid development; a data engineer might care more about sanity and robustness of data.

It's not clear how anyone can judge other engineers' ability based on arbitrary metrics without considering their engineering system's goals and requirements.

As an example, both Braid and The Witness have very limited accessibility; perhaps that wasn't a focus area of yours and again each developer to his/her own.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by collyw on Thursday January 02, 2020 @10:49AM (#21936330)
>Frameworks allow websites to be built faster, maintained with less expertise, and changed faster over time.

As someone that has done maintenance programming on an AngularJS application and a React application in the last couple of years I would say that is not true. Getting some simple changes made is a complete nightmare, there are loads of third party libraries that seem to be inconsistent in the way that they render and are next to useless if you don't use them in a particular way.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by loco5niner on Friday January 03, 2020 @05:40PM (#21951095)
> That things are slower than they could be doesn't matter to most users.

I'm sure everyone wishes these things were faster.

Re:Putting Devs Before Users: How Frameworks Destroyed Web P... by goatinaboat on Thursday January 02, 2020 @06:30AM (#21934533)
Frameworks allow websites to be built faster, maintained with less expertise, and changed faster over time. That is the benefit to the user.

How did the user benefit from breaking changes between framework versions requiring no new features to be delivered while everything is rewritten for no particular reason?

In the Python community 2 to 3 freaked everyone out but webdevs do it every 6 months!