Him: and if it has security what must i do ?Him: what's different ?
Me: depends on the distro
That's the real WTF right there.
Him: and if it has security what must i do ?Him: what's different ?
Me: depends on the distro
That's the real WTF right there.
USE UP SOME DAMN SICK DAYS
Thanks for the definition; this helps a lot. I'm glad to report that we already comply with at least 50% of these requirements.
I've been a regular reader for a while -- in fact, this site is a major inspiration for my enterprise software decision making.
However, I still haven't quite managed to pin down the exact definition for "enterprisey".
For something to be enterprisey, does it need:
1) more support personnel than any non-enterprisey system
2) more moving parts than a comparable system that's not enterprisey
3) a very large number of users being inconvenienced when it fails
4) a high price tag
5) something else
or
6) all of the above?
Honestly, I'd like to know. I'm working with a horizontally scalable database system, but given that it's based on free databases in the bottom and just a single C++ process on top, I'm afraid our system might not qualify for "enterprisey, " so I need to know what we're missing.