Re:Visual Studio Code is designed to fracture
by JoeOfTexas on Sunday September 29, 2024 @11:51PM
(#41693380)
That just sounds painful if you work on large projects.
[ Parent
| on HN ]
Re:Visual Studio Code is designed to fracture
by __MatrixMan__ on Monday September 30, 2024 @12:52AM
(#41693656)
Then again, maybe large projects are a bad idea.
Re:Visual Studio Code is designed to fracture
by tobyhinloopen on Monday September 30, 2024 @01:40AM
(#41693907)
Proudly written on a device run by a huge collection of huge projects
Re:Visual Studio Code is designed to fracture
by broodbucket on Monday September 30, 2024 @01:02AM
(#41693710)
They tend to have this nasty habit of running the entire world, though.
Re:Visual Studio Code is designed to fracture
by TZubiri on Monday September 30, 2024 @02:21AM
(#41694096)
Rarely, it's mostly small projects, but many many many of them.
Re:Visual Studio Code is designed to fracture
by jamesfinlayson on Monday September 30, 2024 @01:21AM
(#41693791)
Yeah, early in my career I got by with gedit on Ubuntu but before too long a 700,000+ line PHP project with deep, deep inheritance trees showed up and I very much embraced an IDE.
Re:Visual Studio Code is designed to fracture
by TZubiri on Monday September 30, 2024 @02:08AM
(#41694040)
Would running a command line debugger be too different from your approach.
I would consider bothering with some static analysis tool, but definitely not with php or other runtime heavy languages.