14 ms·
I don't care how you web dev; I just need more better web apps
- pier25 4y ago> Icelanders also tend to be blind to rank in conversation which regularly leads to accusations that we’re being disrespectful. Non native English speaker here... What does "blind to rank in" mean?
- grzm 4y agoParse error: blind to rank in conversations Meaning ignoring class/hierarchy when speaking with others
- pier25 4y agoLOL thanks for the clarification
- accrual 4y agoI occasionally work with a guy who opens every email with "Hey <person>" regardless of who it is and it always struck me as informal. I wonder if it's a similar rank-blindness in conversations.
- ajkjk 4y agoAmericans increasingly do that all the time. It's super weird as a (relatively) young American to treat anybody differently from anybody else.
- ytdytvhxgydvhh 4y agoI feel like in the American workplace we’re expected to be casual and friendly with everyone while also being acutely aware of rank. So if your boss sends a silly meme, you might want to reply with another silly meme. But if you go over your boss’s head and send an unsolicited “hey <first name of the boss’s boss>” email, you might still be in for repercussions. Just because everyone is on a first name basis and drinks beer together at happy hour doesn’t mean they’re really on equal footing.
- octodog 4y agoHow are you supposed to address your boss's boss?
- n4bz0r 4y agoI suppose the point is that you aren't. You talk to your immediate superior instead. And then your boss does the same if he/she decides there is a talk to talk.
- jackson1442 4y agoI think some places still expect you to use their honorific prefix and address them by their last name. Definitely a dying trend though.
- syradar 4y agoSwede here, it’s really prevalent in Sweden to just use first names irrespective of who it is. Your boss, boss’s boss, your doctor, or as the case of an athlete winning an Olympic medal: even the prime minister, even calling her a nickname[1]. I believe it is partly due to a reform back in the days dropping thou and titles[2]. 1. https://www.aftonbladet.se/sportbladet/a/Bj4Lkg/os-2022-nils-van-der-poels-roliga-svar-till-statsminister-magdalena-andersson https://www.aftonbladet.se/sportbladet/a/Bj4Lkg/os-2022-nils... (Swedish) 2. https://en.m.wikipedia.org/wiki/Du-reformen https://en.m.wikipedia.org/wiki/Du-reformen
- conartist 4y agoTotally agree we should be talking about great web and native experiences rather than the tech that sits under them. Whenever I see people arguing about frameworks I think of the midwit meme where the opposite ends just use what they know.
- nomdep 4y agoArguing about framework is people talking about great developer experience
- 0xb0565e487 4y agoOne thing I've noticed is that almost all new web frameworks I come across nowadays seems to be catered towards search engine optimization (i.e.: getting 99/100 on Google PageSpeed Insights).
- hoten 4y agoAre you confusing SEO with performance? Lighthouse does have a SEO category but it isn't exposed through the PSI web app.
- httpsterio 4y agoGoogle uses (or at least used to use) page speed results as one of the ranking factors for their SERP .
- synicalx 4y agoAFAIK they still use it, and it plays a huge role (based on my fairly limited experience). A couple months back I did a little consulting on the side with a small ecommerce store that had recently struggled to get any traffic despite all their SEO analytics showing green except for page speed. They ranked poorly for just about every keyword that they had previous been doing well on. Bit of CDN/Caching, upped them to a better hosting plan and they're back on track again - rankings are back to normal and page speed is way up.
- Nowado 4y agoA separate signal is user leaving SERP, going back to it and checking another site - somewhat clear sign of failure of a site to deliver. And users leave if your page loads slowly.
- dgb23 4y agoIt's a very specific kind of performance. It doesn't measure long running apps, interactions and visualizations. When you play a video game you might have to download and install it first, which might take quite a while, but we don't say "this game has bad performance" because of that. Lighthouse measures that first second or first few seconds after you visit a site at position 0/0. It doesn't care about how much bloat comes after you scroll. It discourages you to pre-load resources (including JS and CSS) which you don't _immediately_ need for that first hit. It is really about content and marketing websites with low interaction. You can absolutely make good interactive applications that also get a high Lighthouse score, but the overlap is not necessarily always feasible or the best tradeoff to make.
- altdataseller 4y agoHow does the OP define “good” web apps? Apps that are pleasant to use? Apps that solve a problem?
- pketh 4y agopleasant/enjoyable to use was my interpretation, which I think is a sufficiently high bar that few websites (and native apps for that matter) meet
- layer8 4y agoMy take would be: Apps that do the job they’re supposed to do in service of the user, without friction for the user. The pleasantness for the user doesn’t come from the app proper, it comes from the user being able to achieve what they want without friction. It’s a bit like what is often said about film music: The best is the one you don’t notice is there.
- blitz_skull 4y agoSure, I’ll bite: LunchMoney.app
- pketh 4y agorelevant but also self-promo: I build https://kinopio.club https://kinopio.club a spatial thinking tool that's also (I hope) a good website. I'm only one person without the resources to build separate ios/android apps so the website needs to work everywhere and be fast and responsive
- typeofhuman 4y agoThe animations are causing me distress. They're jittery as opposed to bouncy.
- pketh 4y agoWhich animations? I def would want to fix/tweak that
- Hammershaft 4y agoThe ghost logo anchored to the top left jitters when flicking/scrolling using a mobile phone. Otherwise it's an awesome site, the wii shop remix still puts a grin on my face
- pketh 4y agoThe header and footer, including the logo hide on mobile during scroll because mobile safari doesn’t send enough info to position them accurately during flicks. Are you seeing flickering on iOS or android?
- Hammershaft 4y agoAndroid using firefox, so I may be a serious outlier.
- pketh 4y agoAhh that makes sense, android has some known issues that I want to resolve this month so I’ll add these to the list - thanks! (tracking in https://club.kinopio.club/t/bugs-on-android/346/13 https://club.kinopio.club/t/bugs-on-android/346/13)
- rejor121 4y agoThe title is confusing. Do we need much better apps? Or more, better apps? “More better” is such a mind fuck
- deleted 4y ago[deleted]
- dpcan 4y agoMore betterest.
- colinsane 4y agoi think it’s right associative. the author wants good apps to use as examples (and since he’s comparing these against an assumed default, ”good” really means “better” here). the author can’t find many of these better apps, so he’s requesting more of them: more better apps. i admit it’s confusing to have in the headline (easier to make sense of after he’s covered the background), but the language is sort of constraining in this area. he probably wanted to avoid “more good apps” as that would be mistaken for “better apps” (which isn’t exactly what he’s after). “more better apps” is less ambiguous, but only so long as you expect that the author isn’t one to intentionally misuse language.
- Agamus 4y agoI assumed it was a reference to the slang movie title "Mo Better Blues".
- jasonpbecker 4y agoJust an observation: the native apps that are better are built on massive, proprietary frameworks developed by platform owners. In some ways, most of the web frameworks are trying to be the One True Web Platform Framework that similarly makes it possible for developers to make better web apps the way that say, AppKit or UIKit makes that possible on Apple's platforms. So I'm left wondering, did the frameworks fail or did the web developer community fail?
- rektide 4y agoThe new breed of try-hard build-big "final"-framework would-be's plays against what the web is, trades incrementalism stengths for probably-not-all-that totalization. trying to decide & pick the one true platform, giving up the more malleable low level platform is the problem, is what the closed-world expectations have ruined the web's great prospects with.
- layer8 4y agoUntil or unless something equivalent to those platform frameworks becomes part of the browser, the situation won’t change significantly. The fact is that the current interface between web app and browser, that is, HTML, CSS, and JavaScript (and WASM), is highly inadequate for productivity applications.
- noahtallen 4y agoI think “highly inadequate” is a big exaggeration. As an example, many people are fairly productive on slack. (Arguably more productive than email.) Native slack is nearly equivalent to web. Another example is google sheets or google docs. I do agree native had some big benefits. Probably the biggest hindrance to web is that you’re basically downloading the binary from the server and then executing it in line. That leads to a ton of performance optimizations (like optimizing bundle size or async loading things) which make things fairly complicated (webpack) and can also lead to UX compromises. None of which is a problem for native apps.
- ratww 4y ago
- quickthrower2 4y agoI think the article needs to kick off with examples of less better web apps, otherwise I am a bit confused a out what is wrong and what he wants us to fix instead of bikeshedding frameworks.
- omarhaneef 4y agoThe author complains that developers argue about their tools and methods, insist on their favorite techniques, but produce (more) worse apps. Particularly for the amount of time and effort expended on developing the apps. The thing is: the debates aren’t naive. They’re exactly trying to workout the details. When someone says, hey forget postgresql and just use SQLite, and someone else says good luck if you hit n rows, and someone says it can easily handle n+m rows with x memory … Well they’re trying to solve the problem of (more) better apps with their limited resources. That’s essentially the problem of development. Asking people to solve development without discussing the tools and methods is to misunderstand the nature of the discussion. It’s like telling authors to get on and write better novels and not waste time with their opinions on character and plot.
- sidlls 4y agoThe problem of which DB to use is one that can be figured out ahead of time with even modest attention to more rigorous engineering practice. But that’s not what webdevs the subject of this article do. They play guess-and-check games like they are 15th century engineers building a bridge, because they have hacker mentalities instead of engineer mentalities. Not to mention the cult of celebrity and fad following in the industry.
- dasil003 4y agoThe analogies to civil engineering are strained. Sure there is some truth to what you are saying, but also requirements for civil engineering projects tend to be more easily stated at a high level and are depending on the unchanging and unforgiving laws of physics plus some slowly growing list of available materials and construction processes. Everyone understands intuitively that bridges are expensive and you can't just change requirements on a whim without potentially blowing up the whole project and starting over. Software on the other hand can be made to do anything, we can change it any time, and the technical requirements for scale and functionality are hard to predict ahead of time. Trying to apply civil engineering mentality to software results in a process that is too slow and gets beaten by hacker mentality every time.
- aranchelk 4y ago> Everybody seems to have an opinion on how you do your web dev and how websites and web apps should be structured. It’s true and it leads to many annoying unproductive arguments, IMO the reason is a fundamental lack of a scientific mindset in evaluating techniques and tooling. We don’t have theories or testable hypotheses, we have opinions. On one level I like and agree with the author’s idea that results are what really matter. As an engineer trying to achieve outcomes for employers, clients, and customers, this approach has served me well. As a community of professionals, it would be nice to see more effort to work towards rigorously proven conclusions about what works best and why. When someone touts a paradigm, technique, or framework as the best, without any real data or theory as to why, I think they should be told to provide evidence or withdraw their argument, and I’d say that goes double when it’s the framework or technique you like or use. IMO, these shouldn’t be fights about tech, they should be ones about quality of discourse.
- deleted 4y ago[deleted]
- patrick451 4y agoIt's shocking to me how little data there seems to be to support what many consider to be "best practice". About the only real data point I see thrown around is that bugs per LOC being fairly constant. Thus, you get people saying long, two-page functions are bad and should be broken up. But never have I seen someone backup such an exhortation with data. Let alone more nebulous rules like "objects should be open for extension and closed for modification," or anything out SOLID, really.
- lawgimenez 4y agoI'm a little confused on the article. I remember developing web apps where I could just start a LAMP on my machine but times have changed and we should accept that everything is getting complicated. He should try mobile development, it's much more worse in my opinion. I'm a mobile dev fyi.
- cmroanirgo 4y agoAgree. At this point I'm a little bewildered at what iOS and Android has brought to mobile development that wasn't already in j2me, at least in a preliminary way. At the start of iOS it was "look, pretty icons" and "no more permission popups". But, most platforms had icons anyway, and all the apps now get the annoying popups for the same set of permissions (except for networking) that was the bug bear of j2me (at the time). iOS and Android got rid of all the permission boxes for a better UX. So, we're left with the expectation of a seamless web. But it never occurs because of endless permission issues, of which the platforms try to reduce by providing a one-size-fits-all cloud solution (iCloud and Google), both of which allow relentless advertising & gamification of our personal information. It's so bad that governments all over are racing toward digital "identities". I'll take the simplicity of j2me any day thankyou. The development environment was GBs smaller and faster and the problem set is pretty much the same. At least with j2me there was the idea of responsibility to data usage (I generally only get 3G, even now) as opposed to 40MB apps that download 100's more. All the apps I developed during that time were offline first and synced when available. The real complexity I see is in the consumption of video and hi res images as well as the interaction with other apps (eg share menu). Unless I'm seriously mistaken, everything else was in j2me (even opengl). All the other complexity is in the tools we have these days & endless rhetoric on which ungainly monster is better than the next.
- lawgimenez 4y agoThis is true, I started with Java ME too with Eclipse IDE then proceeded to integrating Blackberry SDK and then it started from there. Mobile development's phase right Blackberry disappeared never recovered, it went 0 to 100 real quick from that very moment. I was still hacking some J2ME for a Nokia app then Samsung released an Android phone and I was like wtf is an Android.
- travisgriggs 4y ago> They keep encountering highly flawed websites or web apps and are assuming that regular web devs can do something about it. This is the reality that has been grinding me down of late. Nor do I find it limited to only web stuff. I see it in embedded and other market areas. I was excited over the last few decades to see the field of programmers swell. I have always loved the craft of good software development. I was so excited to see so many others also get into it and naively believed that many more people participating would lead to a larger pool of ideas to draw from and everyone would get on board in some sort of utopian democratic industry wide kumbaya. During the rise of open source, I even felt it was really happening. I now believe I was wrong.
- jdougan 4y agoIf the dev pool of 2022 was like the dev pool of (for example) 1994, just larger, you would have been right. But the software goldrush came and attracted many more who were just in it for the money or just weren't as thoughtful. Scale matters, upscaling people is hard.
- iratewizard 4y agoI've got a strong suspicion that there would be more productivity if the bottom half of developer (or more) left the industry. Control for seniority, of course. The majority of 1Xers produce outright bad code, contribute disproportionately to tech debt, don't read user stories thoroughly, don't test their code properly, and generally get in everyone else's way. The most productive thing our industry could do is create an anonymous blacklist of devs to avoid and code samples of their shit work.
- notpachet 4y ago> anonymous blacklist of devs to avoid and code samples of their shit work. Sounds like Github Copilot.
- blacksmith_tb 4y ago
- melony 4y agoI love web dev because the community is willing to address problems; engineering follows product in a tight feedback loop. Developer experience becomes a target to optimize for, and not just the overall ROI. In almost every other CS/software field save for machine learning, reinventing the wheel is a privilege reserved for large corporations. If you ever worked in the embedded space (or talked to engineers who did) or even a non-IT industry, it is obvious that many fundamental protocols and technologies never changed since the days "their grandpappy did it". Web may move fast but the UX is constantly improving and the value delivered is increasing every day; there is a very good reason why people from almost every other industry is trying to get into software engineering. Even if you don't like the current JS stack, there is nothing stopping you from pulling a Figma and building everything from scratch in WebAssembly, after all, game developers (before Unity) do it all the time. Show me a burnt-out web developer and I will show you ten hardware/mechanical/electronic engineers who would give their arms and legs for the ease of tooling and the large salary of web devs. You are being paid 6-7 figures to debug a bunch of UI code in a high level scripting language, and your biggest complaint is that the churn is too bad?
- rootusrootus 4y agoWhy are tech choices having such an impact on the experience to begin with? Aside from small apps, the web developer is just the guy making the magic happen, there should be an actual product owner somewhere who is making decisions on experience. It's up to the devs to make the experience happen, but poor design is a different problem than what framework you wrote the code in.
- exodust 4y ago> who is making decisions on experience Product Owner: "Let's remove the Save button and instead simply save every time the user changes the value". Developer: "No".
- ratww 4y agoI wish. Compared to 10 or 20 years ago developers have a lot less say in these things. 10 years ago I would be able to block some megalomaniac plan from an UI/UX designer outright. Today it is borderline impossible, as designers tend to have 10x more power than before and don't really care about feedback from developers. Everything is done on a "Parallel Track" sprint, also known as "Waterfall", since designers can't really do Agile. So development teams get a bundle of tasks that's a black box until you open up and there's all kinds of custom shit copied from products from trillion-dollar companies, done by teams of hundreds or thousands. Honestly having to work like this makes me consider leaving this industry.
- sanitycheck 4y ago...followed by a 1 hour debate on slack and a series of meetings with an ever increasing number of non-technical managers before a likely unsuccessful outcome. Arguably worth trying anyway, but let's say I want to say "No" to 3 of these new misfeatures per week. Do I still have time to do any work? Probably not. So I'll pick my battles.
- carapace 4y agoWeb dev is solved: Elm. Just use Elm. https://elm-lang.org/ https://elm-lang.org/ Javascript is going to be more expensive and more hassle to use than Elm for 99.999% of web apps.
- mkl 4y agoI don't think so. The webpage of this language that "solves" web dev is so spectacularly broken that it managed to crash Chrome for me completely. I have literally thousands of tabs open and it trucks along fine for weeks on end ... unless one of the tabs is elm-lang.org. 15 minutes later and every Chrome window and tab was still unresponsive, so I resorted to killing the process, then quickly closed that tab before it fully loaded on restart. Maybe it works for you? That's kind of even worse as it's not even consistent.
- carapace 4y agoOof, yeah, that's bad. But I doubt it could be very common or they would have noticed it and fixed it, eh? Would you consider telling them about the issue? I realize that might be hard since their "community" links are on the bottom of the page that kills your browser, but no doubt they'd really appreciate hearing about it. In any event, one regression (however painful) for one user doesn't invalidate the whole idea of Elm. It's still the right way to go even if it blows a tire from time to time. Interestingly there is at least one effort to write an Elm-to-native compiler, so your Elm "web" app could also be compiled to native code & GUIs.
- loh 4y agoI was just thinking about this exact topic less than an hour ago. We seem to be slowly reaching a consensus on various best practices and tools, and it's obvious which ones are winners and will be here to stay for the foreseeable future, despite the inevitable churn. There will always be discussion (and disagreements) on how to make things better, and when I was less experienced, I (ironically) used to be way more opinionated on the best approaches, but over time, after witnessing the evolution over the years, it always comes down to one core tenet: choose the best tool for the job. Even this isn't purely objective, as it can vary depending on your individual circumstances, time constraints, and the people (and their skillsets) available to do the work. I've always imagined a future where almost anyone can quickly assemble high quality applications (both software and hardware) to meet almost any human need. We're seeing this trend with all of the low-code/no-code tools popping up, but to take it up a notch, it will probably require some standardization of tooling and practices. I think this is the next phase of our technological evolution and would be a great solution to the author's request for "more better web apps".
- jillesvangurp 4y agoI think the author's points are very valid. Despite the continuous debate and ever shifting landscape of what is fashionable in web development (which I find very tiresome to keep track off), most web apps pale in comparison to native apps. Why is that? Whatever it is, it seems elusive for web developers to come close in quality and experience. And they seem stuck in endless iterations of "maybe this will work ... nope". And of course with web assembly, you can actually replicate a lot of that native experience in a browser and even run very slick 3D games or emulators running entire desktop operating systems. So, it's not necessarily true that browsers are not technically able to do a better job because they clearly are. It's just that web developers and web developer tool makers are just not doing a great job leveraging those capabilities judging from most popular web apps. My personal observation as somebody who focuses on backend mostly but also needs to worry about having a decent frontend for that backend is that we are being limited by an industry that is perpetually suffering from maturity issues. Both at the technical and personal level (I agree with the author on this). A lot of the technologies and tools are simply not great when compared to native app tooling and they only compare to each other. So, you get these elm, angular, vue, react, etc. proponents each arguing how their preferred thing is better than the other thing and why. What they should be debating is the huge gap with native apps that none of them come close to bridging and why that gap fundamentally is still a thing in 2022. Why do people have to reinvent so many wheels to build a simple web app? And why is delivering a slick web app experience such an elusive goal? The future is 25 years ago when any idiot with an MBA could open up Visual Basic, Delphi or whatever and click together a working native app in an hour or so. A lot of really bad enterprise software was created that way. But nothing similarly usable ever really got popular for the web and I'd argue using most enterprise web apps is a similarly dreary and miserable experience as it was a quarter of a century ago. It's gotten harder to build those but they still suck. Mobile developers have had visual UI tools like that available all along even though many would prefer not using those. But in terms of the underlying component frameworks, mobile development is a lot more similar to how Delphi and VB worked 25 years ago than modern react development. IMHO, those component frameworks are a key reason people like the "native" experience. The web based equivalent component frameworks (there are many) are just a lot hackier, messier and ux challenged. Ironically, with Blazor, you can target the web and get your good old VB code to run in a browser. Not sure if that's the future but it sure seems to work. Again, the problem is not browser limitations but tools. If MS can target browsers with their decades old tools, web developers can raise the ambition level a lot more as well. Why don't they? Apple and Google have a stake in the current status quo of the web sucking more than their mobile walled gardens. So don't look to them for answers.
- noduerme 4y agoc'mon. the only way to build a coherent web app these days is to hire one coder freelance, then work him daily for 15 years into an early grave. Then build version 2.0.
- mb7733 4y ago>I’m hard-pressed to name more than a handful of web apps that I would say are genuinely good with no major flaw. >Content websites are a different matter. A static or server-rendered content website with adequate typography and semantic markup is generally going to do its job pretty well. I feel the exact opposite. Most web-based applications are pretty incredible these days. It's the "content websites" that are insanely bloated and over engineered (and unnecessarily turned into "apps"). E.g. news sites, new reddit, recipe sites
- kitsune_ 4y agoAgreed. Most web apps are perfectly fine and can be phenomenal, especially when compared to what we all did back in the 90's on GeoCitites. And as you rightly point out, visit a recipe site, especially on mobile, in comparison.
- deergomoo 4y agoIt’s so bad now that an ad-blocker is rarely sufficient, because even without the ads every other paragraph is broken up by some autoplaying video or some callout to a different article. In some cases I genuinely struggle to read an article without reader mode or an RSS reader that can scrape the full article.
- unsupp0rted 4y agoIt's been years since I tried to read an article without reader mode. Reader mode is fast enough and accurate enough now that there's no need to bother not using it.
- honkdaddy 4y agoAirtable, Draw.io, Google Docs, and Photopea are all incredibly well-made web apps that are essentially complete products without any major flaws I can think of. Those were just the first four to come to mind, there are countless countless other wonderfully engineered full featured applications which run totally in your browser. It’s actually a bit of a marvel, when you think about it. There are great web apps and there are great native apps. I think what the author is asking for here is just “better software” and well, wouldn’t we all love that :)
- EnKopVand 4y agoI think the bad “web” has a lot more to do with the business side of things than whatever development tools you use. If the website is free to use, it’s either a passion or community project or it sells you. Sometimes that works out sort of well in places like HN, and other times it works out less well like on the infinite amount of shitty news papers. But those news papers can be shitty in all technologies even in the physically printed form. I do think we need a better tool for finding the passion projects. Because search engines have basically become the “portals” they replaced by curating search results into being about herding us toward sales, but I’m sure we’ll see a shift sooner or later. It’s sort of already happening with more and more people returning to things like news letters instead of reading blogs.
- tuxie_ 4y ago> I do think we need a better tool for finding the passion projects I like the idea! I wonder though how that would look like. How do you imagine such a tool? Would it be something like a "directory" from back in the 90s where people submit their link under a specific category?
- aabbcc1241 4y agoIt may be similar to ShowHN? Probably easier to search and discover.
- divan 4y agoWeb dev community should just acknowledge the simple fact that typesetting engine from 80s (HTML) and legacy hacks built around it (css and js) is not a good foundation for making modern apps. It's like trying to build apps with a spreadsheet cells (it's actually possible, but we don't do it, thankfully) by throwing a lot of abstractions and frameworks on top of it that would hide the ugliness of the foundation layer. Once this acknowledged, thing can start moving fast. A lot of good stuff has been developed and discovered in the web dev community, but the foundation of it is total and complete crap. Also I believe we are in the good moment of time to build a better web, as there's virtually one major player in browser engines market and it's easier to experiement with adding support for new foundation layers (think wasm or dart vm). But so far, no matter how much hacks web community can come up with, web apps will be predominantly associated with horrible experience, performance and quality.
- gen_greyface 4y agohttps://www.photopea.com/ https://www.photopea.com/ this is a webapp
- divan 4y agohttps://www.gamedeveloper.com/design/3d-engine-entirely-made-of-ms-excel-formulae-enjoy-this-doom-xls-file- https://www.gamedeveloper.com/design/3d-engine-entirely-made... this is Doom engine in Excel
- gen_greyface 4y agodifference being its an esoteric experiment. and that webapp is used regularly used by thousands. naive of you to even compare both.
- divan 4y agoNo ad hominem please. Both examples are cool apps built with the foundation layer not designed for the task. - text markup language isn't a good choice for modern performant graphics editing apps. - excel sheet isn't a good choice for 3d game engine. The difference here lays only in the fact that for Doom 3D engine, authors had another choice.
- myrryr 4y agoDoesn't want to talk frameworks, but has this as a problem.... "The problem is that doing a Single-Page-App ‘properly’ is even more expensive than doing a mediocre Single-Page-App, which in turn is considerably more expensive than an old-style multi-page web service. If a lack of resources is the limiting factor for the project, any suggestion that involves more work or more resources makes the problem worse." The point about the frameworks is that having single page, and multi page apps done properly isn't more expensive than even static stuff. It looks like they have created their own problems here.
- dusted 4y agoI don't care how you web dev; I just need more better native apps.
- Gareth321 4y agoI hate web apps with a passion. Has anyone ever used the iOS YouTube app? This thing is hailed as a marvelous examples of web apps working "like native." Bollocks. It's an absolute mess. If one of the wealthiest companies in the world can't build a decent web app, there is no hope for anyone else. Web apps get the user 80% of what they want with 50% of the cost, so the business case is clear. That's why these apps are proliferating. They are not proliferating because they're good, as good, or better. They're just not.
- biztos 4y agoThe trillion-dollar company is often less able to produce quality products than a small shop, because of bureaucracy and hubris and dead weight. So while I agree that the business case for web apps incentivizes mediocrity, there is still plenty of hope for everyone else. If your startup has a really great web app with awesome UX, you will have a pretty big advantage.
- ratww 4y agoTrue, but not so fast: small shops are also constantly trying to copy the bureaucracy, the hubris and dead weight. Eventually I expect all of them to get there.
- julianbuse 4y agoBy web app, I believe the author meant apps served in a browser, not a mobile app made from html/css/js with a cordova/capacitorjs wrapper. Also, google has problems delivering functionality in general. Have you tried using google home? It never works properly for me, and for some reason I can't log in to my family's home with my google workspaces account. Most things except for search are a mess there, and search is getting worse as well.
- plaff 4y agoI think it's because most apps are influenced way too much by "standards" that people expect but actually sucks. I have 2 examples of web apps working really fucking well: Missive (https://missiveapp.com/ https://missiveapp.com/) is an email client web app with features that should be standard in every other email client. I run it via Firefox and it's the best damn email client I've ever used. It uses JS extensively but they use it very well. Migadu (https://migadu.com/ https://migadu.com/) is the absolute golden standard of email inbox services. It's not fancy but oh my days, does it work and it's so damn easy to use. Every time I have to set up emails I get happy because these guys spent exactly 0 seconds on trying to appeal to people who equates parallax-scrolling with competence. Migadu does not use JS as far as I can tell. As a counterpoint to both, Office 365/Outlook is a gigantic, floppy donkey dick of a web app that makes all sorts of assumptions, has 3 different interfaces and is generally just a pain in the ass to use. Somthing as simple as logging in/out is a muddled, technical mess that makes it a god damned chore to change accounts.
- dom_inic 4y agoThis article could be about 20% as long if you cut out the rambling. You say modern SPAs are terrible but don't provide any examples of what you mean by that. You go on a completely irrelevant rant about Icelandic culture in the middle. But it's a post complaining about how modern web dev sucks, so HN will upvote it anyway! We don't need more talking about what apps are good and what are bad. We need more doing and building (coincidentally what the people actually working in these ecosystems and trying to improve them are engaged in)
- dncornholio 4y agoBecause of the writing, I could not get past the first chapter.
- jmull 4y ago> The problem is that doing a Single-Page-App ‘properly’ is even more expensive than doing a mediocre Single-Page-App, which in turn is considerably more expensive than an old-style multi-page web service. Is that true? Having some experience with both styles, I don’t see a difference in time (after the learning curve for doing something new).
- Existenceblinks 4y agoIf we ended javascript, 3/4 of these crazy disagreement will be gone. And no one will be seen as anti-react / anti-js anymore.
- iamsaitam 4y agoIf we ended the web, there would be no disagreement.
- capableweb 4y agoBetter yet, end the web and the internet and there would be no disagreements at all about anything web related. The only for disagreements you'll have will be with the people in your immediately vicinity. And to solve that, I propose another solution: End all human life, and then we've solved every single problem of the world. No racism, no sexism, no bigotry and no problems for as far as the eye can see.
- krapp 4y agoIf the solution to your problem isn't "kill all humans," you haven't considered it deeply enough.
- Existenceblinks 4y agoYep, I would start at a small inner most of generalization.
- gherkinnn 4y agoI usually like Baldur's writing but this is all over the place. > What we end up with is an industry plagued with cost and time overruns. Projects go way over budget and get delivered much too late, if ever. I was there pre-Angular and pre-React and cost and time overruns were a thing. They always were and always will be. Unsatisfying software is a broad and complex problem and no matter your views, you will find confirmation. Agile coaches will see it in waterfall, Baldur sees it in SPAs, and somebody else will see it in tracking and metrics.