I agree, but there's also benefits of looking at a quality piece of code to see how it's done.

I lost it at the starwars elevator music.

I always chuckled at how imperial armor is so plasticy, and they only doubled down on it since the trilogy.

This ray tracing demo just about caricaturizes it.

Some modern armor is made out of UHMWPE plastic.

https://en.wikipedia.org/wiki/Ultra-high-molecular-weight_po...

Armor tested:

https://www.youtube.com/watch?v=UsjOV7tcGRI

In my opinion, most CSS bad bits are a byproduct of bad use, not a problem of the language(?) itself.

SASS, BAM, OOCSS, etc are all good practices. You can/will abuse those as well without proper understanding and planning.

> In my opinion, most CSS bad bits are a byproduct of bad use, not a problem of the language(?) itself.

I've seen far too many bad languages come and go to believe that anymore. People used to say that about PHP and VB6 too.

PHP eventually stopped with the "only bad programmers use me badly" and grew up, and VB6 died. A win in both cases.

CSS could be far better; and bad practices won't disappear until doing it the right way is easier than doing it the wrong way.

-it is not possible to decrease scope

-tooling is hard e.g. to detect unused styles

-scope problems are a pain to debug

-some constructs are awkward (e.g. tooltips with :before and positioning styles)

-vertical text behaves unexpected wrt box model

-variables are suboptimal

There are probably a lot more.

1. I require more of an explanation as to what you mean by decrease scope. I could interpret that in different ways.

2. Sure, I understand the discipline necessary to prevent that is difficult in a team setting. I would say that likely at reaching that point something went wrong before then. That seems a tooling problem, not a language problem. How many languages provide features out-of-the-box that assist with discovering unused code without some form of third-party exploring that space?

3. In what way? What scope problems? I can think of several bad practices that lead to scope problems. I can think of examples of two people following two different best practices creating such problems.

4. I know it's not exactly a fair thing to say, but I don't have those issues with the example you provide. I'm sure there's plenty of examples of showing how to do it.

5. Flex. But, granted, old practices didn't handle vertical issues well because originally HTML wasn't intended for that.

6. In what way? Do you mean variables from a pre-processor or CSS custom properties?

I'm sure there are more, just like almost all languages have their quirks and issues that make it difficult to address if not understood. Do you have any other examples that we could discuss? Are there any specific use cases where you are having difficulties that I might be able to help out with?

If the language were better, they would have learned the good practices while they learned the language, and they wouldn't even be able to express bad practices without extra effort.

I think this is an important topic for teens to understand and be able to openly talk about with their parents or other trusting grownups.

As grownups, I think we start to ignore hoping that kids will be able to figure out on their own without realizing what lasting effect it will have on their future relationship

I see a new business selling face data

I wonder if there are any companies aggregating some sort of book of faces.

eeerm... Yeah, like Facebook (it's the actual name)

(best to just spell out the obvious)

As a UI developer, I think we tend to over-think too much with the aesthetics and workflow. I think a simple confirmation prompt/or a 5 second timer before initiation would have prevented the issue.

I think this is where mentorship is paramount to junior/entry level engineers.

I agree. Also, most development happens with ambiguous requirements and wants that can never be translated/interpreted correctly by machine (yet?)

Also, most work is some form of addition to an existing code base that simply cannot be re-written every time.

That's why we need to have ML for project management first

I'm curious about how it handles design changes. Will it just rewrite from scratch? or adjust the code it has already written?

This approach rewrites everything from scratch.

However, it's an interesting technical problem to adjust the code. Does anyone have a rough idea how to implement it?