I've been deep in the weeds building out a course. Today I wanted to share a snippet of building out an express + passport auth scheme using the latest async/await patterns. It's really nice to not be in callback hell. Even though passport mostly uses callbacks we can still do our app-specific code like looking up a user by email, de-serialization, and serialization in an async function if desired.
I have an email signup if you want to get the full working code same.
Correct. We're leveraging localStorage to save answers across "pages" (using Vue). We could probably serialize / base64 encode the object we've saved and then let someone share it.
I think the way the question was worded raised my eyebrows a bit. It left me thinking that "sharing socially" would be turned into "let's include this social sharing widget that will track our users" (which always turns me off of a product) vs "let's make sure a shareable link works a single (or multiple) times for people who have the link".
I think that an opinionated framework like Rails will be around for a long time.
Technology has its fads, but somethings stick around. There are plenty of people still coding in C. Laravel is a pretty big PHP framework.
There are plenty of companies that built on Rails. The cost of switching to a new technology is likely unfeasible. So likely the product/company will continue to use Rails.
I have used digital ocean and vultr. From a technical review I used vultr and digital ocean differently. On vultr I ran some large Windows servers. For digital ocean I run all sorts of things.
In my experience, Digital Ocean's support is much much better than Vultr. Towards the end of my used of Vultr I had some pricing disputes for some IP address blocks.
On the other hand Digital Ocean gave me account credit when I reached out.
Good to see a first hand review. Just checking if anybody in the forum has used and/or considered server4you.com. Their prices and server specifications look very competitive
Thanks for the feedback; vultr seems to have newer hardware which results in faster servers; but I also read some where else about their bad customer service.
Awesome, thanks for the recommendations. I'm switching over to grunt-node-webkit-builder.
I'm going to try to make it as easy as `npm install slack-for-linux -g' to get the client in your path.
So this looks a lot cleaner than the other yeoman grunt generator I used initially.
As for node-notifier, this seems easy. I guess the only thing is hooking into the events emitted by the Slack Javascript? I need to dig in further for this.