ervine

6 ms·

61.
by ervine 2y ago
Yes, 100%. Although you end up with some super gnarly types sometimes, so much better than marking a bunch of properties as optional but not handling certain combinations of them being passed in correctly. Lord knows I still do that most of
62.
by ervine 2y ago
Big time.
63.
by ervine 2y ago
Old paradigm (media queries): You make layout changes based on the width / height of the viewport (browser). New paradigm (container queries): You make layout changes based on the width / height of the containing element. This let
64.
by ervine 2y ago
Yep - seems clients have a knack for asking for the most complicated way of doing things. Frustrating as a developer that is already slammed, but good for the business overall. But how many times have we all built extremely complex features
65.
by ervine 2y ago
Ideally design would be using a design system - you can alter all the spacing utilities in Tailwind to match the design spacing if they don't go by the multiples of 4 that Tailwind does. If you're getting Figmas with inconsistent
66.
by ervine 2y ago
Yep but Tailwind is not about replacing native CSS.
67.
by ervine 2y ago
We do exactly that. And if you're not thinking semantically with Tailwind, you probably aren't thinking semantically with css / sass variables anyway, as it's the exact same thing.
68.
by ervine 2y ago
Sample size of 1 here. I lived through every CSS fad for writing "maintainable" css, and have settled on Tailwind. It doesn't limit you, you can always add normal old css files to your project if you need / want to. But
69.
by ervine 2y ago
Not at all, Tailwind lets you define your own classes - so you can have text-primary text-secondary, just like you would with sass or css variables (in fact you can use css variables to generate your tailwind classes).
70.
by ervine 3y ago
Sprayed spot remover on my dog. Next day he was gone.
71.
by ervine 3y ago
Yep and it split the ecosystem / documentation / dev efforts / codebase. Should've been a different product.
72.
by ervine 3y ago
https://github.com/vercel/next.js/discussions/46722 If only this had been brought to their attention recently with a bunch of good-faith discussion.
73.
by ervine 3y ago
What limitations? You mean like not being able to use the full node API in your middleware that's being run by the node server that you control in your own infrastructure? And how about that dev rel... no response since August of last
74.
by ervine 3y ago
Man I agree with all your comments so far. You get it!
75.
by ervine 3y ago
Yeah that's a great point. Nothing makes me start really looking closely at a merge request than when a useEffect shows up.
76.
by ervine 3y ago
You're right, but I haven't touched a React project in ages that wasn't using a fetch library of some kind that give you hooks. Cause you're inevitably gonna want to track loading state, error state, refetch on error, re
77.
by ervine 3y ago
But all the lifecycle methods were magic that needed to be understood... hooks just let you co-locate related logic in one place instead of scattered across 3 or 4 lifecycle methods.
78.
by ervine 3y ago
I'll never understand the "hooks are bad" people. I don't find useEffect confusing, creating custom hooks is a breeze, life is so much better than old class components. When I read complaints about hooks I'm either
79.
by ervine 3y ago
Yep absolutely, I agree and understand how much we're getting for free. On the other hand, their marketing and hype machine has gotten the industry at large to buy into their product. So when you promise enough to get companies to move
80.
by ervine 3y ago
I never claimed middleware doesn't work when self hosting. I claimed that it's not as useful as it could be, because your company has prioritized edge deployments over supporting self-hosting. As someone in that discussion rightfu
81.
by ervine 3y ago
Are you against typescript or types in general?
82.
by ervine 3y ago
Yep their github management is atrocious. I understand it's a popular product so you get a lot of low quality issues opened, but there tons of real problems where no developer ever appears, and then are closed by the bot because of ina
83.
by ervine 3y ago
It's easy but there are decisions made that hamstring you - like being unable to change cache-control headers in the next.config.js or middleware or have your middleware use node APIs, which is especially stupid because when self-hosti
84.
by ervine 3y ago
Listen there are so many examples in that thread that this question is nothing but disingenuous. I'm sorry man.
85.
by ervine 3y ago
https://github.com/vercel/next.js/issues/22319 https://github.com/vercel/next.js/discussions/46722 Let us take control when self-hosting, please!
86.
by ervine 3y ago
Absolutely, this is the number one issue I have with next.js - they did a huge ecosystem-splitting update, but now recommend switching to the new paradigm for any issues with the old all while saying they are maintaining the old.
87.
by ervine 3y ago
Please take this seriously: stop advising in github issues to switch to App router as a solution to bugs in page router. It's not an option for large next.js projects, and certainly does not convey what you're saying here.
88.
by ervine 4y ago
Why is stevespang's comment flagged as dead?
89.
by ervine 4y ago
Eh, sometimes the predecessor is me, the fact that a large refactor remains between me and the end goal is still a blocker.
90.
by ervine 4y ago
I don't have a car. Cyclists don't need your advice, we know it's increasing our risk to ride around idiot drivers. Let's change the rhetoric from "cycling is dangerous" to "driving a car is a serious resp

More ›