Hot reloading isn’t special anymore, it’s table stakes for modern app development. In the meantime, the most productive development stack for me is nextjs with vercel, where I get seamless UI and sever-side hot reloading capabilities all delivered in a single NPM package. I really hope this isn’t the start of a pattern. This is a clear backslide, especially because hot reload did not start out as being only for Visual Studio. Orthogonality and cross-platform always wins in the end. It’s even more disappointing looking at the source code to see that support for it was ~1-2k lines of code, and that code has now been ripped out at the last moment. NET version of the kinds of things you see in other ecosystems (vercel/nextjs, reactjs, etc.) that are all delivered via a package manager. It’s disappointing to see dotnet watch have the existing support it’s had for a long time now get dropped. NET team, and I hope they're willing to reconsider the decision.Ī former PM for F# said it better than I could: I can only assume this decision is being made by people outside of the. This seems like a short-sighted decision that will harm the. This was going to be a flagship developer experience feature that I could get other, newer. NET is excellent developer tooling, but all too often that's been lacking for developers who stray from Windows+Visual Studio. I've been using this feature as part of my cross-platform workflow, and I was incredibly excited for it in the broader context of the. dotnet watch hot reload already seemed great to me, and if necessary it could have been moved behind a preview flag like other. I can certainly appreciate competing priorities, but this is still very disappointing. We are doubling down on VS 2022 with support for VS4Mac coming later As a result, Hot Reload will not release as a feature of dotnet watch tool. To clarify, given the number of scenarios we are working on, we had to prioritize :(. □ 1993 Atulin, KoziLord, OrganizationUsername, cartermp, LiteracyFanatic, PJB3005, JustinPealing, gortok, druchem, mgiles, and 1983 more reacted with thumbs up emoji □ 90 schmitch, artiface, townie, greglamb, nickpainter, TheAnachronism, aacevski, Je12emy, ChadJessup, mbway, and 80 more reacted with laugh emoji □ 102 schmitch, artiface, greglamb, nickpainter, EduardoLarios, TheAnachronism, aacevski, Je12emy, Hellevar, ChadJessup, and 92 more reacted with hooray emoji □ 133 dpiatkowski, aacevski, Je12emy, ChadJessup, PavelStefanov, caxepok, davidroth, ShreyasJejurkar, viniciusCamargo, alysson-souza, and 123 more reacted with confused emoji ❤️ 171 schmitch, Yanitrix, Atulin, artiface, xparadoxical, crozone, basecde, jprdonnelly, ErikReider, greglamb, and 161 more reacted with heart emoji □ 105 schmitch, artiface, greglamb, nickpainter, TheAnachronism, alexyakunin, aacevski, Je12emy, Hellevar, ChadJessup, and 95 more reacted with rocket emoji □ 239 AnthonyMastrean, gortok, JohnLouderback, schmitch, cfbao, jwillman, a10r, daltonks, marcantoinecouture, Kableado, and 229 more reacted with eyes was kind enough to clarify on Twitter (and to be clear, I do appreciate it please don't shoot the messenger):
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |