5 ms·

> [pro tip] Add this code to a new HTML file: > <link rel="stylesheet" href="https://unpkg.com/mvp.css https://unpkg.com/mvp.css"> That’s not a "pro tip"; tha

by hk__2 4y ago

> [pro tip] Add this code to a new HTML file: > <link rel="stylesheet" href="https://unpkg.com/mvp.css https://unpkg.com/mvp.css"> That’s not a "pro tip"; that’s a very bad advice: you should always use versioned URLs. What if I find this project cool; add this URL in my HTML; and then the author changes things in ways I don’t like? It’ll break my website. If I used something like `https://unpkg.com/mvp/v2.3.45/mvp.css https://unpkg.com/mvp/v2.3.45/mvp.css` I’d be sure it wouldn’t happen.

duxup 4y ago
Is this likely to change a great deal? An mvp css? You can always just copy it yourself.
- hk__2 4y ago
  Yes, you should copy it and include it in your project rather than pointing to an external URL.
  - duxup 4y ago
    Generally that’s what I do for consistency for small projects / sites I make so I know I don’t have to worry about it.
andix 4y ago
Embedding external styles may also violate users privacy and may not be okay with the European GDPR. To be on the safe side, you should only load external resources after the user agreed in a consent dialog. Or just host them on your web server!
sockopen 4y ago
To quote further down the page “An MVP is a temporary site, it doesn't have to be and shouldn't be perfect.”
- hk__2 4y ago
  To quote someone else in this thread [1]: "there's nothing more permanent than a temporary solution." [1]: https://news.ycombinator.com/item?id=32808640 https://news.ycombinator.com/item?id=32808640
agloeregrets 4y ago
First thing I saw looking a the site. I was like "This is incredibly idiotic." I'll take a basic tailwind install for this use any day. Not it's not minimal but it is reliable and straightforward for prototyping..
_fat_santa 4y ago
True, but given the use case I think it's fine. Another commenter pointed out that they abuse HTML semantic elements which also isn't great. But if you're using this for the intended purpose (building an MVP app), all those things really don't matter. Sure the next version might break things, but by then you would have in all likelyhood moved on. I use this framework a ton and it's great for things like building an API where you need an absolutely minimal frontend. For things like this I'm already writing minimal CSS, this just lets me slap a one liner in the head and make the frontend look marginally nicer. Issues like the version and semantics are not a concern because the "point" is to build the API and the frontend will get tossed (and yes I realize I can use Postman/Hoppscotch, i use those as well).
awb 4y ago
Hi, author of MVP.css here. Fair point. I’ll update the site soon to explicitly use a version. Thanks for pointing that out!

by hk__2 4y ago

duxup 4y ago

Is this likely to change a great deal? An mvp css? You can always just copy it yourself.

hk__2 4y ago
Yes, you should copy it and include it in your project rather than pointing to an external URL.
- duxup 4y ago
  Generally that’s what I do for consistency for small projects / sites I make so I know I don’t have to worry about it.

andix 4y ago

Embedding external styles may also violate users privacy and may not be okay with the European GDPR. To be on the safe side, you should only load external resources after the user agreed in a consent dialog. Or just host them on your web server!

sockopen 4y ago

To quote further down the page “An MVP is a temporary site, it doesn't have to be and shouldn't be perfect.”

hk__2 4y ago
To quote someone else in this thread [1]: "there's nothing more permanent than a temporary solution." [1]: https://news.ycombinator.com/item?id=32808640 https://news.ycombinator.com/item?id=32808640

agloeregrets 4y ago

First thing I saw looking a the site. I was like "This is incredibly idiotic." I'll take a basic tailwind install for this use any day. Not it's not minimal but it is reliable and straightforward for prototyping..

_fat_santa 4y ago

True, but given the use case I think it's fine. Another commenter pointed out that they abuse HTML semantic elements which also isn't great. But if you're using this for the intended purpose (building an MVP app), all those things really don't matter. Sure the next version might break things, but by then you would have in all likelyhood moved on. I use this framework a ton and it's great for things like building an API where you need an absolutely minimal frontend. For things like this I'm already writing minimal CSS, this just lets me slap a one liner in the head and make the frontend look marginally nicer. Issues like the version and semantics are not a concern because the "point" is to build the API and the frontend will get tossed (and yes I realize I can use Postman/Hoppscotch, i use those as well).

awb 4y ago

Hi, author of MVP.css here. Fair point. I’ll update the site soon to explicitly use a version. Thanks for pointing that out!