tag:blogger.com,1999:blog-3554166144204741789.post8298349526866553797..comments2023-12-31T02:16:32.747-08:00Comments on 1-800-MAGIC: Unix vs. WindowsSergey Solyanikhttp://www.blogger.com/profile/03811112928687191837noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-3554166144204741789.post-23321129071855042652007-12-20T17:49:00.000-08:002007-12-20T17:49:00.000-08:00:) as I sit here and stare at kd I just have to s...:) as I sit here and stare at kd I just have to smile ;)Chris Grayhttps://www.blogger.com/profile/01390218243410866133noreply@blogger.comtag:blogger.com,1999:blog-3554166144204741789.post-4262920534098380812007-12-20T10:25:00.000-08:002007-12-20T10:25:00.000-08:00NT kernel is a mess. While KD seems to be adequate...NT kernel is a mess. While KD seems to be adequate for the job it is a very low level tool and you do need to be a black wizard to fully utilize it. You do need to understand what Windows does on assembler level to KD it. But I saw some people very good at it, so it can be done, I guess. The biggest issue with NT is interdependence. You *REALLY* have to know what is going on in *ALL* Window guts even if you just write a non-trivial mini-filter. That is much harder to do so. You may read a lot of code ( if you work for THE company) and try to understand it, but it is a very difficult task and as Sergey said you may need help of few people from different components to get job done. People outside may not have this luxury , so, writing drivers is very hard and if not BSOD, they will cripple you system most likely in one way or another.<BR/><BR/>As for high level API... whatever ;-) Most luck any logic, so, they come and go. The practical approach: cook books and samples. Like it or not, but it may be easy to get the idea and adapt it to you needs. That sounds bad for people who want to know it ALL really well and "become really proficient" but is it worth it if you will only work with it say for 1-2 years or less? There is just no good choice and our brain seems to be excellent patern recognition machine up to this task. It is just not practical to really learn big complex frameworks that can be very different in concept to what you know and used too. Good Hot-to book is my choice and if you will have to stick with technology you will ultimately master it in a few years anyway :-) and if not, who cares ?DzembuGaijinhttps://www.blogger.com/profile/18060101061698045052noreply@blogger.comtag:blogger.com,1999:blog-3554166144204741789.post-48174178191795299752007-12-20T05:28:00.000-08:002007-12-20T05:28:00.000-08:00Compare, for example, a learning curve for regular...<I>Compare, for example, a learning curve for regular Windows UI programming model (which I think was really well designed) with Avalon. The former requires maybe a day to get right, and maybe a week to become really proficient. The later I have no idea, because after trying to grasp it for a couple of days, I gave up.</I><BR/><BR/>Maybe you are just tired of computer programming? May that's why old good technologies is better for you?<BR/>I've spend plenty of time to learn f*ng GDI. It's a technology makin you thinking about your UI from the viewpoint of technical restrictions. "You do not supposed to use multiply composition because f*ng core will loose control of object handlers". "You are not able to redefine view of a control because its behaviour is strict bound to existing one." And so one.<BR/>But I've just read Sells book on WPF to be full-armed to make Avalon UIs of any complexity.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3554166144204741789.post-14933756610838072652007-12-20T00:02:00.000-08:002007-12-20T00:02:00.000-08:00You're not supposed to use raw libX11 to draw UIs....You're not supposed to use raw libX11 to draw UIs.<BR/><BR/>That would be equivalent to use raw NT kernel calls to write Windows programs.<BR/><BR/>You understand, libX11 should implement X11 protocol. If you want it to be more abstract, you'll either have to bloat libX11, which is conceptually wrong since everyone would use raw calls to program their own toolkits anyway, or bloat X11 protocol, which would be terrible wrong.<BR/><BR/>The kind of xlib you really want is Xaw, but it's not really supposed to be used now :)<BR/><BR/>As for the rest of article, it was interesting, mirroring my own experience.Илья Казначеевhttps://www.blogger.com/profile/08047072519984995214noreply@blogger.com