22 ms·

I can only think that modern front end development has failed

• cryptica 6y ago
  All software development has failed. Everyone is mindlessly copying megacorps with terrible development practices. Then when their crappy systems fail constantly, they blame the tools and demand even more complicated tools from their corporate masters... Which make their code even less reliable. Tooling is not the problem, the problem is you and your selfish subconscious urge to create more complexity to create more work and more income for yourself.
  • swader999 6y ago
    I don't think greed has much to do with the complexity. Insecurity seems to cause a lot. Devs feel if they don't go with all the latest stuff to all the nines they aren't worthy.
    • futureproofd 6y ago
      I have to agree with this, but I think insecurity may affect junior developers more so than their seniors. Most of the new, in-demand tech that companies require of their applicants can be learned within a week or two, to be able to successfully contribute. That is, if you're already experienced with a number of complex frameworks or libraries. Then, It's simply a matter of reading the manual to figure out how to move the data from one place to another. On the other hand, for a junior dev trying to break into the workplace, selecting the correct technology could be considered an important investment of their time, and ultimately their livelihood.
  • rantwasp 6y ago
    you are probably right that there is a lot of complexity for complexity sake. it’s sad actually. also solving problems that you don’t have and you’ll never going to have (k8s I’m looking at you)
  • deleted 6y ago
    [deleted]
• runawaybottle 6y ago
  Media websites are a bad way to judge the state of web app development (which sucks for its own reasons). If you manage to hire good developers on a media site, they will try to optimize how ads and the endless list of third party libraries are pulled in. If you didn’t get some dope developers then they will just half ass dump all of the stuff needed onto the page (which is why most of the the web sucks). What’s worse is that these sites sit under a publishing/media business, so they aren’t tech companies (the devs are second class citizens). Everyday I run into at least one site where they couldn’t figure out a sticky header, or a decent ‘accept-cookies’ box (where it takes up half the screen, and when you hit X (if you find it), it stutters away, as if css transitions is a mind blowing concept). Then after that, the page janks down as a whole ad gets rendered. Zero effort is being put in at some of these places. I would consider lazy loading content in the visible viewport the moon for these sites. This is a necessary discussion because the web is becoming a tech slum with these poorly designed websites. To bring it back to the larger web development (both app and website), it can be difficult to suggest to a team a very simple question - ‘Do you not see that the end result looks and feels like shit?’. It’s too abrasive, but all of us need to start asking these basic question for quality’s sake.
  • rini17 6y ago
    Media are on shoestring budgets, unlikely to sustain good developers. But it's not only media, many other services neglect the user-centric optimization. That case is probably due to proliferation of various kinds of outsourcing/seo consultants whose interests don't overlap much with users'.
• antirez 6y ago
  Regardless of my tweet, that is a personal opinion based on my feelings, background and experiences, the discussions in the replies are interesting from the POV of understanding what different people think in the programming community. Some will say that critiques are only from old people, in the style "when I was young we had only zeroes! You now have ones and zeroes". Others say that the web is slow because of ADs and trackers and modern frameworks would otherwise be fast. There is who believes that the problem comes from big companies imposing new standards in order to turn the web into the new Java applets (a full fledged application platform), and so forth.
  • notjustanymike 6y ago
    I read it and feel it's the same as how we perceive modern music. Everyone says music "used to be better" but that's just survival bias. Just like music, there was a LOT of trash web development back in the day as well. Sites built with tables in dreamweaver best viewed on netscape navigator at 800x600 with animated gifs bogging the download speed existed long ago. What we have today are the same problems with a new wrapper, created by a not dissimilar group of people from the past.
    • barrkel 6y ago
      We had functional applications for forms and the like, in the 90s, running on machines with 8MB or 16MB of memory. They weren't as pretty, but they had simple development paradigms, VB and Delphi, easy to get started. HTML has been the wrong place to make creating UIs (as opposed to marked up text) for such a long time. Things are getting better from multiple angles, but it's still very uneven.
      • notjustanymike 6y ago
        It's always easy to solve a problem by taking away a number of it's requirements. VB was good at forms but visually unacceptable for branding. It was difficult and unsafe to deliver over the internet. And again, there were a LOT of really bad VB applications that hurt usability and performance. If all you're doing is building forms for an application then it's acceptable, but that's an easy problem solved with elegant solutions today as well. HTML can immediately deliver the styled application without installation to every device regardless of OS. It can propagate changes without reinstallation. It is accessible for every kind of user. And it does this while looking miles better than any VB application.
• noxer 6y ago
  You cant even find a website that passes html validation these days.
  • 542458 6y ago
    I like valid HTML as much as the next guy and try to always write valid HTML myself, but it’s not the be-all-end-all: if Safari, Chrome and Firefox can parse your site 99% of users are happy. No end-user cares if you have charset set on a script that doesn’t have a src attribute, or that you’re technically not supposed to put style tags inside noscript tags.
    • simion314 6y ago
      The problem is that nobody can create anew browser engine because you not only need to implement all the standards you also need to make your browser work with broken html and work in the same way Chrome and Firefox work. IMO we would need 2 split the document part from the application part. Have a set of elements and a document format just for blogs and news websites , and more complex components and APIs for application websites. Then you could have a browser that would be more simple that will be enough to browse blogs,forums and news sites and a more complex browser for SPA applications.
      • BlueTemplar 6y ago
        That first part is the Web, while the second part are native programs with Internet connection.
        • simion314 6y ago
          I think you could have web rich documents with basic interactivity and as an option web application that are "native app like" , with tons of APIs for camera/microphone , bluetooth, canvas, 3d , complex sound APIs. We have to admit that rich web application can be very usefull, even during Java or Flash days we known that sometimes you need an animation or a simulation on a page to better present some content. Though it makes you think if we had an 100% open source Flash, then you could have used it for complex SPA like Figma while keeping all the bloat into an optional plugin , if the plugin was optional developers would not be tempted to use it unless is needed and it it was needed they would have use something like Flex (a Flash GUI tookit) and not reinvent the wheel constantly.
• guscost 6y ago
  Counterexample: Figma.
  • dxdm 6y ago
    Could you elaborate? I don't like Figma very much, but I think that's because I prefer typing code into text files. So, probably not for reasons pertinent to this discussions. Anyway, I'm interested in why you would consider it good.
    • guscost 6y ago
      It is efficient enough to make you rethink the limitations of JS apps, it is basically glitch-free, and it works remarkably well as a full-featured tool for designing screens collaboratively and/or working with SVG. That said, Figma sort of exists in an “app-like” vertical when it comes to web frontends. The other big vertical, and the one probably being alluded to in this tweet, is “magazine-like”. Those frontends have a much different goal, one that prioritizes responsive design, accessibility, progressive enhancement, and so forth. NY Times has been among the best in that vertical for a long time.
  • meritt 6y ago
    Figma is written in C++ and compiled to wasm, and it's amazing, you're right. But that approach represents maybe 0.001% of modern front end development. The curent popular path is React/Vue and the endless JS toolchains to compile these horrible bloated broken apps.
• inamiyar 6y ago
  This sentiment of "modern web has failed" is echoed often but it is always a generalization. Do I want to stab my eyes out every time I go to a news site? Probably. But there are good websites out there, many of which are "modern." It's not about web as a technology or frameworks or even "webdev culture." Some companies just decide having a good website isnt worth it. Sidenote: I also think there might be too many websites in general. I always kind of think between Wikipedia and archive.org and other information Freedom projects that's all we need. Maybe a little IRC as a treat :)
• vbezhenar 6y ago
  I don't think that web is slow, unless you're running seriously underpowered computer. That's not the case for me. Web is not as fast as it could be. And that's because customer does not want to pay for fastest website in the world. It should be fast enough and then features matter. You can spend year making your website load in 0.1 second while your competitor will implement important features and his 2-second loading website will win. And that's not really about web. It's about software in general. Discord launches in 8 seconds. Ventrillo launches in 1 second. But people will use Discord, because 8 seconds is not that bad and then features matter. And that's not really about modern software, as old software was slow as well. Also it was very buggy. Windows 98 used to BSOD here and there, so you had a routine to press "Save" button every few minutes and keep few copies just in case. Emacs was expanded to "Eight Megabytes And Constantly Swapping". There's some old software which survived till today and it's now wicked fast, because it was made for old hardware. But people still prefer to move on to new software, because of features or just shiny new design.
  • runawaybottle 6y ago
    All of that is true until it isn’t. Ask all the stock trading apps how Robinhood out-UXed them. When the out-user-experienceing happens, you pretty much will lose your entire business if you don’t undertake a paradigm shift. Stay ahead of the curve a bit.
    • jackson1442 6y ago
      I think it could be argued that Robinhood’s UX is a sort of feature on its own. Stock trading isn’t simple by any means, and Robinhood found a way to make it really approachable for everyone and that’s almost admirable. Everything else about their business sucks, but that one piece was truly impressive.
      • runawaybottle 6y ago
        I’ve echoed this point a few times too. There’s a lot of apps that can barely figure out a todo-list (every glorified note take app/PM software), and here’s a company that boiled down Derivatives (with a capital D) trading in about two or three screens. It’s an absolute masterclass.
• peanut_worm 6y ago
  It makes me really angry when a simple informative site is a bloated SPA app for no good reason.
  • softwarebouwer 6y ago
    Me too. Recently I was visiting what should have been a "simple" site, but for some reason maxing out my cpu because of some refresh loop. Maybe a bug, but the whole site could have been static html.
  • tjpnz 6y ago
    In many of the cases I've seen the company would've been better off with server rendered markup and perhaps some light client side validation (vanilla JS or jQuery). I'm at a loss as to how they ended up with this instead.
    • scruple 6y ago
      Where I work it's because we have all of these frontend developers and they need work to do. We keep sticking with ReactJS as the default because we have these folks and theres a snowballs chance in hell that they'd go, from their perspective, backwards in terms of the technology they use to do their jobs.
  • verisimilidude 6y ago
    It's not just simple content sites. The other day, I placed an online order for curbside pickup (with a national brick-and-mortar chain). When the time came, I drove up to their curb. But I couldn't access their "I'm at the curb, bring out my stuff" page. It just kept loading and loading. I had to go into the store to get my order. When I got back to my PC, I discovered a massive webpack bundle on that page, along with an absurd level of tracking software. The page had transferred 50MB before I could even use it. They knew their curbside page would be used exclusively by people on their phones, in their cars. They knew some of those people would pull up to stores with poor cell reception. That page should've been as light as possible. The page was ultimately just a simple form, so it should've been possible.
