I've spent most of this week figuring out how best generate device specific thumbnails for my blog.
I've spent most of this week figuring out how best generate device specific thumbnails for my blog.
Thinking of it another way, computers of a long time ago could do only basic things like printing strings or drawing lines. Computers of today can still do those things, in addition to a host of other things that are now only possible due to technological advancement, like streaming video. But in some environments it is possible to limit yourself to having the computer do just the simple things - it's just a matter of deliberately opting-in rather than doing the only thing that's possible to do. For example I'm trying to write a "Web 1.0" webpage in the style of early 2000's design like Praystation[1], ignoring the shiny new technologies that do a lot more, because I believe that "more" is not necessarily "better". I believe you have to be ideologically motivated to do this now, because it seems like a lot of average web users have come to expect SPA-style apps with fancy animations and client-side interactivity, and that's where a lot of interest in web design appears to lie at present.
Of course, for a video-sharing app this doesn't really apply because the platform it runs on was proliferated fairly recently. The oldest model in the smartphone lineage came out at the start of 2007, and in order to build apps for it, it was necessary to install a full-blown developer toolchain with visual layouting tools and hundreds of APIs available for use. That's the simplest it can get. In the 1980's you could just 20 PRINT "HELLO WORLD".
I think it would greatly help if the author published the source code, as he briefly mentions considering. At least then it would be possible to judge exactly how technically complex the software is, and people could learn from it also.
However, at the point where you need to rely on complex cloud infrastructure like AWS to build things like video sharing applications, it might turn off anyone not completely interested/invested in app building. Although, I do believe a completely invested/motivated 16-year-old could pull off something similar, given the amount of documentation and free libraries on the web. That's not discounting the difficulty of actually accomplishing such a thing - for a young newcomer it would be necessary to learn many disjoint concepts for such a thing as video streaming. But given a significant amount of effort and motivation, it's at least possible to do in the present age.
A key point the author made in the article was that simplicity is appreciated. Here's an analogy: if Snapchat is the equivalent of an SPA-style site with fancy animations etc, then his app is a static webpage.
Just consider for a moment: the reason these analogies to old technology are even necessary is because what this one amateur did today would have definitely taken a team of engineers to accomplish 12 years ago.
You are absolutely correct, the standards for professional pop tech are always being raised to new levels, just like with every field, e.g. cooking. Nobody is saying opening a successful restaurant is getting any easier. However, amateur gourmet cooking for the family is demonstrably much easier today than ever before in history.