Thanks for this, I didn't know people thought that nuclear-proof meant that it could literally take a nuke. I certainly hope people haven't been thinking that a MOPP suit will make one a super soldier impervious to nukes or anything considered a chemical (which could be interpreted as all matter).
It's not even that Ublock/bloat is slowing things down, web sites are plagued by bad development and multi-standard requirements leading to tons of wasted processing time waiting for elements which eventually error out. I've analyzed performance on multiple websites, even big-name and high-traffic websites like Youtube and found that 60%+ of load time is just sitting there doing barely any processing while waiting for extra remote services to be contacted only to never load and finally fail allowing to page to go interactable. It's like having a beast of a computer but forgoing actual RAM in place for pagefile-as-ram; all other components could be amazing, but you're paying that performance tax no matter what.
He says this because he kind of ignorantly (his own wordage) wrote in machine code for quite some time before realizing assembly was a thing. So for Linus inline assembly is to machine code as python is to c for a lot of us.
It was never exactly a feature, it was to do with how websockets handled new posts. They're movinig away from websockets in 0.18 so it won't be a thing anymore.
Read openAI’s papers on chatGPT. They define it as a next token guesser and detail the exact hidden layer functions that accomplish this. It’s not an oversimplification, it’s what the creators of these AIs define their creations as.
Other properties may be there, but as you say they are emergent; emergent properties rely on two or more sources, if one goes away so do they.
That's the thing with sites that run on user generated (and moderated) content, there's positive growth/decline feedback. More users -> more content -> more users, and on the flipside fewer users -> less content -> fewer users.
I'm not sure, client.js has entries for displaying and interacting with the 'more' button; it just hasn't been doing anything.
Oddly enough, I think it was just fixed for comments but still not on posts. Probably something in showMoreButton, though from what I see of it everything looks normal.
Oddly reminiscent of this. I just wish we got a chance for Bernie.
Thanks for this, I didn't know people thought that nuclear-proof meant that it could literally take a nuke. I certainly hope people haven't been thinking that a MOPP suit will make one a super soldier impervious to nukes or anything considered a chemical (which could be interpreted as all matter).
Seems like a serpentine-type. Black, glossy, intrusive with non-conchoidal fracture planes.
It's not even that Ublock/bloat is slowing things down, web sites are plagued by bad development and multi-standard requirements leading to tons of wasted processing time waiting for elements which eventually error out. I've analyzed performance on multiple websites, even big-name and high-traffic websites like Youtube and found that 60%+ of load time is just sitting there doing barely any processing while waiting for extra remote services to be contacted only to never load and finally fail allowing to page to go interactable. It's like having a beast of a computer but forgoing actual RAM in place for pagefile-as-ram; all other components could be amazing, but you're paying that performance tax no matter what.
If the set of sets is not a set then why did you just define it as a set? Checkmate.
Your probably right.
Thanks to the use of markup language in our comments we're
all^coding^anytimewe comment.He says this because he kind of ignorantly (his own wordage) wrote in machine code for quite some time before realizing assembly was a thing. So for Linus inline assembly is to machine code as python is to c for a lot of us.
It was never exactly a feature, it was to do with how websockets handled new posts. They're movinig away from websockets in 0.18 so it won't be a thing anymore.
Read openAI’s papers on chatGPT. They define it as a next token guesser and detail the exact hidden layer functions that accomplish this. It’s not an oversimplification, it’s what the creators of these AIs define their creations as.
Other properties may be there, but as you say they are emergent; emergent properties rely on two or more sources, if one goes away so do they.
Be brave; live life on the edge like our OSes used to.
That's the thing with sites that run on user generated (and moderated) content, there's positive growth/decline feedback. More users -> more content -> more users, and on the flipside fewer users -> less content -> fewer users.
I'm not sure, client.js has entries for displaying and interacting with the 'more' button; it just hasn't been doing anything.
Oddly enough, I think it was just fixed for comments but still not on posts. Probably something in showMoreButton, though from what I see of it everything looks normal.
Three dots doesn't work for us on lemmy.world. 😅