mattdawson

I honestly don't mean it as any kind of personal slight or insult. My apologies that I came across that way. (I'm tempted to edit the OP, but won't for clarity purposes.)

For what it's worth, I acknowledge that many/most of these are indeed applicable to all people. I know you're not asking for this, but the points that jumped out at me as possible opportunities to highlight challenges specific to a wider group (most pertinent bits highlighted):

* Figure out the financial plan. I.e. Do you have enough money in savings, do you have friends/family who can provide seed investment, can you bootstrap, can you reduce your spending and save enough give yourself 6-12 months to work on your idea?

* Often times there are hard barriers preventing people from starting a company. In these cases my best advice is to move to a tech hub (preferably the Bay Area) and work for a tech company until you can save the money, make friends with the right potential teammates, or discover the problem that you are passionate about.

* Producing results isn’t necessarily how you move up the corporate ladder. Internal politics are usually as important, if not more so. <- Noted since it's often more than politics.

Yeah, that'd be fine - if they worked for all people.

The lack of even a nod to diversity issues (race, gender, class, etc.) that the tech industry is dealing (or not dealing with) is tone deaf and insulting to the extreme.

I'll consider myself lucky if I get to work on a project that only creates 49 regressions in 4+ years (which appears to be how far this changelog currently goes back).

> I can't imagine how I would construct a scene with a gold/white dress and then take a picture that looks like the one in the OP

I can. To me, this initially looked like a situation where the background is lit with incandescent bulbs with the dress being in sunlight. In a photo where you have parts of the scene that are lit with incandescent bulbs and other parts are lit with sunlight, correcting white balance for the incandescent part of the scene (yellow -> white) will make anything that's white in the sunlit part of the scene very blue. That's what I was seeing here.

I have, and I'd even be up for using it on a production project. I'd go so far to say I like it even. But the fact stands that the current project I'm working on has a Gruntfile that just flat out wouldn't work in Gulp - which is a combination of things that I'm doing that don't have an analogue in Grunt, likely mixed with a few that I simply wasn't able to figure out.

If Grunt makes sense on some projects, and Gulp makes sense for others, why the need for all the value judgements? I still stand by the assertion that such claims add nothing to the conversation and muddy the waters for everyone.

Yeah, but it's also trivially easy to wrap a 3rd party task in your own task and munge the config at run time. (I'll admit that that pattern didn't become apparent to me until after using Grunt for some months, but once I saw you could do that, many things that seemed onerous got easier.)

I practically live and die by the 5 Minute Rule, and as a counterpoint, I've always found Grunt intuitive, if verbose. In particular, I love that its files API is so flexible. I frequently find myself asking questions that look like "I wonder if I can do this X way", and things just work.

Saying Grunt is "very bad" is harsh and only serves to amplify hyperbole that causes much of the churn around JS tooling.

[edited for a grammar nitpick]

"One of the reasons I wrote that post a year ago was that I had to own up to the fact that we looked better than we actually were."

How very un-Internet-y of you. :)

I think you underestimate the extent to which SXSW has gone mainstream. There are likely a lot of conservatives who deplore Snowden's actions participating in SXSW.

Totally agree with the "might me good for maintenance mode" sentiment. I'm working on a pre-1.0 project. I'm thinking about the few commits where I was first implementing localStorage caching. Tons of files were effected on each commit. If there was a particularly tricky line in there (there were several), how would I have specified it in a commit? That'd be extremely hard to read when compared to the alternative of putting the comment above the code.

This is most definitely not git flow. Git flow advocates explicit merges pretty much everywhere with no fast-forwards and definitely no rebasing.

No, it actually does both - which is why I was so interested in it initially.

from the above link: "generates code to be used to easily build RPC clients and servers"

TBF, I haven't used it as a developer, but I did contract work with a company that had invested in it heavily. From what I saw of their workflow, it ended up being a pretty nice bootstrap tool and little more.

edit: Oh, I see what you're saying. Yes, you're correct - thrift does not wrap existing APIs.