thejameskyle

6 ms·

1.
by thejameskyle 5y ago
Something I didn't mention in the post that might deserve calling out specifically is that Rust maintainers actively decide to work in crates instead of in std for many things. This means that you have the language designers themselves
2.
Cloudflare security incident and impact on Yarn users(yarnpkg.com)
16 points by thejameskyle 10y ago|0 comments
3.
by thejameskyle 10y ago
No they did not suggest doxxing, and yes the information they want to aggregate is public, but that is not the point. The point is that they want to build a tool which will primarily be used for doxxing by random internet users. Also, d
4.
by thejameskyle 10y ago
The difference here is accessibility. There's a number of public ways (which could be automated) to find out information like people's home addresses, but generally it's pretty difficult to figure out how (provided someone is
5.
WikiLeaks is “thinking of” putting me in danger(medium.com)
9 points by thejameskyle 10y ago|5 comments
6.
by thejameskyle 10y ago
> Creating a static attribute on a class and initializing it right there, as in: class A { static b:B = new B(); } That is how the ECMAScript spec is designed. And TypeScript _should_ follow the spec.
7.
by thejameskyle 10y ago
Flow tries to integrate with the existing ecosystem as much as possible. By taking advantage of Babel, ESLint, Atom, etc. With Flow you don't even have to opt-in to a new syntax. You can just use comments: function foo(val /
8.
by thejameskyle 10y ago
Those all exist in Flow as well. I assume the original poster is talking about how few types you actually need to write in Flow because of how good the inference is.
9.
by thejameskyle 10y ago
If that's too much you can also do: function bar(x) /* : string */ { No compiling necessary
10.
by thejameskyle 10y ago
Comments is definitely the easiest way to get doing. But also if you're already using Babel and ESLint, you can add Flow in very few steps: 1. Setting up with Babel: (note that if you are already using the "react" preset you
11.
by thejameskyle 10y ago
I got to work on Lerna for about two months while working at Cloudflare in order to ship cf-ui. Otherwise it was in the middle of a period where I mostly backed out of doing open source because of frustration with the community from early t
12.
by thejameskyle 10y ago
Anything more than the two presets "es2015" and "react" (we never should have shipped "react" on by default, we just didn't have a pluggable parser before) required configuration in Babel 5. A regular comp
13.
by thejameskyle 10y ago
People keep assuming I have something against sharing criticism or frustration. I never said that. I explicitly said that's not what I'm trying to say. I'm saying that when someone does it in a way that is in pure unadulterat
14.
by thejameskyle 10y ago
The change in Babel 6 was this: $ npm install babel-cli $ babel src -d lib To this: $ npm install babel-cli babel-preset-es2015 $ echo '{ presets: ["es2015"] }' >> .babelrc $ babel src -d lib
15.
by thejameskyle 10y ago
I can't read the article so it's hard to say. But if it was just about the security vulnerability and you weren't calling their software shit, then that's not what I'm trying to cut away at and I'm not sure why
16.
by thejameskyle 10y ago
I wasn't saying that people don't have a right to be frustrated or angry. I wasn't saying we shouldn't voice our criticisms as developers or that we shouldn't disagree with one another. The only argument I'm re
17.
by thejameskyle 10y ago
> What did you build with angular 2? Is it public? Heh, I build the same thing every time because I am not creative. Here's the Marionette version: http://marionettewires.com/ I could put it out there. The problem i
18.
by thejameskyle 10y ago
You assume I was being paid to work on Babel. I was not. I worked on the UI team for Cloudflare, where we didn't even use Babel until earlier this year shortly before I left. I worked on open source on the weekend. The vast majority of
19.
by thejameskyle 10y ago
yo @cpojer come fite me
20.
Yarn: Lockfiles should be committed on all projects(yarnpkg.com)
6 points by thejameskyle 10y ago|2 comments
21.
by thejameskyle 10y ago
npm should not be terrified, we've been working with them and they've been very encouraging. From their perspective it's very difficult to make breaking changes to the client because of the sheer number of people depending on
22.
by thejameskyle 10y ago
Yarn supports `yarn [install/add] --flat` for resolving dependencies to a single version
23.
by thejameskyle 10y ago
Similar, but even more similar to Rust's Cargo https://crates.io/
24.
by thejameskyle 10y ago
You can run `yarn clean` and it will clear out all the extra files you don't need: https://yarnpkg.com/en/docs/cli/clean
25.
by thejameskyle 10y ago
Sorry about that, there are very likely still some bugs out there we weren't able to catch in all our testing which will be ironed out by the community in the next few days. Can you open an issue with details about which package failed
26.
by thejameskyle 10y ago
npm's been involved since the early days, they wrote up a blog post here: http://blog.npmjs.org/post/151660845210/hello-yarn
27.
by thejameskyle 10y ago
And Yarn it deterministic! :party_parrot:
28.
by thejameskyle 10y ago
registry.yarnpkg.com is a proxy, it doesn't contain any package data except for what gets cached by Cloudflare. Just a Cloudflare'd "CNAME registry.yarnpkg.com. registry.npmjs.org."
29.
by thejameskyle 10y ago
Lots of ways you can install Yarn over here: https://yarnpkg.com/en/docs/install
30.
by thejameskyle 10y ago
Oh hi Steve! https://registry.yarnpkg.com is just a proxy to the normal npm registry provided by Cloudflare so we can add additional caching and work on network performance (lots of stuff we could layer on top). It should hopefu

More ›