rmrfrmrf

35 ms·

331.
by rmrfrmrf 9y ago
I actually see two red flags based on the candidate’s response, so I’d argue that this answer is rather telling. 1) The candidate demonstrates a lack of intellectual curiosity (and maybe even common sense) when they say “that’s impossible!”
332.
by rmrfrmrf 9y ago
I think you mean “should have stuck with Java applets”. They’ll be back in 10 years and you’ll all be sorry! /s
333.
by rmrfrmrf 9y ago
Good point. I’ll talk to some guys and we’ll turn off the World Wide Web tomorrow. Fun experiment but there were a few security bugs (fixable, but why spend the time?) and, most importantly, @mulmen didn’t like it too much.
334.
by rmrfrmrf 9y ago
Yep, only authors who are good about using `npm version` and pushing the resulting git tag to origin are going to have the proper linkage.
335.
by rmrfrmrf 9y ago
I also think that with tree shaking and last-mile minification being more common these days, auditing might not be as daunting as it seems.
336.
by rmrfrmrf 9y ago
To be precise, new tools are continuously created to address the weaknesses of other tools. This happens in other languages, just more slowly due to smaller community sizes.
337.
by rmrfrmrf 9y ago
Right, and that non-zero overhead is part of being a software developer. It’s also laughable that npm is accused of being a hack and yarn is accused of being over-engineered.
338.
by rmrfrmrf 9y ago
Because when you’re on top, everyone loves seeing you fail. A quick CVE search pulled up 18 vulnerabilities in RubyGems, including remote code execution.
339.
by rmrfrmrf 9y ago
I suspected that someone would mention this, but the fact of the matter is both systems are mostly interoperable. The switch from npm to yarn would be nothing like migrating from Gulp + Browserify to Webpack. To switch to yarn, I printed ou
340.
by rmrfrmrf 9y ago
Yes, if your company has Artifactory or similar. I think most of these outraged folks are just memeing.
341.
by rmrfrmrf 9y ago
You should be using the --frozen-lockfile flag in any production build system.
342.
by rmrfrmrf 9y ago
From my understanding they’ve always had one, but until npm@5 it wasn’t safe for concurrent access (side note: Maven still isn’t) and was prone to corruption. I think they’re making their way toward true offline cacheing a-la yarn, if they
343.
by rmrfrmrf 9y ago
It’s a drop-in replacement CLI tool. Let’s not be dramatic.
344.
by rmrfrmrf 9y ago
You need to disable `SharedArrayBuffer` and `performance.now`, which Firefox already did.
345.
by rmrfrmrf 9y ago
> I'd argue that Maven is lightyears ahead of NPM or pack or gulp or whatever the fuck the kids are using these days. Would you? You think a build system that’s so pointlessly convoluted and verbose that you’re literally encourage
346.
by rmrfrmrf 9y ago
It’s a de facto platform driven by 3.5 billion users. No one “deemed” anything necessary, it just became . And it wasn’t for lack of trying, either (see Java, Adobe AIR, et. al.).
347.
by rmrfrmrf 9y ago
The HTML part of this spec is strange. Most of the practical point of markdown has been to allow a limited set of user-controlled formatting without requiring an HTML parser in the browser. Furthermore, HTML has non-significant whitespace w
348.
by rmrfrmrf 9y ago
If `do { }` syntax makes it into ES9, the whole ternary-operator-hate business will be a moot point
349.
by rmrfrmrf 9y ago
I think my issue is that everything about this plugin — from the marketing tie-in, to the rollout, to the effects of the plugin itself once activated — all indicate a complete breakdown of core values. Creating a plugin that modifies conten
350.
by rmrfrmrf 9y ago
I would think the JS part of JSON would preclude any massive integers. It’s still an IEEE floating point at the end of the day, so your max is (2^53)-1
351.
by rmrfrmrf 9y ago
- Lightweight - Portable - Cross-platform - “Fast enough” out-of-the-box - Massive ecosystem - No need for an application container - Actively developed and maintained - Supports procedural, object-oriented, and functional styles equally -
352.
by rmrfrmrf 9y ago
If you intentionally code JS with referential transparency in mind, then this type of refactoring is just as esay, if not easier.
353.
by rmrfrmrf 9y ago
I still think Grunt and Gulp have a place outside of npm scripts for build automation, deployment, and automation of one-off tasks. The fact that Gulp is fully concurrent by default makes IO and environment setup lightning fast. With Electr
354.
by rmrfrmrf 9y ago
Not to mention whatever task you’re actually doing inside the Promise will be an order of magnitude slower than settling the Promise itself.
355.
by rmrfrmrf 9y ago
Do you, as a user, want web pages to spawn multiple threads on your machine?
356.
by rmrfrmrf 9y ago
Multiple async vehicles can and will coexist in JS. IMO there’s way too much FUD about “one async story to rule them all”.
357.
by rmrfrmrf 9y ago
Some style guides enforce your proposal, but I prefer less noise where possible, especially for currying. const plugin = store => next => action => foo(store, next, action) vs. const plugin = (store) => (next) =&g
358.
by rmrfrmrf 9y ago
Now do it with error handling and recovery.
359.
by rmrfrmrf 9y ago
I’ve never had an issue with Amazon’s couriers. It’s not like our UPS/FedEx drivers go out of their way to differentiate themselves from the competition, and as long as my stuff gets here on time and undamaged, I don’t really care abou
360.
by rmrfrmrf 9y ago
Seriously, this is a giant advertisement. The diagram of the jet engine with literally zero technical value is particularly egregious.

More ›