Live data from Hacker News

Pure CSS – Lace

diana-adrianne.com

101–106 of 106 posts

Re: Pure CSS – Lace

#101
post #82

Earlier quoted context omitted.

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.

Its the buisness side that doesnt care. For my personal buisness i make sure everythig is fast, lightweight, and accessible, works on browsers that has below 0.1% usage, do not track users, nor store personal info. But I do not make any extra money doing it.

I think you'd be surprised how much speed matters. Google factors in page load time for SEO, and there's quite a few examples of companies seeing page speed directly relate to sales:

https://developers.google.com/web/fundamentals/performance/w...

Re: Pure CSS – Lace

#102

Earlier quoted context omitted.

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.

At the other end of the spectrum, I've worked on an ecommerce site where I was instructed to ignore that our JS payload was taking more than six seconds to parse on flagship phones (setting aside the network entirely).

Worse still, after loading that code up, only then would it request the manifest that described 90% of the above-the-fold content.

The decadence of web development today, particularly with agencies and large corporate customers, is truly boundless.

Re: Pure CSS – Lace

#103

I know, i know, it's awesome. But, unless it's specifically to make a point regarding the absurdity of today's web (such as eg demonstrating CSS Turing completeness), I can't help finding such hacks sad, because it just blends in to demonstrate how far we've striven from what once was a vision for a rational media architecture with a dedicated vector graphic format.

I don’t think that’s fair, exactly. The point of this exercise is to show artistic expression by pushing a medium outside of its intended use. There’s also an artist that paints in MS Excel, for example. SVG is an incredible and underrated format. You can create illustrations in svg with modern graphics tools, yet still hack and animate them with css and js. And CSS Houdini is a really exciting development, too. Some…

The amazing MS Excel artist mentioned can be found here:

https://pasokonga.com/

Re: Pure CSS – Lace

#104
post #97

Earlier quoted context omitted.

> we're just saying Safari compares to it's peers (Chrome, Firefox, heck, even Edge) like IE6 used to compare to the other browsers back in the day Again, this is nonsense. There is a gap, but it's not bending the shape of the web or costing the average developer hundreds of hours to work around bullshit. Safari is behind on some features... no doubt at all. But to compare that to IE 6 is just wrong.

> it's not bending the shape of the web Safari for iOS (and Apple in general) is bending the shape of the web. For example the poor support for PWAs.

I think that's intentional on Apple's part, though.

Re: Pure CSS – Lace

#105

Earlier quoted context omitted.

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.

At the other end of the spectrum, I've worked on an ecommerce site where I was instructed to ignore that our JS payload was taking more than six seconds to parse on flagship phones (setting aside the network entirely). Worse still, after loading that code up, only then would it request the manifest that described 90% of the above-the-fold content. The decadence of web development today, particularly with agencies and…

Fascinatingly, at a previous ecommerce gig, we had a similar issue. On of the developers ran a test where on one of our main pages, he added performance improvements to get the fastest speed to a reasonable place, and then segmented traffic into buckets that deliberately slowed the server response by various, increasing amounts of time.

And wouldn't you know, it made almost no difference on our primary conversion metrics. As far as we could tell his methodology was sound, but unfortunately it got buried when it was discovered the findings could be abused to show that performance doesn't matter.

Post reply on HN