uptownJimmy

10 ms·

61.
by uptownJimmy 10y ago
This is definitely a stumble for Apple, that much is beyond debate. But as someone who uses both 2012 MBP and new HP Win10 laptops every day for work and play, let me say this: the Windows world might seem suddenly enticing, but you will NO
62.
by uptownJimmy 10y ago
Yeah. It's just a matter of time before that disc at C6-C7 vertebrae slips a bit and you're in agonizing pain for months.
63.
by uptownJimmy 10y ago
Facebook tweaks its algorithms constantly. Facebook's algorithms tweak the algorithms constantly. This is just PR fluffery.
64.
by uptownJimmy 10y ago
Any website that blocks me for using an ad-blocker will never see my eyes again. End of discussion.
65.
by uptownJimmy 10y ago
Bravo.
66.
by uptownJimmy 10y ago
I assume that this is the same issue that plagues the (mostly younger portion of the) dev community these days: there is a LOT of code out there that is simply not visible to us in the way that an NPM module is visible. There is so much app
67.
by uptownJimmy 10y ago
Rails is several percentage points more widespread than Django, but far from any order of magnitude.
68.
by uptownJimmy 10y ago
I think Rails might be a framework that nobody complains about, in the mid-term future. It is showing signs of age. And, though I say this with strong respect in my heart, the Rails governance is as opinionated and inflexible as the framew
69.
by uptownJimmy 10y ago
But I see your point as being precisely backwards: it's the JS crew who constantly evangelize for their way of doing things, and that way of doing things is completely inappropriate for anyone who isn't already expert. "Choo
70.
by uptownJimmy 10y ago
It is one of my most cherished professional goals to avoid ever working with people who think like this. The message this sends to junior devs is so backwards and wrong-headed that it defies discourse.
71.
by uptownJimmy 10y ago
Speaking only for myself, a middle-weight .NET dev who was, not too long ago, working desperately to find my footing in all this: 1. I think the learning curve to doing good work with Node is really shallow at first, and then it quickly get
72.
by uptownJimmy 10y ago
Orwell was the better writer, Huxley the better prognosticator.
73.
by uptownJimmy 10y ago
It makes me feel a little ill to think of all the new-ish devs jumping on the Node train, thinking it's the Next Big Thing in server code. It's a cool technology, and incredibly easy to get into, but then the curve gets so very st
74.
by uptownJimmy 10y ago
My point is this: I am willing to bet that none of those companies are using Node throughout the larger portions of their code bases. Perhaps in parts of their code bases, where they can afford to try new things, sure, but not in the larger
75.
by uptownJimmy 10y ago
I listed some reasonable questions just above this post, and I still don't have a good answer from anyone: what's the current list of apps these companies are running on Node, how special-case are they, how happy are these compani
76.
by uptownJimmy 10y ago
That Quora post perfectly illustrates my confusion with all the claims about Node: every example of Node usage there is 3 to 5 years old, as far as I can tell. I'm really interested in what large-scale production apps, commercial or in
77.
by uptownJimmy 10y ago
Good point, and I've seen this stuff referenced before, so perhaps my comment above is a little over-stated. But my confusion remains: how big are all these Node apps, what are they being used for, how robust have they proven to be, ho
78.
by uptownJimmy 10y ago
Help us out, those of us who remain unenlightened: 1.which app(s) did Walmart build with nothing but Node on the back end? 2.How has it worked out? Are they happy with that software? 3. Any internal plans to rebuild with something else, or
79.
by uptownJimmy 10y ago
No big corporations are building their apps on Node, I think was his point. And he's right.
80.
by uptownJimmy 10y ago
Node isn't "killing it" anywhere, as far as I can see. It's a special-case technology being touted as competition for proper server-side languages, but in reality it is poorly-suited for the job. There's no valid r
81.
by uptownJimmy 10y ago
Total agreement. The suite of tools is, for me, a no-brainer. I'm happy to pay.
82.
by uptownJimmy 10y ago
And then the teenager grows up and becomes an "old person", at which point we'll see them on Facebook.
83.
by uptownJimmy 11y ago
So nice.
84.
by uptownJimmy 11y ago
I'm a technical college graduate, so I have no pretensions about this stuff. But I view the bootcamps as part of the current frothiness and dysfunction around front-end development in general. The idea that one is prepared to grapple w
85.
by uptownJimmy 11y ago
Meteor is pretty unfit for prime time app development. They might one day hoist it over the fence, but for right now it remains a nice idea, I think. For one thing, there were some regrettable architectural decisions made from the start: Mo
86.
by uptownJimmy 11y ago
I did a cursory survey, and saw that remote Django jobs existed, but I didn't do any due diligence. I figured I'd learn the stack first. ;) My rough impression is that Rails remote jobs are relatively thick on the ground, but that
87.
by uptownJimmy 11y ago
Absolutely in agreement. I am 2 years into my app dev career, all of it spent pushing .NET around in the enterprise. But I need to expand my skill set, I need to continue working remote, and I'm interested in OSS in general. Honestly,
88.
by uptownJimmy 11y ago
anecdotes != data;
89.
by uptownJimmy 11y ago
I totally get it. And it's a needed effort. I think I just didn't type my response politely enough.
90.
by uptownJimmy 11y ago
Dan: I did not mean to offend, truly. As someone who has been working in this field for only ~ 2 years, it's just still kinda surprising to see such a thing. I wasn't sure at first if it was serious. But I also understand the real

More ›