nilliams

17 ms·

121.
by nilliams 10y ago
You are incorrect. IE10 implements the wrong spec and it's buggy in IE11. And Edge isn't IE.
122.
by nilliams 10y ago
Flexbox doesn't work in IE. It also doesn't solve the need for conventions around grid breakpoints, when e.g. working in a team. Doesn't come close to replacing Bootstrap 3 (and similar) grid systems IMO.
123.
by nilliams 10y ago
Yeah it's more like the Boostrap 2 grid, which will be a step back for some people used to multiple breakpoints of Bootstrap 3.
124.
by nilliams 10y ago
It only has one breakpoint whereas bootstrap has multiple (xs, sm, md, lg).
125.
by nilliams 10y ago
Do you have any specific complaints with npm?
126.
by nilliams 10y ago
Please don't move to fixtures, your tests are great as-is (thanks for sharing). See my comment above!
127.
by nilliams 10y ago
You should repeat yourself in your tests. See DAMP vs DRY [1]. Also that repetition is valuable feedback that you may have a design problem, that something about your object hierarchy is overly-complex, for example. If you hide it, you&#x27
128.
by nilliams 10y ago
Fixtures are considered an anti-pattern by many as they over-DRY [0] your tests and obscure them by introducing 'Mystery Guests' [1]. [0] http://stackoverflow.com/a/11837973 [1] https://robots.thou
129.
by nilliams 10y ago
Because needing to do something regardless of success or failure is incredibly common (e.g. stop a progress bar, re-enable form inputs & buttons). The (promises) spec is lacking w.r.t. this use-case, and most ajax libraries (and a lot o
130.
by nilliams 10y ago
I tried fetch, the polymorphic-fetch module that builds on this github one and found it doesn't support .finally(), or work with the promise.finally polyfill (yes I know it's not in the spec, but seriously). Also sinon.js couldn&#
131.
by nilliams 10y ago
> WinRT isn't embracing JavaScript because JS is so great, but to make the platform more attractive to web developers. That may be true for WinRT, but I did not mention WinRT. XAML/WPF were around a long time before that. >
132.
by nilliams 10y ago
Windows Forms in not cross-platform. The VS UI to build it is great, but the end result looks dated and only works on Windows. I say the two are comparable because, with talent applied, the HTML version looks better and works everywhere, so
133.
by nilliams 10y ago
>> Probably you are underestimating how complex is to build a GUI for different platforms Presumably you're getting at platform-specific differences. I'd suggest these are no longer as important as once deemed. Pretty much a
134.
by nilliams 10y ago
Sorry, this is just wrong. The time to parse CSS + HTML is negligible and isn't a reason native is better. Native apps have a better foothold currently because mobile platforms had better support for their own native languages, than fo
135.
by nilliams 10y ago
This attitude seems ignorant of the facts and the unfortunate state of desktop development. Perhaps the cancer is the fact the desktop development community has had decades to settle on a decent cross-platform 'native' toolkit and
136.
by nilliams 10y ago
What aspect do you dearly miss? (Honest question, I've never understood the S-expr trade-off, especially if macros are off the table).
137.
by nilliams 10y ago
This is mobile.twitter.com. It's built by twitter's engineering talent.
138.
by nilliams 10y ago
I searched your Medium article for a link to an online demo for Structor and couldn't find one, perhaps that is letting you down. Certainly looks like a promising and very comprehensive project. I'm not using React right now but I
139.
by nilliams 10y ago
On HN you are generally expected to 'get started', rather than insulting projects like that without expanding. I would actually say, though I vastly prefer say Jekyll over WordPress, that generating a static site from a WordPress
140.
by nilliams 10y ago
Same goes for browserify. You can have lots of tiny modules and (watchify especially) is fast to re-build. And yeah perf of 'require' statements at run-time is a non-issue.
141.
by nilliams 10y ago
Just want to be the counterpoint here. I've been building stuff at my last 2 jobs in Backbone (plus good OOP) for the last 5 years, and am only now considering a move to React or Vue, Vue being the conservative choice I may well go wit
142.
by nilliams 10y ago
Not really, you get a warning that said module might not support this 'release candidate' of a major breaking version.
143.
by nilliams 10y ago
There's a difference between being negative with specific complaints versus hyperbolic, drive-by FUD. Regarding your own complaints with Node. You're over-generalising. Nobody says you must use small modules. Larger libraries and
144.
by nilliams 11y ago
The same situation applies in all language ecosystems, there is nothing exceptional about Node in this regard.
145.
by nilliams 11y ago
I generally recommend using nvm [1] to install Node, it's certainly a painless way to get Node 5, then it's also easy to switch version later, or maybe downgrade to the LTS when you're doing 'work work' (`nvm use 4`
146.
by nilliams 11y ago
I think you're pretty heavily stating your own opinion as fact here. I have the opposite opinion and consider the React equivalents much easier to read than the Reagent examples you linked to, because I find the syntax more expressive.
147.
by nilliams 11y ago
The argument I imagine (and that I agree with) is that if you aren't in touch with the code you begin to lose touch (esp. in this fast-moving industry) and you become an ivory-towered twit that your teammates can't relate to and b
148.
by nilliams 11y ago
I don't quite understand your comment, are you saying you are for-or-against feature branches? Your 2nd paragraph seems to be saying you dislike the git-flow model, but the 3rd suggests you like feature branching? Anyway to add my 2c,
149.
by nilliams 11y ago
That 'just as easily' does not cause problems for us cautious devs who pin dependencies with 'npm shrinkwrap' and review changes to our dependencies. Unpublish was an actual problem, and that problem has been fixed.
150.
by nilliams 11y ago
That's how e.g. Bootstrap 2 worked. It sucked. Bootstrap 3 moved to opt-in styles and it is way better. If you really want all buttons to be BS-like you simply write (in Less -- I cba to look up the Sass but it's similarly trivia

More ›