nilliams

12 ms·

61.
by nilliams 10y ago
And yet they're still popular, so it can't be that significant of an issue.
62.
by nilliams 10y ago
Yep, all the native toolkits failed, that's worthy of ranting about, but that is not what OP was doing.
63.
by nilliams 10y ago
I don't get this complaint. This site is aimed at developers. I think it's safe to assume they're either not viewing this on mobile ever, or are going to come back and visit on desktop/etc if they actually want to use it
64.
by nilliams 10y ago
> and has a start up of 10 seconds to compile via Webpack serverside, or 18 seconds if we're doing it inline via JSPM, and compiling client-sid That's crazy, you should check you're not running more stuff through babel tha
65.
by nilliams 10y ago
Because the alternative is a complete rewrite, which is usually very costly.
66.
by nilliams 10y ago
The ergodox maybe? Not easy to get hold of though, especially if you want it pre-built (edit: and potentially just as expensive as the HHKB): https://www.massdrop.com/buy/ergodox
67.
by nilliams 10y ago
Those aren't 'options for styling Github', that's just a framework/lib they provide for your own projects.
68.
by nilliams 10y ago
Don't really agree - what they're doing is very different compared to what, for example Ember does (which they call 'convention over configuration'). Next's routing is much more similar to Jekyll's which quite
69.
by nilliams 10y ago
I don't think many have embraced the .jsx extension. And arguably it doesn't make a lot of sense, because when working with most modern frameworks/libs, JSX is not the only non-standard-js element in the file. Should we call
70.
by nilliams 10y ago
Yep I know, I'm specifically complaining about the current trend of casting off old ajax methods/libraries and moving to 'fetch()' polyfills, as currently the 2 main popular fetch modules both recommend 'es6-promise
71.
by nilliams 10y ago
No need to pick on 'kids' from JS thanks, and actually in my interviewing experience a lot of JS devs don't actually know what a closure is. Worrying, but true.
72.
by nilliams 10y ago
In my example I was talking about avoiding es6-promise polyfill in the browser, because of the fact that it adheres so strictly to the spec that it does not have an equivalent to the safety net you give in your Node example.
73.
by nilliams 10y ago
I agree that handling promises should be by default better than remembering to 'if (err) throw err' but my original comment was about how spec-adhering promise polyfills like es6-promise are basically broken because they silentl
74.
by nilliams 10y ago
Agree with digi_owl, this reads like the ramblings of a child. (And it doesn't seem to be the translation).
75.
by nilliams 10y ago
I disagree. A developer choosing to not handle the 'error' param in an error-first callback at all is incompetence from a node dev, akin to writing 'try-except-pass' in Python, whereas silent swallowing of runtime exce
76.
by nilliams 10y ago
Because it's not just an 'ignoring of errors', it's the fact all exceptions (as in actual errors from the runtime) are silently swallowed. In your example, if you typo in that function body, an exception will be thrown,
77.
by nilliams 10y ago
Yes, this footgun is why I've been really wary of the of the `fetch()` plus es6-promise polyfill bandwagon. I've been giving that a wide berth. Examples why: - http://requirebin.com/?gist=8f13d5147c1c252ab1691115bf
78.
by nilliams 10y ago
Could you elaborate on (or link us to examples of) those 'quite a lot of ways'?
79.
by nilliams 10y ago
I don't think people are confusing those things at all. The comment you're replying to is quite literally saying that using $_POST['somevar'] is too easy.
80.
by nilliams 10y ago
Parent did not 'shift the argument to one about typing instead of superglobals-are-bad' as I read it. They said superglobals are bad because they make it too easy to do the wrong thing. And the followup was about how often people
81.
by nilliams 10y ago
You shouldn't be kicking off CI builds based on unpinned deps (unless you're deliberately doing 'canary testing' etc), because of course that will break. The npm solution for this is to use 'npm shrinkwrap' and
82.
by nilliams 10y ago
Yes it claims to provide a lockfile while locks all your deps all the way down the dependency tree. You can do (and are supposed to do) the same with npm's own shrinkwrap, but people claim that it doesn't work as intended.
83.
by nilliams 10y ago
Straw man basically. Developers shouldn't ever be working with 1000 line files, except as build artefacts.
84.
by nilliams 10y ago
The lack of margin on the homepage, highlighted by the 'Take control of your presentations ... ' feels like bad taste, fixing might create a better first impression!
85.
by nilliams 10y ago
Couldn't agree more, this is one thing that Python/PEP8 got completely wrong. (Leading) column-aligned code falls down more-often-than-not in practice and is a terrible reason to sacrifice tabs. Tabs are superior. [0] [0] http:&#
86.
by nilliams 10y ago
Yep this, basically the things gpp mentioned just aren't problems day-to-day for Python developers. And the 'halfway down the 1000 line file' one was just plain silly.
87.
by nilliams 10y ago
> Do I have to require 'rubygems'? >> No. Never. Your code should not expect/require a particular dependency manager But there's loads of code out there that does that. So the answer isn't clear. > shoul
88.
by nilliams 10y ago
Forgive me for a blunt reply to your snarky comment, but this is ignorant hyperbole, and I'm surprised you got away with it on HN. I've never written 'WordPress plugins and themes'. I've worked in C, Java, PHP, Pyth
89.
by nilliams 10y ago
Well you've picked the perfect example where Python's list comprehensions shine, 1 map, 1 filter, 1 'each'. I think your Java example only looks gross because it's using ugly APIs, and isn't indented well, but
90.
by nilliams 10y ago
>> Remind me again why this is killing Django and Rails for mindshare Staying specific to package managers (which the article is about), Python's Pip doesn't have a dependency resolver [0] and Python packaging is miserable w

More ›