4 ms·
I disagree. Web devs aren't discussing characters and plots but instead argue which typewriter to use. Better tools don't make better apps just like word proc
by croes 4y ago
I disagree.
Web devs aren't discussing characters and plots but instead argue which typewriter to use.
Better tools don't make better apps just like word processors don't make better books.
The best web dev tools are worthless if the UX is bad.
- xwdv 4y agoFrameworks are not tools. You select technologies based on their fit for the requirements of the web app.
- na85 4y agoFrameworks have a direct impact on UX though. How many React monstrosities are snappy and responsive? Certainly none that I've used.
- belenos46 4y agoI can't tell you how many snappy, easy-to-use React sites I've used (I was busy using them, not reviewing their code), but every single time I've said "What the hell is going on, I'm just trying to [simple operation which is the only purpose of the website I'm on]" in the last five or so years, it's some React/Angular/SPAFrankenstein monstrosity.
- moring 4y agoI could say the same about almost every web app that gets rendered on the server because every tiny step of interaction needs a network round-trip.
- croes 4y agoFrameworks are tools
- berkes 4y agoNo. They aren't. Frameworks are the scaffolding, the skeleton. They dictate the shape. It's literally in the name. > : a skeletal, openwork, or structural frame Tools are the things you use to build within that skeleton. More pragmatic: Rails is a framework that dictates an MVC shape, with an RDS, that produces server side rendered HTML or data in a RESTfull manner. The tools you use for Rails development are your IDE, a CI, revision control, a terminal, maybe even the IAAS provider.
- rat9988 4y agoThey are still tools though.
- kitsune_ 4y agoMaybe the word 'tool' is just not adequate and there is no 1 to 1 equivalence here. If you come from woodworking, the saw or drill doesn't end up being part of the table you build whereas the framework code is part of the actual product you build. Or in other words, if you remove the framework after you programmed your solution the solution stops working where as if you remove the drill and put it back into your bag the table still stands. I would argue there is a categorical difference at play here. So maybe words like tool, scaffolding (and even framework) are just not entirely up to the job of describing what a 'software framework' is and ultimately lead to confusion.
- xwdv 4y agoTool is an adequate word, they just need to apply it correctly. Vim is a tool. It’s used for writing code. A framework is not a tool. It is previous work that you build upon so you are not starting from scratch. It is a canvas, already assembled and sized.
- croes 4y agoA framework is a collection of tools to help you building web apps, just like a toolset for building shelves. Your toolset also dictates the shape like a screwdriver dictates the shape of the usable screws.
- Fire-Dragon-DoL 4y agoWhat makes you say that better tools don't make better apps? A screwdriver changes removing a screw task from "extremely hard" to "extremely easy". Same way, a web framework makes writing a secure web server substantially easier than starting from scratch.
- xwolfi 4y agoThis is surprisingly not true, have you tried ? When you start from scratch you realize you have a tiny minuscule surface and securing that very small hole is much easier than say... fixing the log4j 20th level transitive dependency of your giant Spring Framework that was secretly able to interpret random input from logs or someth. Especially if all you wanted was to show a quick html output. It's incredibly common to see giant dynamic web stuff used for tiny static output that could have done without. I've done both in large volume websites and I find now that using as little "framework" as possible and a limited number of "libraries" works better in terms of cost, bugs, dev attrition, business desire implementation and user speed of render. Picture a giant mess of node dependencies surrounding a central giant quirky framework like VueJS. 5 years of dev, all devs left. You need to maintain that, is that going to be easy ? Wasn't for me.
- claytongulick 4y agoI'm living this right now. It's why when I have greenfield I do vanilla web components, with a little lit-html sprinkled in for fast rendering. I've seen so many developers complain about how complex vanilla web components are, and they'll turn around and do React / Vue / Angular and Redux or (shudder) rxjs, etc... I just don't get it. Like, if you need reactivity... Stick a render call into the setter of a plain old property. If you don't, use a variable. The whole computed() thing with Vue makes things so complex... I have to deal with a huge rabbit hole of that stuff all the time. I think to myself... I could just use a property, and I wouldn't need a whole painful build step, type definitions, framework version specific DSLs, massive complex source maps that don't work, Rube Goldberg state machines, crazy pseudo DOM elements that aren't really DOM elements, unless they are, or a ref to something magic that might end up being a DOM element someday, obscure dependency injection cruft that's done way better by just using dynamic imports... I remember when I couldn't wait for Proxy to be widely supported by browsers. Now I'd do anything to be able to shove that toothpaste back into the tube. I don't know. I don't see any of this providing any value. I feel like the emperor has no clothes, but everyone else thinks he's wearing Armani.
- taeric 4y agoWeb devs are typically arguing which produced assembly is better. Granted, we have come a long way, as the typical react site gave up on terse html a long time ago. But, consider, dream weaver and early design tools were ridiculously advanced compared to what most of us are creating in web sites. Flash tooling was a whole other level.
- ketzo 4y agoThis is assuming that software quality is purely a function of the software engineer’s mind and creative ability, almost like art or writing. Many - most? - software devs know multiple ways they could make their apps higher quality, but they just don’t have the time or ability right now, or they have other priorities, or so on. Better tools can, and do, enable engineers to simply do more than they otherwise could, and sometimes “more” actually does mean “better.”
- dusted 4y agoYou're making another important point.. Native have had fairly good tools for making GUIs, since like.. what.. 1991 ? Simple nice tools where you define your windows and drag the widgets onto them where you want them to be.. then hook up code to it... Web.. it's still stuck in the 80's in all the worst ways.. using a f*cking typewriter to define your UI.
- BlargMcLarg 4y agoWouldn't be as bad if making a GUI in a webapp was more intuitive to begin with. But CSS and HTML have a decent number of unintuitive quirks you need to experience and mess around with before it 'makes sense'. Then the best most can do is two views (mobile and desktop) which adapt to some various widths in an obvious way, using loads of whitespace as a solution.
- pzo 4y agoLife got more complicated since introduction of smartphones and tablets - it's probably order of magnitude harder to do decent mobile app than desktop one: 1) you have smaller screen estate and have to split some forms into multiple page wizards ( on desktop if you lack space you just popup yet another window wherever it popups) 2) you have to support different screen orientations (portrait, landscape) 3) you have to support corners cases like notch or foldable screens 4) you have to support different screen sizes and different screen aspect ratio (on desktop still many apps don't allow resizing and its ok) 5) you don't have precision input such as mouse where you can hover on some small button and see via tooltip what it does. 6) you don't have physical keyboard instead a virtual keyboard that on appear eats almost half of your already screen estate and covers other form controls. 7) mobile OS make limitation what you can do in the background, how much memory you can use 8) mobile OS don't allow just dragging windows and resizing, and switching windows easily using native UI
- dusted 4y agoYes, this puts me solidly in the niche, I couldn't care less about mobile or tablet.. They're fine devices for.. I don't know really, making calls and scrolling facebook.. But for anything with writing involved, or.. input in general.. for any period of time.. I'll never be that hip, and I get that I'm "in the wrong", but that does not change my opinion that what the world needs is more stationary workstations with large desks, multiple large screens and good keyboards and mice. I know it's not how the world works, but I wish, if we could just show "them" how good the programs can be, how efficient the user interfaces can be, how awesome it is to use a real proper computer with real proper computer programs, instead of the toys on tablets... But I know I'm in the wrong.. I know it's "just me" and everyone else enjoys their glass plates. grumpy old man shows himself out
- danjac 4y agoTo a point. I don't need to care whether you wrote your novel on Word or a manual typewriter, by the time it gets to my Kindle or a printed paperback that doesn't matter. On the other hand, if your web app takes forever to load because of a huge React payload or poor server performance, I do care.
- kitsune_ 4y agoThese analogies really only go so far. Let's do the music one: how an instrument feels (to you) is intricately linked with how well you can express yourself musically. I guess there are two different view points here, those who think the things used to create something have no bearing on the essence of the thing that is being created and those who think that you cannot divorce the two. Isn't that just a discussion about platonism in disguise?