Registry Explorer: Replacement for the Windows Built-In Regedit.exe Tool

Re:Registry Explorer: Replacement for the Windows Built-In R... by bloblaw on Saturday July 24, 2021 @10:59PM (#27946333)

Wow, how times have changed!

I say that because when C# was released, many Windows developers refused to use it and continued to only write Windows programs in "native" languages like C++, VB6, and Delphi.

I must admit my own bias and state that I still prefer applications written in "native" code on Windows (C++ / Delphi) to C#. It's not really an issue worth arguing over these days (and hasn't been for years), but there it is. FWIW, all the SysInternals tools are C++

[ Parent | on HN ]

Re:Registry Explorer: Replacement for the Windows Built-In R... by userbinator on Sunday July 25, 2021 @02:45AM (#27947279)

The startup times are noticeably longer for anything non-native, and noticeable can turn into annoyance when it's an application you're unlikely to leave open all the time, like a registry editor.

[ Parent | on HN ]

Re:Registry Explorer: Replacement for the Windows Built-In R... by pilif on Sunday July 25, 2021 @01:00AM (#27946845)

VB6 didn’t produce native binaries

[ Parent | on HN ]

Re:Registry Explorer: Replacement for the Windows Built-In R... by bloblaw on Sunday July 25, 2021 @01:48AM (#27947008)

VB6 did support compiling "native" binaries by default, and not to p-code, as previous versions did.

https://blog.decompiler-vb.net/the-truth-about-p-code/

[ Parent | on HN ]