after writing 35+ articles, being featured in multiple email listings, having 1 conference talk as well 5 meetup talks. I kind of slowed down with my teaching initiative… The blog stats are still good, roughly 100 people read the articles every day.
In this light I am considering to cover more topics, like
1. “History of CSS tooling and why is it important to follow up changes in the industry.”
2. “React is Front-End.”
3. “BFF (Back-End For Front-End).”
4. “Micro Front-Ends, the answer to our prays or introduction of new problems which we need to solve…”
5. “Series on the web…
There are many use-cases in which you need to get some information from within the
<iframe> and pass it back to the parent page.
The most popular info is the total height of the content within the
For that purpose, people built libraries such is…
Problem with this library is that it is bloated with features you might not need. It also covers only one use-case, for passing the height / width related data from the iframe page to the parent page and updating the iframe sizing.
Having 1 execution stack means, that no matter of the async nature of the web APIs such is setTimeout or XMLHttpRequest, they are eventually going to get into the same execution queue.
Async doesn’t mean multi thread, just non blocking.
To conclude, Why web workers?
I bet that when you think about PostCSS you must think something like…
Yet the truth is that PostCSS is around for almost as long as React!
Front-End is evolving… wise people even state that it’s catching up with the more traditional types of programming such is Back-End or Desktop development in general.
Some of us started writing HTML / CSS / JS more than a decade ago and nowadays we write CSS in JS or JS in NodeJS or something that we think is HTML in JSX… Crazy isn’t it?
If you find it hard to keep up with the new stuff here are the 3 unorthodox things you need to do so that you are always one step ahead of the progress.
When people say that they dislike CSS it’s mostly because of the cascading. In the modern age of component based development we managed to fix scalability of our Front-End apps or Front-End part of our apps if that terminology suits you better. But CSS is more than less the same old thing if we approach it in the traditional way.
Obfuscated CSS class names == smaller bundle size == less…
Before we begin with the facts I need to stress out one thing. If you think that something is important then please treat it appropriately. I am curious to know since when is brute force solution for such cases?
Programmers who write CSS sure know that !important is actually the negation of important.
Now let’s switch to specificity. I mean what is more important to talk about when !important is the topic…
As you may know things do have priorities in CSS. If nothing else that concept is the core of Cascading part of the Style Sheets.
There are many complex concepts in programming and even more ways to make them seem complicated.
Luckily async / await is easy to understand and I will explain it in just 1 sentence… Wait for it… wait for it… Go!
async function will always return a promise and await operator gives us the opportunity to wait for a promise within the function.
Let’s face it right from the start. People hate rules. There is something in human nature which simply refuses to obey rules. We see them as limitations and an act of domination. I personally, like many of us programmers, felt the same when back in the day I was introduced to code linting.
People are like wolves, we fight for the leadership role.
People are like ants, we fight for each other and the common goal.
No matter if you see yourself as wolf or ant, you will need rules if you are going to be part of either pack…