nilliams

14 ms·

91.
by nilliams 10y ago
Well you should really have that out with them! If you feel they're needlessly switching and putting your project at risk, have them justify it. (Or just have a rule that as a team you try e.g. '1 new thing' per project). Aga
92.
by nilliams 10y ago
The JS community is considerably larger than all other programming communities, and better at promoting (and documenting) its tools/libraries/frameworks (a lot of these tools come with beautiful landing pages, docs and demos). Tha
93.
by nilliams 10y ago
Well page loads are fast, and clicking links within the docs section does feel super fast, but I agree use of the word 'transitions' is confusing (which the author has now addressed elsewhere).
94.
by nilliams 10y ago
Looks like a good take. Your readme would benefit from an example of what luxem looks like, ideally the first thing I'd see, below a short tagline, rather than having to read a lot of text and try to picture what you're describing
95.
by nilliams 10y ago
Unfortunately Promises need to be fixed before fetch will be sane and here's how the promises spec currently looks: - unhandled errors silently swallowed [1] (this is the case for the most popular polyfill [1] too - the one recommended
96.
by nilliams 10y ago
Generally when a story is reported like that there is almost always 'more to it', e.g. the press have probably twisted it and it wasn't actually a case where 3 kids were playing in a fenced-in backyard, totally safely and t
97.
by nilliams 10y ago
Ah okay, I've never used shrinkwrap across platforms (dev in Linux or Linux VMs, deploy to Linux). That does seem like a PITA. > As far as the other comments about npm, I just generally have more problems with it than rubygems/
98.
by nilliams 10y ago
> Shrinkwrap is ridiculous. I'm expected to go look at every resolved dependency and individually add them if I want to update or not? Not sure you're aware of the suggested flow (see here [1]), but it isn't ridiculous. Us
99.
by nilliams 10y ago
> What is reach front end? The one where you wait your js to arrive only for it to issue own API calls, then wait data to arrive, then it to be parsed and finaly shown? No, that's your own straw man definition. > It would not sur
100.
by nilliams 10y ago
For reproducible builds (or at least 'to get the same versions again') you should be using 'npm shrinkwrap'. (Of course there's probably more you should do to get true reproducible builds, but that goes for any pack
101.
by nilliams 10y ago
I often see drive-by bashing of npm, but rarely any justification. What exactly is wrong with it? (Aside from the lack of package integrity check, which I'll grant, sucks).
102.
by nilliams 10y ago
Yep it's maddening. We use pip-compile [1] at work and check-in the then totally-resolved requirements.txt. That is working for us well. However I still head-desk every time I just want to install a local package (with pip install -e)
103.
by nilliams 10y ago
Thank you truly for moment. It has saved my bacon so many times. As other commenters have stated, let us know where we can donate, to yourself or to charity. Best of luck.
104.
by nilliams 10y ago
Why do you think competitiveness of tooling is a bad thing? I understand why it could feel overwhelming, but you really can just pick one (assuming it appears to do what you want) and if it does, stick with it.
105.
by nilliams 10y ago
Only what I addressed. Typography, which you can disable or override easily. Let's be clear, Bootstrap is the most popular CSS framework in the world, whose Github issue threads have been pored over many times more than Blaze's ar
106.
by nilliams 10y ago
You seem to be complaining that innovation is happening. If you don't want to deal with the inevitable 'options' that are going to be offered up by a community as large as the JS community, you could 1. pick a smaller communi
107.
by nilliams 10y ago
What about IE8-10? I agree with pythonistah, that can-i-use data doesn't really map to real-world usage.
108.
by nilliams 10y ago
>> Regardless, any sort of environment where you can do `import extend from 'just-extend';` is going to (have a way) support map and filter. That is not true for the now-fairly-common use case that browserify/webpack sa
109.
by nilliams 10y ago
Cross-browser usage? Map and filter aren't in IE8, which is still in wider use than a lot of people would like to pretend.
110.
by nilliams 10y ago
Unlike template strings this module could be used cross-browser (via browserify/webpack etc).
111.
by nilliams 10y ago
Because npm is a package manager that most devs already need present for their front-end build step (to install their deps for gulp/grunt/browserify etc) , and bower is an 'extra' thing that addressed a need that no long
112.
by nilliams 10y ago
This is a 'terminal emulator' (client). So what you ssh into is irrelevant and Bash etc. are also irrelevant. This is a client you could ssh from (and use whatever shell you like, locally and remotely).
113.
by nilliams 10y ago
.c-button--primary has lower specificity that .c-button.primary
114.
by nilliams 10y ago
Correct me if I'm wrong or misunderstanding, but apart from basic typography (relative sizes and spacing of headings and body text), bootstrap has been opt-in since bootstrap 3. Everything else requires adding classnames or using mixin
115.
by nilliams 10y ago
It's good to see this was recognised as a bug and quickly fixed. Meanwhile in spec-adhering Promise land, a similar problem still exists [1], which is why I recently banished es6-promise, and in turn fetch/fetch-polynomial from my
116.
by nilliams 10y ago
It's not 'going back'. The semantic-markup-with-no-presentation-classes approach is just one way to do it and there are good arguments against. Recommend reading: http://mrmrs.io/writing/2016/03&#x2F
117.
by nilliams 10y ago
Cool, I used to love Wings 3D (best, free UV mapping capabilities). Never realised it was written in Erlang. I recently subscribed to the excellent Elixir Sips screencast series [0] and there're a bunch of OpenGL episodes there too. [0
118.
by nilliams 10y ago
Tbf I just looked over 'standard' and it's improved a ton since it initially came out. Bar one minor rule, the only rule I still object to is the semicolon one, which I'm obvs not going to get into a discussion about, be
119.
by nilliams 10y ago
They are specifically working on it according to this React.js Conf talk [0]. There's also rwb from Pete Hunt [1]. EDIT: Removed comment about 'standard'. Ain't so bad anymore apparently. [0] https://www.youtu
120.
by nilliams 10y ago
Unbelievable, thanks for sharing. I'll be looking out for this dialog on my old Win laptop now that has been nagging me for forever (I don't believe for a second it will run Win 10 well).

More ›