【Old Post 4】What is the best thing to use?

辛昕

【Old Post 4】What is the best thing to use? [Copy link]

I would like to ask, is it better to use DDK or WDK for driver development now? I haven't read the old posts for a while. After an unusually busy week, I have a little free time before going to bed at 12 o'clock in the evening, so I "have a change of heart" - start again [old post] This post was posted in 2009 - to be honest, I am a complete stranger to Windows development, and I am a little embarrassed, because I didn't know that WDK existed so long ago. This post is very simple. The original poster's post is very simple, and the reply is also very simple.

I would like to ask, is it better to use DDK or WDK for driver development now? Because I am a novice, I hope to choose a better starting point in the long run. I don't mean to say any technology is bad, haha, I hope someone can give me some advice, thank you

This content is originally created by EEWORLD forum user Xin Xin. If you want to reprint or use it for commercial purposes, you must obtain the author's consent and indicate the source

辛昕

First of all, I have basically never done any development related to Windows. The programs I have run on my computer are either C/C++ console programs or one or two unfinished QT programs. Well, I wrote Delphi for a while five years ago - don't get me wrong, that was not good enough. So, to be honest, in discussing this post, I have no intention of discussing technical issues shamelessly. The focus of my attention is actually the following sentence.

Choose a better starting point in the long run

辛昕

Looking back at myself, I also had many so-called choices back then, and I was entangled - which one would be better in the long run? I think I must have forgotten many of the choices I made. The only two that have influenced me to this day, I think, are probably my choice of stm32. I chose C. However, are these two choices correct? From some perspectives, they are correct. stm32 has indeed replaced and surpassed the 51 of that year. Recently, the famous Zhengdian Atom in Guangzhou also held an event, which is probably the first event. Unfortunately, I didn't have time to attend the meeting. I signed up online on WeChat, but I was busy with work that day and basically forgot about it. What about choosing C? Well, I just want to say that in the future, apart from work, I will force myself to use cpp to write any code that I wrote in C before. Including microcontrollers. I think this may end my ten years of C language development experience. From the perspective of getting rich, neither of these two choices gave me any signs of rapid success. From other perspectives, except for my little pride in C syntax, I may not have much ambition.

辛昕

I chose STM32 as my general-purpose model. As it turns out, during my working time, the projects I used STM32 in total were less than 30%. In my spare time, although I often choose STM32 whenever I want to verify or do something, I am ashamed to say that I still don’t have any complete STM32 projects. So recently, I began to reflect on how important the so-called long-term is. I used to despise VB. This may be the only serious course I took in college, but of course I basically never heard of it. I also used to struggle with whether to use vs, codeblocks, or something like dev. For graphical interface programming, is it qt? Unfortunately, as mentioned above, except that codeblocks is now my most commonly used console programming IDE, until the last month, I basically didn’t touch qt and fell to the point that I hadn’t even written a basic serial port tool. So, for this question, I plan to end it very plainly like this - when you think about the long-term, you’d better first imagine how long you can have a long-term vision? One project, two projects, or one or two years? Then, in the end, will you be like me and finally accept: whichever is easier, whichever is more suitable? It may even become whichever has a routine, whichever works, whichever is better.

懒猫爱飞

Pass by, take a look, think about it, and continue coding...