HNHacker News
TopNewBestAskShowJobs

dikaiosune

4,199 karma · joined December 10, 2014

http://blog.adamperry.me
submissionscomments
dikaiosune··on Why you should, actually, rewrite some of it in Rust
How much of the standard library works without GC enabled? How many community libraries do?

D has a lot of great things (I am incredibly jealous of their metaprogramming facilities sometimes), but it doesn't seem like many people are successfully using it in the "fast and SAFE" sense as GP defined it.

dikaiosune··on Why you should, actually, rewrite some of it in Rust
The author is actually using it, to actually rewrite portions of C projects in it, and writing about their experience doing this in practice. For example, the linked paper is about using Rust at the I/O boundary in an existing, complex system.
dikaiosune··on Why you should, actually, rewrite some of it in Rust
Please correct me if I'm wrong, but don't Ada/SPARK's memory safety guarantees only hold when all memory is pre-allocated? My memory is that dynamic allocations aren't visible to the proof system (this may be in plain Ada without SPARK, now that I think of it).
dikaiosune··on Why you should, actually, rewrite some of it in Rust
In this case it seems the author is writing about the concrete results they've already obtained, not about something abstract.
dikaiosune··on Why you should, actually, rewrite some of it in Rust
I believe Firefox as of recent versions requires a Rust compiler to be available, and that's a pretty bread-and-butter application to have in your distro's package repository.
dikaiosune··on Language Server Protocol, Rust and Emacs
From your endorsement of "using the compiler's symbol tables" (paraphrasing) I took you to mean that you're proposing binding directly to GCC (or another tool) as a library, relying on it's internal data structures as this C API. Based on this comment, it sounds like you're now suggesting that this API should still be standardized and require translating from the compiler's internals into some standardized AST/symbol format anyways. I still think the latter is bonkers for several reasons (SIGABRT being one), but it's significantly less bonkers than what I had thought you were proposing initially.
dikaiosune··on Language Server Protocol, Rust and Emacs
Agreed, that pipes+json is much higher overhead, just noting that this proposed approach still isn't free.

> Let's get comfortable with what is good, rather than make what we are comfortable with?

I agree in the abstract! I just emphatically disagree with characterizing a C ABI as "what is good."

dikaiosune··on How sandboxing works in Fuchsia
> similar to what a current flagship phone has in terms of resources if not exact architecture.

:)

dikaiosune··on How sandboxing works in Fuchsia
I believe my phone runs a 64bit ARM with eight 2.3ghz cores and has the same amount of ram as the base Acer model?
dikaiosune··on How sandboxing works in Fuchsia
The hardware in that Acer laptop looks surprisingly similar to what a current flagship phone has in terms of resources if not exact architecture.
dikaiosune··on Writing correct lock-free and distributed stateful systems in Rust, with TLA+
There are already a lot of cases where LLVM can successfully optimize away things like safe Rust's bounds checks in loops.

There are also efforts to include "const generics" which will let you use e.g. array lengths as generics that may be able to teach LLVM new optimizations. Maybe someday in the far future that will grow into some kind of dependent typing extension for Rust? That could potentially allow for safe, bounds-check free array access that would currently require unsafe. But I don't know if that would allow for proving the kinds of things this article discusses.

Ultimately though, the unsafe subset is pretty small and is generally in my experience only interesting when building heavily reused abstractions (the kinds of lock-free algorithms OP discusses for example). It'll be really cool if these efforts expose some ways to shrink reliance on unsafe code, but I'm personally not sweating it.

dikaiosune··on Writing correct lock-free and distributed stateful systems in Rust, with TLA+
There's a lot of interest in formally verifying things about the unsafe subset of Rust, for example the Rust Belt project: http://plv.mpi-sws.org/rustbelt/. One thing I've not well understood is how these efforts may be affected by some of the conversations around the unsafe code guidelines effort:

https://github.com/rust-lang/rfcs/pull/1643 https://github.com/nikomatsakis/rust-memory-model

