h3mb3

I think it disappears after a certain time.

You can edit it back.

> Solve the generic problem not the specific one.

It's good that you provided the example...

> i could write a program that reads a csv row by row, converts it to my internal model, then emits those data into a ndjson file. Or I could just write a program that converts csv to ndjson , agnostic of the data. The former costs you every time the model changes. The latter is useful for a variety of system architectures again in the future.

...because in this case I can agree. However, far more commonly unnecessary effort is spent on making generic code when a solution only targeting for the specific problem in hand would suffice. Then later requirements change or your original assumptions turned out to be wrong, and you need to spend time changing the generic solution to fit the new problem. This can require 10x the effort vs. just appending the specific and simple solution.

I think most podcasts post the exact same episodes to all popular platforms. Some may have an ad-free version on Patreon.

With Spotify, it's sort of similar to when the paid YouTube (Red/Premium) became a thing. Yea, you'd get rid of the Google-picked ads, but the in-video sponsored ads added by the video creator would still obviously remain.

Well, Spotify does some of that as far as I know. But I'd never switch to playing my podcasts there just out of principle (even though I pay the subscription too) because I don't like how they are trying to build a walled garden for podcasts and kill RSS as a thing.

A direct link to the folders: https://github.com/react-icons/react-icons/tree/master/packa...

That's how Git submodules [1] show up on GitHub. I didn't actually know the project was using them. Interesting. As far as I know, this is an ideal use case for submodules, yet at least I've rarely encountered them in the web dev scene for some reason (well, IIRC there are some gotchas).

[1] https://git-scm.com/book/en/v2/Git-Tools-Submodules

React-specific: https://react-icons.github.io/react-icons/

The components look really good but I don't quite get why the instructions make you create a new Next.js app? I understood this would work in any React app/framework and doesn't have any opinions on server-side rendering etc.

Bad timing on the New page, I guess. Also, after posting, a couple of days later I realized there was already another PWA for this [1]. I'm glad I didn't find it earlier though so I wasn't discouraged to build my own. I'm glad my implementation handles a certain edge case better I realized: sharing from Spotify doesn't result in a `"null"` title but `""` instead.

[1] hn-share.now.sh

Yup, but see my original comment and the PWA page for why that isn't really satisfactory on mobile.

I don't fully understand how this is supposed to be an alternative to Tailwind while not providing utility classes out of the box? Did I miss something in the docs?

To me the biggest benefit of Tailwind, apart from the great base design system, is not needing to come up with class names for 99% of the things in the app. This is of course only possible when you have some way to abstract components out of the reused parts of your markup – e.g. you're using React.

Edit: The title was "Open Props: Tailwind Alternative from Chrome Dev Team" when I posted this comment.