• xwdv 6y ago
  Modern front end development cannot fail, it can only be failed.
• okareaman 6y ago
  I recently lost my internet provider, so while I wait for a new one I'm tethering from my phone. The Verizon unlimited data plan actually throttles me to modem speed, about 56k, so it's actually not unlimited. Anyway, it's been interesting to judge various websites by how fast they load at that speed. Hacker News comes right up. Twitter is acceptable. Facebook is terrible and often does not even load at all. The same for any site that uses React. I'm not sure why Facebook uses such a bloated system when they are trying to expand their user base into much of the world that does not have high speed internet.
  • jasonpeacock 6y ago
    Search for "Facebook Lite", it's their lightweight frontend for lower-bandwidth connections.
    • okareaman 6y ago
      It appears to be an app for a phone? I have no throttling problem on the phone in case that wasn't clear, but I don't care to look at the small screen and want to use my desktop.
      • michaelt 6y ago
        I think they mean https://m.facebook.com https://m.facebook.com - a lightweight web version.
        • okareaman 6y ago
          I tried it. It's very ugly and featureless on desktop but it does load fast.
          • lostcolony 6y ago
            It actually used to have -more- features. I use it on my phone exclusively; once upon a time I could use messenger from within it. They removed that feature and now try to foist the Messenger app on me. So I don't use FB Messenger from my phone.
• yummypaint 6y ago
  Obligatory: https://www.youtube.com/watch?app=desktop&v=Yx6k6WR8GRs https://www.youtube.com/watch?app=desktop&v=Yx6k6WR8GRs
• watwut 6y ago
  In what way are current websites not usable?
  • minitech 6y ago
    A lot of websites: - reimplement browser features and do a bad job of it - are unnecessarily slow - try to stop being slow by breaking even more stuff Some examples I’ve come across within the last week: - Twitter pages randomly failing to load until the next hard refresh, probably because of service workers somehow (which are unnecessary for user experience improvement since HTTP cache exists and I don’t have notifications enabled) - Twitter’s offscreen tweets not being searchable with browser find because they were optimized out of existence – and I want to do this in the first place because it decided to refresh itself while I was in the middle of reading - YouTube application state getting out of sync with browser history that it overrides when I navigate Back too fast for it – the URL stops matching what’s playing and the navigation doesn’t take place - GitHub’s reimplementation of browser navigation reimplementing a loading indicator but not the stop button (I think I’ve also gotten it out of sync before) - Form state not being restorable across history navigation because the fields didn’t exist when the page loaded - Reddit’s redesign is so unusably sluggish that I don’t stay on it long enough to run into any other problems
    • napsterbr 6y ago
      > Reddit’s redesign is so unusably sluggish that I don’t stay on it long enough to run into any other problems I agree with everything you said, but allow me to reiterate this point. Reddit's redesign is the most hostile thing I've ever seen. It explicitly blocks me from reading the discussion. What's the point, then? It's absolutely unusable. If they ever remove old.reddit.com, I'm not following a Reddit link ever again.
    • sdfhbdf 6y ago
      I started reading your list looking for something to argue with but I'm sadly agreeing with all your points which I encountered myself. I didn't even realize they're reimplementing browser features and that's a really cool observation. I think it's paramount to understand that this is not a list of bugs to fix, it's a list to convince us that we should consider Server Side Rendering more often and avoid client side navigation, history API with all its possible race conditions...
• m_j_g 6y ago
  I think that this branch of engineering is still in its infancy (like electrical engineering int the times of edison). I am courius how front end development will look when dust will settle, maybe in 50 years? Maybe todays, heated disucions will be setted for good? Or something new, better will be invented?
• CM30 6y ago
  This topic seems to come up on Hacker News every few months or so. Not saying the post is necessarily wrong there, but it's certainly something people here love discussing nonetheless. As for why front end development may be a bit of a mess here? Well, it's really a problem that doesn't have just one cause. On the one hand, business pressures likely have a huge impact here. Companies love analytics, tracking, ads, etc, all of which contribute greatly to the issue of slow loading, broken sites. If you include everything and the kitchen sink, then things will clash or time out or break. There's also an issue with businesses focusing on speed and working getting done quickly rather than well. If you're given unrealistic deadlines, and the feature set is changed midway through development because some manager/sales team thought of a shiny new idea that needs implementing... well it seems like optimisation, usability, etc often end up on the cutting room floor. And yes there's a bit of envy from developers towards Facebook/Google/Apple/whatever there too, and a need to 'test out the shiny new toys' so they can potentially get hired there in future. I suspect CV padding is definitely why SPAs are way more common than they used to be, and why simple static or server rendered sites seem nearly nonexistent now.
  • deleted 6y ago
    [deleted]
  • deleted 6y ago
    [deleted]
• caseymarquis 6y ago
  I'd like to add a bit more nuance. Modern frontend development provides many opportunities for failure. These failures often make their way into production. I, personally, get great results with modern FE development. My users are happy. I am happy. It's all very successful. All the defenders of modern FE development will likely chime in with the same sentiment. I also get great results with C, which arguably provides even more catastrophic opportunities for failure. I wouldn't say "C is a failure", but I absolutely hate working in C, and I'm glad we've made improvements to systems programming. I think the point I'm moving toward is that we absolutely should strive to make better tools for delivering web content, but the reasons for failure are far more complex than the tooling itself. So, let's not frame things in black and white and call something that's been used with large amounts of success a failure. That's not very productive and is just flame bait. The real question is, "What's next?", how are we going to improve the current situation?
  • bjornjajeja 6y ago
    I think a lot of it had to do more with business requirements than art or science. The business folks stroll in and make these generic one-click deploy type things to get sites up and running quickly, at the expense of being vetted by good artists and scientists. A good analogy I think is any person using MS publisher to create a book layout. Sure it can be done quickly because the software does the thinking; but should it? Good books have skilled typographers designing the proportions of the pages relative to text block, the fonts, et cetera. The end result is a book that one scarcely notices but feels very pleasant to hold and experience. We need websites that are subservient to their content; sites we scarcely notice but thoroughly enjoy. EDIT: one last point: I think part of the problem is also that browsers have an identity issue. E.G. they started as a static publishing platform, but now they are a full blown operating system with web assembly etc. As we know, anything that does too many things is inherently complex, and hence “bloated.”
  • darkhorse13 6y ago
    >Modern frontend development provides many opportunities for failure I think this is the important thing here. Everything feels less stable, and more prone to breaking, on the modern web. You write some simple HTML, style it with CSS, and write vanilla JS for the parts that need it, and everything feels solid. You start a new project with a framework, and it seems like there is this whole area of your project that is essentially a black box, ready to break (or misbehave) any time.
• bob1029 6y ago
  It's never too late to consider server-side web technologies (new or old). We would have closed up shop a long time ago if we hadn't discovered Blazor and all of the productivity gains that go along with it.
• BrandoElFollito 6y ago
  I think that front dev is fantastic today, especially for amateur devs such as myself. I used to do some HTML and CSS 25 years ago and it was a nightmare to make it look like I wanted. Today I use Vue+Quasar and everything just works.
  • CRConrad 6y ago
    > I used to do some HTML and CSS 25 years ago and it was a nightmare to make it look like I wanted. Did you ever stop to think if the point perhaps wasn't to make it look like you wanted, but like the user wanted? I think that's a major part of the problem with the Web in general: A severe case of designitis. The web was never supposed to be a glossy magazine. The server was supposed to serve up content, (mainly text), and then the browser was supposed to render that content according to the user's settings — by all means, let the artsy-fartsy types use some fancy designer font; but above all, let those of us who are getting on in age use a slightly bigger one, so we can frigging see what it says in the first place. Compared to that, I don't give a shit if it messes up the precious "flow" or layout. Designitis -- it's the curse of our times. (Well, that, and advertising.)
• LandR 6y ago
  I run no script, if i cant get it working allowing no or very minimal js, i close the tab. Life is too short for shitty slow, bloated websites and buggy apps. Just dont use this trash, if the devs aren't going to up their game and prioritize user experience over profits then fuck them. The only way web developers are going to improve is if they start losing users and money. Until then they'll keep crapping out garbage.
  • futureproofd 6y ago
    I'd argue that life is too short to use no-script. And why point the finger directly at web developers. Product managers throw a requirement over the fence and web developers figure out how to satisfy their wants, while squeezed into sometimes unrealistic time constraints.
• scrose 6y ago
  I started out working primarily on the front end when React was still in its v0 days, and it still amazes me how many options there are to build a simple form, how often it’s done wrong, and how often what could be a 2 hour MVP turns into sprints worth of bike-shedding on the tools to use. I now work pretty much exclusively on backend systems and I’ve never felt better.
  • pjmlp 6y ago
    That is why I am so happy to have mostly focused on Java and .NET and their SSR stacks.
