Pwntheon

Opened the homepage on mobile and it craps out majorly. Horizontal scroll with some white space and weird floating graphics, content hidden by overflow, etc. Is this a joke?

>One thing I'd mention is that graphic editing (photoshop/GIMP/etc) is still stuck in an interface taken from paper. And that when CorelDraw and Inkscape showed a better interface that also uses a few synergizing tools, other software failed to adopt it. But the pressures on graphics software seems to be different.

As someone who has only used these applications briefly, I would love to know more about this.

Cogmind is a newer roguelike that uses lots of effects like this. It looks amazing

And also with some mega tags that prevent me from pinch zooming.

Me too. The Elongated kind has had more of a media presence, but I prefer the normal one.

Only in the most obvious of cases. Your cat reluctantly steps on an item? Cursed. Grey stone moved less than X tiles when kicked? Loadstone. Hundreds of these.

What's the context here? This is not the whole book I think?

Take this with a grain of salt because I'm not super well read on llms, but isn't their entire function built on prediction?

Sounds like a reasonable approach could be to have a separate "channel" which focuses entirely on the concept of "where is this conversation going?" could give a pretty good baseline for when and how to interject.

I believe a more accurate quote is "Everyone lies".

Maybe someone wants to start up a new store?

I can only speak for myself, but the few times I encountered xslt in the past it was in the context of bulky and verbose SOAP services. The syntax felt off to me (and still do).

I think this was at the time I was learning jquery and using css selector syntax for finding elements, and the difference between that and xpath was pretty stark.

I basically (probably with insufficient knowledge) filed xslt away with vb and tables for formatting as old, complex and soon to be replaced

I have a hard time articulating exactly why, but I believe tailwind is popular because it allows developers who are not designers to ignore design/css best practices and just write inline styles again like they used to, before everyone starting telling them that this was bad practice.

I had a rough road learning css, and have been in a few situations where my css/design skills were insufficient to the tasks I was expected to solve. Inline styling let me work more intuitively, and in large part skip learning a whole new paradigm/architecture "just to style some components".

As I eventually grew and had time to work on styling/design in a less stressful environment, I gradually got better at it. Not by practice so much as by learning a new way to frame the problems of styling differently from the problems of "pure" programming.

Had tailwind been around back then I'm sure I'd be a big proponent. It's a product that proposes to solve the cognitive dissonance for a programmer with lots of experience coding, but little experience designing being asked to structure and reason about their work in an uncomfortably different way.

I think tailwind solves a real problem, just not the one we're being told it does.