Dunno why this was moderated 0. It's fairly sound advice. At the age of 45, I lost 40 lbs this way, going back to the shape I was in my 20s, even though I did not put forth any effort to restrict or count calories, and I only exercised 15-20 minutes a day. Everyone I know who has done this has experienced good results. I will say that I think different people have different ratios of the above that are optimal for them. Some need more meats and fats, others need more vegetables and fruits.

It's a variation of the old Atkins diet, now called Paleolithic, or Primal, or "whole foods". I think it is just a question of connecting the dots: for most foods, do what involves the least amount of change from the natural state and you are likely doing what is optimal for the body. Get away from the industrialized food chain as much as possible. Why buy vegetables that might have been picked two states over, endured a train ride and a truck ride, then packaging and setting on a cold shelf for a week when you can go to a farmer's market and buy something that was picked today or yesterday? Why buy orange juice that has been sitting in a vat for 90 days, denatured of all flavor, then has flavor added back via industrial "flavor packs", when you can buy fresh oranges and juice them yourself? Or better yet, just eat the oranges. Why buy meat that has been raised in a completely unnatural state from what the animal has historically experienced? (Cows are not naturally grain eaters).

For the most part, the only type of food processing that I think does make sense is the ancient fermented food arts, which led to cheeses and various types of fermented vegetables, which have been shown to beneficially affect gut flora.

Currently using FreeBSD (in the form of PCBSD) on my home workstation. It works quite well with the latest KDE, Firefox, Thunderbird, LibreOffice, etc... Nvidia card gets perfect 3D acceleration via the FreeBSD driver, audio works great (I much prefer FreeBSD audio to Linux audio).

Also using FreeBSD on my cloud hosted webserver: one main instance of FreeBSD hosted via KVM, running several jails, so I essentially get VMs inside my VM. Performance is great, and I sleep much better at night managing a FreeBSD server than any standard Linux distro.

Keylime Pie

Having a truly open source (and community developed) fork is one of the main reasons, however we actually have been developing features independent of what oracle does. Pretty much the entire MySQL optimizer team left Oracle and moved to the MariaDB project. They took the time to fix subqueries so they were actually usable and improve many other features. Take a look at the comparison:

https://kb.askmonty.org/en/mariadb-vs-mysql-features/

https://kb.askmonty.org/en/community-contributing-to-the-mariadb-project/

We (yes, I work for the project) are always looking for new contributors. There are lots of exciting things happening right now.

Possibly Dark Angel?

I'm not a filesystem expert, but this is what I believe they are referring too: http://en.wikipedia.org/wiki/Log-structured_file_system

Not only more nutritious, but it makes them taste better. Although, for the eggs, you should say "pastured" rather than grass fed. Chickens will eat a certain amount of grass, but they are more likely to eat seeds, small leafed plants, and of course, insects. Best bet is to have the cows mow a field and leave droppings everywhere, then rotate the chickens through to rake through everything, eat the bugs and disperse the cow droppings, and then maybe some other animal like pigs or goats.

For me, there's no denying how much better I feel when eating grass-fed beef, fresh pastured eggs, and unpasteurized grass-fed dairy. Proteins and fats are the body's energy powerhouse. Add to that mix some fresh greens (and reds and oranges) from my garden, some herbs, and some fresh local bee honey, and I'd be happy to never set foot in a supermarket again.

Add to that list of links http://www.polyfacefarms.com/ about a farm that has been using polyculture, pasture rotation and natural symbiotic methods for decades, since before all the current organic hoopla. Owner Joel Salatin achieves almost an order of magnitude more return per acre than than monoculture farms in the vicinity, and has much better soil conditions. There are lots of Youtube video interviews with Salatin, BTW, if interested.

The biggest mistake made by farmers in the Western world is to isolate conditions and *think of them* only in isolation. If you decide you only want to be a corn farmer, or a hog farmer, you end up missing some incredible advantages that could be had by farming both at the same time, using one to feed or fertilize the other. Then, if you add a few other judicious crops and/or livestock to the mix, you have even more opportunity for capitalizing on the interactions. Of course, this does take more planning and forethought, but isn't that why we humans have the big brains?

Not only that, but the chickens and goats are full of shit, which is a good thing. Since moving to a place in the country where I have a 1-acre field and a small barn, I started raising a few chickens and goats. I find that each year, I get slightly better soil from the field, some of which I scrape and use for my garden, and thus each year I get a little more produce which I can feed back to the animals. Trying to work toward a self-supporting system where I don't need to bring in any outside feed... 50% of the way there already. Such an environmental disaster... I should be ashamed of myself.

