Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)AT
Posts
0
Comments
80
Joined
2 yr. ago

  • "We will provide you with a tool to emit garbage and a platform to share content. If you put the two together, you are liable."

    Attractive nuisance much? Is it too much to ask that they should have to label it a garbage generator instead of "AI"? Why does honesty always have to take a back seat?

  • Tell me you are too oblivious to implement CI/CD without telling me you're too oblivious to to implement CI/CD. Their builds and packaging should have been fully automated if it was such a pain. If you can make a Mac version of any software, you can make a Linux version. The debate internally was likely management being dumb as rocks and overruling anyone who actually knows anything.

  • O.C.: Have you consulted about this “tables” approach with other Lua developers?

    I.T.: After that, I went back to Dmitry and asked him if my understanding of “everything is a table” was correct and, if so, why Lua was designed this way. Dmitry told me that Lua was created at the Pontifical Catholic University of Rio de Janeiro and that it was acceptable for Pontifical Catholic Universities to design programming languages this way.

    Lol what? Is there some kind of inside joke about Catholics and tables?

  • I share what I find interesting from my RSS feed.

    Thank you for doing that. Human-curated links shared here is exactly what we need.

    To the complainer: People upvoting and downvoting posts will be the arbiter, not someone whining like a 14yo.

  • So you've got me thinking about a potential dark browser pattern relating to this that I think was introduced by Google in Chrome.

    Wayyyy back in the day, you might have a page full of animated gifs all doing their thing, and what you could do once the page was loaded was to hit the stop button (or hit the stop button twice if the page was still loading), and all of the gifs would stop animating. Today you couldn't do that, because the stop button has been intertwined with the refresh button; once the page loads, the stop button turns into the refresh button.

    I bring this up, because there used to be a simple universal mechanism to indicate that you wanted to stop things from moving/animating, and it would do so, but now there isn't. Funny how that mechanism has been subtly removed from an advertiser's browser, where it is in their best interest to keep the ads blinking and changing to draw your attention to them.

    It's too bad that there is no longer a mechanism that is as simple and universal that can stop movement. Now every site has to devise its own way to handle stopping movement, and there will be competing standards and methods, and it will no doubt end up being a pain intentionally, just like cookie popups.

    Maybe browsers should bring back universal stop for animated gifs, SVG, video, and (some) CSS, with an event to notify the page script.