News for hackers. Stuff that matters.
Re:The creeping scourge of tooling config files in project r... by sroussey on Wednesday August 05, 2020 @09:23PM (#24067330)
This is a UI problem, not a file location problem. GitHub and VS Code (both M$), could implement a nice way of grouping these files out of the of other files at the tip level.
Re:The creeping scourge of tooling config files in project r... by spanhandler on Wednesday August 05, 2020 @09:33PM (#24067364)
Oof, I hate it when an IDE/editor tries to "helpfully" present the file tree differently than it actually is.
Re:The creeping scourge of tooling config files in project r... by lokedhs on Thursday August 06, 2020 @01:20AM (#24068318)
Like what the Windows file manager does. This is something that absolutely infuriates me every time I use Windows. It's actually difficult to figure out what directory you're actually looking at sometimes because ever the address input bar is lying to you.
Re:The creeping scourge of tooling config files in project r... by FridgeSeal on Wednesday August 05, 2020 @10:29PM (#24067627)
Looks pointedly at Visual Studio.

Few pieces of development-related software frustrate me more than Visual studio.

The seeming disconnect between what's on disk, where on disk it is, and where and how it's displayed in the UI is cavernous. It also outright ignore things that are present in the folder unless you explicitly add it through the interface. God forbid you drop a file in, add it through the UI then move it because you discover you've dropped it into the wrong one of the 3 million nested folders large dotnet projects seem to generate.

Changing things on disk underneath it practically gives it an aneurysm. VSCode and IntelliJ IDE's handle the same situations without panicking, so why is VS so fragile?

Re:The creeping scourge of tooling config files in project r... by balfirevic on Wednesday August 05, 2020 @10:49PM (#24067705)
> The seeming disconnect between what's on disk, where on disk it is, and where and how it's displayed in the UI is cavernous. It also outright ignore things that are present in the folder unless you explicitly add it through the interface. God forbid you drop a file in, add it through the UI then move it because you discover you've dropped it into the wrong one of the 3 million nested folders large dotnet projects seem to generate.

This is no longer the case for "new style" VS project files (used by default on .Net Core projects). It works sanely now.

Re:The creeping scourge of tooling config files in project r... by overgard on Wednesday August 05, 2020 @10:47PM (#24067699)
I think it's because of C++ in large part. For whatever reason there's been weird conventions in different code bases on how to structure headers vs source (like, put them in the same dir, or have an "includes" and "src" dir that mirror each other, or have an includes dir that doesnt match the src dir at all. Not defending it because it sucks, but I think .NET just inherited that weird interface because its what C++ did.
Re:The creeping scourge of tooling config files in project r... by alpaca128 on Thursday August 06, 2020 @03:08AM (#24068771)
In my opinion that belongs to the problem category "the software thinks it's smart and tries to simplify something for you".

Some programs try to "correct" your input, some hide or even remove settings so they can't confuse users, some produce all kinds of popups in order to help but only obstructing the view of some information or messing up UI focus in the process, and the list goes on.

This is the best way to make me use other software whenever I have the choice.

Re:The creeping scourge of tooling config files in project r... by jonoc on Wednesday August 05, 2020 @09:28PM (#24067345)
This assumes everyone is using GitHub and VS Code - I think the main issue is applying it to the node ecosystem as a whole