3 ms·
While I don't agree with other points, things got clearer once I reached the following: > Marketers, content editors, SEOs, designers – they’re all locked out
by vladms 1y ago
While I don't agree with other points, things got clearer once I reached the following:
> Marketers, content editors, SEOs, designers – they’re all locked out of the process. Because now, even simple tasks require technical fluency.
I worked in web development in the 2000s and then restarted in 2020s. The power of the tools, the speed of development and the result are all much better. The downside? You need to know more (because you can do more and some required things are more complex and people expect more) and less people might be required (ok, this is a downside for some people only...).
Why are we talking about some megabytes transferred nowadays? Most of us have in our pockets a computer 100 times stronger than the first one that beat a human at chess (not to mention that one was occupying rooms). It is more important to have the flexibility and to be able to scale complexity when you need to (hard and not given even with the frameworks), than to "save" some megabytes.
- wffurr 1y agoThe fast pocket computer might be fairly common in fully developed countries, but bandwidth is not. It’s trivial to run into use cases with limited network bandwidth regardless of how fast your iPhone is. And if you broaden your idea of your user base a bit, even the fast computers aren’t ubiquitous. Try using a low end Android phone sometime, or a hand me down iOS device still on iOS 12.
- immibis 1y agoA low-end Android phone that is 100 times as fast as a Cray 1, yet still can't load a blog post.
- deleted 1y ago[deleted]
- em-bee 1y agobandwidth is not the problem. latency is. a site where every interaction requires an http request and a reload of the page performs much worse over low latence than an SPA that is designed with a local first approach where all interaction is local and data requests happen in the background. not all SPAs are designed like that. but none of the traditional sites are designed like that either because they can't. take hackernews as an example. in order to write a reply i have to click a link, wait for the page to load, click submit, wait for the submission to complete and for the updated page to load. i live with bad internet. submissions and pageloads on hackernews frequently time out. with an SPA the first click would open a text field without any server request at all, and submit would happen in the background while i can keep reading. and it can be repeated if it fails without me noticing and having to worry about it. likewise updating for new messages could happen in the background without me having to wait for a page load. on top of that new messages could show up in a different color without having to track that in the server.