dikaiosune··on Emulating the Rust borrow checker with C++ move-only types
Not funny ones, in my experience
dikaiosune··on Painting with Code: Introducing our new open source library React Sketch.app
For anyone missing context, naming is hard.

https://blog.expo.io/expo-sketch-expo-snack-a444f8dec72b

dikaiosune··on Ask HN: Who is hiring? (April 2017)
Expo | Software Developer | Palo Alto, CA | ONSITE, FULL-TIME | https://expo.io

Expo (formerly Exponent) lets developers build truly native apps that work across both iOS and Android by writing them once in just JavaScript. It's open source and free and uses React Native. Several of our engineers are core contributors to React Native, and we regularly collaborate with Facebook and other companies on the direction of the framework.

Our technology is built around an Android/iOS application which allows developers to load their JavaScript projects on the fly with no native build dependencies. Out of the box, developers using Expo get access to native mobile APIs like push notifications, camera, maps, and more (https://docs.getexponent.com/versions/v15.0.0/sdk/index.html).

We have a lot of irons in the fire, and we're looking for engineers who can comfortably own and work on multiple projects. Some examples of recent projects at Expo:

* Creating cross-platform APIs (like our new WebGL implementation) that provide developers native mobile functionality within JavaScript

* Building Snack (https://snack.expo.io), a JSFiddle-esque tool for React Native

* Designing and implementing a community front-end to explore applications built on Expo

* Building the foundation of a scalable infrastructure to host our take on a new mobile web

Some projects that are underway or on the horizon for us:

* Greatly expanding the functionality available in our SDK's API

* Improved monitoring and alerting for our infrastructure

* Increasing our test coverage and improving overall reliability

Some buzzwords: React Native, JavaScript (ES6/ES7, Flow), Android, iOS, Node.js, Electron, Go, Kubernetes, Google Cloud. We don't expect candidates to already be proficient in these, but it's what we're currently using day-to-day.

Please send an email to jobs@expo.io and mention this post if you'd like to start a conversation with us. Definitely include links to any applicable resources: resume/CV, your blog, GitHub profile, recent projects or open source contributions, etc. Typical interviews with us include remote pairing, small take-home projects (1-2 hours), and we usually finish with some more traditional in-person interviews.

dikaiosune··on It’s time for a memory safety intervention
At one point I made an attempt to do this from the CVE database, but it's difficult to do since CVEs aren't really machine readable from a "memory safety vs. other security flaws" perspective. I recall finding a lot of reported vulns with buffer, overflow, null pointer dereference, double free, etc., but that's far from scientific.
dikaiosune··on Hiring without whiteboards
Posting a reply for @tsion, who seems to not be able to post at the moment:

I interviewed on-site successfully at Google Seattle about a year ago, and I was given the option between writing code on a whiteboard or in a text editor on a Chromebook, being projected onto the screen in the room, so the interviewers could easily follow without awkwardly looking over my shoulder.

Of course, I picked the text editor. I can't imagine wanting to write code on a whiteboard. However, I did use the whiteboard voluntarily as a thinking and planning aid.

Unfortunately, I also heard that the text editor option was only available at certain offices at that point. I really hope coding in a text editor becomes a universally available option because it's just so much more natural. It essentially put my mind at ease and helped me think more clearly.

On a more general note, my strategy, which seemed to work well for me, was to treat the whole situation like a pair programming task. Even though the interviewer won't directly tell you what to do, they will often comment on things if you question yourself out loud enough.

dikaiosune··on Introducing Sketch: A Playground for React Native from Expo (YC S16)
Absolutely. Naming is hard.
dikaiosune··on Introducing Sketch: A Playground for React Native from Expo (YC S16)
https://www.adobe.com/products/sketch.html
dikaiosune··on Introducing Create React Native App
Hi! Sorry for the very late reply, there's been a lot of interest and I haven't had time t get back to everyone yet.

I'm very surprised to hear about the behavior you ran into with the loading messages on top of each other -- we haven't run into this issue in the native client yet (I don't think). If you're interested, I think a GitHub issue may be best so that I can have a reminder to look into this later on this week.

dikaiosune··on Introducing Create React Native App
You do need an Expo account to create a standalone app. If you want to create an app for the App or Play Stores yourself (i.e. without an account), then you'll need Xcode and/or Android Studio.
dikaiosune··on Introducing Create React Native App
I'm very sensitive to the concerns you've raised in this thread. I've discussed these issues quite a lot, and ultimately decided that it's better to provide a net win to the React Native tooling ecosystem, and try to smooth out the gaps between React Native and Expo. I do think CRNA is a good improvement over the current state of "getting started" in React Native.

Regarding your concerns about "private entities," React Native is open source. Expo is open source. React Native was created and is maintained by Facebook, a private entity. Expo was created by and is maintained by Expo, a private entity. Do you have the same concerns about the recommendation in the RN docs to use Airbnb's maps library?

In order to use CRNA, you need to have a client that can fetch and load the JavaScript bundles. CRNA is agnostic to which client you use, which is why app.json puts any Expo specific configuration under an `expo` namespace. Anyone is welcome to implement their own client and use that if they prefer. I'd be very happy to review PRs which support loading React Native JavaScript in an alternative client. As an implementation detail of the Expo client, a number of native APIs are exposed, and it would be infeasible to block CRNA apps from accessing them.

We don't push users towards the Expo SDK, and the template project doesn't make use of any Expo APIs. If users choose to include a dependency on Expo's code, then we warn them that ejecting will break that dependency -- that's it. We choose a default choice in that prompt on the basis that we don't want to push users towards breaking their app.

dikaiosune··on Introducing Create React Native App
Babel is on by default in the React Native packager, which is indeed used under the hood by both CRNA and Expo's devtools. The template projects include a .babelrc file.

The `registerRootComponent` function is essentially a facade to `AppRegistry.registerComponent` but it also configures hooks for Expo's asset system.

dikaiosune··on Introducing Create React Native App
It does. There's an option to include the sdk in the ejected app, but it's not the default.
dikaiosune··on Introducing Create React Native App
Hi! Sorry you ran into problems. Was this just using the basic starter project? If you want to include some platform information in a GitHub issue I'd love to look into this.
dikaiosune··on Introducing Create React Native App
Sorry for piling on! This is definitely something we could be clearer on in the docs.
dikaiosune··on Introducing Create React Native App
Which build server? If you have an Expo account you can create a "standalone app" with our service, but that's not a part of CRNA's workflow and it's certainly not required to use this tool.
dikaiosune··on Introducing Create React Native App
Hi! Expo is definitely a private entity, but the tools used by CRNA are also definitely open source:

https://github.com/exponent/exponent

https://github.com/exponent/exponent-sdk

https://github.com/exponent/xdl

Also, the RN packager runs locally on your machine, there is no dependency on Expo's build services when working with Create React Native App.

The concerns you raised were front and center when we were working on this project, and we worked hard to make sure that CRNA has no service dependency, it works completely offline.

dikaiosune··on Introducing Create React Native App
Probably not. One of the biggest advantages of CRNA is that we built it from the ground up to not require integrating with Expo's accounts or services. If you've already opted-in to those services, then you're probably getting what CRNA offers plus a little extra.

EDIT: That said there are definitely some areas of CRNA that have had more polish than Expo's current tools, and I'm going to be spending a lot of time in the coming months bringing them closer to parity.

dikaiosune··on Introducing Create React Native App
The biggest advantages of CRNA right now are:

* Doesn't require an Expo account

* Faster to get started than using XDE

* Smooth 'eject' integration with react-native-cli, if you know that you're eventually going to need custom native modules

I'm sure I'll think of some others at some point. One goal we have right now is to start bringing the same level of polish to the existing Expo tools.

← PreviousPage 3 of 22Next →