HNHacker News
TopNewBestAskShowJobs

wycats

6,755 karma · joined August 18, 2008

submissionscomments
wycats··on I don’t belong in tech
"I offended everyone" is not defacto evidence that you're doing something right.
wycats··on I don’t belong in tech
That hasn't happened here, so your opposition is, itself, raising spectres.
wycats··on I don’t belong in tech
Where did the author deem anyone a bigot? Your pattern matching algorithm has severe bugs if it identifies this post as deeming families as bigots.
wycats··on I don’t belong in tech
This thread is full of obvious cases of toxicity.
wycats··on I don’t belong in tech
There is plenty of place for polish and deep understanding in the user-facing sphere. Apple is renowned for their work in this area. My company's product, Skylight, has made a virtue out of "all the little things" - understanding problems deeply and solving them well.

I think it's reasonable for people to wish that more of user-facing software worked this way, even though it's out of sync with how Silicon Valley and Venture Capital tend to work.

wycats··on I don’t belong in tech
This post is not about perfection, but rather about a deep, legitimate frustration that the tech community spends so little time really understanding the problems it sets out to solve.

Here's a key paragraph:

> I am not solution-oriented. I don’t see a problem and get giddy at the idea of solving it, patching it up and sending it on its merry way. I want to poke it and ask it questions. Where did it come from, what is it doing, what’s its story? I want to take it to tea and hear about its life and understand it to its core. And if, at that point, I’ve come to a wholistic understanding and am able to solve the problem, by all means, let the problem-solving commence! But my instinct is never to solve, but to understand.

This is not a statement of perfectionism, but rather a deep yearning for like-minded people who believe in trying to understand the problems they're trying to solve.

The RFC process, which has gained more prominence through projects like Ember, Rust, Swift, and Yarn, operate on the same principle: that we should try to make sure we understand, not just rush in with the first solution that comes to mind.

Iteration and contact with reality are important. A desire to understand is not in conflict with a desire to iterate and work with communities. But too often, the tech community makes a virtue out of moving fast, breaking things, and never coming to a deep understanding even in many of the most successful cases.

I think we owe it to ourselves and our community to get past a knee-jerk reaction to this post.

