cteague

Agreed on the lean startup principles/short deadline. You've got to get something into the hands of users as soon as possible. You might also want to consider doing some design up front and making a landing page. Perhaps you can gauge interest that way and receive feedback.

It's worth noting here that the issue isn't duplicated css, but duplicated html. Ideally, this is handled by some other templating / component library (e.g. React).

The idea is that if you have `bulletpoint__container`, that's going to be specific to this component only and hard to re-use in a different part of the application.

It seems like Tailwind's main value proposition is that it forces developers to select from a limited, pre-defined set of options in styling which can then be used as building blocks for components. It basically circumnavigates css entirely to the extent the page can be styled using Tailwind's options.

As far as I can tell, it's not really aimed at eliminating code-duplication per se. That should optimally be handled by whatever is generating your components.

This article https://adamwathan.me/css-utility-classes-and-separation-of-... explains it better.

Demand is inelastic? Meh, my brother is living in Brazil and has been using a ton of private healthcare services because it's cheaper. Again, you're engaging in all or nothing thinking. As the price of LASIK goes down, more and more people use it. Americans go to the doctor less because it's more expensive. Healthcare demand is the furthest thing from an 'inelastic'.

Healthcare is bigger than just things that you absolutely need. Obviously, there are those things, but that's what INSURANCE is for. Then, when you are healthy, you can shop around and when insurance is too expensive and has too many items you don't need, you can instead get a barebones plan which would cover the things that you seem to be worried most about.

If a person failed to get insurance, well... that's not good. We shouldn't encourage that as a society. If someone runs out of resources and has to demand it from others, they are a burden and that is bad. If too many people do that, society collapses.

Obviously, there are going to be those people and I'm not saying we shouldn't care for them, but the more we have a socialized system--one that has a shared resource pool everyone takes from--the less efficient it will be because the incentives applying to individual encourage them to use as many resources as possible because they aren't the ones who bear the cost.

You're engaging in 'all-or-nothing' thinking. The vast majority of medical expenses are not like that. And that's the whole point of insurance--to be covered in case something happens so you don't have to negotiate on the spot.

That's like saying we should socialize food distribution because people can't negotiate when they're starving.

Every market has information asymmetry. Software is probably the biggest one today. Yet software keeps getting better and better...

I agree there are needs for regulations--more like proper norms though and a good tort system.

American healthcare is nowhere close to a "free market".

Have you noticed how there are next to no startups disrupting the health industry? Why can't you sign up for insurance like you can sign up for a stock account on RobinHood?

There's no free market. Government licensing and regulations have created huge barriers to entry. I thought this would be more understood by those technically/entrepreneurially minded.

When things are too expensive, you need to raise the supply to get the price down. Not create price controls and socialize markets.

Read this article because it explains the problem better than I can.

https://hbr.org/2004/06/redefining-competition-in-health-car...

Thinking about disabilities that are not necessarily physical such as dyslexia, adhd, and other things that affect cognition--I would say an optimal programming language should be as easy to understand and read as possible. This would mean choosing the style of the language and the syntax so that it optimizes for readability. Also, removing the amount of the context someone needs to understand a piece of code. Perhaps this could be accomplished by strict enforcement of modularity and things like auto-generated or required documentation so that interfaces can be understood without diving into them if possible.

Obviously, inherent to programming is diving deep into chained function calls and managing all those levels in abstraction in one's mind. However, for someone with a limited working memory for whatever reason--adhd, depression, chronic pain, anxiety, headaches and more--having this minimized as much as possible would be a lifesaver.

Many of you are speaking about the social aspects of smartphones and social media, but I think a big issue is also the cognitive impact of short-term gratification due to internet/tech addiction. Happiness often comes from feeling competent. If teens attention spans are dwindling due to this addiction, they are going to grow up without the grit to persist and develop skills.