💠#WebDev Time to grow up or wake up!💠

We can't solve the current problems of web app developers with another shiny new framework, it's a crazy road to infinity hell.

What goes around comes around also in #dev #tech; about #CSS: Before CSS, nearly all presentational attributes of HTML doc
and I point to @tailwindcss here, which has a built-in sunk cost, that many developers will discover, when they need to refactor their codebases to use something newer / better / modern / shiny.
I think frameworks can't solve the CSS UI problem with the current approach, because this is a design problem (which @tailwindui is trying to solve, but is based on the wrong approach); this is interesting: Inheritance is a key feature in CSS; it relies on the ancest
Why is it interesting? For this reason: Inheritance in CSS is not the same as inheritance in class-b
It's looks like the solution to the UI Oriented CSS is by making CSS fully Object Oriented with encapsulation (native or via compiler) "to separate the contractual interface of an abstraction and its implementation": In his book on object-oriented design, Grady Booch defined e
Working on web apps is a frustration and I always feel that we are doing it wrong: components are great when they can be reused, but we use them in a completely different way, because we incorporate the UI, states, and business logic into them, turning them into microservices.
We need a separation of interface and business logic.

To many, it may not look at first glance, but the browser is not an operating system, but a game engine (therefore JS has no main function, only we are directly in the "game" loop) ...
... and we are actually dealing with a graphics engine (DOM is a layers descriptor). If we want to solve application development problems, we must either embrace game development paradigms or create a new runtime environment for web applications.
I am talking about the coming time when we need to separate document layer context from application layer context in browsers due to rising sunk costs which block the possibility of web application development. We still treat the browser as a playground, but it's time to grow up.
By the way: yesterday blog post @kyleshevlin about facade pattern - kyleshevlin.com/facade-pattern/ - gave me a hint of hidden costs sunk in Tailwind.
if you want to see what I'm talking about, when I mention graphic engine, check as an example of that behavior and why we're doing it wrong, thinking about DOM as a document

• • •

Missing some Tweet in this thread? You can try to force a refresh

Keep Current with Jarosław Janota 🎭

Jarosław Janota 🎭 Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!


Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!