HNHacker News
TopNewBestAskShowJobs

LegNeato

751 karma · joined May 2, 2013

I worked @ Robinhood on various things. I worked @ Facebook on mobile app releases. Before I worked @ Mozilla on Firefox releases. Before that, I worked @ Apple on Mac OS X releases.
submissionscomments
LegNeato··on What Is Proper Continuous Integration?
If you switch to a modern build system like Bazel or Buck with remote caching, you will likely get that down to < 5 mins per change...
LegNeato··on Firefox 51.0
Fun fact: Alex Keybl and I based them on 1Password's release notes (https://app-updates.agilebits.com/product_history/OPM4).

Here was the old style:

http://website-archive.mozilla.org/www.mozilla.org/firefox_r...

And the new style:

http://website-archive.mozilla.org/www.mozilla.org/firefox_r...

The new style has since been tweaked a bit since we left Mozilla.

They also always had a list of all bugs fixed (for example, http://website-archive.mozilla.org/www.mozilla.org/firefox_r...).

LegNeato··on Squash your commits
Awesome! Phabricator got me addicted to the clean history of squashing commits and the logical changes staying together in source control (as opposed to grouping in a PR).
LegNeato··on How we built Facebook Lite for every Android phone and network
Why laugh? We were already using proguard heavily. We eventually hit build perf issues and had to patch it too (https://github.com/facebook/proguard)

Do you think we wanted to do a crazy runtime patch and didn't explore every other short/medium-term option? Do you think we wanted to write our own build system (Buck)? Or our own JS view layer (React)? Our own PHP virtual machine (HHVM)? Our own database (Presto/RocksDB)? Our own IDE (Nuclide)?

You "laughing" tells me you have never worked on a large codebase with hundreds of engineers shipping very quickly, so you can't empathize with the sort of problems that come up.

Btw, every time Google Apps hit the limit they merely bumped the limit in AOSP and dropped support for old OS versions...

LegNeato··on On Your Cute Release Notes
Writing release notes for consumer software doesn't make sense. They are a throwback to boxed software and should be abolished:

1. With A/B testing and server-side feature flags they don't reflect what the user will see.

2. With technology like React Native and PhoneGap changes are decoupled from shipping an updated ipa/apk.

3. With most apps shipping quickly (some every 2 weeks) localization of release notes becomes a long pole.

4. Simple text is not effective for showing users potential benefits or training how to use something.

5. They can be misleading...saying something like "fixed a startup crash" doesn't mean for a particular user the startup crash they are experiencing is fixed.

6. More and more users have automatic update turned on and don't even see release notes is the app store UI.

7. Users don't read release notes (or anything really). HN folks may read them...normal people do not.

Do you know what version of Facebook.com you are using and all the new features they push out daily? How about Gmail? Nope, you use products for core functionality and then discover what's new in the course of actually using them and not in a text pop-up up front. This is how apps should be.

A much better and more effective strategy is contextual in-app callouts / new user experiences.

The above only applies to consumer products. I believe release notes can be valuable for enterprises/frameworks/libraries/tools/etc.

PS: I know all about the tradeoffs...I wrote release notes for Mac OS X, Firefox, and Facebook. I was the one that decided to stop doing them at Facebook for the above reasons.

LegNeato··on Amazon has no idea how to run an app store
A lot. It's the largest pain point shipping on iOS. More specific details and some suggestions:

http://christian.legnitto.com/blog/2016/01/02/ways-i-would-f...

LegNeato··on Google Launches Android Studio 2.0
Instant run sounds a bit like Buck's exopackage:

https://buckbuild.com/article/exopackage.html

Although the example they show is editing a resource, so it could be fast-pathing resource-only edits (buck does that too).

More docs here:

https://sites.google.com/a/android.com/tools/tech-docs/insta...

LegNeato··on Atom 1.1 is out
If you were seeing Atom Helper take 100% cpu on launch or when viewing packages (especially with Nuclide), it should be fixed. Please comment or file a task if it is not!
LegNeato··on Developing Atom Packages, Part 2: So Much Potential, So Many Bugs
Relatedly, this is how Facebook develops and releases their ~40 Atom packages:

http://blog.bolinfest.com/2015/10/hacking-on-atom-part-ii-bu...

Totally different from the "standard" way and works really well for them.

Disclaimer: I used to manage the Nuclide team at Facebook.

LegNeato··on TTNT: Test This, Not That
Facebook does this to scale their tests, you can hear Katie Coons talking about it in CI at the end of https://www.youtube.com/watch?v=X0VH78ye4yY. There are also rules that say "if you changed this file, run all tests" for things like CI config and such.

Also, the build tool Buck (https://buckbuild.com/) enables this because it knows the graph and associates tests with the code they test...so you even get this test minimization locally as a developer (that is, outside CI) for free. I'm sure Bazel likely has a similar feature too.

LegNeato··on Rust in 2016
I wonder if you can use Buck with its distributed cache to make this go way faster?
LegNeato··on Relay Technical Preview
Buck was not "ripped off" from Google any more than Hadoop was "ripped off" from Google.
LegNeato··on Building Nuclide, a unified developer experience
Indeed. I guess I shouldn't quit my day job!
LegNeato··on Building Nuclide, a unified developer experience
That's me in the video (hi!).

Re: pico. You'd be surprised what editors new employees and interns use when presented with a shell prompt :-D. At FB everyone is free to use their editor of choice...we don't force Nuclide on them.

Re: what's different. Xcode does Objective-C well. IntelliJ does Java well. PHPStorm does PHP well. Tons of editors do JS well. As soon as you start mixing technologies, the IDEs quickly degrade in overall usefulness and you basically have an IDE for one tech and a dumb text editor for the other. Nuclide is opinionated and provides a nice integrated end-to-end experience if you buy into the tech it supports. If you don't use any of that tech (Hack, react, buck, react native, flow, phabricator, mercurial, etc) or only use 1 language/platform at a time (like a pure objective-c iOS app) then Nuclide basically is Atom.

Nuclide's value is super apparent with React Native. You need to be able to edit JS and Objective-C and eventually Java, and it would be nice to have all the autocomplete/click-to-symbol/code search goodies for all three. Let alone debugging all of them and jumping between the stacks. No IDE provides all the features you need for a project like React Native out of the box. So we built one (leveraging Atom of course). It is magic working on a React Native app and using the same debugging UI to step through the JS, and then the Objective-C, and then using the SAME interface to debug your Hack code on the server.

Finally, over time you'll start to see a bunch of really, really smart integration with tools and libraries like Relay and GraphQL. We already have some internally--I can "click to definition" in a GraphQL query and see where it is defined in JS, and then click through and see where it is implemented in Hack on the server. Simple symbol search can't do that and spanning multiple languages and stacks is unsupported by most IDEs. Nuclide is opinionated so we can do deep integration like that...we leave the general editor-stuff to Atom proper.

Re: clumsy demo. I actually converted from vim when we started Nuclide...I even used vim for most of my JS/Android/Hack/iOS programming. For the demo I didn't install the vi bindings because I wanted fewer things that could go wrong. Because I wasn't a huge IDE user previously you see me using the mouse a ton instead of (generally) standard IDE keyboard shortcuts.

LegNeato··on Nintendo files Patent Application for Hand-Held Video Game Emulation
So invalidate it! http://patents.stackexchange.com/questions/10689/nintendos-r...
LegNeato··on Alcatraz – Package manager for Xcode 5
I actually wrote that patch! Are you sure you are using a version of clang with support for it? As far as I know a new release hasn't been cut with the included patch. At Facebook we use clang-format with that patch and it works.

I should note that Alcatraz's clang plugin looks to have a compiled version of an old clang-format in the tree...that's likely why this doesn't work with that plugin.

LegNeato··on Xctool: a replacement for xcodebuild to build and test iOS and Mac projects
Check out http://www.libimobiledevice.org/ and https://github.com/ios-driver/libimobile-java
LegNeato··on Xctool: a replacement for xcodebuild to build and test iOS and Mac projects
It works, we use it here at Facebook
← PreviousPage 5 of 5