nilliams

20 ms·

151.
by nilliams 11y ago
In Bootstrap 3 you shouldn't have to override anything. I think I've found one exception which is the toggle button in the navbar element that seems to have some annoying defaults I have to override every time, but that's it.
152.
by nilliams 11y ago
Yes, flexbox is not supported in IE8 & 9, wrong spec in 10 and buggy in 11, therefore the 'terrible'. I'm talking in the context of websites that have to work on the open-web (where unfortunately a lot of people still use
153.
by nilliams 11y ago
My naive understanding is fastboot actually understands stuff like your client-side routing, and how an Ember app 'loads' and fetches data (from your API) so you don't have to recreate that stuff with duplicate code on the se
154.
by nilliams 11y ago
Yes, if you only write JS for Chrome and Node, not sure how many JS devs fall into that bracket!
155.
by nilliams 11y ago
This is rendering a component server-side though correct, a la. React? (In the comment above Tom is suggesting fastboot goes significantly further than this, to make your 'client-side app' render server-side).
156.
by nilliams 11y ago
Yes, and I didn't claim they were unique. My comment was in response to a post about flexbox making all CSS frameworks redundant.
157.
by nilliams 11y ago
Can you explain or give any examples where this is the case? At my work we build totally bespoke designs with Bootstrap and are having a good experience.
158.
by nilliams 11y ago
I don't find this to be the case. There are a ton of conventions in Bootstrap, an obvious one being its variables, that are very useful when working in a team, and (in our experience) with outside contractors. I couldn't imagine g
159.
by nilliams 11y ago
Unless I'm missing something, its grid doesn't really match the capabilities of Bootstrap's. Only one breakpoint for a start?
160.
by nilliams 11y ago
Both are fairly unintelligible to me (probably partly due to my lack of interest in prime numbers), so it seems like splitting hairs to draw comparisons, but if I had to figure out what was going on, I'd rather be staring at this (~ES6
161.
by nilliams 11y ago
Well with regards to clunkiness and awesomeness, are they not still less 'naturally' composable and (as a result) less readable in composition than collection pipelines? I don't see a good reason to prefer them over: co
162.
by nilliams 11y ago
I'm not sure what your specific gripe is with npm. It's one of the fastest and most capable package managers out there, is easily better than Python's Pip (which doesn't resolve dependencies) [0] and Go's go-get sil
163.
by nilliams 11y ago
Sure but that's not a common use-case and won't affect people who want to use Atom as a day-to-day code editor.
164.
by nilliams 11y ago
I don't think that the belief that feature X was created at the expense of feature Y is a reasonable assumption. Who knows how this feature came about? It could have been a Githubber's 20% project, or weekend hack project, or larg
165.
by nilliams 11y ago
Well for one 'class Foo extends Bar' will work without any further code to make inheritance work in the way you'd expect, including use of super() etc. Whereas your second example is using non-trivial framework code, that som
166.
by nilliams 11y ago
You have 2 possibilities yes, but afaict Angular 2 doesn't push you to use 'its way', unlike the early days of Angular 1 where 'the way' to do state was $scope. So I could see how you could comfortably use Angular 2
167.
by nilliams 11y ago
To be fair, not everyone is suggesting you need a scripted build system, but you do need some sort of build step, because <script> tags just aren't sufficient for anything beyond a trivial app. (Also ultimately, you do need to mi
168.
by nilliams 11y ago
Because it's a useful pattern, that people were using heavily. Not sure why you're trying to suggest some kind of ill-intent. A nice thing about prototypal inhericance is that classical inheritance can be implemented in it. People
169.
by nilliams 11y ago
'class' wasn't added to make it look like Java. It was added as sugar for a common pattern that everyone was already using. Many languages other than Java have a class keyword.
170.
by nilliams 11y ago
It's mainly useful for 3rd party (or 'minified') HTML, just to make it readable. It's rare you'd want to use it on HTML you've written yourself.
171.
by nilliams 11y ago
Yeah it's really bad. I feel for anyone that has stuck with these old-school 'cross-platform toolkits' over the last few years, they have really been missing out for a while now. On top of this, the whole scene is just stagna
172.
by nilliams 11y ago
I don't agree with your characterisation. GP was complaining about downvotes to anti-MS comments, and that's nothing to do with 'attracting a readership'. More like the specific criticism of Microsoft demonstrated in thi
173.
by nilliams 11y ago
> A lot less hassle then dealing with this over engineered client side bullshit. I like to deal with client-side apps which talk to a simple JSON API. It's a lot less hassle than dealing with this over engineered server side bullsh
174.
by nilliams 11y ago
What's bizarre about it? Apple developers tend to own other Apple devices and are likely to want to learn Swift on the go.
175.
by nilliams 11y ago
Way I read it the overuse of SO (along with C&P programming) thing was just one example/potential symptom -- he wasn't making a broad generalisation that all SO usage is bad.
176.
by nilliams 11y ago
If you always use something like 'data-bind' for binding and keep classes solely for CSS it's easier to maintain simply because you know 'what classes you can delete' without having to look in two places (CSS and JS
177.
by nilliams 11y ago
'python -m SimpleHTTPServer' is actually fairly terrible if you try to use it to share a file amongst coworkers. Try it and you'll see, downloads will actually fail. It also freaks out if the root dir is blown away, which can
178.
by nilliams 11y ago
As that is a CSS spec, the implementation of which you don't like, it's the browser that's offending, not the CSS.
179.
by nilliams 11y ago
socket.io and ws are apples to oranges. ws does not provide hand-shaking, retries or fallbacks. These are important things if you're building a production app.
180.
by nilliams 11y ago
Can you give an actual example of the 'so many problems' you describe? Your previous comments address the paradox-of-choice idea, but the uncontroversial path in Node is to 'just use Express' right? How it that a worse s

More ›