I mean insanely more complicated than jails, not insanely more complicated than other standard VMs. Have you used jails? I was on a project to deploy Docker instances on a large scale, and it took me 6 months to create an infrastructure that could have been done in 1 month with jails. I will agree that Docker has some nice abstractions, but the details and special cases and workarounds were endless. And I still don't see the actual advantages over FreeBSD. There's simply nothing stopping one from creating a few shell scripts to spin up thousands of BSD jails, mapping drive storage and networking however you want. A lot of this stuff the Linux guys are thumping their chests over now was in mass deployment over a decade ago in certain BSD hosting companies.
Yes, that's a good start, but remember that Docker also has a... social landscape I guess we could call it. There's a central website and blog, and then there's the all-important Docker Registry where you can search for existing images, and build your own images on top of base images you download. And Docker has a built-in feature to fetch images right from the registry. Makes it very easy to experiment and toy around with images.
Docker made these seemingly superficial things priorities from day one, sometimes at the expense of good architecture and security. For example, earlier versions (as of 1.2 AFAIR) did not have an easy way to delete built-up cruft from images you had imported.
So the challenge would be to accomplish these benefits without some of the huge gaping security/stability/malware holes that Docker has had to deal with.
Sounds like a thing that needs doing. Where do we start?
So what we have is an insanely more complicated way to manage your "VM-ish" things, a really, really odd way of approaching your containerized system where it doesn't actually get to have a full userland (no SSHd, etc...) unless you do all sorts of insane tweaks (believe me, I know because I spent the better part of last year doing this), and in the end the only real advantage of Docker over jails has nothing to do with the intrinsic design of the system, but the build infrastructure surrounding it?
That sound about right. All FreeBSD needs to compete with Linux containers is an image repository and a Git-like method for managing and building images. There are already tons of jail management tools for snapshotting, migrating, moving, templating, etc... And given that jails have a much longer history and are likely to be much more stable and easy to manage, it seems like a natural next step, BSD guys. Hint, hint...
Of course you have to have built on things throughout your career TANSTAAFL and all that. Point being, think strategically. Play to your strengths and to the true underlying needs you can meet, rather than chasing after the hot new technology trend that can have you chasing your tail.
But age is not the whole story. I didn't become any kind of developer until around 33, and certainly had no serious understanding of databases until my late 30s. And yet, here I am, a very much in-demand expert.
Bingo. The real key is to go deep on something and specialize. As a web application developer approaching 50 who did a lot of database work, I realized I had put serious time into learning the ins and outs of the relational model, SQL, business rules thinking, etc... and I had also put lots of time into understanding Linux. Turns out database and Linux skills are in high demand. So I've dropped most of the web app programming (Honestly, in that domain you are competing with a worldwide talent pool, most of whom are willing to work cheaper than you) and really strengthened my enterprise database skills. I now do PostgreSQL consulting almost full-time, and really it is a pleasure to do more serious knowledge work instead of constantly scrambling for scut-level web application work.
Also as you age, put more time into the things that change least. SQL isn't going away anytime soon. Ditto for Linux. Web app frameworks change every freaking *year*. Leave that stuff to the young guys.
How do OIDs solve this? Updating a record it still updating a record. OIDs don't magically make that problem go away.
One solves this problem the way one solves any other data problem: logical thinking and planning ahead. If you are creating a long-running business application where things like addresses may change, you design your database to take that into account. You store a timestamped address with every order record, or you store multiple addresses by date range. It's not exactly rocket science.
There is literally no reason to use OIDs except as a crutch when one has created a table without a primary or candidate key--and even then OIDs won't save you from bad logic, such as duplicate records or other idiocy.
BTW, it is important to also remember that OIDs are not enabled by default for new table creation. Many times the PostgreSQL core team has discussed whether to deprecate OIDs completely. The decision was made to keep them for two reasons: a) some applications still depend on them, however misguided their reasons and b) Some PostgreSQL add-ons and external solutions (replication, etc...) use them.
I wouldn't even recommend bothering with hstore. There are several even better ways to use Postgres in a "NoSQL" setting.
For example there is the Mongres project, that lets a PostgreSQL database emulate the MongoDB protocol. So you could literally drop Postgres into a Mongo-powered application with not a single hiccup, and get a) better performance and b) all the back-end relational stuff you need when it comes time to do reporting or other business logic.
There's also the new JSONB datatype in PostgreSQL 9.4, which I would recommend over hstore if you want to just store "free-form" data in records.
EnterpriseDB did a very well-thought-out study on PostgreSQL/NoSQL.
That's not even close to what "referential integrity" means. In fact, it could be used to accomplish quite the opposite.
OIDs are one feature of PostgreSQL that should be buried inside the implementation and not allowed to be accessed from the developer side. Otherwise you are pretty much completely going around the whole point of the Relational Model. If you are developing an application in such a way that it needs pointers to rows, you might as well just store data on the filesystem and be done with it. Or use one of those fancy NoSQL thingies and enjoy your data corruption.
"Lifting heavy" is relative to one's capabilities, genetics, age and so on. I don't mean you should lift beyond capacity to control a weight or keep proper form. And, lifting light is how you repair joints, IMHO. If there are joint problems, start light, do high reps, slowly and carefully focusing on range of motion and keeping joints seated right. Then as the body begins to adjust, gradually add weight, but never to the point that you are sacrificing form. Also, lifting heavy is only a small component of good fitness. Other sorts of high-intensity work (like rock-climbing, sprinting, swimming) help round out the picture, and I think even low-intensity exercise (long walks) fill out the picture completely. That which is highest intensity should be done to shortest duration.
Some people don't add a lot of muscle mass, but small gains are still gains ( Usually offset by fat loss, making the subject think nothing's happening). If you are adding strength you are going in the right direction.
Really, I have to remind myself often that most people (even slashdot nerds) are simplistic binary thinkers. They latch onto a certain way of looking at something (ooh, I'm all sciency!) and try to hit everything with the same hammer.
What we are having here is not a scientific study. Nor is it a debate. What we are having here is a discussion. This being a discussion forum. When I bring up something anecdotal, it doesn't mean I am basing a decision or opinion purely on that anecdote. It just means I find it interesting and possibly indicative of a truth. I look at all sorts of anecdotes around me, I look at scientific studies, I look at statistical reports (statistics alone are not science), and I also like to use logical inference when I examine ideas (again, this is not science). When a broad preponderance of different types of evidence points me in a certain direction, I tend to give it credence. It's not an absolute, any more than science itself is a set of absolutes.
Here's an example of empiricism: every damn person on the planet knows that if you want to strengthen a muscle, you have to exercise it, and in general the more intense the exercise, the greater the gains. Of course there are limits after which too much exercise will be counterproductive, blah blah blah, but the core truth is there. Don't need a scientific study to prove that. It is part and parcel of everyone's experience, just like everyone knows you have to breathe in order to stay alive. When the variables get more complex of course it's not always so clear, but one has to be a particularly obtuse person not to agree that in general exercise leads to better health. By logical inference, better health would obviously lead to the likelihood of living longer. Where scientific studies help is in identifying just what the upper and lower bounds are to these benefits. But I'm not here to do your work for you. I'm just shooting the breeze on a Sunday afternoon. If you want that sort of information, complete with box plots, scatter charts, and explanations about sample size and selection bias, well you have access to the same information I do. Get to it.
My overall takeaway from years of reading on the topic is that variety is key. Note that the cardiologist wasn't saying "only lift heavy", but just saying that it's a "should" (I.E. make it part of your routine). If you never lift heavy--as in pushing your body up to and past plateaus--your body never experiences certain types of hormesis. And heavy is relative. I wouldn't recommend some 70-year-old woman be deadlifting 300lbs, but there should be a certain amount of strength exercise that actually...exercises the muscle instead of just fatiguing it.
My routine is a combo of calisthenics, weights, general outdoor work (living on 2 acres), running on occasion, and sprinting on occasion. Let's just say my health and mental attitude have seen an absolute turnaround from the age of 45-49 as I implemented all this. Currently deadlifting up to 345lb and I can tell I'm nowhere near my limit yet.
No. Hell no. You don't understand empiricism at all.
Exactly what anonymous said. Anything can be overdone, and this tends to happen when people go on crazes. The jogging craze was last generation's example. Jogging can be an excellent part of an exercise regimen, but when you do it to the exclusion of all else, for 2 hours a day... you're courting disaster. Ditto for the current "crossfit" craze, where people with zero experience are jumping around in the gym, lifting (or even throwing!) heavy weights with zero ramp-up and zero instruction on good form, and once again you're courting disaster
And how does this have any bearing? I was responding to a claim that any lifespan gained would be spent in exercising. Which isn't the case unless you are way overdoing it.