Introductions #3826
Replies: 3 comments 5 replies
-
|
Hello Morgan, While I may not be the best person to provide feedback since I've not invested time in build_runner, the reasons I haven't may be relevant.
I would like my code base to stay clean and tidy:
|
Beta Was this translation helpful? Give feedback.
-
For what it's worth, I've been super pleased with IntelliJ's file nesting. Dart already has a bunch of file nesting rules for It would be nice if the dart plugin included at least the |
Beta Was this translation helpful? Give feedback.
-
|
Oh, interesting, thanks. It turns out VSCode has such a thing too, but it's disabled by default; search in settings for "file nesting". It helps with vertical space, which is nice; but it causes the filename to be indented with a |
Beta Was this translation helpful? Give feedback.
-
|
I use file nesting in visual studio but if some files use generation and others do not, you end up with an uneven structure |
Beta Was this translation helpful? Give feedback.
-
|
That does sound annoying. I think IntelliJ takes the win on this one :P |
Beta Was this translation helpful? Give feedback.
-
|
Hi :) ... and thanks for the feedback! Those are all great points, I'm almost 100% in agreement. I do like having I'm fully focused on performance right now; when that's under control I think "quality of life" for generator users is probably next on the list: so, more stable, better-integrated into workflows. |
Beta Was this translation helpful? Give feedback.
-
|
For me, the main issue with |
Beta Was this translation helpful? Give feedback.
-
|
Getting close now to a release that will improve performance :) it's been quite a trek. |
Beta Was this translation helpful? Give feedback.
-
Hi everyone! As you may have figured out by now, a direct result of the cancellation of macros is that I'll be working on
build_runnerfor a while. So I thought I'd introduce myself so y'all know a bit what to expect.Please call me "Morgan" :) ... my first name is "David" but I don't use it for work as I often find myself on a team with more than one "David". Precise naming is useful ;)
I've been at Google for 17 years(!).
The first big thing I worked on was AdWords, which was using GWT, the "Google Web Toolkit", a Java->Javascript compiler. That's what I was working on when I discovered Dart, and pushed for my team to be an early adopter, before being part of the whole-AdWords rewrite to Dart. I wrote built_collection and built_value and gave a talk about them at a Dart developer conference.
Right after giving that talk in 2016 I joined the Dart team--sort of. I worked on fully Google-internal Dart infrastructure: bazel builds, codegen, dev tools, SDK integration. I've spent a lot of time benchmarking dev cycles and making them faster.
At the start of 2024 I switched from working on Google-internal things to things y'all care about :) and joined the macros effort.
The tl;dr is that I'm very much into Dart codegen, dev tools, and fast dev cycles; and hopefully with lots of useful experience to apply to the problem; but also still a newbie when it comes to the internals of Dart SDK tooling and
build_runneritself.Since I've been mostly focused on Google-internal things I also haven't interacted much with "the community", except via the
built_valueissue tracker :) ... that should change I think, I look forward to hearing more about what people want from codegen and figuring out what we can do.Edit: I should have ended on a question to encourage people to say "hi". So ... ehhm ... what's your top three wish list for improvements to
build_runnerthis year?Beta Was this translation helpful? Give feedback.
All reactions