3 ms·
It took the best part of a week to make a bit of text a link. This highlights the problem with web dev quite nicely. Not doubt you weren't really just making s
by onion2k 7y ago
It took the best part of a week to make a bit of text a link.
This highlights the problem with web dev quite nicely. Not doubt you weren't really just making some text in to a link. I know the sort of thing bootcamps do, so you were probably installing and learning React, displaying a set of components, implementing React Router, and figuring out how to update app state based on the browser's History API. All with a template library that was a terrible choice for learning (because it didn't have docs). You could summarize that as "making a bit of text a link", but that's glossing over the details.
What you were really doing was learning component orchestration, reactive state management, and a browser API. Why wouldn't that take a week?
So the problem with web dev is actually that it's really, really easy to trivialize. You can make hard things sound like they should be very straightforward because they look a lot like something simple from the past. And when people find that they're not really doing the simple thing any more they complain because the new, harder way of doing something (which is actually doing something completely different eg reactive state management and in-browser routing vs asking the browser to do a GET) is hard.
- dynamite-ready 7y agoAnd there's the problem... "...component orchestration, reactive state management..." Webdev tool makers are sadists, and many of the 'thought leaders' in the field have Stockholm syndrome. Some aspects of web development certainly are hard (security especially). Frontend development however, does not need to be as hard as it currently is. At the very least, I think there's an opportunity to simplify that layer of the stack, and give the control back to design professionals. Dreamweaver to my mind, represented a more productive direction than React currently does.
- reroute1 7y agoSure there's lots of reasons to not use React and many places don't. Bad management/decision making is more to blame in this case than anything.
- onion2k 7y agoOn the contrary, front end isn't good enough yet, and getting to the point where it's ideal will require more complexity. Users want things to work fast. If you're including a roundtrip to a server your app will never be good enough for a user on a rural 1Mbps satellite connection with 500ms latency. That's the goal - your app has to work well for that guy. You can't get it to be fast if you're using the network a lot. We need concurrent rendering, async background processing, and as much work shifted on to worker threads as we can manage. All the things that native apps do to crank up the performance need to happen on the web too. Also, don't forget that the web is fantastically backwards compatible. You can write web apps without the complexity if you want to. You can use Dreamweaver! You can server-side render every page. It works. If that's what you want to serve your users then you should do that. Just don't complain when they use the competitor's app that's faster, more responsive, and does fun things like working offline.
- dynamite-ready 7y agoMore than any framework, what most market leading applications need to provide a competitive service, is greater access to creator resource (developers / designers / content creators, whatever) and / or innovation in pre-production and design. The problem with current development trends is in how the complexity found in the tools, makes the pool of available creators (at a want for a better term) a tiny, exclusive club. This has a detrimental effect on efforts to innovate at design / pre-production stage, because the designers are near enough held hostage by us developers. It also has an overall effect on project velocity, because work that could possibly be covered by techically competent designers (namely HTML/CSS development), can only be addressed by expensive and exclusive 'framework specialists'. I strongly believe this can change by rethinking where the complexity lies. The culture built around over-complicated tooling is possibly analogous to placing the responsibility for the production of a feature film in the hands of the VFX and lighting teams, or perhaps only deeming a mechanic as having the aptitude to drive a car. I'm not rigidly stuck to this idea, I'm just musing here.
- onion2k 7y agoperhaps only deeming a mechanic as having the aptitude to drive a car This analogy is a really good one, but you've got it slightly wrong. The website user is the person driving the car. The developer is the equivalent of the person building the car. Saying the development process is "too complicated" is like saying developers should only ever build compact family cars like a Ford, but some of us want to be building BMWs and Teslas and Porsches and F1 cars and monster trucks and semi-trucks, etc. Sure, it's more complex and difficult, but the end result suits the user better, fulfils their needs better, and often just makes them a lot happier.
- bokwoon 7y agoIf a simple link to another page requires component orchestration and reactive state management I'd say it is a bit over-engineered.
- KaiserPro 7y agoThe actual task was this: There is an Icon, and some text that reads: "you are on a trail find out more" The find out more is a link, make sure all the text _and_ the icon are included in the link. So its not creating a new state or widget. its literally moving a href tag. Well it would have been, if it wasn't for the template engine, and what ever the state engine was/is. Now, if this was QT creator, I'm pretty sure I could have done this task in about 4 hours (I don't know C++ very well and I've used QT about 3 times before, each for less than a day.)
- KaiserPro 7y agoWhich leads me onto the next gripe As this is all templateable and composable. why in living fuck isnt there a GUI to do this sort of thing? I mean, on a large website you need to make widgets, then you need to compose those widgets into screens. Those screens maintain state (basically flash, but with 100x worse performance) the people that are styling the widgets are not always the same as those adding the logic, so why not make a tool where a visual artist can actually work visually? So why on earth is it not drag and drop? Yes some things are auto generated based on context, but a lot of things are static screens where the widgets update the state.
- onion2k 7y agothe people that are styling the widgets are not always the same as those adding the logic, so why not make a tool where a visual artist can actually work visually? Framer X. Sketch. Adobe Xd. etc I mean, on a large website you need to make widgets, then you need to compose those widgets into screens. Storybook (sort of). So why on earth is it not drag and drop? Dreamweaver. The tools you want all exist. Those are just a few examples. There's hundreds more. You just didn't look very hard.