After I finished refactoring my android app to use a 3rd-party public API for the user data, I needed a way to quickly promote my application to users. The API I used is inherently insecure with virtually no standard REST API security in place and designed with a top-down approach to suit their own mobile app. Their whole premise being to secure the mobile app with 2FA and having an API that’s quite literally a bunch of wrapper functions around database queries exposed as endpoints.
TADA68 with the aluminium case Why TADA68? After first coming across the Keywalker IFD68 on Massdrop for just $99 I almost bought it. But after trying to find some reviews online I also found the TADA68/SABER68 designed by originatives, which is a very similar keyboard with the exact same 68 key layout and even the type and color of keycaps. But the few differences that tipped the favor towards me buying the TADA68 were; first the Keywalker being a Bluetooth keyboard with an included battery the shipping increased to be just too expensive, second the Keywalker uses a proprietary firmware with a flashing tool to program the keyboard only available for windows platform.
For the past couple of weeks I have been slowly setting up my Vim and tmux config files to just the way I prefer, creating the perfect workflow for working on C/C++ and Rust projects that increases my productivity by not only not having to constantly switch between the keyboard and the mouse/touchpad for every little task/navigation but also to just touch type my way to glory :). Especially since with C and Rust not having a single canonical IDE and inherently requiring to interact with the terminal for compiling and debugging, Vim coupled with a language server (I’m using cquery for C/C++, RLS for Rust) is the perfect IDE for these languages.
Does anyone else also feel that we need lightning [network] desktop and mobile app wallets that can connect to your remote lnd server with gRPC (using rpc username and password) instead of every app loading and syncing their own chain on device? Leading to multiple wallets and coin fragmentation among those wallets.
Update: My pull requests implementing the techniques discussed here were merged into the zeit/next.js with-data-prefetch and with-apollo examples. You can easily combine the various examples (including the above two) to achieve your desired functionality. For most modern web apps, network speed and latency is still the biggest constraint for high performance and great UX. Universally rendered Isomorphic applications do a great job to solve that to some extent without sacrificing interactivity by processing the complete DOM of the first request on the server and subsequent requests on the client. But there is a lot more we can do.