VbAsyncSocket VS tls1.3

I wonder if it is possible to make https://github.com/wqweto/VbAsyncSocket compile on Visual Basic 4, then you could target 16 bit.

What is impressive (or hilarious) is that someone opened an issue because it wasn't compatible with VB5[0]. The maintainer added a VB5 branch which apparently fixed the issues.

[0] https://github.com/wqweto/VbAsyncSocket/issues/4

You are right.

What is a good idea however, is to implement a TLSv1.3 library in Visual Basic 6[1], that doesn't have any external dependencies, by embedding machine code for AES encryption generated with MSVC in the source code, that you patch into memory at runtime, by using all sorts of tricks to do things in VB6 that you aren't supposed to do in VB6. Yes, that VB6, that was released in 1998, superseded by VB.NET in 2002. Because Microsoft has just announced it's supported on Windows 11.[2] So when developing new software, why not use something future-proof?

[1] https://github.com/wqweto/VbAsyncSocket

[2] https://docs.microsoft.com/en-us/previous-versions/visualstu...

After a quick Google Search, I found this: VbAsyncSocket

Anyway, that link for VB6 looks poromising: https://github.com/wqweto/VbAsyncSocket - it is using calls to ws2_32,dll, so it is up to date. I'll dust off VB6 to see how it works in that version, before I try to use it with VBA. VBA is not quite the same as VB6, very similar language, but not all of the same features can be implemented.

Largely because of myths surrounding it, for example parenthesis syntax and lack of editor support. With paredit, you get meta level direct AST manipulation support in emacs that is still light years ahead of any programming IDE out there. I think the other fear factor is you have to think a lot more about how to approach the problem when writing Common Lisp and it requires a more complete engineer due to a smaller library ecosystem. Usually there is one and sometimes two libraries for doing X and if not you’re up for making a library yourself.

I’m attaching an example of how quickly you can write TLS 1.3 by a single person in Common Lisp. At the time I wrote this library most websites still struggled with TLS 1.3 support.

https://github.com/mateuszb/tls1.3

If you want an example of expressivity you can take a look at

https://github.com/mateuszb/tls1.3/blob/master/elliptic-curv...

For EC crypto with a full NIST vector test.