Those cases were easy to fix by using eg htmltidy on the UGC.
Honestly I don't think it was killed by one thing, or by anything. Just no platform really cared and it wasn't a win for anyone and occasionally a loss.
Yes, this is what you'd want. It doesn't have to be a complicated as the HTML5 algorithm either. That's complicated because it was a harmonization of at least 3 browser's multi-decade heuristics and untold terabytes of existing HTML practice. An algorithm unconcerned with backwards compatibility could much simpler, but still clearly define error behavior much easier to use than "scream and die".
And it's still unambiguous. You can cringe at what some people do, but it would be strictly a taste issue rather than a technical one, as the parse would still be unambiguous. And if you think you can fix taste issues with technical specification, well, you've already lost anyhow.
I mean, we aren’t ok with that for PDF. That’s why PDF renderers have incredibly baroque rules for parsing weirdly or brokenly formatted documents, and why many PDF documents fall back to embedding images or absolute-positioned pixel-like layouts for compatibility purposes.
I mean, the linked page and the comment above say it is:
> It is explicitly forbidden for clients to accept any page that doesn't conform with the specification. This prevents the standardized diabolic rules that one must implement in order to correct a
I think I'm just too opinionated to go there. If I see something that works fine, but isn't the way I'd do it, it doesn't matter if a human or an LLM wrote it I'm still in there making it match my vision.
I concur, and I think that is one of the most difficult aspects of reviewing another's code. It's difficult for me to sometimes differentiate between what is acceptable vs. what I would have done. I have to be very conscious to not impose my ideals.
So you are going to waste everyone's time getting another developer to write code the way you want? This resonates with me because at my company I get this all the time. At that point, you might as well close my PR and do it yourself, whatever way you want. I really like the advice from the book 0 2 1, to assign different areas of responsibility to people, so that there is no conflict.
FIRE isn't about job market, you can't control that. Though in tech most people are still making quite large incomes which does help.
Rather it is about controlling expenses. The thing you can actually control. My sister's family of 5 lives on less than 50k CAD / year, because they simply must (low income) so if one is making a 100k white collar salary (for example) one can live a lifestyle higher than hers while still banking 50k/an. Etc.
That would not work well in the US with annual out of pocket healthcare expenses that can be up to $21.2k per year per family, or $10.6k per year for a single person.
Plus the monthly insurance premiums. Financial independence without a large sum of money does not make any sense, and a large sum of money comes from either inheritance, or income.
Obviously you need money and obviously you get it from income. But it is easier to reduce your expenses than to increase your income, and reduced expenses also result in excess income even with no income changes.
Yes there is a floor to this strategy. If you are going to the food bank to feed yourself because you don't have enough income you're unlikely to be able to reduce expenses enough to make this happen. But if you're lower-middle-class or above it is possible.
FIRE is definitely about income just as much as it is about being frugal and saving. Having a high income is what enables the RE part.
There is a base level beyond which you can't save much, so first order of business is maximizing your income (e.g. better job/raise/promotion) without going bananas and sacrificing your health for it.
Yes talking to a human is good and necessary. But for diagnostics humans are not good at it. I'm happy for to human to use a tricorder and then tell me the answer.
reply