Which in itself isn't an unreasonable position. Complying with the law isn't optional just because it happens to make an otherwise extremely profitable business more difficult or expensive to run.
What we should be doing is going back to first principles and asking what we're trying to achieve with the kinds of restrictions that IP laws impose, and what sorts of trade-offs and incentives are in the best interests of our society overall. Laws that serve those purposes should be kept or introduced as necessary, and everyone should comply with them. Laws that no longer serve those purposes or perhaps never really did should be removed.
I didn't want to be a dick, and milligram seems like a nice minimal grid which I don't think we have enough of, but it serms like they changed .btn-primary to purple and shipped skeleton.
It does seem so, but Milligram seems a lot more usable. It's written in sass and everything seems nicely organised. Skeleton is just a single css file.
I like skeleton. It has been ported to sass as well.
> it seems somewhat dead
The beauty of skeleton is that it still accomplishes exactly what it is meant to, without needing attention.
To be fair, it is only html and css, so there aren't huge security concerns or dependencies like a big project would have. But that is the point. You can make a super quick website without using a bootstrap and it is very logical and minimal.
That's true, but there are lot of issues and even PRs that IMO should be dealt with/merged.
Forms are another thing. They are a pain and it's useful to have something like this to form a base. But what if you only want the forms aspect and not the rest? Seems like you could do that with Milligram but not Skeleton.
Incidentally, I have been playing around with the concept myself (client work) and it turns out you can hack a semi-working solution in just a handful lines of js:
The one I posted is (mine and) amateur, don't use it.
It will probably be around for 5 years, but is not undergoing active development, and it was a side project I worked on for funsies (I may come back to it one day, and it's kind of a leave-it-be project, especially without 100s of users).
Please refer to the other ones for a serious (or at least more well thought out) solution.
The idea that rebuilding from disaster generates jobs doesn't require a mention of the Broken Window Fallacy. No one is creating the disaster with the aim be 'generating jobs' or attempting to argue that the disaster is a good things because it creates jobs.