I would challenge you to read up on Joel Salatin's methods (http://www.polyfacefarms.com/). He has run a successful farm with pastured cows, pigs, and chicken for generations. They bring no feed, seeds or fertilizer onto their land. Just using the natural intertwined capabilities of the various animals with rotational grazing, they have actually made their land much more fertile than any surrounding monoculture farms. Tell me exactly how this taxes the ecology. The fact is, local and grass-fed can be done. It just requires a longer view toward farming, and of course a willingness to fight the bureaucratic morass that is our current food system.

While there is no "sell all" feature, they have added a nice solution to your problem. You can now "star" or "x" items. There is no added functionality besides the visual indicator but it makes it easy when going through the vendor to quickly sell all your X'd items. I star my important, must keep items and then during downtime (waiting on co-op buddies) go through and X anything I want to sell.

Kludgy? You must be talking about MySQL's "solution". The one that is not really truly transaction-safe, nor dependable. I can't tell you how many times I've logged into a MySQL server in the morning only to find replication broken.

Native replication has been available for almost two years now. The fact that it uses the write-ahead log in conjunction with streaming is exactly the kind of solution you need if you want dependable transaction-safe replication. I suggest that PostgreSQL took longer to achieve built-in replication precisely because they chose not to kludge it.

Materialized views? You mean you can't figure out how to use triggers and rules? it's all there for you. Triggers or rules give you the ability to specify exactly how the materialization works, including such things as spreading data over multiple tablespaces and partitions for performance.

Core business-friendly features like foreign table wrappers, nested transactions, windowing queries, table partitioning? Check to all those. The only major ones I can think of are multi-master replication and OLAP, for which you do have to go 3rd party. IMHO multi-master replication is one of those things that is very hard to get right no matter which DBMS you use (MySQL's MMR is a cruel joke). Generally it should be avoided unless absolutely necessary. Much better to have robust, well-understood master/slave failover with beefy machines (cloud serving can actually help in that regard) than complex and fragile multi-master with many smaller distributed machines.

Yes, there are all sorts of interesting strategies you can employ once you separate the physical storage from the logical presentation... can't be said enough.

Unfortunately, I haven't found a really good guide of the type you are looking for. I can give you my experiences, going from MySQL to PostgreSQL, back to MySQL to support it at a large company, and then back to PostgreSQL. Generally, these days there is really *nothing* that I can find about MySQL that can't be done better in PostgreSQL. I mean it. At least for awhile MySQL could boast of native replication, but Postgres biw has that and it is arguably much more robust than MySQL's solution (had the misfortune to support MySQL replication for 2 years). Ditto with full-text indexing, and just about any other MySQL feature.

Main differences:

1. PostgreSQL is much more "correct" in how it handles data and has very little (essentially no) unpredictable or showstoppingly odd behavior of the sort you find in MySQL all the time. Your main problem in migrating an app to PostgreSQL will be all those corner cases that MySQL just "accepts" when it really shouldn't, such as entering '0000-00-00' into a date field, or allowing every month to have days 0-31. In other words, PostgreSQL forces you to be a lot more careful with your data. Annoying, perhaps, if you are developing a non-mission-critical system like a web CMS or some such, but absolutely a lifesaver if you deal with data where large numbers of dollars and cents (or lives) depend on correct handling.

MySQL has provided for a fair amount of cleanup for those who enable ANSI standard behavior, but it is still nowhere close to PostgreSQL's level of data integrity enforcement.

2. MySQL has different table types, each of which support different features. For example, you cannot have full-text indexing in InnoDB (transactional) tables. PostgreSQL has complete internal consistency in this regard.

3. MySQL has an almost entirely useless error log. PostgreSQL's can be ratcheted up to an excruciating level of detail, depending on what you want to troubleshoot. Ditto with error messages themselves.

4. MANY MANY more choices in datatypes and functions to manipulate them. Definitely a higher learning curve, but worth it for expressive capability.

5. Don't get me started on performance. Yes, if you have a few flat tables, MySQL will be faster. Once you start doing anything complicated, you are in for a world of pain. Did you know that MySQL re-compiles every stored procedure in a database on every new connection? PHP websites with per-page-load connections can really suffer.

6. Don't get the idea that PostgreSQL is more complex to work with. If you want simple, you can stick with the simple parts, but if you want to delve into complex database designs and methodologies, PostgreSQL pretty much opens up the world to you.

- Glad to be back in the PostgreSQL world...