Live data from Hacker News

Pure CSS – Lace

diana-adrianne.com

71–80 of 106 posts

Re: Pure CSS – Lace

#71
post #32

Earlier quoted context omitted.

You do not deserve to be downvoted. As a developer, I wholeheartedly agree with you (anyone remember Safari's super buggy indexed DB implementation?!)

The downvotes are happening because this would have been as possible to achieve in Safari as in Chrome had the author chosen to develop purely in that, and Chrome would have been one of the engines that look broken. At this level you’re relying on engine quirks rather than spec compatibility.

Actually the downvotes are coming from people who don't have experience developing websites to support Safari.

>The downvotes are happening because this would have been as possible to achieve in Safari as in Chrome had the author chosen to develop purely in that, and Chrome would have been one of the engines that look broken.

This is not true.

>At this level you’re relying on engine quirks rather than spec compatibility.

I think you're misunderstanding - the art was developed with standards. Safari is the piece that is failing the standards, not the art.

Re: Pure CSS – Lace

#72

Earlier quoted context omitted.

Devs not caring about compatibility and instead focusing only on a particular browser that abuses its market position to impose its own standards on the industry? Chrome is the new IE.

As a frontend developer, IE and Safari have always been awful and give the most trouble. They also pretty much always lag behind Chrome and Firefox when it comes to new standards. Rather than targeting your frustration towards developers who don't want to or have the time to bend over backwards to accommodate terrible browsers, how about directing that energy towards encouraging those browsers to catch up and stop ho…

A "standard" seems like an odd word to describe a process in which one company does new things, and all other companies take some time to do the same.

Re: Pure CSS – Lace

#73

Doesn't seem to render correctly on Safari.

Safari is the new IE

People who spout this nonsense don't recall how bad IE was. Comparing the current state of any browser to IE (6-7-8) is utter nonsense.

There is a really good center of the road set of web browser features which all modern browsers support. This was not the case when IE was big, in order to make nice, functional web pages you needed to either give up supporting one platform or the other or you needed to spend tons of time and energy making 2 (or 3) pathways for extremely basic features.

If one browser is 1 year or two behind standards generally doesn't matter because as web developers we need to support 3-4+ year old browsers regardless. The truly crappy thing about IE was that Microsoft had zero commitment to web standards at all and many things they did outright contradicted them. Since IE had such massive market presence they undermined the standards process for more than a decade.

Re: Pure CSS – Lace

#76
There's something oddly lovely about making art with such strict constraints. I've started making fun little pieces of my own with React and CSS. It's a great way to harness creativity through restrictions. Also requires some fun math on occasion. A good exercise is to make a Bauhaus or Swiss style poster, then animate it.

Re: Pure CSS – Lace

#77
post #27
post #2

Is there any video where the artist talks about the process? I'm really interested in understanding how the artist approached this. Anyways, beautiful work.

Not exactly what you are asking for, but she does provide more information on the 5 key properties: https://diana-adrianne.com/how/

Each of the images without one of the key properties is oddly satisfying in a semi-abstract kind of way

Re: Pure CSS – Lace

#79
post #25

Having been inured to loading 100KB-200KB of boilerplate CSS for a web project, I'm just amazed that the raw CSS for this is 43KB, un-minified: https://github.com/cyanharlow/purecss-lace/blob/master/style...

Developers don’t care about performance, and haven’t for multiple years now. Multi-megabyte JS packages for normal websites are visible across most of the web, and no-one tests on the actual problem devices which are low- to mid-range android phones on slow connections.

no-one tests on the actual problem devices which are low- to mid-range android phones on slow connections.

I do. But I work in healthcare for the rural and poor. Some of my target devices the kind of craptastic phones people on HN would buy as a joke burner, but for millions of people is their entire family's only connection to the internet.

Post reply on HN