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.
4,199 karma · joined December 10, 2014
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.
> 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."
:)
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.
https://github.com/rust-lang/rfcs/pull/1643 https://github.com/nikomatsakis/rust-memory-model
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.
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.
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.
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.
The `registerRootComponent` function is essentially a facade to `AppRegistry.registerComponent` but it also configures hooks for Expo's asset system.
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.
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.
* 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.