4 ms·
I'm not exactly trying to attain the platonic ideal of a web page, here. My goal is to build something that people find valuable, quickly. I don't care if it
by redthrowaway 11y ago
I'm not exactly trying to attain the platonic ideal of a web page, here. My goal is to build something that people find valuable, quickly. I don't care if it requires js to render, because it's not worth the tradeoff to try to get it to show up for that one guy trying to render a web page on his TRS-80.
>Your content can't be archived properly by the Internet Archive.
IA doesn't factor into 99.999% of what I build.
>Your content can't be accessed by anything user-agent less sophisticated than a full-blown browser.
I build things for browsers.
>Your content can't be indexed by a search engine that doesn't have the resources to crawl using full headless browsers.
I can barely be arsed to submit sitemaps to Bing.
>Your content won't work with tools that attempt to scrape and expand content
When supporting those things becomes a priority, I'll do so.
----
RMS looks at a microwave and writes an essay about whether or not the software that drives it needs to be FOSS.
I make my food hot.
- techdragon 11y agoSo true and yet so sad.
- bottled_poe 11y agoGreat, so your advice is if I can use a device that is a few years old, I just have to buy the latest version of $BRANDED_PRODUCT. Developers can actively support or resist this wasteful practice. It seems pretty clear where you stand on this.
- redthrowaway 11y agoI have no idea what you're trying to say. I'm not offering advice, I'm saying I build applications to be useful, not to conform to a set of abstract ideals. If 1% of visitors can't use it, I need to weigh the value of serving those 1% vs the value of spending my time building features. I'm not Google or Facebook. My team at work is me and two co-ops. I'm not going to triple our development time just so I can get some Internet back pats from purists.
- deleted 11y ago[deleted]