• leephillips 6y ago
  I am not an expert chef. I can cook pretty well, and my guests enjoy my food. But it doesn’t compare to what a professional chef can do. I am not an expert abdominal surgeon. If we are in Antarctica and your appendix becomes inflamed, I will try to save you by cutting it out. But you will probably die. I am not an expert front-end developer. I make sites for myself, for others, and have even been paid for it a few times. But I know I am basically an amateur. However, my sites are far, far better than almost all sites in the wild, created by teams of full-time, professional front-end developers. They work identically in all browsers, are fast, easy to navigate, and people say they look good. They validate, too, except for a few nonstandard htmx attributes. There is something very strange in the WWW, when a self-taught amateur like me can make a site that is better than the New York Times’.
  • rantwasp 6y ago
    not saying that you’re wrong, but do you have the same constraints as the “crappy” websites? there is definitely an explosion of tooling, frameworks, etc, but past some obvious things, IMHO most websites are crippled by business people (that will likely not be using the website) make all sorts of technical decisions what must go in and how it’s supposed to work (ads and tracking crap is one of the things that jumps up).
    • leephillips 6y ago
      No, I don’t have all the same constraints. For example, I would walk away if any of the organizations that I work with insisted on tracking visitors. I stopped taking paying customers years ago for this and similar reasons. But if a site is bad for the reader, it’s bad. The developer has failed, even if the customer got what it wanted.
      • rantwasp 6y ago
        i get it and i am in the same boat as you (ie make it awesome for the reader), but unfortunately this is not what happens in the real world :(
  • 6y ago
• softwaredoug 6y ago
  Has it failed? Or is the current state that people prefer “native” apps to this kind of rich interactivity with long lived state? And instead the browser is a place that feels like it’s going to load a somewhat interactive document. The front end work here is often seen as grunt work on top of backend services and not a discipline in its own right. So instead the awesome front end dev has switched from making something like Slack or VS Code work great in Chrome to building it in something like Electron for native experiences.
• tazjin 6y ago
  HN seems to be pretty split on this issue. I concur with the linked tweet. Using the web beyond very simple pages like HN feels like wading through garbage. Everything is slow, laggy, loads ridiculous amounts of stuff (I live in a country where traffic is very expensive at the moment, so this becomes more noticeable). Things are also flaky and need reloading whenever they get into broken states. The only way I use the web now is with uMatrix blocking everything, and then whitelisting stuff that pages want to run piecemeal. It's still terrible. The larger a company is, the less usable its web stuff is also. Google Chat for example is unusable in very active rooms. I hope that frameworks like Hotwire make server-side rendering "cool" again and that we can get out of this tar pit.
  • tffgg 6y ago
    Why would you want server side rendering? As a user it's painful if you have to wait after each click
    • slt2021 6y ago
      is it painful for you to click on HN? I find this website rapid fast. Also because you dont have long running JS processes the RAM consumption is low and everything feels very quick, unlike most SPA garbage
      • tffgg 6y ago
        Yeah, I kinda wish clicks would respond instantly
    • goostavos 6y ago
      Your comment made me legit chuckle. Rather than "waiting" after each click, we get an instant 'page load', half of which can't be interacted with (looking at you, Amazon.com), and then a sea of loading spinners -- all under the guise of 'not waiting'. I'm not sure which of those I prefer, tbh. I'm partial to good ol' fashion SSR sites these days, as I do most of my casual couch browsing on an old chromebook running Ubuntu. The number of heavy-weight SPAs that I just can't run on the hardware anymore seemingly climbs by the day. :(
• ergot_vacation 6y ago
  Nothing has "failed" on a technical level. I'm sure if a company hired a bunch of highly experienced devs and said "build us the fastest, most user-friendly site ever, everything else is secondary!" you'd get an amazing site. You get what you optimize for. User experience is not being optimized for. The ability to prey on users via ads, dark patterns, info harvesting, tracking and even malware is. This in turn happened because people discovered that, mostly, there are only two ways to make significant money online: 1. Be the first to deliver a revolutionary service everyone loves in just the right form for it to catch on. 2. Gather a bunch of users via some shiny object and then exploit the hell out of them. For obvious reasons, #2 caught on, dominated the web, and will continue to do so until various regulations slow it down.
• coldtea 6y ago
  >I can only think that modern front end development has failed Well, one can just as well say "in-memory stores have failed" based on some impossible to meet criteria of their own device...
• tootie 6y ago
  This isn't a development failure. Content businesses have been struggling to turn a profit online for years and we're at an inflection point now. Some sites are opting for squeezing revenue from every spare pixel and bombarding social media with clickbait. The rest are going to start pushing subscriptions really hard. And there's going to be a widening gulf between the two.
• glued 6y ago
  Modern frontend development hasn’t failed, the industry has. Frontend development is looked down on as “not real programming” or “simplistic” but it takes years to master and requires skills of both an engineer and designer. Leetcode and bootcamps will not prepare you for architecting a high performance, scalable, accessible, SEO optimized, visually appealing, usable experience.
• dranka 6y ago
  I miss the passive nature of the web. A page got loaded and then it was idle. Now I can stare at a page of text with my cpu spinning at 100% in the background, it adds nothing extra to my experience except for a quiet hum from the CPU fans
  • mro_name 6y ago
    Not to mention animations. Adding a second's hand to https://mro.name/o/testbild.svg https://mro.name/o/testbild.svg makes 25% CPU load on modern hardware. Ridiculous. But even more so, that it's often enough done anyway.
• AltruisticGapHN 6y ago
  What about advertising on websites has failed us all? Anyways, ViteJs and Tailwind jit recently are making development fun again. Too bad TypeScript still ruins the party.
• beidve 6y ago
  The tweet is too vague so I don’t really know what they are referring to. Reddit is slow now because they made what should just be static HTML that is updated occasionally into a web app for whatever reason. React is much better than any alternative. I tried using native js but you really need all of the things react brings. Now you could go back to server-side, but it isn’t suitable for web applications. There are just too many interactive elements that don’t work with a HTML push to client and reload on every change approach. Server side plus client side is a lot more work and hard to maintain. Still, I really hate front end development.
• defanor 6y ago
  It's hard to argue with that short textual message after it took me 3 attempts to finally load it. The quote for those who still struggle to access it: > I look at the web today. Not as a programmer, but as a user of broken sites that are unable to obey the most basic rules of navigation and usability, terribly slow despite the hardware progresses. And I can only think that modern frontend development has failed. Though it's probably not exactly a failure if usability, accessibility, and/or speed are not primary objectives for most, and discussing just that once again probably won't be very useful for fixing it.
• abetusk 6y ago
  In my opinion, it's a question of what you want to optimize for, speed of execution/accessibility/responsiveness or speed of software development. The modern web is a stack of abstractions that separates the code in what the site is written in from the underlying machine that renders it. This stack of abstractions makes it many orders of magnitude slower than it theoretically could be to render, but makes it many orders of magnitude easier to program. In other words, this seems like the age old debate of "interpreted vs. compiled" [0]. While the front end ecosystem is sprawling and modern web pages are slow and clunky, the barrier to entry, for most people, is at an all time low. It's easier now to create a web page that works consistently for the vast majority web browsers with minimum effort. The render speed and accessibility might suffer, but this is always the price of abstraction. Jonathan Blow has a talk specifically lamenting this point [0]. [0] http://blog.gmarceau.qc.ca/2009/05/speed-size-and-dependability-of.html http://blog.gmarceau.qc.ca/2009/05/speed-size-and-dependabil... [1] https://www.youtube.com/watch?v=oJ4GcZs7y6g https://www.youtube.com/watch?v=oJ4GcZs7y6g https://www.youtube.com/watch?v=FvBySbGueww https://www.youtube.com/watch?v=FvBySbGueww https://www.youtube.com/watch?v=URSOH4F3vbU https://www.youtube.com/watch?v=URSOH4F3vbU https://www.youtube.com/watch?v=MlIZ2Q3Rvc8 https://www.youtube.com/watch?v=MlIZ2Q3Rvc8 https://www.youtube.com/watch?v=jpk9Q5gCyIY https://www.youtube.com/watch?v=jpk9Q5gCyIY https://www.youtube.com/watch?v=xK6YZ3NFjuE https://www.youtube.com/watch?v=xK6YZ3NFjuE
• throwaway4233 6y ago
  The advancement of what is possible on the FE has not given ample time for FE developers to scale accordingly. That I believe is because of lack of standardization across the WWW and the reliance on existing libraries like Babel to accommodate this gap. The variation of how code behaves underneath now changes depending on what library you use and that tends to libraries or developers overcompensating for their code to run anywhere. IMO, we need to stop inventing the new, ensure browsers behave the same across 90% of users and then start innovating again. Sure, we might have to do this every few years or so, but the gap would keep increasing and thus have longer periods of stability.
• avl999 6y ago
  Hacker News and the old reddit is the pinnacle of user experience for a site of its "genre". The new reddit perfectly exemplifies what @antirez is saying. It's amazing to me that hundreds (thousands?) of people who work at Reddit thought that that user experience was an "improvement" over the old reddit.
  • danjac 6y ago
    If it forces us to download a native app because the website is unusable, that's a "win" in their eyes.
  • deleted 6y ago
    [deleted]
  • thekyle 6y ago
    It really amazes me how bad new Reddit is. I have a Windows computer from about 5 years ago that I sometimes use. It takes about 10 seconds after clicking on a story for the first comments to load, and there is about a 5-second delay between pressing a key and the character showing up in any of the text input forms. Even on my new M1 MacBook Air it takes 2/3 seconds for every page to load.
• root_axis 6y ago
  I don't find the argument convincing. I've used the web all day for decades, it's fine. Some sites are slow, some sites are buggy, some sites don't meet contemporary design standards... this is nothing new, it's the same as it ever was. The one quality that truly differentiates the new web from the old web is the Cambrian explosion of ad tech, but this isn't a "front-end" problem, it's a cultural problem rooted in the shifting expectation that everything on the web should be monetized. There isn't really a solution to this, ads are the opposite side of the coin for people producing goods and services that are ostensibly providing value to the economy in the abstract sense... this is the web we all wanted.
  • runawaybottle 6y ago
    There are good examples of ad integration and bad examples. People spend a whole lot more time talking about app architecture versus how to elegantly load, render/position and refresh ads.
    • root_axis 6y ago
      Agreed, but the people complaining don't really register the "good" examples, understandably.
• mrkramer 6y ago
  "I can only think that modern front end development has failed" I think web devs have no real incentive to improve their front end since search engines don't stimulate and reward them to do so. Ranking algorithms are blackbox but you can notice that popularity is more important than quality of content so eventually web gets bloated and you end up in information overload.
• marvel_boy 6y ago
  So true.
• TruthWillHurt 6y ago
  For me it failed mostly because the complexity involved. Even a rather simple interactive website requires weeks/months of coding & testing. WYSIWYG editors don't cut it, and we need to implement same things over and over again (i.e login).
• BlueTemplar 6y ago
  As a recent example : Substack is worse than Wordpress. And it's probably related that you can read Wordpress comments with JavaScript disabled, while not Substack comments.
• pictur 6y ago
  modern front end development is very prone to producing shit. and it can happen in a very short time, not in years. If user experience and performance are still important to you, you can do good things. But if your only concern is to try new things and mess with your application, the end will be producing shit.
• iambateman 6y ago
  Not so fast. Front end development is in fantastic shape for an industry that’s 25 years old. In a quarter century, we’ve participated in reshaping how billions of people spend their free time and get their work done, seen the rise of social giants, endured the creation of millions of mediocre small business sites, learned to build apps, and taught millions to code in the process. Now, some of our current development paradigms are either underdeveloped or outright broken. News websites are a cultural disaster. Web app development changes weekly. This is the natural result of many people trying many things. But the web mostly works most of the time. Eventually we will have fully baked standards with supervisory committees and enforcement and professional certifications and insurance and all the other trappings of a fully grown industry. But right now we get to enjoy the growth of one of the most exciting industries in history, despite it’s problems. Front end development isn’t broken, it’s teething.
  • pnt12 6y ago
    It's an industry with established UX guidelines defined 20 years ago which are mostly ignored today. Slow, inconsistent and confusing interfaces seem to be the norm, not the exception. There were some revolutions, like responsive design, but all the rest feels very shallow compared to the bad UX experienced in so many applications and websites.
• secondcoming 6y ago
  It still surprises me that twitter, one of those high-flying SV companies that overpays massively for talent, still has a truly terrible UX on low-end hardware. Opening a link brings my (admittedly old) iPad to a halt.
• hyperpape 6y ago
  I'm bothered by a lot of contemporary web development. Many things are implemented using far too much heavy JS code, and user experience suffers. I also think a lot of people drastically underestimate how much we get out of modern tools. In a followup tweet[1] and in this thread, antirez says that we haven't improved interaction in 20 years. Let's consider gmail, which is close enough to 20 years old. But at the time, it was an example of a very rare and complex app build on top of ajax. I don't personally quite remember this, but it apparently didn't have rich text editing for a year after it was released. Ask yourself: how long would a competent front-end developer need to make a decent 2004 gmail clone using modern front-end tools? The ideal would be to build more lightweight websites, but exploit modern tools where they pay for themselves. While we're at it, we can write fast software without premature optimization. [1] (https://twitter.com/antirez/status/1378274076859502593 https://twitter.com/antirez/status/1378274076859502593) [2] https://en.wikipedia.org/wiki/Gmail_interface#cite_ref-RichText_26-0 https://en.wikipedia.org/wiki/Gmail_interface#cite_ref-RichT...
  • simonw 6y ago
    From defining the entire approach when it launched, Gmail has somehow turned into the single best argument /against/ SPAs. I dread opening it, because I know it's going to be slow to load and slow to use. I don't know how it went so wrong. Original Gmail was a revelation. Today it's sludge.
    • simonw 6y ago
      ... I just loaded Gmail on an empty cache and watched the Firefox Network pane: it made 304 requests and loaded 29.65MB of stuff (9.8MB compressed) - taking 8s to get to "loaded" (on a very fast connection) and over two minutes before it stopped loading extra pieces.
    • perryizgr8 6y ago
      Try to use the basic html version. It is a masterpiece of UI design and is blazing fast. https://mail.google.com/mail/?ui=html&zy=h https://mail.google.com/mail/?ui=html&zy=h
• pacifika 6y ago
  It’s been the same problem since the web design should be pixel perfect days, instead of print design the web is now in love with app design. The difference now is that there is less good practice. But look at gov.uk and you see the difference between good web design that doesn’t need to be an app or have carousels. Web development now has the Sharepoint problem: it can do everything given enough effort. It’s not about what is possible but it’s about what you want from it. Before it was flash intro movies now it’s a shop front with modals and carousels.
• lame88 6y ago
  Plenty of discussion has been had around incentives and I agree with all that, but also there's another angle here: aside from dark patterns, I think the problems of terrible front-end experiences are most prevalent in the middle of the bell curve - the front-end products developed by rather mediocre skill levels and budgets. Which is usually a pejorative, but thinking of it as literally in the middle, not great but not terrible, a wide range of skill levels where people are more or less competent at their jobs. These are where I start to notice the worst effects of the median trying to adopt the technologies and practices that high skilled developers at good companies with huge budgets are able to utilize effectively, or outright make themselves, especially when there is so much churn that being "up to date" with technology is like a pipe dream to most people. These median teams inherit all the complexity, but due to budget or time pressures, etc. aren't able to overcome it effectively to produce a product with high quality, and users feel the sluggish experience and bloat that comes as a result. This pertains to more than UI of course but eventually manifests to users that way. Something feels wrong. The median should be able to inherit the benefits of technology produced at the high end without such inheriting massive costs.
  • runawaybottle 6y ago
    The implication is rough, but it is part of the truth (not all of the truth). However, I will add that the anointed ‘high-end’, your lifelong long backend devs, devops, data engineers, etc are adding to the problem. Backend people taking up the frontend hat under the fullstack guise create tons of awful end results, and this is even more common because they already exist at the company and are given a blanket ‘competent’ rating (in other words, they get a chance to mess with the curve before anyone else). All of this is part of the pervasive problem that your post is slightly tainted by (my attitudes are tainted by it as well), which is a general disrespect for frontend. No matter, the truth of these attitudes will show up in all of our products. It’s always obvious to me which teams take frontend seriously and which don’t (the quality is always literally visible).
    • lame88 6y ago
      I do have a bias against front end development being from my perspective quite a mess, in the same way that physical scientists often look at the social sciences, though the social sciences are still quite important. But for what it's worth, I consider myself somewhere in that median band, and my perspective is motivated by and applies to front end as much as other parts of software dev/delivery. I agree you can tell the difference, though I would place blame for those situations more on an organization than the developers who get shifted toward that work out of their specialization. It could be some dubious values, but it also could be project budgets.
• gumby 6y ago
  I had hoped the end of Flash would have brought this nonsense to an end but it seems the bozos just moved on to continue doing damage.
• vikingcaffiene 6y ago
  People trot this one out every now and again and what they mean is “front end used to be the easy part of the stack”. If you lived in the bad old days of jquery spaghetti and in-line php templates you’d realize what a bad take this is. Yes it used to be that anyone could jump into the front end. And the front end _sucked_ because _anyone could jump into the front end_ and so they did. There was no organization. No architecture. Nothing. Just a bunch of files that got harder and harder to maintain as the app increased in functionality and scope. Modern FE is a discipline every bit as complex as anything that we face in the backend. It requires that we actually apply an architecture. Design our code so that we can respond to changes in our business requirements etc. Serious engineering rigor in other words. Hell I could make the argument that in some ways backend dev is much more straightforward. I think it’s fair to say that we often put too much business logic into the front end. Fat clients are not something I agree with. But to say things used to be better is just flat out incorrect.
  • withinboredom 6y ago
    > I think it’s fair to say that we often put too much business logic into the front end. As a back-end dev, this reminds me of the time I used our own product and saw a read-only field on the UI. It was some interesting bit of data that only existed in the database (we didn’t expose it in the API) and I brought it up how cool it was that we were doing that now. The front end dev said, “oh, it’s not from the database, we make several API calls to get the bits we need and then calculate it the same way we do on the backend” I facepalmed. Like, just ask to expose that data, it’s a single line of code! Instead we made 7 API calls... :sigh:
    • vikingcaffiene 6y ago
      Yeah I generally think the UI should only manage stuff like that cosmetically. Stuff like form validation etc. The real work should happen on the backend and not care about UI stuff. So it just throws if the user tries to get cute. IMO that is a nice separation of concerns and keeps the client thin and presentational in nature.
    • jasonlotito 6y ago
• danlugo92 6y ago
  Most of the issues I see in front end code are repeats of problems that were solved decades ago, some of them even 100 years ago! (debouncing). No separation of concerns, no layers, or if there's layers there's controller code in view layer or view code in controller layer. etc.
• ryanSrich 6y ago
  And yet, “performance improvements” are often the excuse for making every single site and web app look the exact same. Dull, flat, ugly, homogeneous design has sucked all the life out of the web. Remember flash? Remember when websites were cool? Where it was fun and exciting to go to certain sites simply because of how they were designed? Remember the early days of CSS 3 experimentation? But but but! Skeuomorphism is slow! We need fast sites. We need accessibility! We need to improve our performance! Now look. The web is both ugly AND slow. The big question is why? To me, it’s all about commoditization and making money. Why spend money on expensive artists, designers and engineers to make sites look good If we can band together (big tech) and make flat design the norm? Everyone will forget that the web didn’t used to suck as bad. Instead, we’ll absolutely decimate performance with loads and loads of ads and nonsense JavaScript. We’ll hire product managers to track every single interaction imaginable so user’s experience sucks and we can invade their privacy! Basically big tech ruined the web. They ruined design and everyone pretends like this never happened.
  • stevenicr 6y ago
    I concur with most of the sentiment here- and am happy to push much blame to big google, pointing out that if you are not in google you basically don't exist on the web - (and for many on the planet if you are not in fbook than you are not on the internet) - when google says google web vitals, speed all that ranks you in the top or you are not in the top and you become invisible - it's a thing. However I think the global move away from desktop computing to phones, ipads and cheap chromebooks are the real fun killer for great art and design. I used to love making sites pixel perfect at 1024 - and today if we spend a lot of time making fancy desgins - most people will never see it, since they are checking it out via phone surfing. This is what I point to for people inquiring about design today - basically it's up to the client to provide the design - what pictures and text do you want to put on the small screen? that's your design. Even if you put a note on the small screen telling people to visit our Hd/Desktop version for more cool effects they would enjoy - many (most?) people don't even have a way to access a large screen for computing. Maybe there will be a shift with people casting to TVs and 'smart tvs' browsing better and turn the tide - then we'll need some kind of 'report back framework' to tell us people can see and navigate via the larger view - then we could try to remake flash coolness via html video for the big screen - but then we wouldn't know how close they are to the TV - so how large would navi buttons and pop up text need to be.. meh - back to basic plain stuff. Personally I think we need better zoom-in controls for browsers that people can easily use and understand - this could give us more flexibility as designers, like the hamburger menu - if you can expect people to know how to use it - not holding my breath though.
• mitchdoogle 6y ago
  This diagnosis needs more precision. What/who, exactly, has failed? What needs to be changed, specifically? You look at the comments here and you see many different people are taking this different ways.
• baron816 6y ago
  If I were to just look at the bookmarks in my browser, I'd get the impression too that frameworks are useless. They're all a bunch of sites that render pretty static content. But the app that I work on in my day job (that I don't personally use) could not possibly be built without a framework. td;dr: a lot of things don't need a framework, but they are still very necessary in many cases. Likely not ones that regular consumers are exposed to though.
• bit_logic 6y ago
  What upsets and concerns me the most is when I see poorly developed SPA on really important sites. For example, government service application websites. If reddit or nytimes has a bloated, intermittently failing SPA site, that's an annoyance. When it's a form to apply for unemployment, ACA health care, DMV, or other critical services, it's a critical failure. Especially since these services are most often used by exactly the population most impacted by bloated SPA (they tend to have slow or unreliable internet and slow computers, maybe even a cheap android phone is all they have). Such sites should be using minimal or no JS. These aren't meant to be pretty interactive sites, they need to be solid bulletproof sites so people can get critical services. And I haven't even mentioned how SPA sites often lack any accessibility features (which is so much easier to implement if sticking to standard HTML+CSS and no/minimal JS).
  • clairity 6y ago
    what concerns me more than that is how government sites require google and the like (captcha and analytics at the very least), giving them opportunity to hoover up all of our sensitive data in one convenient place.
  • lifeisstillgood 6y ago
    I am going to :+1: the UK census site - built on code developed by the gov.UK digital service, it has been apparently bulletproof at taking 20 million plus individual households through a moderately complex survey. sometimes it can be done right. And it uses a framework :-)
    • devit 6y ago
      Which framework?
      • WickyNilliams 6y ago
        If my memory serves me right, it's Python/Django. I contracted in that department a few years ago. Edit: Just remembered it's all open source too! Look here and search for repos beginning "eq-". Survey runner is the app I believe. When I was there the plan was to use that, though perhaps they eventually wrote a fresh app. Anyway the code should all be there https://github.com/ONSdigital?q=Eq&type=&language=&sort= https://github.com/ONSdigital?q=Eq&type=&language=&sort=
• bitwarrior 6y ago
  I'd say we're likely comparing apples to oranges here. It's a common complaint on HN that frontend development is a mess and evolves too quickly, that it isn't "what it used to be". Static pages, small downloads, very little coding overall. What we miss is those kind of sites still exist, but they're not the sites we're complaining about. Back in the late 90's and early 00's, most websites were largely "brochure" websites. Companies were getting online because they heard about this whole internet thing and they knew they just needed to "get on the internet". You largely saw companies uploading whatever brochure they had basically into a digital one online. Those websites were insanely straightforward. Render a page, static content, the end. Maybe it's a little more dynamic than that, perhaps you're running a basic LAMP stack listing, say, real estate. Query the database, render the page, we're done here. Very little interactivity. Those websites still exist, but they're likely not the ones we're complaining about. Site's like boeing.com are those traditional brochure sites which deliver very little interactivity. Relatively quick and nimble, the hero image is larger than all the JS they load (and, honestly, they could probably remove most of their JS now - they're using jQuery, modernizer, underscore, stickyMenu, require.js and a bunch of probably unnecessary jquery plugins we can eschew today, but we're here to complain about today, not praise it amirite?). What we're actually complaining about are usually the interactive sites. Your Twitters, Facebooks, even sites like Reddit that dynamically load content as you scroll, click posts and download more content, comment - all manner of interactivity. Typescript? React? Functional components? Hooks now? Learn Redux? Unlearn Redux? CSS flexbox? CSS grids? My website now has a build process? I used to just edit the PHP file and upload it via FTP. What the hell? These are not simple "brochure" websites, so yeah, they're more complex. They're applications. And being that they're applications, we shouldn't be comparing them to brochure websites, since they're delivering a completely different experience and have a completely different goal. We should be comparing them to desktop applications and the desktop application development environment, and therefore, comparing their stacks against the likes of C# and WPF, Swift and Cocoa, C++ and Qt or C and GTK. And compared to those tools, how does the modern web development tool chain stand up? I have no idea, I don't write desktop applications! But what I do know is companies like Slack and Discord have elected to use electron rather than create their products in whatever desktop application framework. VS Code is electron-based and being a Microsoft product they had all the reason in the world not to do that - and it's dominating it is space today. Offerings like Figma, which by all rights one would imagine should have been desktop software elected to be an online tool and has completely shut out the competition. So if you're going to complain about online applications, don't compare it against an old programming paradigm that would never apply to these products. Compare them against the modern desktop application development experience and let's start the conversation there.
• dmje 6y ago
  It's the same as it's ever been. The same mistakes, the same things done right, just all in different shaped packages. Fundamentally it comes down to the same thing: use appropriate tech. Use it because you should and not because you can. Don't build a SPA if you can do it in a simpler way with plain HTML and CSS. Don't build an app if you need a website. Don't bother with some enormous backend horror if your site is never going to need to scale to that size. It was the same way back with Flash, dhtml, html5, early JavaScript, CSS, Dreamweaver, whatever - if you need something, use it, if you don't, don't.
• mLuby 6y ago
  What we're missing in front-end development is more abstracting away solved problems so you don't have to think about them ever again. Shared frameworks and libraries do help significantly with this but the fact that they still undergo substantial churn tells me they haven't completely solved the problems they address. When's the last time you needed to drop down into Assembly to fix your JavaScript? Probably never—you can operate at that higher level, which lowers barriers to entry and increases productivity for developers. (Put your hand down, you wonderful machine code hobbyist, you.) In contrast, we still "drop down" from web app components into JS/HTML/CSS all the time.
• fctorial 6y ago
  Javascript being enabled by default motivates developers to include javascript in their site by default. It was a mistake.
• neonological 6y ago
  Given that a lot of people have the title “front end web developer” of course there’s going to be backlash. Most people aren’t unbiased enough to hate on the thing they’ve spent years mastering. Frankly front end web development is a huge mess if you look at it from an unbiased perspective. HTML wasn’t designed for multimedia, JavaScript was designed in a week. Now the entire modern industry of web development are a series of endless hacks built on top of the old framework. React, typescript, css are all skin grafts on top of technology that was designed for something else. Of course the end result is going to be inefficient. The entire web is new tech patching up old tech. It’s like the 737 max, all of modern web development is an MCAS on top of html. It’s not even a single thing. It’s like hundreds and hundreds of MCAS’s with some MCAS’s built to patch up other MCAS’s. The fix of course is to start from scratch. Given all of our knowledge of Modern web GUIs design a singular native api that can achieve what we need with significantly less complexity and better performance. Of course some front end engineer with 10 years of experience isn’t going to openly embrace a new api that is not only better but can possibly mastered in a month by any average dev. If you’re primarily a front end developer I have to say that I cannot trust your opinion. I do not believe any person has the impartialness to deride the very thing that defines their career and expertise. Literally front end developers are just experts at navigating a universe of patches and hacks and no such dev wants to admit it. I’m interested in peoples opinions though, it’s just in a thread like this it’s impossible to get an unbiased opinion.
• crazygringo 6y ago
  > sites that are unable to obey the most basic rules of navigation and usability, terribly slow despite the hardware progresses. And I can only think that modern frontend development has failed. We have more information and services available than ever before. And it's never been cheaper or easier to start something new. I don't know what "basic rules of navigation and usability" the author is referring to, but I virtually never come across a site that can't be navigated or isn't usable. And all software gets "slower" as hardware grows faster [1], it's not anything specific to the web. The web is amazing, nothing has failed, sheesh. Yes there's always going to be room for improvements both in speed and usability -- developers are human, nothing will ever be perfect -- but the idea that the most popular digital interface technology of all time has "failed" is ludicrous. [1] https://en.wikipedia.org/wiki/Wirth%27s_law https://en.wikipedia.org/wiki/Wirth%27s_law
  • fctorial 6y ago
    > And all software gets "slower" as hardware grows faster Quoting a statement doesn't make it good. It's bad.
    • crazygringo 6y ago
      I'm just saying it's not specific to the web. It's not some specific failure of front-end technology compared to others. It's not a failure at all, nor is it amazing, it's just par for the course.
• aristofun 6y ago
  Frontend development is fine. People failed at it. Like they always do at first in important things. And it’s not even developers who failed, but users and managers who just don’t care enough.
• mathgladiator 6y ago
  Yes and no. I both agree and disagree. For a lot of it, yes, it is a giant mess. I'll posit the reason modern front-ends are a giant mess has to do with the fact that everyone tries to hack, slash, and transform the document model into an application model. This means they don't want to reload the page, and they then have the burden of manipulating the DOM in a very crude way. This creates a predictable empire building game of building a framework to make it easier, and every framework succeed to a certain degree. Now, they succeed in a number of great ways, but then they run in the abstraction leakage which causes them to bend in strange ways. For many applications, that's fine, but as the number of applications grow this creates problems for the common case. So, quality gets harder to achieve. Now, the philosophy that I believe is that we just don't think simple enough. Most people don't think deeply about this stuff (and good thing because we would never get anywhere without people running forward making messes), so what do we do? Well, I think the real answer may not be to fix front-end development. Instead, I'm coming to the conclusion that we should fix back-end development. Instead of using the tried and true work-horse of request response (i.e. HTTP), we need streams (i.e. WebSocket). Streams let you pair-bond state, and this is exceptionally important. Ignore the complications of WebSocket for a moment (I don't deny there are problems, but they are solvable; just no good common solution yet). What a stream lets you do is pair-bond/entangle objects, and this lets you simplify the development model to a great degree such that the front-end object is a proxy to the back-end model. This entanglement then forces you to contend with two things: (1) how do I change the object, (2) how to respond to object changes. Once you address those two concerns, you can build applications fairly easily. Using this framework, we can then see work towards understanding why modern web development is so painful. Since objects don't tell you how they change, you have to reconcile that change. This is why things like react have a shadow-dom, but you still have to read state from server then shred it into components for that to work. It's easy to miss an important data point since there is no direct entanglement. Ultimately, you have to take an entire object and then mangle it into a form that is pretty to the user without disruption because the DOM has hidden state (i.e. scroll bars or text selection). Classic web avoids so many problems because that disruption is built in. Since failures of the request will happen, you further have to deal with partial failures of state changes which is why you generally need a thing like Redux to be an immutable state container so you can rollback state changes. OR, you need GraphQL such that the client only deals with atomic failures. However, most people fuck up GraphQL, so you have to have both GraphQL and Redux. Things like svelte are better because it uses language techniques to help you shred your data into DOM, but it still suffers. My claim is that you can simplify front-end development BUT you must also simplify the back-end, and I'm doing this over at http://www.adama-lang.org/ http://www.adama-lang.org/ where I'm solving the problem for board games. I claim that board games are a limit point of technical complexity for transactional interactions between people, and partial failures are catastrophic for the experience. The way that I'm building a game right now is that I have a client which I can connect a giant JavaScript object to the server. There is no proxy, just an object. The server will then get an update, then update the object and tell you about it via a change callback. These change callbacks allow you to synchronize the DOM to the object without an intermediary. The DOM callbacks can safely read the object. This lets me use vanillaJS without fear. When some DOM callback wishes to change the object, then all it does is send a message via the stream to the back-end which will (1) authenticate it, (2) validate the change, (3) incorporate the change, and (4) spit out a data change. Much like a database, the UI is a tailer of the log. The JavaScript library I have is in its infancy since I'm balancing my time between the language, the devkit, the client library, the distributed system design, the game tools, the canvas renderer, and ultimately the first game to launch.... And I'm only working on this 2 hours every evening until I retire, so... it's going to take time.
• viburnum 6y ago
  It’s mostly just ad tech. Sites without ads are usually pretty good.
• rover0 6y ago
  We fail at manual state-management, and the mostly used patterns we are using are complex leaky abstractions.
• CyberRabbi 6y ago
  I want to say this is hyperbole but it’s actually correct. I don’t even have JavaScript enabled anymore.
• the_dice_wizard 6y ago
  I've been working over a year as front end dev and my main complain is that I feel the whole thing is a bit unstable. How do you choose the right tool when it comes to JS? You can go vanilla, use jQuery, Angular, React, Vue, Svelte... and that's just talking about the big ones. CSS seems a bit more stable with BootStrap still having the biggest share and Tailwind coming as a strong contender. I'm pretty sure we all thought about JS frameworks first when we read 'front end development has failed'. But how about UI/UX? We had 4 designers so far at work. One of them was really good and left. The others were good designers, but not good web designers. Modern design is bloated, sometimes not intuitive because we all want good looking things, who cares if they aren't as functional. And after all, when you visit a website, not as a programmer or a designer, as a consumer, what do you want? Speed, usability and content. You don't care about animations, parallax effects or if the company used jQuery or React. My opinion is that there are use cases for certain technologies but sometimes we overdo things.
• davidkell 6y ago
  Has anyone found a frontend JS framework + backend combination with the developer ergonomics of say Rails, Django or Phoenix? Would love to hear.
  • pyotr55 6y ago
    i'm currently trying out https://turbo.hotwire.dev/ https://turbo.hotwire.dev/ which is a new library from the basecamp guys, which makes it really easy to create SPA feeling sites with rails, using little to no javascript, and in a very unobtrusive, intuitive way. i'm guessing it's going to be an integral part of the upcoming rails 7 release.
• deleted 6y ago
  [deleted]
• jariel 6y ago
  Some things that have changed: 1) We've gone from function to content mostly. 'Apps' used to mostly deal with files, like Word, otherwise, hey were standalone. Now we deal with an incredibly variety of content. 2) We've traded consistency and reliability for speed to market, and rapid evolution. App releases were once a year, web releases can be daily. In other words 'the web' is not 'about apps', it's about something slightly different.
• ta20210403 6y ago
  This is what happens when you let sociology majors with dyed hair who take a two month "coding boot camp" become "full stack engineers".
• ta20210404 6y ago
  This is what happens when you let sociology majors with dyed hair that have a two month "coding boot camp" in their resume become "front end engineers".
• csbartus 6y ago
  I'm designing and developing web sites and apps since 2005. First with PHP (Wordpress, Laravel, Yii), then with Ruby (Rails, Sinatra), now with Javascript (Gulp, Gatsby, Next, React, Lodash, Immer, Typescript). I also do / did static sites with Jekyll, or my own framework. Among all Javascript is far the worst experience. In all areas like the language, the types, the state, the hooks, blogging engine, toolbelt, hosting, packaging, publishing, documenting, the community. The situation is so bad that I quit. It eats my nerves. Instead of creating I'm patching and fixing bugs all day. That's why the web is what is it today. It's Javascript driven, and Javascript is totally flawed.
  • rabuse 6y ago
    It's just so easy to write horribly structured code in JS. It's where PHP was years ago, where everything was just slapped together, and you just pray for no errors.
• anhanhanh 6y ago
  These type of comments always come from people who have zero real life experience working in the intersection of code and business.
• taeric 6y ago
  I want to agree with this, but I do have reservations. The competing priorities of anything are hard to balance. Try building a physical store sometime. Even a simple garage sale. Layout for navigation and perusal is not a trivial problem. Especially if you don't have the space to make comfort a priority. To that end, how much is actually broken, versus you notice the maintenance costs? Ever looked at public restrooms? Are they broken, it just under funded?
• joduplessis 6y ago
  It has? I can think of very few areas in software development where there is this much innovation & diversity in frameworks & approaches to building something. Maybe our approach to usability has failed with all our "necessary" popups & cookie dialogues - there I agree. But to say "front end development" has failed simply because its evolved is a bit myopic IMO.
• shadowgovt 6y ago
  There have always been bad developers. Unless he means that he expects that by now, someone would have developed a completely idiot-proof infrastructure for making UIs, we can always assume that there will be people making websites who do not have the time or inclination to learn the tools and technology and make the wrong decision at every turn. ... And even though some idiot-proof frameworks exist, they still require somebody to put enough effort in to discover and use them. I mean, we can apply the same criticism to the giant pile of crapware in the mobile stores. Some software is good, some ain't.
• wonnage 6y ago
  You try writing a UI that: 1. works visually at all screen widths and resolutions 2. returned from a server with zero knowledge of said screen widths and resolutions 3. without shipping redundant assets 4. responds immediately to user input 5. but all visual updates go through this slow and crappy DOM API 6. oh, and it's all single-threaded 7. and there's no standard library for stuff like virtualized lists, modals, etc. so have fun picking your own and shipping it down 8. and your options for navigation are either losing all local state at each navigation, or writing a SPA that some neckbeards on HN hate for esoteric purity reasons
  • deleted 6y ago
    [deleted]
• wideareanetwork 6y ago
  That’s a really negative, glass is half full viewpoint. How can anyone not see the incredible wealth of unbelievable awesome that is the modern web? How can anyone use 200 popular websites and see shit instead of being astounded by how awesome it all is? I look at the same thing and see unbelievably powerful web applications, the web browser as the most sophisticated fabulous software ever built (alongside Linux), a constant drive amongst front end developers/libraries/tools for new and better ways of doing things. And I see so many websites that it’s impossible to make sweeping generalizations about front end development. The world contains certain people who want to see the bad... this is what’s happening here.
• neilv 6y ago
  Soon after Web banner ads appeared, researchers discovered that users quickly learned to tune them out. Sometime after that (after clumsy false starts), what used to be advertising people took over the nature of the Web. HCI and human factors engineering (i.e., technology in service of the user's goals) was largely forgotten, and UX (i.e., technology in service of the developer) was born. Be skeptical of most UX you've seen, since much of what we're now taught, much of what tools/platforms are available, much of what the jobs are... are now generations away from the needs of users. If you want to genuinely serve the needs of users, question everything, including all the implicit and explicit conventions of your field. Product concept and design are in some ways harder than they used to be, since, e.g., users' conceptual models, fashion, and available platforms/technologies have been shaped by a pervasively user-hostile and manipulative environment. But, as designers, you still have a lot of leeway to operate creatively within that. Question everything.
• aiisahik 6y ago
  I can only think that modern power generation systems have failed. There are so many advances in power generation in the last 100 years - from nuclear, wind, solar, hydro, and even biothermal. Yet when I look around all there are so many dirty combustion engines and coal power plants spewing greenhouse gasses and toxic fumes. Both statements are moronic. Taking advantage of modern design philosophy, modern CDNs, modern framework - all of that takes time, attention and MONEY. If you don't put in the investment in all of these, the fact that you have access to "modern frontend development" is meaningless. It's like asking why is not everyone in the world driving Teslas.
• alpaca128 6y ago
  I would go a step further and say this often also applies to GUIs in general and not just websites. Because too often the problem is not the framework, it's the little amount of thought that goes into the UI. If someone spent time on it usually it's so it looks a bit nicer, actual considerations about workflows and expectations of real users seem to be ignored completely. And then there are user interfaces where the developers actually tried to make a difference but stopped somewhere in the middle, like with current Firefox versions. Don't get me wrong, I think the UI customization feature is fantastic and I love that it now supports a large zoom indicator/control in addition to larger address bars and tabs - as the first line of support for my relatives I appreciate that this is now more visible. But then there's that tiny download button/indicator which, for less tech-savvy people, is often simply invisible. As much as I dislike the huge bar at the bottom that was introduced with Chrome, I have to admit it is better out of the box than a tiny blue arrow that desperately tries to be more visible than all kinds of website animations and ads.
• jevgeni 6y ago
  I started going to Awwwards to find what to avoid doing.
  • mitchdoogle 6y ago
    Interesting take.. I love going to that site because I want to see new things that push the limits of the browser. I would love the opportunity to build some of the sites that are showcased there, just to try new things. I don't think these types of sites are "broken" at all. Most of them work very nicely in my experience and use clever ways to hide load time or other negatives. I wouldn't ever use most of the cutting edge ideas in sites I build commercially because the sites I build are for a more mainstream audience that probably isn't tech savvy, so I keep it to the basics, but the awwwards stuff is still very cool to me. I think the broken stuff the tweet refers to is all the online publishers with floating video ads, 50 tracking scripts, bloated pages, zero accessibility, etc on a page for a 500 word article
    • jevgeni 6y ago
      Oh, those are impressive websites, don't get me wrong. But I think that the intent and purpose in design matters. And awwwward website's purpose is pretty vacuous. The websites there are ad brochures. A single short sentence in huge font above the fold, a compelling image - the purpose there is to grab attention, while offering little information. Compare it with densely packed, more honest and less thirsty websites of the 90s and you'll see why a lot of people are nostalgic.
    • CRConrad 6y ago
      > I love going to that site because I want to see new things that push the limits of the browser. Browsers are so hugely (over-)capable nowadays that anything that comes even close to "push[ing] the limits of the browser" has to be at least as huge and complex as, say, MS Excel. 99.9... Well, "five nines" ring a bell? -- percent of web sites are light-years from needing anything like that. Sounds like complexity for complexity's sake. Web wankery.
• barry27 6y ago
  I thought Antirez was too mature to jump on this boring bandwagon.
• azmodean_kvkv 6y ago
  This infantile false dichotomy again. We get it; BE engineering is far superior to JS/FE engineering so therefore anyone belonging to the BE/non-JS tribe is a far superior intellect and person. We’re glad you feel better about yourself. I challenge you to be the change you want to see: 1) build something better 2) get wide adoption of it.
• SilurianWenlock 6y ago
  I only have experience with backend non web development, so my experience may not be worth much, but... Setting up a frontend web app with React (or Angular) is insanely hard to self teach and I would consider myself very good at self learning. Its hard to workout how to integrate React with Bootstrap and you often start to get problems you are not even sure how to fix. When you look at tutorials online, they all have slightly different tech stacks which complicates this further. Second to this working out how and where you get your graphics from is impossible for me. Frontend blows my mind! (And this comes from a guy who has done +1000 leetcode problems for fun) Also, in this thread people say this or that is bad without specifying examples of websites and a problem which could be fixed. Is anyone able to name 2 to 3 concrete websites and examples from which others can look at and learn what is wrong?
  • perryizgr8 6y ago
    I can sympathise with this. I have no professional experience with web technologies. Whatever little I have done has been a hobby. And I can never learn anything "generally", the way I know how to make a C program. Every react/angular tutorial throws a bunch of high concepts at me, and then a list of commands that will do some magic for me. I am unable to use this info to start my own web project and translate whatever is in my mind to the screen. Everything I have been able to do, has been by modifying existing examples/projects. Like you, I consider myself to be a good self-learner. I was able to go through a couple of rust tutorials, and with generous consulting of the manual, I am able to write simple rust programs, and figure out how to do what I have in mind.
• zapzupnz 6y ago
  Loads of comments in the Twitter thread trying to pin the blame on someone. It’s product managers; no, its frontend developers; no, it’s backend developers; no, it’s users… An organisational way of thinking is to figure out whose blame it is and charge them with fixing it. Me, I don’t give a crap who’s to blame. Just fix it. Stop collectively waiting for someone to do something about it and just do something about it. Fix your own code. Make your own code better. Be an example to the world.
• ilaksh 6y ago
  I have a feeling that I am supposed to keep this a secret, but if you are tired of broken and slow websites, check out the Gemini protocol as a break from the BS. It's not going to fix the web or replace it in a lot of cases, but it's nice to have an alternative for some things.
• stcredzero 6y ago
  I know game developers who lament the passing of Flash. Though the runtime had issues with efficiency and power use, the programming environment was great for games, in terms of being truly write once, run everywhere. Even networking had serious quality of life benefits for both devs and users. The equivalent in Javascript is an order of magnitude worse in those regards. It's ridden with compatibility problems, everywhere.
• dvfjsdhgfv 6y ago
  If you share the feeling, join the small Internet movement: https://cheapskatesguide.org/articles/small-internet.html/ https://cheapskatesguide.org/articles/small-internet.html/
• poisonborz 6y ago
  I think every discussion in this topic is just a collection of of every commenter's inner question "am I satisfied with the project I'm currently working on?".
• segmondy 6y ago
  The worst is the dynamic DOM manipulation, where what you print isn't what's rendered on display.
• franklyt 6y ago
  The tools exist the solve these problems: blame developers. TypeScript and modern frameworks with contemporary understanding of app design kills nearly every historical pain point of web development, but many are stuck writing jQuery and using WordPress.
• tmwed 6y ago
  what a dramatic and ridiculous statement. i suppose you could say i have a vested interest in holding an opinion like that. however the dude that posted that tweet is in the tech space, therefore (imo) excludes him from being “just a user of the internet”. furthermore, REAL USER demands and expectations increased from native mobile app usage, so of course the complexity of pages/apps on the web have followed suit.
• zerubeus 6y ago
  Thank god I quit frontEnd, the story was like this: - 2010: dude look this new thing "angularjs" a model/controller(vue?)/STAR*, the $scope dude it's crazy, something dynamically changes in the $scope and HOPP it appears instantly in the page :D Few years fast-forward, have a watcher in a model that changes something in another model, unpredictable changes down/up, random mutations...duhh da heck?? We were good sending HTML from the server missing those days... - 2014: dude look this new thing, it is called "React" and you know what?, forget about the state up/down, down/up and allover the place, the state is ONE DIRECTION with React, and it is backed by Facebook bro. -(me) Oh yeah? Ok what about the 3 years I spent battling with AngularJS? - Don't bother bro Google is dropping active development and maintenance of AngularJS, it is either you switch or use their beta Angular 2. -(me) No, thanks I'll go for React. - Dudeeee look it is Redux, you dispatch an action, and it takes care of updating the state, and you know what, you can combine it with Redux-thunk to avoid race conditions. -(me) Wait wuuuut? Race conditions in the front? Feels like it is becoming a game engine bro da heeeeck... - Brooowww, look dat new baby, VueJs :D -(me) wait wuuuut? Don't tell me Facebook is letting down active development of React. - No bro it's just another cool front lib it is really dope, and it's only the V(vue) part of the front taking care of reactively updating the DOM. -(me) ok but what's new? - Now you can have a DSL addition in HTML cool stuff like 'v-for' to dynamically hide/show a DOM element without writing any code. -(me) wait, wuuuuut, this reminds me of something I've seen before, the ng-if AngularJS is coming back with another name? I'm loosing my mind broooo. - Dudee look its Gatsbyjs, generates a cool static site, but you have to write React and graphql for it -(me) ok. - Dudeeeee look svelte is killing them all. -(me) ok. - Dudeeeee this one is an absolute killer, nextjs everything is server side rendered, you write your React component you describe the data and the server takes care of building the static html and send it to the client. -(me) wuuuut? But that's what we were doing back in 2009? - 2019 duuuuudeeeeee ... -(me) STFU I quit. (and since then, I'm happy cloud solution architect)
• ramin_hal9001 6y ago
  Others have mentioned the trend of making everything a SPA, which I agree is a huge part of the problem -- it is a cultural issue, not a technological one. Most apps only need to be HTML with minimal client-side scripting. People who teach front-end need to start out by teaching people how to use static site generators, rather than immediately telling everyone they need to start learning React or Vue. But I'll also say that the web as an app platform was fundamentally broken from the very start, and this is because it was built on a fundamentally bad programming model. *Why is it* that everyone feels the need to use use virtual-DOM frameworks and CSS preprocessors for all the apps they design? Why is it that whenever I build an app for the web, NPM needs to download and compile around 10,000 modules (no exaggeration) in order to build the app? JavaScript was originally going to be a Lisp-like language, but OOP was in fashion at the time and so it was made to be more like Java. Had it been a Lisp from the start, at least CSS preprocessors would never have become a thing because with Lisp you have macros. I am not saying the web needs to be based on Lisp, although it would definitely help if things started moving toward web assembly so people can start using better programming languages and frameworks than just the ones that compile to JavaScript to program front-end apps.
• throwaway823882 6y ago
  Software development in general has failed. 20 years ago I had an iPAQ, which is basically a handheld Windows machine. Today I have an Android. 20 years ago, the iPAQ had 32 megabytes of storage. My Android, if it only has 32 gigabytes, is used up in a month by just a couple of apps. I could do the same things 20 years ago with my iPAQ that I do with my Android today. Yet today it requires 1,000 times more storage space and 100 times more processing power.
• hardwaregeek 6y ago
  I really dislike these posts. Not because they're wrong. They often have some truth in them, albeit an uncharitable, selective truth. I dislike how these posts just keep on complaining same tired points. I dislike how they don't offer solutions. I dislike how lazy they are. If you're going to offer criticism of front end, then please include some strategy to fix these problems. It doesn't do much to repeat the same "muh SPAs are too slow". And yeah, I understand that proposing solutions won't fix your state's DMV site from sucking, but it's at least constructive. It at least makes it feel like you're trying to help instead of keyboard criticizing. Even better, build products with these solutions! Plenty of users would love fast, efficient sites. I know I love it when Hacker News opens instantaneously.
• drumttocs8 6y ago
  Websites for giant retailers like Walmart, Home Depot, etc are shit, and it blows my mind. How much are these developers getting paid to make the modern web so unusable?
  • seandoe 6y ago
    They don't get paid to make the modern web usable. They get paid to do what their project managers tell them. I see this first hand everyday. I've tried to fight it. I've tried to prioritize performance, usability, etc. It's not a priority for a lot of companies. At my company, the priority is delivering features that the sales team need to close a new customer.
• deleted 6y ago
  [deleted]
• ericls 6y ago
  Wrap them inside Electron, now they are not web anymore, would you have the same complaints?
• cutler 6y ago
  Anyone remember http://www.useit.com http://www.useit.com in 2000? Bring back Jakob Nielsen.
• shruubi 6y ago
  I'm amused by certain "big names" coming in and responding with arguments about how front-end wasn't that great back when either. This idea that modern front-end has failed is not some absolute statement that means that all that came before was a success. In fact, it's a statement that with all our modern technology and idea's, we're still in a situation where we haven't improved on front-end tooling and development. Also, just because front-end has exploded and created a huge amount of jobs, doesn't mean we're doing it right or well. There is just as much evidence to suggest that we need so many front-end developers because our current tooling and methods have made front-end development a massive job requiring many people.
• cutler 6y ago
  One thing not mentioned often enough about SPAs is how complicated they make simple operations. In this component - https://gist.github.com/polydevuk/96d89642f114707b2f1a0cc3161339b7 https://gist.github.com/polydevuk/96d89642f114707b2f1a0cc316... - I have a select box for tzdata Regions (Europe, America etc.) and when a region is selected it populates a Locations menu beneath it (London, Paris etc.). Simple in jQuery or pure JS. In React, however, once a region and location has been chosen it caches some kind of hidden index value for the selected option such that a subsequent region choice (without a page refresh) selects the item in the new Locations menu with the same hidden index value as the previous selection instead of the default header option. What was initially simple HTML + minimal JS becomes a complex attempt to manipulate React-specific magic. Using react-form? Fine .... until you need to mix it with react-select or material-ui then you're in for a world of pain deciding how to mix controlled and uncontrolled components. Add Redux into the mix and you're adding orders of magnitude more complexity. Frankly, I don't have the time. I would much rather be using that time to add features to my Rails back-end and spend time with my family. Back in the late 1990s and early 2000s CSS browser compatibility and DHTML was the big time-sink. Now it's SPAs. Back then we dreamt of a day when web standards were fully supported. Today that dream is a reality but you wouldn't know it because we've just made everything even more complex. The only development which I can see saving us from this mess is Stimulus/Hotwire from the Rails team and implemented in other frameworks such as Djano, Laravel and Phoenix.
  • codethief 6y ago
    It took me a while to understand your React example (or at least I hope I get it now). But I don't know… I agree that React has some pitfalls and lots of people don't get it right (especially forms!) but there are ways (clean ways, in fact) to solve this. It's not React's fault, though. Handling complicated state has always been hard and it's not exactly easier in jQuery or pure JS.
    • cutler 6y ago
      But in this case, which isn't atypical, it WAS easier in jQuery. Much easier. I had it working fine with jQuery but wanted to see if I could make it work with React. Here's the full component: https://gist.github.com/polydevuk/96d89642f114707b2f1a0cc3161339b7 https://gist.github.com/polydevuk/96d89642f114707b2f1a0cc316...
• Havoc 6y ago
  I mean the code / tech isn’t the issue really. A newsletter pop up a cookie banner an Adblock warning and inline flashing ads later you can’t even see the website. Experience sucks but that’s not due to bad tools
• raspasov 6y ago
  Avoid any flavor of 'the sky is falling'.
• santa_boy 6y ago
  As someone with very limited resources I keep looking for cookbooks to do UI/UX tasks. Any actionable checklist of these "basic rules of navigation and usability". Sorry the basic question.
• gameswithgo 6y ago
  At a fundamental level the "web" has the following core engineering flaws: 1. it is standard to send json from server to client, a format that takes up more space on the wire, and takes more cpu power to serialize and deserialize than various binary options, all because nobody can be bothered to build tooling around debugging a binary format on the wire and a serialization library that is efficient into the browser 2. We require two separate text markup languages to define a ui (html and css) rather than compiling that down to an efficient binary format 3. We rely on a dynamic language built in 9 days to write client side code, rather than a byte code that any language could target and choose to be dynamic or not as the domain demands (wasm may one day finally change this) Then rather than a trend of fixing these problems, we instead let these problems spread, as electron brought the html+css+javascript model to desktop apps, nodejs brought javascript to the server so you could use one language for your web app, and on and on. There is hope though, wasm at the forefront. Today only non garbage collected languages are viable for wasm without adding the overhead of downloading a large runtime, but that is an engineering problem that could be solved. There are so many trivial inefficiencies that can be trimmed away. But perhaps the biggest obstacle to a nice web experience is intentionally user hostile design. The modal popups, the cookie warnings. These waste more time than parsing and fat downloads for most of us. I'm not sure how to solve that problem. People give you blank stares when you complain about it.
• andrewsouthpaw 6y ago
  I usually read toxic undertones of gatekeeping in tirades like these. "Real engineers like me wouldn't produce such garbage, and frontend engineers aren't real engineers because they learn and like this stuff."
• flippinburgers 6y ago
  The real pain points: - react programmers who solve every "problem" by pulling in yet another 3rd party dependency - understanding react vs react with hooks + to redux (or not) + saga? thunks? etc etc... - webpack
• atoav 6y ago
  If your thing is considerably worse than any (handwritten) HTML page, maybe you are doing it wrong? Well written HTML even without CSS is fast and accessible and this should be your baseline. Modern CSS is extremely powerful and you can get good looking websites with just handwritten CSS. If you change your site once a week instead of uaing a CMS maybe consider using a static site generator like Lektor (fast, no need to worry about people hacking your wordpress instances). If you really need server side code/interaction reduce dependecies and still let HTML do the heavy lifting. I did some experiments with WASM and Rust and it is really neat, but IMO it doesn't beat the simplicity of a basic HTML page yet.
• prince005 6y ago
  I think the bigger reason here is that devs jump directly into Frameworks rather than understanding the basics of web development itself.
• wilde 6y ago
  Don’t worry, you can make a server rendered site slow too. It’s not the tech, it’s that “good enough” is measured in seconds for human willingness to wait.
• kitsune_ 6y ago
  I have around 25 years of web development experience and I'd also put some of the blame on PMs and growth hackers who want to build rich UI experiences where often a simple site would suffice. Add UX people with limited knowledge of HTML and CSS, or backend engineers who only want to build APIs. All the trackers and auto playing videos do not help either. Ah well...
• hcarvalhoalves 6y ago
  Big web companies killed open protocols (remember reading news via RSS?) in favor of exploiting and evolving web technologies as a way to push effectively proprietary UIs with spyware builtin. The whole web was based on the premise server (media provider) and client (media consumer) could be created by different parties and should therefore assume nothing and rely on protocols - that’s not what happens today since with JavaScript the same party effectively “takes over control” of the user agent. My radical opinion is that open protocol based web was killed the moment JavaScript adoption became standard, the same way an open web wouldn’t be possible with Macromedia Flash becoming a standard.
• foofoo4u 6y ago
  I believe a part of this is due to a pipeline issue. I wanted to become a web developer about seven years ago. I decided to read articles, watch videos, and attend some online courses to learn all about it. I even decided to join local developer sessions to see what the community is actively engaged in. Not once did I ever see or hear about developing a website as a traditional multi-page site (MPA). Literally everything was about SPAs. React, webpack, etc. Naturally, I wanted to ensure I was learning employable skills. I didn't want to learn how to make MPAs when that methodology is soon to be obsolete and going away like the dodo bird — or so I thought. Sadly, I think many new devs are like me. They follow an online tutorial and learn how great a framework like Django is. But the tutorial guides them into serving the site as an SPA, completely ignoring the fact that Django has a highly practical and powerful built-in template system that makes web development easy for most use cases! This has left an impression on me that this community has a "shiny object" problem. We throw away perfectly good tools and methodologies for the next great thing without thoroughly thinking through the use case to see if the increased complexity is justifiable. There is nothing wrong with SPAs. It's just that they have become the hammer and nail problem. Not every website should be an SPA. Just like how every website shouldn't be a MPA.
• XCSme 6y ago
  Some people create poor websites, others create great ones. I personally love all the Dutch public websites, they have great UI/UX and are fast. For example: https://coronadashboard.government.nl/landelijk/vaccinaties https://coronadashboard.government.nl/landelijk/vaccinaties
• ajani 6y ago
  Yes, just as cooking has failed. With so many recipe books how can you have bad cooks?! Just as architecture has failed. Just look at those buildings! Art has failed! What happened?! Where are the Michelangelos? The Leonardos? The Picassos? There are many more people writing code now. History will only remember the greats, and forget the rest. There were always websites that loaded poorly. Even "back then". And there were good ones too. Same as today.
• MakKG 6y ago
  Hi all! We are a team of researchers working on a new digital product. We are calling for Front-End and Full-Stack Developers with fluent speaking English to participate in our study. If you are interested please fill out and submit a short screening form by following this link: https://forms.gle/1BJhD7jjtNtKNn6M9 https://forms.gle/1BJhD7jjtNtKNn6M9 For the selected participants, you can expect a ~30 minutes long interview next week at your availability. As a reward for your time, we will be giving away $100 Amazon gift card upon interview completion.