vanwaril

If a candidate can be eliminated from consideration because an interviewer marked him/her as a "B", I don't think that's more strongly correlated with innovation than SAT scores and GPAs. It doesn't mean the interviewer is being a good judge of technical chops. And on top of that, the article doesn't say technical skill or ability correlates with innovation, but individual drive. So really, nothing adds up here.

Which is a very valid reason.

My current theory is that this is an arbitrary one. Its really, really, really easy to cross a megabyte with statically linked libraries.

and it also opens it up to a rich set of well-known problems: sharing between processes and memory management, lock issues, system-call latencies, not to mention dealing with the monolithic environments that are almost definitely changing between each instance of your program you want to run (this 'environment' includes the shell, userspace services, kernel version and features...). Decomposing a program into multiple programs isn't always a good idea, there is a very broad trade-off here that needs to be evaluated for the needs of every program.

And why would you say systemd is monolithic? Have you looked at the source-code for it? Have you looked at how services are configured with it? I would argue its far more modular than sysVinit.

Go for it!

What about a trade-off between compound-ness and duration? If you want a 10-minute link, you really probably want something that's dead-simple to say like "zigg.be/fit". If its a 30-day lease, you might be willing to go for "zigg.be/greencatjumps" This allows shorter URLs to stay in a faster reuse pool.