Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #1594

P

PVS-Studio

Company blog · pvs-studio.com/en/blog · on HN as AndreyKarpovprogrammingsecurity

PVS-Studio is the company blog at pvs-studio.com, writing about programming and security. Since 2021, 46 different Hacker News readers have linked it 147 times, most often “What's New in .NET 8?”. No feed was found, so read it on the site itself.

147mentions?
46HN people?
2021–2026first – last linked?
Links on Hacker News per year · peak 47 in 2022

Too few sampled comments (14) to say how often HN recommends it.?

Why HN links it

HN readers link PVS-Studio blog posts as references on C and C++ pitfalls, undefined behaviour and static analysis, such as lists of mistakes in comparison functions and coding rules.

Summarised by Claude from a sample of 14 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

A static analyzer for C, C++, C#, Java, Go, JavaScript and TypeScript code. Works on Windows, Linux, and macOS. Analyzes code for 32-bit, 64-bit, and ARM embedded platforms.

The author on HN?

AndreyKarpov · 4,144 karma · member since 2011

Andrey Karpov. DevRel. Andrey Karpov is a co-founder of PVS-Studio — the company that is developing the PVS-Studio static code analyzer. The tool is designed for early detection of errors and potential vulnerabilities in C, C++, C#, and Java projects. Andrey is the author of many publications devoted to writing quality C++ code. Articles published in the company's blog: https://pvs-studio.com/en/blog/posts/?author=andrey-karpov

From their public HN profile, which links to this site.

Most-linked posts?

  1. What's New in .NET 8?
    3 people · 4 mentions · first linked 2023-11-14
  2. Terrible Tips for a C++ Developer
    3 people · 3 mentions · first linked 2023-06-19
  3. C++ programmer's guide to undefined behavior: part 1 of 11
    3 people · 3 mentions · first linked 2024-06-07
  4. The Question of Programming, Refactoring, and Everything
    2 people · 2 mentions · first linked 2022-09-11
  5. Visual Studio 2022 ate up 100 GB of memory and what XML bomb is
    2 people · 2 mentions · first linked 2021-09-09
  6. C++ is faster and safer than Rust (2020)
    2 people · 2 mentions · first linked 2021-08-15
  7. /
    2 people · 2 mentions · first linked 2025-09-25
  8. /en/blog/posts/cpp/0509/
    2 people · 2 mentions · first linked 2021-09-09
  9. .NET 7: suspicious places and errors in the source code
    2 people · 2 mentions · first linked 2022-12-14
  10. Analyzing Erlang's C and C++ modules that have been running for decades
    2 people · 2 mentions · first linked 2025-11-07

