Why is user-select: none and pointer-events: none applied to the content here? In the DOM it's perfectly serviceable content, even if the divs are absolutely positioned to achieve the editorial layout. If you disable these CSS properties the text is selectable and pastes in the right order as expected, since its based on the DOM ordering which matches the line order...
Additionally overflow is hidden, so you cannot read the entire text on desktop without using a very small zoom... and as others have noted, mobile is fully and completely broken. If the bubbles weren't so huge at least you could read a paragraph or two on mobile.
Full of emdashes and AI comparisons like "The performance improvement is not incremental -- it is categorical" too :-\
I'm sure this is really smart but boy is this a pain to read. I even tried holding the orbs in hopes of reading the text but it kept reflowing so much that I gave up after 5 minutes.
Edit: I just realized that clicking once freezes the orbs.
I was clicking and clicking hoping for the reflow madness to stop.
Thanks for this tip -- BTW we need to click _each_ orb.
Occationally a previously untamed orb will start making its presence known until it is stopped. OK I think I have been able to catch every orb now. Now onto read about the future of text layout.
I kmow all of the css/js hacks and tricks but the information i need is the screen size in real mm.
Currently i put up a visibility:hidden position:absolute left:-9000px div with nobr, put the first line of text in it, then get the width of it with computed style, calculate the root font size to make it the line exactly the screen width. Then the div is removed and the rest of the content is allowed on the page.
No idea how I'm supposed to read the end of this. But it seems kinda interesting? Not that like, require('fontmetrics') doesn't exist, but it's definitely true that most JS needs more font rendering then the browser seems capable of giving us these days.
I hesitate to even call this a solution in search of a problem because... Well come on.
A completely useless demo that can't operate on mobile of a way of displaying text that is less functional than every other way of displaying text. Table-based html layouts were better.
Why is user-select: none and pointer-events: none applied to the content here? In the DOM it's perfectly serviceable content, even if the divs are absolutely positioned to achieve the editorial layout. If you disable these CSS properties the text is selectable and pastes in the right order as expected, since its based on the DOM ordering which matches the line order...
Additionally overflow is hidden, so you cannot read the entire text on desktop without using a very small zoom... and as others have noted, mobile is fully and completely broken. If the bubbles weren't so huge at least you could read a paragraph or two on mobile.
Full of emdashes and AI comparisons like "The performance improvement is not incremental -- it is categorical" too :-\
Here is the article's text, extracted from the .js source: https://pastebin.com/5uguB0bs
I can’t read it at all on mobile because I can’t scroll down. Is there a summarization?
Yeah, this is a very underwhelming promotion, I'm afraid.
I'm sure this is really smart but boy is this a pain to read. I even tried holding the orbs in hopes of reading the text but it kept reflowing so much that I gave up after 5 minutes.
Edit: I just realized that clicking once freezes the orbs.
I was clicking and clicking hoping for the reflow madness to stop.
Thanks for this tip -- BTW we need to click _each_ orb.
Occationally a previously untamed orb will start making its presence known until it is stopped. OK I think I have been able to catch every orb now. Now onto read about the future of text layout.
Click the spheres to stop them from moving, so that you can read the text.
I kmow all of the css/js hacks and tricks but the information i need is the screen size in real mm.
Currently i put up a visibility:hidden position:absolute left:-9000px div with nobr, put the first line of text in it, then get the width of it with computed style, calculate the root font size to make it the line exactly the screen width. Then the div is removed and the rest of the content is allowed on the page.
This is the only thing that works.
No idea how I'm supposed to read the end of this. But it seems kinda interesting? Not that like, require('fontmetrics') doesn't exist, but it's definitely true that most JS needs more font rendering then the browser seems capable of giving us these days.
am more curious to see if browsers will investigate integrating/moving to https://sluglibrary.com/
I hesitate to even call this a solution in search of a problem because... Well come on.
A completely useless demo that can't operate on mobile of a way of displaying text that is less functional than every other way of displaying text. Table-based html layouts were better.
Just show the text, there's no problem here.
Maybe Markdown?
This is insane! And so underrated even though it is brand new
A shame there doesn’t seem to be any vertical text support yet
I have zero idea what I’m supposed to be looking at? I assume it’s totally broken on mobile.
Seems the entire “blog” is ai generated images. So I assume this is more slop.
Yet another "this is the future!" project that completely misunderstands why the present is the way it is.
The website does not work on mobile. If you used CSS you wouldn't have this problem.