deanotron

When I meditate I often combine it with tiny yoga exercises - not formal yoga poses, but just stretching and going where my body wants to stretch. What's funny is that I often find myself in a position similar to Muslim prayer (or, if one were observing from the outside they might think that is what I was engaged in).

[edit] I bring this up because whether engaged secular-ly or not there is something very grounding about the experience.

There is a large difference between the ability to read emotions and "..vicariously experiencing the feelings, thoughts, and experience of another..".

A great salesman can also be sociopathic. We are all salesmen to some extent, so this isn't to denigrate the profession or the ability to read people and use it for personal gain.

I suppose the difference lies in whether what one is selling tends towards symbiosis or exploitation.

I haven't seen anyone mention this but part of the success is that they had git in their name. All social platform successes aside, they had the right technology at the right time.

Before I had ever heard of GitHub, I had seen presentations at the large company I worked for praising git. Git was thrown into the limelight at the same time as subversion, CVS, perforce etc. were being eschewed.

This is true about infrequent updates - it may be more for providing the appearance of total control.

I would love to see a user-friendly universal app for managing static sites (Jeckyl, Docpad) that is something someone of my Mom's tech capability could use. (and let's be honest, WP itself is sometimes "way too much")

I agree that React and all the sweetness it contains does have this effect when working on a large - or simply dynamic - application.

But all of the benefits of the React Virtual DOM don't really come into play if the content is static (like most WordPress sites). If no data is changing, you don't need observables to automatically update views, and the built in underscore.js templating will do a fine job.

HHVM was needed at Facebook because it's a dynamic app with rapidly changing content.

WordPress sites are typically static content that are perfectly fit for static caching with a CDN - it really shouldn't matter how many milliseconds you are able to save on the server if your site is only being hit once every two hours from the CDN.

The 8 million caching plugins are unnecessary when you can just sign up for cloudflare.

Static CMS's are great for personal projects, or very tech-friendly clients, but most clients paying for a website want the ability to manage content in a user friendly way.

I'm sure the vast majority of WP sites have been built for a paying client.

The thing about WordPress is that for most clients you'll likely end up running on a managed WP server like WP Engine.

The vanilla WP environment means goodies like React (which requires V8 to compile on the server) and HHVM are not in the cards. But PHP and WordPress really doesn't need to be fast (just put it behind a CDN).

Isomorphic rendering over the WP-API is all you need - I've had a lot of benefit using logic-less templates like Handlebars on the client and the server.

Exactly - the ambiguity related to what is 'viable' is what allows any first-run product to be called an MVP.

Nobody releasing a product into the wild is going to be 100% happy with every aspect of it - it is then labeled as a MVP.

On the flipside, throwing ideas against the wall to see what sticks may be far too "minimum" in a saturated market.

The viability is what drives the whole concept.

The warnings comparing carbon-nanotubes to asbestos are simply because of the shape of the structure - they are both microscopic needles and our white blood cells don't do a good job of breaking them down.

Not all nanomaterials are dangerous (just as varying sizes of dust are not), but many new materials may adopt unnatural properties that our body doesn't know how to deal with. So there is still handwavyness to it all.