I've almost never touched web development, but as an active HN reader I have at least passing familiarity with almost all the terms used in the article. So, honest question: can a person fully understand how modern HTML/CSS work without diving in the source code of one of the browser engines? Because as a developer, if I was forced to use such a complicated technology, grooming source would be my best guess at making…
In web design, everything easy is hard again
11–20 of 335 posts
Re: In web design, everything easy is hard again
#12I've almost never touched web development, but as an active HN reader I have at least passing familiarity with almost all the terms used in the article. So, honest question: can a person fully understand how modern HTML/CSS work without diving in the source code of one of the browser engines? Because as a developer, if I was forced to use such a complicated technology, grooming source would be my best guess at making…
Re: In web design, everything easy is hard again
#13This is my experience of web development, every time I return to it. I’m really not an expert in web dev, but it _feels_ like web dev has been badly engineered. JavaScript is a very badly designed programming language (yes, even in its modern form), which I think has caused a lot of problems. Many JS developers don’t know much about programming language design, so they can’t see how bad it is, and they make matters w…
Re: In web design, everything easy is hard again
#14That's where all the complexity comes from: people are trying to build/collect the missing pieces of a platform, and then try to build their stuff on top of it.
And you can see it everywhere: from CSS (which still pretends that modularity doesn't exist or that complex constraints in layouts do not exist) to DOM (which hasn't seen a proper API design in years) to Javascript (whose idea of a standard library is adding an underspecified `fetch` after 15 years of people writing wrappers around XMLHttpRequest).
Re: In web design, everything easy is hard again
#15I've almost never touched web development, but as an active HN reader I have at least passing familiarity with almost all the terms used in the article. So, honest question: can a person fully understand how modern HTML/CSS work without diving in the source code of one of the browser engines? Because as a developer, if I was forced to use such a complicated technology, grooming source would be my best guess at making…
As as web developer the most important skill to learn is to let go! You fix it for whatever browsers the client uses and forget about the rest.
Re: In web design, everything easy is hard again
#16> Directness is best in my experience, so a great photo, memorable illustration, or pitch-perfect sentence does most of the work. Beyond that, fancy implementation has never moved the needle much for my clients.
> Last month, I had to install a package manager to install a package manager.
...
I sure as hell know about spaghetti workflows and spaghetti toolchains. It feels like we’re there now on the web.
Re: In web design, everything easy is hard again
#17I completely share the thoughts of the author of this article. However, I'm not sure if his proposed solution would work for most people. It's not that I want or like to use npm etc. - I'm forced to use them as it's the new default way of working with almost anything useful in today's web development work. An alternative would be to start from scratch - and then reinventing all these things again, making another full…
People were saying that was the problem 10 years ago. Those exact words. Apps aren't docs.
All you need to do now is propose a new language and call it XHTML. Or maybe make markup extensible and functional, we could call it, ummmmmm, XSLT.
Re: In web design, everything easy is hard again
#18I've almost never touched web development, but as an active HN reader I have at least passing familiarity with almost all the terms used in the article. So, honest question: can a person fully understand how modern HTML/CSS work without diving in the source code of one of the browser engines? Because as a developer, if I was forced to use such a complicated technology, grooming source would be my best guess at making…
Understanding ALL of CSS is tricky, because it has a long history. It's also incredibly tricky to understand how it all works together when different display modes are combined. But you don't need to understand ALL the parts in order to build something useful. Just skip over the parts you won't be using.
Do you think any of the alternatives are truly much better?
Re: In web design, everything easy is hard again
#19I completely share the thoughts of the author of this article. However, I'm not sure if his proposed solution would work for most people. It's not that I want or like to use npm etc. - I'm forced to use them as it's the new default way of working with almost anything useful in today's web development work. An alternative would be to start from scratch - and then reinventing all these things again, making another full…
I know people have different needs, and that reasonable people can make reasonable choices and end up in very different places. What I don't understand is how anyone could end up in a place where this kind of website is ok. Give me a pdf; give me plain html and css. https://fermatslibrary.com/s/shelling-out-the-origins-of-mon...
Re: In web design, everything easy is hard again
#20This is what I feel like everytime I try to keep up with web tech... For crissakes, the last training I went to had a session on Razor Pages, which set off my PTSD from years of doing ASP.NET WebForms, back before we decided that was a really awful, painful way to do things.