Web Frontend Stack 04/04/20

Up until now I haven't used any frontend practices for a small or large application of my own. I have only dabbled in JQuery & CSS and always feared of how to structure the HTML. From many failed attempts I've come to know better and I now understand how to achieve such level of comfort when talking about either role - front or back.

Choosing PHP as my backend language is a natural step for me, since it is the language I am most fluent in from my 5 years of professional experience with it.

When talking about JavaScript (Vanilla), HTML and CSS , I had to go a little further backwards for each of them, even to the very beginning. Now, I would go so far as to say that I don't fear JavaScript and CSS - for each of them, it is only a matter of keeping up to date with all of the Web APIs (JS) and CSS selectors, attributes and methods. When talking HTML there is but one pitfall: I am not quite sure I know how to properly structure a page.

Furthermore - I don't think I am willing to go the distance to know the subtleties of proper SEO or "correct" HTML structure. As part of my agenda, I am more than happy to use another person's hard time and work in order to save my time, which is why I'll go with learning Bootstrap to cover my HTML & CSS for now, with the hope of learning more as I go. For the past some time I've worked with Vue.js and TypeScript, and even used different module bundlers and modern frontend tool chains, and have grown a custom to working with tools such as Webpack, Vue-CLI, NPM, Yarn etc.

After building a website using the Vue-CLI template, SCSS, RSCSS methodology and Typescript, I've come to realize that my original resolution was only half true. We shouldn't ignore other people's hard work nor should we take their abstraction and use it blindly without knowing the underlying implementation of said work or solution.

Knowing the basic building blocks enables you as a developer a wider means of expression to change, extract or use only a small portion from a giant code-base and tailor it to your project. As web developers, our work is basically a glorified process of applying duck tape to certain issues with libraries and syntactic sugar of all sorts. A true developer should know underlying technologies for the sake of brevity.

Update (08/10/22)

The above paragraphs were written by a deranged boy who desperately attempted to understand the most incomprehensible technological platform in existence: the modern web.

Leave all of this garbage behind.

Focus on simplicity.