reuser

How do you take away anybody's freedoms without coercion?

Sartre's relevance or value depends on the relevance or value his arguments, not his age or affiliations or sex life. It happens that I think he was full of steam, but it wouldn't make him any better simply to be a woman, or young.

Example of a category error (stolen from Ryle): you are handed both the left glove and the right glove, and you ask where the pair is. The pair is not a separate thing from the left glove and the right glove.

'Category error' does not mean a quantitative or scale difference at all.

More tightly couple your code to Heroku.

There are lots of ways of doing things, and more than a few of them are sensible. Without zeroing in on a specific well-defined problem, you usually won't have any hope of identifying anything like 'optimal' solutions - let alone uniquely optimal solutions.

"user in mind" and "have a real problem" and "get things done" and "responsive design" and "designed for Humans" and "make it happen" and "never compromise the API" are vague platitudes which don't even provide interpretable advice, let alone specific usable information.

It can be slightly obnoxious when a battle-hardened grayhair begins to hold forth on vague general principles in this way - it can still be productive to listen insofar as knowledge is being shared. What information is being shared here, and what experience or reasoning is there to ground it as knowledge?

If you write some gnarly asynchronous GUI code, it is a lot easier to point to why it is nice to have objects.

(And MVC, for that matter).

I think this is part of why objects blew up in the 80s

Maybe one part of the reason you hate them is that they have been associated with so much marketing bullshit and pseudo-religion. It helps to realize that actually there is not one unitary concept of what 'OO' means. You can defeat your object allergy if you stop engaging with people's rhetoric and ideology about objects, and just evaluate particular language features individually.

If the same task can be done with a function/sub or with an object, objects typically add two problems:

1. Added boilerplate: before I do work I typically instantiate an object, etc. In many cases it is really obvious that this is just adding pointless lines of code and pointless plumbing. It doesn't help that the big OO languages have accreted so many bad, verbose coders and cargo-cult methodologies, enhancing the extra-boilerplate effect.

2. Unlike locals inside a function, objects' mutable state is accessible in multiple places at multiple times (and merely using getters and setters does not fundamentally change this - and add even more ridiculous boilerplate of the sort which causes people to have gigantic IDEs writing highly repetitive code for them)

Here's what you are missing: objects are just a kind of mini-program, with a more flexible interface and execution model than subprocesses. It's a generalization of the subroutine and largely equivalent to a coroutine.

Even if that doesn't work for you, they are still handy as 'bundles': e.g. a point in 3-space with x, y, z components AND an attached set of methods for doing normal things like dot products, all passed around together. This isn't necessary, but it can make things neater just like bundling certain wires together into a cable.

Evaluate them like 'here is this thing, what can it be used for?' You might decide you like objects, or perhaps just that they have their place.

Possibly as opposed to 'verbs' (e.g. processes, mutations, transformations, open-ended mappings - descriptions of what is being done)

Personally, I doubt there is a real quality problem with those platforms. But running .NET on those platforms looks unnecessarily expensive to me. If I were married to Microsoft (as SO is) then I would avoid 'the cloud' for that reason.

Given that one wishes to use Windows/.NET, I feel the decision follows pretty naturally from an analysis of costs - no vague argument about culture necessary

You can't really create a massive co-located setup on demand for big jobs, then tear it down ... use the right tools for whatever job you're doing. EC2 being more expensive for your Postgres deploy doesn't mean it is an expensive toy

It's software for everyone, as long as they are people who want to write Java.

That's cool and stuff, but why do I have to write Java?

Gnome shell on Ubuntu is really misleading. On Fedora the support for it is first class so it works wonderfully, out of the box, including features like this.

(I like Unity too, but it needs work on things like multiple monitor support)

I do this on Gnome 3 every day! I have it bound to right-click on the titlebar

Any VPS host, or EC2, will let you run ZeroMQ in whatever way is appropriate to your problem.

edit: and same for if you run your own server or rent a server, obviously

Token economies are as old as the hills. It's also called "secondary reinforcement" - although cognitive psychologists will be bothered on ideological grounds if you reference any psychology from before 1950 or so