"Cyanogenmod is in many was less customized and more like stock Android"
So not stock Android, eh? What was your point again? I'm consistently impressed by the amount of whining that happens here these days. Years ago, we used to whine about things that were actually significant to professional developers, not whiny users whining about their phones.
Isn't it the big two? Android or iPhone? So why not just get a Nexus 4 or 5, unlocked, nice and cheap? Root it, and you're done.
The definition of gaming as a hobby is not, "Gaming where ever, whenever you like, however you like."
I remember hearing that back in the mid-80's. May I introduce you to bubble memory?
Hmmm...here in Tokyo a lot of the power is coming in through overhead lines. Our building gets fed off a pole and we haven't had an outage in years. That includes during the multiple typhoons that come through every year. They tend to insulate the wires and wrap them with steel cable here, though, so maybe that's a big difference.
Skynet begins to learn at a geometric rate. At 1:35 A.M. Eastern time it runs out of disk space and crashes horribly
Most of the answers to your questions are "it depends" I don't understand what you mean by a "software shop" - is this a consulting company, a company that produces a large scale product, a company that produces a small product, an online service or what?
Your ratio of junior to senior developers depends on the kind of product you're producing. If you have an application that has a big, overarching architecture and then lots of relatively simple modules for specific cases, you want many junior developers to pound out those simple modules (e.g. different types of data entry screens).
Coding standards and standardization are always good. For a small shop you're best off looking around for one that you like and adopting it rather than trying to make your own from scratch because it is not a revenue producer and you can burn endless hours in meetings arguing about spacing, comment style, etc. Make an executive decision and move forward.
Tools and languages, again, it depends. Use the right tool for the job.
Since you don't know any of these things or how to make the tradeoffs, what you need is to hire a director of engineering who does because if you try to hire some developers and apply the vast depth of wisdom that you've acquired from this thread on Slashdot you're probably going to fail miserably.
And there's nothing in North America except trees and savages. What a short-sighted view you have.
There's a lot of value in having humans along. Currently, launch costs are so high that the costs of bringing along the life support for humans is prohibitive, but if it got cheaper many things would work better.
Consider Philae - if it had landed a few meters in another direction it would still be working. If it had been a manned expedition, that wouldn't have been an issue.
Or look at the Mars rovers. Great stuff, but there's little ability to improvise. Think up a different experiment you want done? Well, it'll have to wait for the next rover because that one can't do it.
Uh no, the Linux kernel is monolithic because it runs the drivers as if they were a part of the kernel rather than running the drivers as separate processes.
That's such bullshit. We didn't understand the atom until a little over a century ago. Quantum mechanics even later. Just because it's been thousands of years and we haven't figured something out doesn't mean that it's unknowable.
It isn't in the actual init system, it is an optional daemon that uses the interfaces that systemd exports so there is nothing that actually forces anyone to use it. My Debian based firewall runs systemd with unbound without any problem.
Did it actually not boot or did it seem to hang and the guy resets it after a minute? I ask because my PC had exactly this problem. Ages ago I had a drive die in my system so I pulled it but missed one of the references in
The systemd update a few weeks ago finally gave me a nice message on console to let me know that one of my fstab entries was timing out so I checked, found the entry and now everything boots faster.
And the criticism from those who are against systemd is extremely important to consider. The complaints are very sound, from a technological perspective. They're also based on decades of real world experience, which just cannot be ignored.
I'm not a total fan of every design feature of everything systemd has done but gave you actually read their supporting references? I'm most of the cases boycottsystemd has rephrased events to make the systemd folks look as bad as possible in ways that would make a Fox news reporter feel proud. A good example is their comment about requiring "bug for bug" compatibility with glibc was instead a use of a certain non posix flag needed for thread safety and complaining that it is tightly tied to Linux is about as helpful as complaining that udev is tightly tied to Linux.
At any rate, I find it very telling that they don't actually mention any of their supporters.
Or Greeks, I guess? Or the tons of other countries in which octopus is not an exotic food?
Intel CPUs are not defective, they just act that way. -- Henry Spencer