wycats··on I don’t belong in tech
I hope nobody quits tech, and certainly not because they are frustrated that the tech industry chronically celebrates solving problems we don't understand.
wycats··on Yarn – A new package manager for JavaScript
We're not using Yarn at Tilde yet, but I've been using it on Yarn itself and when working on Ember packages, and it's worked well. As far as performance, we have good benchmarks tracking yarn's performance in a whole bunch of different scenarios (https://yarnpkg.com/en/compare)
wycats··on Yarn – A new package manager for JavaScript
Is npm the bazooka or C++? As someone who's worked with C/C++ (and its hilarious explosion of tooling -- half-a-dozen at Google alone), maven, bundler and Cargo, I think it's just not accurate to say that the npm ecosystem has a particularly high level of complexity.
wycats··on Yarn – A new package manager for JavaScript
That's exactly what Cargo does, but it also takes a further step of making `^` the default operator and strongly discouraging version ranges other than "semver compatible" post-1.0.
wycats··on Yarn – A new package manager for JavaScript
I more or less agree with this.
wycats··on Yarn – A new package manager for JavaScript
As a practical matter, the npm ecosystem today relies on duplication, and no new client that made the "highlander rule" (there can be only one) mandatory could succeed.

Yarn does offer a `--flat` option that enforces the highlander rule, and I'm hopeful that the existence of this option will nudge the ecosystem towards an appreciation for fewer semver-major bumps and more ecosystem-wide effort to enable whole apps to work with `--flat` mode.

Plz send halp!

wycats··on Yarn – A new package manager for JavaScript
Yikes, thanks!
wycats··on Yarn – A new package manager for JavaScript
This is something I hope to work on over the next few months. It's a priority for Ember :)
wycats··on Yarn – A new package manager for JavaScript
At least speaking for myself, the npm package ecosystem is critical and I wouldn't want to do anything to undermine the integrity of the npm registry.
wycats··on Yarn – A new package manager for JavaScript
This is something I really want to explore more through less-compatible modes. It was the original way yarn worked, but it wasn't compatible enough to be the default mode: https://github.com/yarnpkg/yarn/issues/57
wycats··on Yarn – A new package manager for JavaScript
I wrote a post explaining why I'm psyched to be working on it:

TLDR:

- open, community governance that will support long-term evolution

- the technical details get a lot right out of the gate (decent performance, predictability, and security)

wycats··on Typosquatting programming language package managers
That would mean that, for example on crates.io, you couldn't create a `libm`, because `libc` is already very popular. I don't think that works.
wycats··on WebKit is now 100% ES6 complete
So are you saying that, for example, the change to CORS from <script> in <script type='module'> has multi-vendor consensus?
wycats··on WebKit is now 100% ES6 complete
> Contrast that with the agreed-upon work in the WHATWG HTML Living Standard discussed at https://blog.whatwg.org/js-modules, which is relatively finalized and is being actively implemented now in all browser engines.

Just to clarify, unlike TC39, the WHATWG HTML ("Living Standard") spec requires no consensus at all in order to add new features. Consensus is arrived at once all implementers have implemented the relevant features to the stable versions of their browsers.

To say that what is in the spec has consensus at the same time as browser implementers are beginning implementation (and expressing some concern over details) gets the WHATWG process backwards.

wycats··on Helix: Rust and Ruby, Without the Glue
The Rust version does a type coercion from Ruby VALUE to Rust String. The type coercions are defined generically using Rust traits (see the Helix README) so once somebody defines RubyString -> String once everyone benefits.

In this case, the coercion needs to ask Ruby for the encoding tag and ask Ruby to validate the encoding (which is does often enough that it's often cached) but after that we can safely coerce directly into a UTF8 string.

If we wanted to support other encodings, we could fall back to using Ruby's transcoding support (string.encode("UTF8")) and again, once someone does the work once it'll work for all helix users.

wycats··on Vulnerability #319816 – npm fails to restrict the actions of malicious packages
>> ● Require 2 factor auth for publish operations

> This seems very reasonable, and the easiest to implement. It also has the nice effect of being a captcha to the publish operation, which gives it some of the gravitas it deserves in an open ecosystem like npm.

I agree, especially since Google Authenticator makes this pretty easy to implement.

wycats··on Vulnerability #319816 – npm fails to restrict the actions of malicious packages
All package managers (that I know of) for dynamic languages offer a mechanism for compiling native code for packages that include bindings to C libraries.

That mechanism could easily be used to achieve the same goal, even if there was no explicit "post-script" mechanism.

wycats··on Vulnerability #319816 – npm fails to restrict the actions of malicious packages
The note offers this workaround for npm: "Use npm shrinkwrap to lock down your dependencies", which will prevent the worm from spreading purely because of an install of a checked out app.

Any application package manager with a lockfile-based-workflow (like Bundler, Cocoapods, Cargo, etc.) would at least have this mitigation as a default part of the workflow.

wycats··on CocoaPods downloads max out five GitHub server CPUs
For what it's worse, both of these characteristics indeed weren't an accident.

At the time, I wrote a script that hammered git commits into a repository using different strategies and looked at what the git repository would look like after 100,000 and a million commits. The "one version per file, nested in a flat structure" had serious issues.

There may still be scaling limits with the Cargo approach, but if we reach them, we have plans to create a new registry with a new initial commit and let the old registry age out, then rinse/repeat. At the moment, we haven't hit limits yet (with about 1/3 of the packages that Cocoapods has).

wycats··on An 'in' operator for Ruby
The difference here is that `` literally maps onto a method called `` in Ruby. I find this aspect of Ruby delightful and it's not something I willingly chip away at.

Generally speaking, Ruby eschews syntax that invokes a protocol behind the scenes for a consistent 1:1 mapping between method syntax and the methods they invoke.

wycats··on Neon: Node plus Rust
I'm actively working on it (https://github.com/tildeio/turboruby) and in fact was racing @dherman to finish. He beat me by a mile :( but I hope to wrap up a usable first version soon.
wycats··on ES7 Proposal: The Pipeline Operator
Fair enough.

I personally consider compound operators (asymmetrical) to be pretty risky (the do, indeed, depend on background), and I like '->' because it has a clear meaning outside of programming.

But you're right, this is a bikeshed.

I'd prefer either version of the pipeline operator to bind.

wycats··on ES7 Proposal: The Pipeline Operator
Only if those methods are added to NodeList, which they haven't been.

(and of course 'sortBy' is nonstandard)

wycats··on ES7 Proposal: The Pipeline Operator
CoffeeScript should have thought of that ;)
← PreviousPage 2 of 18Next →