This is a proposal for a lightning talk at Reactive Conf. Please 🌟 this gist to push the proposal! If you're on your phone, please request the 🖥 desktop site to star this gist 😇 #ReactiveConf
// Example of NFC using Windows Proximity APIs | |
// Tested using Sony RC-S380 (make sure you enable NFP in the driver). | |
use winrt::*; // import various helper types | |
use winrt::windows::foundation; | |
use winrt::windows::networking::proximity; | |
use std::{thread, time}; | |
const URL: &str = "https://dcoles.net"; |
So I really don't like most new things. The only reason I even got involved with Node.js early on was because of its sweeping promise: "One language, spoken by developers across the world." By consolidating parallel efforts, it would accelerate the pace of innovation, and quickly lead to more transformative and disruptive developer tools. It would create tremendous value for software businesses by unlocking efficiencies in the hiring and implementation process. And best of all everyone would waste less time on boring stuff.
Still, there was a problem. While it's true most developers have touched some JavaScript callbacks up there in browserland, in the bowels of the application server, there tends to be a lot more asynchronous things going on. And that causes all sorts of issues. All those callbacks also make for a way steeper
export class ApplicationController { | |
constructor() { | |
this.foo = 'bar'; | |
} | |
} |
/** | |
* HomeController | |
* | |
* @module :: Controller | |
* @description :: Contains logic for handling requests. | |
*/ | |
module.exports = { | |
index: function (req,res) { |