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.

With a ZNC bounce, a simple ircd server and 5 minutes you can avoid paying for communication and keep your company chat logs secure and on your own infrastructure.

Having watched a coworker spend a solid week getting our company's ircd setup (and this was our VP of Engineering, mind you), I've gotta call BS here. Also, until I started using irccloud[1] a few months ago, I was using ZNC, and that's no walk in the park either.

[1] https://www.irccloud.com/

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.

http://thrift.apache.org/

Mediocre Javascript developers are easy to find

FTFY.

In all seriousness, though, I'm the lead developer on a web applications team at a medium-sized client services company and my experience has been that competent JavaScript developers are among the hardest kind of developer to find right now.

> Perhaps you mean the phenomenon of popular artists that are so big that they are household names across all demographics across the globe/nation. If so then your probably right. Probably we will see less new justin timberlakes/drakes/britney spears level superstars, and more local/regional/niche stars.

No, the big artists will only get bigger, because those are the artists that can afford to tour and have the backing of their labels. It'll just be harder for smaller acts to become bigger acts.

FWIW, this is also the way O'Reilly's JS Pocket Reference explains it.

Do you know of any tutorials that follow this "deep dive first" approach? That's exactly how I like to learn.

Yep, me too - it's a known issue. https://github.com/Kodowa/Light-Table-Playground/issues/448

The same is true in Python - in single inheritance cases. (The rules for Python's method resolution order are more complex where multiple inheritance are involved[1].)

1. http://python-history.blogspot.com/2010/06/method-resolution...

Huh. Shocked that the install numbers for vim-nox are so low. That's always been my goto package.

It's been over a year since I had to set this up, but I used HAProxy in a similar setup and still needed stunnel.

In the whole of my DevOps career, getting SSL working with web sockets was one of the most frustrating.

I've looked at Peewee (albeit before the rewrite mentioned here), and, more to the point, my first response was "why didn't he write this in SQLAlchemy." SQLAlchemy is a battle hardened toolkit that's both broad and deep. At its lowest levels, its a toolkit for building ORMs. IMHO, if you're doing SQL in python, there's almost no reason to look anywhere else. That's how good it is.

A little off topic, but forms are a big PITA using Flask and extensions, too. Forms are definitely not a solved problem in the python world.

I don't care how simple a framework is. There are always dusty corners that are hard to understand. There will always be bugs. And the ability to get help from fellow users when you hit those is, in my experience, crucial.

You're only addressing part of the problem. File size is a much easier thin to fix than refactoring DOM bound soup.

> Backbone is all good and well for small projects, but I think it's be best to look elsewhere for larger projects.

This is such ridiculous FUD, and I'm surprised every time I hear it. Compare the apps built with Backbone section of their site against similar lists of any competing framework. There are some seriously complex apps there. More big ones than any competitor.

Just because a framework is minimal doesn't make it ill suited for large projects. That goes for all frameworks, not just js ones. And yet I see this argument trotted out against minimalist frameworks in every language I work in.

I'm using Brunch[1] for a current project, and have used Backbone Boilerplate[2] in the past. Brunch is pretty great, though bbb is better hooked up with requirejs out of the box, if you're into that kind of thing.

I really want Yeoman to take off, in particular because I really want one of these tools to become the breakout hit. I'd rather everyone be focusing on improving one tool instead of all this effort going diffuse across a bunch of different solutions. I'm a python dev, and I thank the stars that pip became so standard. (Not that this is a direct analog to pip, but pip provides a subset of this functionality when it comes to packaging.)

One note: the Ember init is waaaay basic. I know that these are going to be community maintained, but I would have hoped that the Ember generator bundled with this initial release would have included at least commonjs or requirejs integration.

[1]http://www.brunch.io [2]https://github.com/tbranyen/backbone-boilerplate

This toolset has a completely different use case from jQuery Mobile. jQM prescribes that your backend responds with typical HTML web pages. While it's conceptually possible to write an app that loads something like JSON into jQM, it's not straightforward.

This is more of a lower level transitions toolkit - only one piece of what jQM does, and I would imagine easier to fit into your hand rolled js app.