I don't really want my app state spread over CSS, HTML, JavaScript... How would you ensure that "easily animate between states" within CSS doesn't cause confusion and complexity?
I started HTML and CSS on Myspace! I love teaching and solving difficult problems. I really enjoy using frameworks but I love the challenge of rolling your own. I try VanillaJS until I need more.
Great point! I would stray away from this in a medium to large size application for the same reason.
This is a nice technique for someone who is doing a simple marketing site that doesn't really have "state".
I would argue that some state is already in CSS. A lot of these are pseudo selectors. :hover, :focus, & :checked are examples of this.
I am not saying this is the "correct" way to do it, but a simple one for a simple use case. It is all based around your needs for your specific project.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't really want my app state spread over CSS, HTML, JavaScript... How would you ensure that "easily animate between states" within CSS doesn't cause confusion and complexity?
Great point! I would stray away from this in a medium to large size application for the same reason.
This is a nice technique for someone who is doing a simple marketing site that doesn't really have "state".
I would argue that some state is already in CSS. A lot of these are pseudo selectors.
:hover,:focus, &:checkedare examples of this.I am not saying this is the "correct" way to do it, but a simple one for a simple use case. It is all based around your needs for your specific project.