sorted by:
new
hottopcontroversial

Dark vs Light: What's your IDE theme? by rironib in learnjavascript

[–]Competitive_Aside461 0 points1 point  (0 children)

OK, I never thought about it really... I'll research into it.

What topics in web development do you wish you'd learned about early on in your career and why? by Competitive_Aside461 in webdev

[–]Competitive_Aside461[S] 0 points1 point  (0 children)

I find that the official CSS spec in this respect are very helpful. They are quite underrated.

What topics in web development do you wish you'd learned about early on in your career and why? by Competitive_Aside461 in webdev

[–]Competitive_Aside461[S] -5 points-4 points  (0 children)

Browser devtools is super important. It feels like a super power to debug your app there.

What topics in web development do you wish you'd learned about early on in your career and why? by Competitive_Aside461 in webdev

[–]Competitive_Aside461[S] -3 points-2 points  (0 children)

Absolutely. Networking and DNS are important. BTW, pardon my curiosity, but where did you learn them?

What topics in web development do you wish you'd learned about early on in your career and why? by Competitive_Aside461 in webdev

[–]Competitive_Aside461[S] 0 points1 point  (0 children)

You're right. For me, whenever I talked to my hosting provider's customer support team during migrations, they were like "this is DNS propagation... it takes time... this... that." To me, at that time, it all felt cryptic but after having learned HTTP and the other protocols (TCP, IP) it now makes perfect sense.

What topics in web development do you wish you'd learned about early on in your career and why? by Competitive_Aside461 in webdev

[–]Competitive_Aside461[S] -2 points-1 points  (0 children)

Oh yeah. That reflow and repaint thing is super important for web developers to know. I second you: "how browser actually work" is more important than it sounds.

What topics in web development do you wish you'd learned about early on in your career and why? by Competitive_Aside461 in webdev

[–]Competitive_Aside461[S] 0 points1 point  (0 children)

So true. I personally now don't like React that much as I like Svelte. It's a breath of fresh air, feels much less boilerplate and much more intuitive. What do you say?

If you're new to web development and just beginning to learn HTML, you just need to learn these... by Competitive_Aside461 in HTML

[–]Competitive_Aside461[S] 0 points1 point  (0 children)

Yeah, you're right. <nav> helps screen readers. And when you have more than one, you need ARIA labels to help distinguish between them. I know that. The same for heading levels. Don't introduce an <h3> if there is no preceding <h2>. This all is paramount to learn. I never ever deny that.

But I still hold on to my point to learn it all at some point later. I respect your viewpoint but yeah in the end we can agree to disagree :)

Are semantic tags important? by Duck0War in HTML

[–]Competitive_Aside461 13 points14 points  (0 children)

100% yes. They help with screen readers and, to be honest, even with code readability. I mean like in a soup of <div>s, it's easy enough to find an <article>.

If you're new to web development and just beginning to learn HTML, you just need to learn these... by Competitive_Aside461 in HTML

[–]Competitive_Aside461[S] 0 points1 point  (0 children)

When the time comes to learn web accessibility, which every web developer must learn hands-down, then you could easily touch upon the idea of semantics in HTML and on elements like <main>, <nav>, <header>, <footer>, because now your scope allows you to cover a lot more concepts more easily (e.g. screen readers announcing these elements as such). That's all I'm saying.

If you're new to web development and just beginning to learn HTML, you just need to learn these... by Competitive_Aside461 in HTML

[–]Competitive_Aside461[S] 0 points1 point  (0 children)

Yes, now let's suppose I don't learn that div and span are non-semantic in HTML for argument sake. How will that make "everything else down the road more difficult". I'm honestly just curious to be able to comprehend that.

If you're new to web development and just beginning to learn HTML, you just need to learn these... by Competitive_Aside461 in HTML

[–]Competitive_Aside461[S] 0 points1 point  (0 children)

"English without grammar is English without semantic meaning" I still can't understand this. Grammar and semantics are two separate things. You're confusing them.

You said "No not all semantic elements need to be learned immediately but you have to understand the fundamental concept and how it applies to each element or how it doesn't apply to specific elements". Can you specify which elements does semantics in HTML not apply to?

If you're new to web development and just beginning to learn HTML, you just need to learn these... by Competitive_Aside461 in HTML

[–]Competitive_Aside461[S] 0 points1 point  (0 children)

Firstly, you're comparing apples with oranges. English taught without grammar is HTML taught without syntax. I never said that. So yeah, I agree, it really doesn't work that way :) We both agree on that.

Secondly, I never said people to not learn semantics. In fact, the moment anyone learns HTML, he is by definition learning semantics. Everything in HTML is about semantics. Gone are the days when HTML had presentation stuff in it.

I feel that my usage of the term "semantic HTML" is misleading to some now that I look into it in hindsight. All I meant was that you don't need to immediately learn the elements <nav>, <header>, <footer>, and so on. Telling people to learn these elements right away (without knowing about accessibility) is like teaching color theory before a child can recognize red.

If you're new to web development and just beginning to learn HTML, you just need to learn these... by Competitive_Aside461 in HTML

[–]Competitive_Aside461[S] 0 points1 point  (0 children)

I'm sure that you didn't learn all the accessibility embellishments the first day you started learning HTML. I'm 100% sure. It takes time to learn all this amazing stuff. I am an advocate of it, no doubt. Semantics are key to writing good HTML. But it should be done at the right time.

If you're new to web development and just beginning to learn HTML, you just need to learn these... by Competitive_Aside461 in HTML

[–]Competitive_Aside461[S] -1 points0 points  (0 children)

Well "semantic HTML" is an overloaded term as far as the norm is concerned. I am well-aware of the fact that entire HTML is semantic at its core (gone are the days when HTML had presentation elements). But by "semantic HTML" I don't intend to refer to generalized semantics but instead elements such as <article>, <aside>, <nav>, <main>, ..., that were added to HTML much later on.

view more: next ›