ervine

8 ms·

91.
by ervine 4y ago
It's alright man, we'll agree to disagree. Housing is artificially constrained by treating it as an investment opportunity. Your solution is to pick up and leave everyone and everything you know because someone else decided that h
92.
by ervine 4y ago
It's not just the hip spots anymore. This comment is pretty out of touch.
93.
by ervine 5y ago
> blurs so many boundaries with a pretty poor tradeoff when compared to "normal" APIs. I'd love to hear more on this, I've been feeling this way for a while when using graphql-code-generator and apollo-client with rea
94.
by ervine 5y ago
"In hindsight it sounded fun and interesting."
95.
by ervine 6y ago
I mentioned it as an example of one of the more popular solutions available. Yes, it's complicated and requires a deep understanding of what it's doing - and even then it has warts that you have to work around - but we're tal
96.
by ervine 6y ago
I consider it anything that doesn't take place in the user's browser. Writing the APIs, interacting with the DB, defining the backend data models, dreaming up the microservice architecture, whatever your workplace is doing. If it&
97.
by ervine 6y ago
Agreed that it's complex, but I think the "needlessly" part is up for debate. Considering we're all here on hacker news, we're all used to and just fine with the idea that if you want fresh data, you refresh the pag
98.
by ervine 8y ago
The big win for me is if you're making an SPA, all the knowledge of the app state is already stored in JS (redux, or local state, or handed down as props if using React). So instead of toggling styles on a class, you just hand the stat
99.
by ervine 8y ago
You generate a css file with something like webpack.