The compilation stage is likely going to be the only major bottleneck with that PC. That would be a concern with an IDE or command-line.
The main question is how long would it take to complete the compilation for what would be an average sized amount of code for you. Is that time lag acceptable?
More memory and/or a faster processor certainly would speed things up.
If you want an IDE for that PC, I would recommend Code::Blocks. It is less of a hog than Visual Studio.
http://forums.codeblocks.org/index.php?topic=16779.0
C::B is also more agnostic when it comes to operating systems. You get used to how to do things with C::B on Windows, switching over to Mac or *nix
should be easy.
The specs of the PC IMO might be better suited to doing command-line work. YMMV.
The choice is yours, on my programming PC I use MSVC and C::B.
The minimum requirements for VS2019 don't look all that hefty considering it is Windows and MS:
https://docs.microsoft.com/en-us/visualstudio/releases/2019/system-requirements
VS2017 is about the same:
https://docs.microsoft.com/en-us/visualstudio/productinfo/vs2017-system-requirements-vs
A summary of the stats for my programming PC (over 6 years old, pieced together from a used PC box):
Operating System
Windows 10 Pro 64-bit
CPU
Intel Core i5 2400 @ 3.10GHz
Sandy Bridge 32nm Technology
RAM
12.0GB Dual-Channel DDR3 @ 532MHz (7-7-7-20)
Motherboard
Hewlett-Packard 1495 (SOCKET 0)
Storage
232GB Samsung SSD 850 EVO 250GB (SATA (SSD))
1863GB Hitachi HDS5C3020ALA632 (SATA ) |
The only major change since I built this PC up as a used kit was getting the SSD to replace a regular SATA HD. That really does make a difference in overall performance.