Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Well-designed or not, it exists, and sometimes you just want to use it, without a lecture on how it's suboptimal.


sort by: page size:

You know you wouldn't have to make use of functionality just because it's there, right?

Just because the features exist does not mean you have to use them.

The user isn't required to use it - it's an option

Using it is not mandatory, using it is convenient.

I don't think it's a YMMV thing: no one claims it is useless, in fact, there's several specific examples of it being necessary.

Why not? It's simple, it's efficient, and it gets out of your way.

Fortunately they don't need a strong argument. Convenience and minimized boilerplate suffices.

Because those features are generally safe and unsurprising, people don't need to understand them.

It doesn't need to be popular for you to use it.

Just because you've never dreamed up a situation where it might be useful doesn't mean that they don't exist.

You don't have to learn it, you can just use it.

It doesn't have to be all or nothing. There's plenty of stuff you can reasonably do without significant inconvenience.

Lack of options is 'elegant' and 'just works' and 'for people who aren't nerds'.

Just because you've never had to use it doesn't mean it's useless.

You can come up with these excuses and caveats, but at the end of the day they don't matter.

You don't need it, but it has a lot of little things that you wouldn't implement but since you have them you use.

You don't need a robust definition to implement something practical that deals with the clear cases.

That's fine but it doesn't have to 'take off' everywhere to be useful and interesting

It's not "necessary" - it just is.
next

Legal | privacy