I understand the language.
I understand the language. I don't understand what they mean by "patterns". Common edge cases where js/css/html is broken in specific ways? If you write html/css in a relatively compliant way, things will not be so broken that a browser vendor needs to account for them in a "long tail". If your js is broken, well tough luck. Are they just talking about how to implicitly handle commonly malformed HTML, as all browsers do?
Posted by leeoniya on Feb 26, 2015, 6:01 PM
Tags
Related issues
- This is my biggest problem with agents, they constantly defensively code for cases that have no chance of happening and in most cases a p...
- I wish there was something like LEAN for biology.
- The issue is really the extreme difficulty of programming them, especially for anything sequential (rather than combinatorial).
- I probably could have beared with it if it was only limited to programming, but it showing up in creative fields has made me feel all sor...
- I hate that I'm in deep enough to know what you mean.
- The biggest problem with “AI” is that big corps are shoving it down our throats.
Raise real-world problems, find people facing the same issue, and discuss solutions.8,000 issues0 comments
reliability (Other)
This is my biggest problem with agents, they constantly defensively code for cases that have no chance of happening and in most cases a p...
I wish there was something like LEAN for biology.
The issue is really the extreme difficulty of programming them, especially for anything sequential (rather than combinatorial).
I probably could have beared with it if it was only limited to programming, but it showing up in creative fields has made me feel all sor...
I hate that I'm in deep enough to know what you mean.
The biggest problem with “AI” is that big corps are shoving it down our throats.
in the middel of a coding session with 5.6 sol.
[Hero Run] 535B-A23B on 18T tokens
I understand the language.
I understand the language. I don't understand what they mean by "patterns". Common edge cases where js/css/html is broken in specific ways? If you write html/css in a relatively compliant way, things will not be so broken that a browser vendor needs to account for them in a "long tail". If your js is broken, well tough luck. Are they just talking about how to implicitly handle commonly malformed HTML, as all browsers do?
Comments (0)
No comments yet. Start the discussion.