211–220 of 318 posts
Earlier quoted context omitted.
Yeah let's do that. You have everything related to your component on place instead of jumping between files.
Vue, Svelte, and Surface manage to do this without forcing you to inline all your styles
CSS in 2025: Let's write html inlined styles as if it was 2005 and separation of formatting/representation was never invented. I talk of tailwind, of course.
CSS in 2025: Let's write html inlined styles as if it was 2005 and separation of formatting/representation was never invented. I talk of tailwind, of course.
Wait until you see React & JSX... At least html and CSS are both presentation. React/JSX now confuses presentation and business logic.
Earlier quoted context omitted.
The deadest horse in web development is the myth of “separation of concerns”
I was recently doing some very specific web scraping of some very public very static documents. About 25% of them use a soup of divs with hashes for class names. Not a or or in sight. I am fine with the idea of what tailwind does but like at least using semantic tags where appropriate could be a thing.
Probably half of it still doesn’t work in Safari.
Earlier quoted context omitted.
The drop cap example is also broken for me on the latest Firefox version. It still requires a manually set line-height of 1.
Also broken on latest Safari & iOS. They should add screenshots how it supposed to look
Earlier quoted context omitted.
The deadest horse in web development is the myth of “separation of concerns”
I was recently doing some very specific web scraping of some very public very static documents. About 25% of them use a soup of divs with hashes for class names. Not a or or in sight. I am fine with the idea of what tailwind does but like at least using semantic tags where appropriate could be a thing.
Earlier quoted context omitted.
It's a choice. The dominant paradigms choose not to. I disagree. And that makes me the loser here
I agree, it’s a choice. So is the opposite. Complaining about other people’s choice of doing things on the web is the choice I’m actually tired of.
Earlier quoted context omitted.
But for that designers should care about the limitations. But they don’t care. Not even about the more basic ones. I’m quite sure many of them don’t even know. Mainly, because their customers are not the one who code. I got many designs for websites where customers told me that they want a pixel perfect version. The funniest one was when my boss who supposed to be a “senior” web developer told me this. Of course, the…
This doesn't solve the problem but: If the designer is not aware of the ins and outs of the medium they are supposedly working with, they are not a very well informed and educated designer. Just like I don't presume to be able to make a great product packaging design, without knowing firstly much more about visual composition and design, but also secondly the material and form and shape I am designing for. Will that…
I’ve learned in the past decades that people who care about quality is the minority.
Look at any B2B software. They don’t care because their customers are different than who uses their products. They care about their customers only (managers). They pay attention to users as much as minimally possible without loosing customers.
This happens at every level.