<snip> in particular their integrated form designers and debuggers.
IMO, it doesn't matter how good a language is, if debugging the code written in that language is time consuming/difficult/cumbersome, the time cost erases any gains the language itself may provide.
Until about a year ago, I still used VS because of its debugger. Now it is somewhat rare that I use it for the debugger, when I do it's because its debugging of assembly code is still the best there is at this time (unfortunately.)
As a programming environment, I consider VS a complete disgrace. When it comes to editing code, I think even the missing link would run away from that thing. It's a binary inquisition, medieval torture (MS should provide free morphine with every VS download.)
Of course, I still use it because there are some libraries out there that are only available in C and porting them to Pascal is too much work.
Another very significant advantage of the Lazarus/FPC combination is that 64 bit assembly is supported and, while it is very rare that I resort to assembly, when I do it's because coding it in Pascal (or C) has very severe shortcomings. The lack of 64 bit assembly support in MS C/C++ is what caused me to have another look at FPC (looked at it before that and decided it didn't cut it at that time.) After determining that 64 bit assembly was supported, the next priority was determining the environment's debugging abilities which at the time were, for practical purposes, GDB centric and basically "adequate" (Lazarus is likely one of best front ends to GDB.)
There are good, solid and practical reasons to choose the Lazarus and FPC combination but, it's not the "groovy"/"in" language, therefore it is ignored or worse, criticized/put down, by the "enlightened" (like the OP) who believe they are programmers because they can write python code. Yeah, like the Pope is an astronaut.