Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
Picking the right architecture = Picking the right battles + Managing trade-offs
Where you able to produce a binary directly from the Rust build tools that you could submit to the app/play store?
Not quite, but I tried to get as close to that as was reasonably possible. Alas, things ended up a little convoluted.
For iOS, I have a nearly empty Xcode project with a build script that copies my cargo
produced executable into the .app
that Xcode generates (before Xcode signs it). The build script also uses lipo
to merge the executables for each architecture I’m targeting (e.g. armv7 and aarch64 for non-simulator devices) into a single, universal binary.
On top of that, there are various iOS-y things that need to happen before my application’s main method is called. SDL2 provides the Objective-C code that does all of that. In a C or C++ game, SDL2 renames main to SDL_main, and then [inserts its own mai
https://writings.quilt.org/2014/05/12/distributed-systems-and-the-end-of-the-api/
"A distributed system is one where a machine I've never heard of can cause my program to fail" - Leslie Lamport
Cute, but "my program" is kind of quaint now, isn't it?
"...multiple processes that must communicate to perform work" - hmm, hmm, let me tell you about disk controllers. Oh wait, that's your point... almost, "an air-gapped computer" is considered nondistributed, but well whatever.