The added bonus of not being able to select the text on this webpage made it so difficult for me to stay on the post! It's amazing what it does from a UX point of view.
This feels like a very realistic take and is probably already occurring given what you can see on LinkedIn and the like: people are using “prompt engineer” in their job titles ancillary to their primary role.
I didn’t interpret it as a break in compatibility, more so that simply because a new feature or addition in CSS arises it doesn’t stipulate that you have to adopt it. You can still continue on writing CSS how you want to. I appreciate that it makes it more difficult when new features come about in a language and you have to work on a shared codebase, you sometimes spend a while looking at many differing ways to achieve the same result.
It absolutely has breaking changes! But most developers will never notice. I work on a complex browser based web development platform and we’ve had certain specs change under our feet leading to incidents that required us to disable features until major browser vendors reverted things. I do not envy spec authors. Huge respect for their patience.
That article does a great job of further explaining why the practice is cruel, by also showing how the ducks are left in an albeit not as typically cramped, but nonetheless dank, large shed.
The quote seems to make people think it could be ethical, because the prior treatment is slightly better than average?
Unfortunately the code base has had too many chefs in the kitchen, so to speak, and now we're trying to consolidate things bits at a time.
One or two smaller sections is okay to demonstrate with, but it definitely helps seeing larger projects as the "end-goal".
