You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's worth reading through #74 to get an understanding of why the changes were made. There's a lot of discussion. There were a lot of problematic bits about the previous simple template that have been ironed out, but I can see how if you were used to those idiosyncrasies, you might miss them.
In particular regarding the modules approach, it's easier to go from no modules to modules as rust-analyzer has an extract module refactoring built-in. It doesn't however have easy move-code-to-module refactorings (yet). I previously wrote:
I have a strong (evidence based) opinion against pre-emptively organizing a project into horizontal layers. Having worked on many projects small and large, horizontal segmentation leads to poorer long term maintainability for a variety of reasons. Doing this would be pre-emptive. Put another way, if I was using the simple template personally, having the extra file would be an annoyance that I'd always want to revert. Reverting would be annoying. Refactoring in the other direction is fairly simple though - highlight code, extract to module, done.
There's definitely room for different templates to be added here. I'd suggest building it up from practices you're using in your apps, perhaps as a pythops/ratatui-template or something.
Having control on the app: terminal settings and the drawing loop.
The old templates has some advantages that I miss in the current one:
The text was updated successfully, but these errors were encountered: