@mattpocockuk My Advice: Always define the type of the props inline. If you need the type somewhere else, use React.ComponentProps<tyopeof MyComponent>
@FlyingGuibou @ChShersh I feel strongly the same. Nix solves so many problems so well, once you know it it's almost frustrating that people still try solving these problems without it, or by reinventig a worse version of it.
@mitchellh I think that's the price for platform independence. I'm definitely not going to build an app that looks different on every OS, and if we have to pick one OS's style, which one do you suggest?
@housecor I'm doing this since yesrs already and really like it. What i havent found out, though is how to have dialog not inherit the style (portal) but still inherit the context.
@grhmc Yeah, at least for us it made the most sense because we really needed newline support. It'd be cool if there was a widely used and trusted command that takes in JSON and produced shell instructions compatible with the detected shell.
@mattpocockuk@turborepo The current situation is a bit unlucky. I tried to get people on board with https://t.co/ZH15O0fAch but without success. We won't see good solutions for a watch-mode soon, I guess.
@mitchellh Interesting. I honestly think that TS is the best language out there currently. It's typesystem isjust phenomenal. But yeah, the ecosystem is changing a lot, which makes it hard to keep up and codebases age really fast.
@domenkozar .env files should be killed with fire IMO. There's no standard for the format, and every tool reads them differently. That's a nightmare when your variables have newlines and other special characters in them. Better use json, toml or yaml, or anything really :D
My Nix journey so far. I still stand by that its the #1 most positively impactful technology I've learned in recent years.
- 2020: `nix-env`
- 20H2: `nix-darwin` my Mac
- 2021: NixOS, Nix Flakes dev envs
- 2022: Nix in CI to exactly match dev
- 2023: Nix to build Docker images