What Hacker News says?

  1. That's a bad coding style document. There's no rationale given, except for a bunch of references at the top, which are clearly argument from authority. I think the no "loop initial declarations" is for consistency with "all declarations at the top". Other coding style guides favor "declarations as close as possible to first use", including guidelines for mission critical systems (if you resort to argument from autho…

    Comment linking /en/docs/warnings/v2551/

    on “Suckless.org: software that sucks less”
  2. Submitted “Google” programmers. How one idiot hired a couple more idiots as a story · 141 points

    HN discussion
  3. > Both actually. That would be quite the surprise to me. Quite unfortunate that you can't find a source given what the -fanalyzer docs currently say. > Any UB exploits not catched by -fanalyzer would need to be disabled. I'd be curious as to the hypothetical performance impact of this, as well as the amount of work it'd take to make -fanalyzer reliable enough. > When writing Frama-C what I was thinking of was actual…

    Comment linking /

    on “Git: Introduce Rust and announce it will become mandatory in the build system”
  4. Submitted C++ is faster and safer than Rust (2020) as a story · 83 points

    HN discussion
  5. > Huh, don't think I've heard that commitment before. Do you mean that the GCC devs intend for -fanalyzer to (eventually?) guarantee catching all exploitable UB (which would be... ambitious, to say the least), or that -fanalyzer is a best-effort analysis? The docs currently state the latter more or less ("It is neither sound nor complete: it can have false positives and false negatives.") Both actually. Any UB explo…

    Comment linking /

    on “Git: Introduce Rust and announce it will become mandatory in the build system”
  6. Submitted I _____ hate arrays in C++ as a story · 20 points

    HN discussion
  7. Every single time I see Tizen, I get reminded of this, https://arstechnica.com/gadgets/2017/04/samsungs-tizen-is-ri... https://pvs-studio.com/en/blog/posts/cpp/0519/

    Comment linking /en/blog/posts/cpp/0519/

    on “Samsung accidentally freezes its smart fridges with a software update”
  8. Submitted Visual Studio 2022 ate up 100 GB of memory and what XML bomb is as a story · 17 points

    HN discussion
  9. Not only an insightful post, but also a fair number of interesting comments. A couple of resources I found in the comments: * A short list of safety rules for C: https://en.wikipedia.org/wiki/The_Power_of_10:_Rules_for_Dev... * A much longer document, 42 rules for coding in C and C++: https://pvs-studio.com/en/blog/posts/cpp/0391/ Update: also, a 210-comment thread from 2018: https://news.ycombinator.com/item?id=183…

    Comment linking /en/blog/posts/cpp/0391/

    on “Teaching C (2016)”
  10. Submitted Checking Barotrauma with the PVS-Studio static analyzer as a story · 16 points

    HN discussion
  11. Just look at this: https://pvs-studio.com/en/blog/posts/cpp/1129/ - 11 parts about C++ undefined behavior from people who specialize in finding this stuff. And that’s only the tip of the iceberg. I use C++ daily, and it’s an overcomplicated language. The really good thing about Rust or Zig is that (mostly) everything is explicit, and that’s a big win in my opinion. In defense of C++, I can only say that lots of inte…

    Comment linking /en/blog/posts/cpp/1129/

    on “In Defense of C++”
  12. Submitted Box of bugs (exploded): Perils of cross-platform development as a story · 7 points

    HN discussion
  13. Detecting errors in the LLVM release 13.0.0 - https://pvs-studio.com/en/blog/posts/cpp/0871/

    Comment linking /en/blog/posts/cpp/0871/

    on “LLVM 13.0”
  14. Submitted Bugs in games that have become features as a story · 7 points

    HN discussion
  15. > the footguns in C++ are more benign I don't think I can agree. https://pvs-studio.com/en/blog/posts/cpp/1215/

    Comment linking /en/blog/posts/cpp/1215/

    on “Fun with C++26 reflection: Keyword Arguments”
  16. Submitted Top Reddit communities for Devs and ITs: from beginners to advanced as a story · 7 points

    HN discussion
  17. avg_dev · 2022-09-07Recommends
    Replying to myself to add some things I think are real boons to development: - https://pvs-studio.com/en/blog/posts/ - I don't code in C or C++ but I love to read these posts with the limited understanding that I possess - GitHub has another product which is good https://github.com/dependabot - similar in nature to Snyk, Renovate, etc. - there was an HN thread yesterday about govulncheck which looks pretty nice as a…

    Comment linking /en/blog/posts/

    on “Quantifying GitHub Copilot’s impact on developer productivity and happiness”
  18. Submitted Holy C++ as a story · 7 points

    HN discussion
  19. What it means is that since i as the variable is monotonically increasing, an array indexing operation that is in the loop body can be replaced with an incrementing pointer instead, which eliminates quite a lot of code. An example here: https://pvs-studio.com/en/blog/posts/cpp/0374/

    Comment linking /en/blog/posts/cpp/0374/

    on “A Guide to Undefined Behavior in C and C++ (2010)”
  20. Submitted C++ programmer′s guide to undefined behavior: part 8 of 11 as a story · 5 points

    HN discussion
  21. What's new in .NET 8? - https://pvs-studio.com/en/blog/posts/csharp/1080/

    Comment linking /en/blog/posts/csharp/1080/

    on “.NET 8”
  22. Submitted What 's new in .NET 7? as a story · 5 points

    HN discussion
  23. Integration of a static analyzer into an existing project may be hard. Especially if the project is big and old. In fact, it’s not as scary as it seems to be. There are ways to do it as easy as possible: How to introduce a static code analyzer in a legacy project and not to discourage the team - https://pvs-studio.com/en/blog/posts/0743/

    Comment linking /en/blog/posts/0743/

    on “Everybody makes mistakes when writing comparison functions”
  24. Submitted Embedded system developers do not know how to program as a story · 5 points

    HN discussion
  25. The main specific is that it’s one of the most common errors. People don’t check comparison functions, but those functions have errors. You can read more here: https://pvs-studio.com/en/blog/posts/cpp/0509/

    Comment linking /en/blog/posts/cpp/0509/

    on “Everybody makes mistakes when writing comparison functions”
  26. Submitted Top bugs found in C# projects in 2021 as a story · 5 points

    HN discussion
  27. Unfortunately, I don't fully understand your comment. PVS-Studio has a variety of diagnostics. However, such simple errors still exist. By the way, PVS-Studio found errors in IntelliJ IDEA as well :) - https://pvs-studio.com/en/blog/posts/java/0603/

    Comment linking /en/blog/posts/java/0603/

    on “Everybody makes mistakes when writing comparison functions”
  28. Submitted What's New in Java 25 as a story · 4 points

    HN discussion
  29. So I want to add an explanation. As I see from the comments, many of you thought that the PVS-Studio analyzer warns about a function's unused argument. That's not quite so. Or, to be precise, this is so, but the analyzer processes this case smarter than most linters or compilers. It's a bad idea to program an analyzer so that it just issues a warning to unused arguments. Such analyzer would produce many false positi…

    Comment linking /en/docs/warnings/v2537/

    on “Everybody makes mistakes when writing comparison functions”
  30. Submitted Court is in session: Top most notorious C and C++ errors in 2024 as a story · 4 points

    HN discussion

Search all of HN for pvs-studio.com

Linked by the same people?