3 ms·

ChatGPT can do it. Perhaps this won't be viable in-browser for a while, but I could see somebody using it in a static site build pipeline to convert space chara

ChatGPT can do it. Perhaps this won't be viable in-browser for a while, but I could see somebody using it in a static site build pipeline to convert space characters to   at compile-time. --- Break the following headlines up into individual strings where each string is an idiom that shouldn't be broken up. If words aren't part of an idiom, they can be their own string. "One year on, and what's next for remote workers?" "Hurricane Ida Gives New York What For!" "Ice Town Costs Ice Clown His Town Crown" --- "One year on" "and" "what's next" "for" "remote workers?" "Hurricane Ida" "Gives" "New York" "What For!" "Ice Town" "Costs" "Ice Clown" "His" "Town Crown"

philsnow 4y ago
I think it needs to be done while the browser is flowing text, because it should look good with nearly any width, like: Ice Town Costs Renowned Ice Clown His Town Crown and Gown vs Ice Town Costs Renowned Ice Clown His Town Crown and Gown
strogonoff 4y ago
Thanks for expanding on my point. Yes, LLMs or plain algorithms, the capability is here. It just won’t be used for this.
atoav 4y ago
> ChatGPT can do it. This is truly the kind of suggestion that makes me wonder about the energy efficiency of websites. To me it seems, that many web developers/designers are so happy with the fact that what they are doing actually works, they often forget other (more boring?) considerations like stability, maintainability, resilience, efficiency and such. We have a LEGO set with infinite pieces and a good website in my eyes doesn't try to use as many as possible of those, but to use just as many as needed while still getting what you aim for.
- atoav 4y ago
  Additional thought: The problem space of how to break a specific text depending on the size of a window is sort of limited as well. So if someone had the idea to solve this using machine learning, the best idea would be to run these calculations once (per page, serverside), and then just use a lookup table or something of the sorts after. Just store the line break positions for each text on the page for all possible widths that make sense and check that table when rendering. This has the advantage that a human typesetter could output to this format as well or they could correct the machine generated output. As there is a limited number of ways to break text the table wouldn't even have to store all pixel widths, just those at which the words break differently.

philsnow 4y ago

I think it needs to be done while the browser is flowing text, because it should look good with nearly any width, like: Ice Town Costs Renowned Ice Clown His Town Crown and Gown vs Ice Town Costs Renowned Ice Clown His Town Crown and Gown

strogonoff 4y ago

Thanks for expanding on my point. Yes, LLMs or plain algorithms, the capability is here. It just won’t be used for this.

atoav 4y ago

> ChatGPT can do it. This is truly the kind of suggestion that makes me wonder about the energy efficiency of websites. To me it seems, that many web developers/designers are so happy with the fact that what they are doing actually works, they often forget other (more boring?) considerations like stability, maintainability, resilience, efficiency and such. We have a LEGO set with infinite pieces and a good website in my eyes doesn't try to use as many as possible of those, but to use just as many as needed while still getting what you aim for.

atoav 4y ago
Additional thought: The problem space of how to break a specific text depending on the size of a window is sort of limited as well. So if someone had the idea to solve this using machine learning, the best idea would be to run these calculations once (per page, serverside), and then just use a lookup table or something of the sorts after. Just store the line break positions for each text on the page for all possible widths that make sense and check that table when rendering. This has the advantage that a human typesetter could output to this format as well or they could correct the machine generated output. As there is a limited number of ways to break text the table wouldn't even have to store all pixel widths, just those at which the words break differently.