mvf4z7

Can you share a link to your implementation?

Another company developing similar technology in the US. https://www.motmot.ai/

Gretchen, stop trying to make Elixir happen.

Could not agree more. The All In guys stopped engaging in thought provoking and critical conversations a long time ago. And holy hell, Jason Calacanis is the biggest weasel on the podcast. At least the other turds own who they are, while Jason will be whatever gets him access to the “in crowd”.

I used to use a client app like this. But after I switched phones, I never re-downloaded it and have found that using the browser works just as good for such a simple application.

Should be replacing state in the history stack rather than pushing a new state.

Basically Little's law. It is queues all the way down.

https://en.wikipedia.org/wiki/Little's_law

Additionally, here is a great talk on queuing theory and load shedding. One argument this talk makes is that autoscaling is not the silver bullet you think it is (similar to queues).

https://www.youtube.com/watch?v=-oQl1xv0hDk

Detroit checking in. I pay anywhere bewteen $0.182/kWh to $0.237/kWh (varies depending on time of day).

Furthermore, our electric utility has some of the worst reliability in the country. Riddle me that. Some of the most Detroit shit I have ever heard.

I bet there were a lot of essays written about Aardvarks at that time.

I think one of those circumstances is when you previously worked for the company behind Remix. He is probably just really comfortable with the framework, so it makes sense for him to use it.

https://www.linkedin.com/in/kentcdodds/

Jonathan, is that you?

I was under the impression that you create a button component and apply the atomic styles in that component. That way you don’t don’t need a “btn” class, you just use the Button component anywhere you need a button.

Especially not in the state of Michigan.

This reminds me of Reacts "dangerouslySetInnerHTML" prop.

https://reactjs.org/docs/dom-elements.html#dangerouslysetinn...

My biggest problem with using JWTs for authenticating a SPA is where do you store them so that a user does not have to login every time they visit your application? Every SPA tutorial I have seen says to throw them in the browser's localStorage. Well now you just opened yourself up to XSS vulnerabilities. Any code running on your page can access localStorage and make requests to ship the tokens anywhere they would like.

I prefer session cookies for web applications. Sure you have to worry about CSRF, but that is easily solved with CSRF tokens. Furthermore, is CSRF even really an issue when you are using a JSON API and have CORS properly configured.

This is the first usage of blockchain technology that I actually find compelling.

Now might be a good time to check out Dynatrace if you are a current New Relic customer. https://www.dynatrace.com/

Has anyone here actually used DDD for building a significant production system? I have read a lot of material on the subject, and everything always sounds good in theory. But whenever I attempt to put the patterns to practice it seems like there are endless pitfalls and gotcha moments.

I would love to see an example repo of a successful implementation.

This is awesome to see. I have gotten interested in CRDTs in the last couple years due to them being used in the Elixir/Phoenix ecosystem.

One question though, how do you integrate a backend into your library? I don't see anything mentioned in the docs.