←back to thread

58 points Ezhik | 1 comments | | HN request time: 0.196s | source
Show context
ktpsns ◴[] No.46221220[source]
I remember that not having the right VB DLL was a frequent issue when trying to run EXE files produced by people with visual basic. For me, this Windows "nocode" environment was a big gatekeeper which hindered me in learning programming. It may sound a bit sentimental, but I learned C with Linux, because docs where readily available and open. I literally read man pages.

Today the tooling is just better. Just think, for instance, of the go and rust tool chains which easily produce ready to ship EXE files. Classical toolkits such as Qt still are around.

replies(2): >>46221717 #>>46223638 #
kwanbix ◴[] No.46221717[source]
If you did it in Delphi it will work no matter what.
replies(1): >>46225768 #
gaigalas ◴[] No.46225768[source]
"no matter what" is pushing it.

It was very common for Delphi programs to use stuff that required external DLLs.

replies(1): >>46237701 #
kwanbix ◴[] No.46237701[source]
Only if you wanted to include database options.
replies(1): >>46238111 #
1. gaigalas ◴[] No.46238111[source]
Connectivity to databases was one of Delphi's main selling points.

I think one dude spread the myth of no DLLs in the Twitter thread, lots of people repeated it, and since Delphi 6/7 is not around anymore and it's hard to check, they got away with a slight historical innacuracy.