![]() ![]() Clear and easy-to-read characters to reduce eye strain when spending hours looking at hundreds of lines of code.So what’s in a suitable programming font? Here’s what you need to look out for. Some programmers may not even realize they’re using a subpar font until they switch to a community-backed alternative and realize how better things can be.Ī good font can minimize headaches, make your code easier to scan, and even revolutionize how you work. While most of these programs offer the ability to switch fonts, many people don’t take advantage of it. Usually, they use a monospaced system font, and while it may work fine for some, others report eye strain or poor readability. IDEs and developer tools don’t always come packaged with the best font. I'm paying good money every year for all products pack and can barely use the software anymore in its current state.Check Out Our Video Guide to the Best Coding Fonts File icons popping in one at a time over 5 or so seconds, indentation in the file tree also "loading in" later. The apparent cluelessness as to what can cause this is astonishing.Īpart from that, it's just gotten really slow. I always loved JetBrains IDEs but recently I find myself using VS Code more and more because of this. Constant indexing (including excluded directories, freezes only remediable by killing the IDE in task manager, etc.) - and the Toolbox won't even let me go back to 2020.2. My colleagues are also experiencing this. My PhpStorm IDE (2021.3.1) also behaves exactly as described by OP since mid-2020 and it is getting worse with every version. Or check if this happens on a simple IDE restart. So please check if this happens if you gracefully exit IDE. Of course, IDE would feel sluggish when it's doing a full reindexing. Was IDE shut down forcibly? Or did you by any chance initiated OS shutdown/reboot while IDE was running? This is a typical reason for a complete project re-indexing. You can keep both IDE installations for a test.Ģ) there was a re-indexing event triggered by an incorrect IDE shutdown. These delays could happen when IDE fails to access some of the OS libraries, this could happen when IDE is installed using 3rd party app managers like snap. I can see there's ~15 seconds pause/delay on an IDE startup. You've uploaded a log file for a single IDE startup, which might not be sufficient to analyze the whole picture.ġ) try to download & install the IDE using our standalone installer. I am left with either the option to do a standalone installation of 2020.2 (not snap !), or move to Visual Studio or somethingĬould you please re-upload the logs archive instead? It contains indexing performance metrics as well. What going on, Jetbrains? Please make PHPStorm reliable like 2020.2 was. The bells and whistles (let's look at one example: remote coding, CodeTogether or CodeWithMe or whatever you call it) is realistically used by a small % of users and can be worked without anyway, we had perfectly fine solutions and workarounds.īut making it THIS slow in favour of adding such bells and whistles ? Well, it's at a point where I dread doing either, now it's at the point where it's in the back of my head: "&*^&, I have to restart PHPStorm".ĩ9% of your users would rather choose a reliable, fast, software in place of one that has 500 extra bells and whistles since 2020.2 onwards, making it nigh on impossible to work with. Have to work with 2 (or god forbid, 3 or 4 microservices) at once? Wait 5m, 5m, 5m. Have to free up resources for something else? Wait 5minutes reopening it. and by 2021.2 however, indexing is extremely slow and CONSTANT, nigh on impossible to work with. 2020.3 started indexing every time, it was. My configuration does not even matter, because the simple fact of the matter is this: My system is by no means slow either, this should be clear. ![]() FINALLY, on 2021.2.2, I am as of now at 2021.2.2 and the indexing has become SO SLOW and problematic that it now takes 5m EACH TIME I open up the software. So, I just caved in because of snap pm, and just let my PHPStorm software get updated quarterly, because I deemed that should be the case, anyway, ultimately.ģ. I used to snap revert my package because of it, but snap package manager cannot be configured to NOT update packages (what a stupidly annoying decision but this is another story), so every few days I would see my PHSTtorm back up to 2020.3. On 2020.3, it was the first version (in my experience) where it started indexing every time I opened up the sofware, taking 1m-2m or so on my various projects. On 2020.2 it would index every few weeks / months or so. Ever since 2020.2, every time I open up the software (on Debian by the way), it takes a lot of time.ġ. This is exactly my same issue and this has NOT been resolved, in fact it just became worse with each version apparently. I have found a ticket that has since been closed, somebody complaining about 2020.3 being slow: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |