wlaurance

Are you gonna setup Adsense? lol

My favorite quotes:

- super satisfying, like a bubble wrap mmo

- global fidget toy

- This is brilliant! The websocket server must be going brrr

https://x.com/itseieio/status/1805986839058079896

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.

Thanks!

​

Will

Looks like my email provider ConvertKit had some database issues this morning.

SMH.

Welcome!

I was looking for a way to share with my coworkers in Slack.

Looks really smart!

One thing I'd like is a way to share the final link where I see the projection and ideas

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.

So if you like Ruby/Rails, I say go for it!

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.

I can't speak for linode.

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.

Thanks,

Will

Internally it is using an iframe.

So that should continue to work decently. It's the building and packaging of the thing that will break.