Post by R.Wieser
i dont say i belive it, but still i just dont know
You seem to be falling for something called FUD (Fear, Uncertanty, Doubt).
Don't. When you do not shake it you won't be able to move forward. :-\
Lets face it, whats the *absolute worst* that can happen. That would be
that the next update removes that DLL. And that won't happen because the OS
needs it, and scores of other commercial software relies on it.
The next-worst think would be that the next OS version (Win11 ?) will not
have it anymore. But thats a problem for over a couple of years or so, and
than you will also know what its than replaced with.
So, stop worrying and start coding! :-)
its not quite about this fud (though partially)
its more about i got experience in winapi but i got no experience in winapi network coding and i just dont know whats best for this purpose
wininet seem most logical but i would prefer to know it a bit more (besides i not code it yet as i code other things, i will be coding it later, no hurry here)
right now i decided to read slight over whole map of winapi and get bigger sight
check btw i am using other parts of winapi and im not much more worry as they
partially marked as deprecated (as they are somewhat core of winapi and much things stay on it)
for example i use a lot of blitter from gdi (gdi is said to be deprecated) i would use it still hovever GDI was
and probably is scandalously slow
- if i would like to write text editor and render true type fonts hovever i would probaby still using just gdi
for sound output i also used winmm which is probably also said to be deprecated (im not sure) (i used WaveOut kind of staff, not much of it hovever it worked)
this is all becouse my primary app target of choice is "windows xp 32 bit and above" and also i like old core components, this means i dont fear of deprecation but i just want to know what is just technically best