31–40 of 78 posts
Well, I don't know about the API, but that's certainly the worst blog software ever made, requiring me to enable JavaScript and execute code in order to read some simple HTML and CSS. Why‽
Reading his site on an iPhone is nearly impossible.
So is this badness from over-engineering, or from complexity due to other parts of the API?
They should simply make a new one.
Well, I don't know about the API, but that's certainly the worst blog software ever made, requiring me to enable JavaScript and execute code in order to read some simple HTML and CSS. Why‽
People still disable JS in 2016? I take it that 80%+ of the web is horribly broken for you guys.
This is actually quite usable, but on about 3% of websites, it doesn't work. These site are usually those horrible abomination of bloat-pages that, for no good reason whatsoever, need javascript files from 20 different domains in order to display a static page (I'm looking at you, Wired.com). In these cases, it becomes too tedious to pick the domains that should be whitelisted.
Most times, I simply close the offending website. In the rare case that I actually want to visit the site, I temporarily switch to Chrome.
I still go through the hassle of using NoScript, because it un-breaks pages that would otherwise for no good reason whatsoever decide it's OK to intercept common key combinations (CTRL+t), disable right-clicks, serve pop-ups, pop-overs, or pop-unders, start playing videos or sound without me asking for that thank you very much, or generally try to hijack my browser, my data, or my computer.
I also thought it was perhaps a tad strange to equate CSS, DirectShow, and the Android SDK as examples of tough "APIs" to master. I get his point, but those are three pretty wildly different levels of abstraction there.
Well, I don't know about the API, but that's certainly the worst blog software ever made, requiring me to enable JavaScript and execute code in order to read some simple HTML and CSS. Why‽
People still disable JS in 2016? I take it that 80%+ of the web is horribly broken for you guys.
Earlier quoted context omitted.
Perhaps consider that coming on here and being condescending about the impact your own browsing habits have on the web experience of your (very small, but very vocal) JavaScript-disabling demographic makes the rest of us web developers really not very interested in building sites that meet your demands. I agree that the site shouldn't need JavaScript to function, but I don't think comments like these help the goal of…
OP is a bit excessive but he's right --- this website doesn't work for people without JavaScript or on mobile phones.
I think most of the author's comments apply to the Win32 API in general. Windows game developers are probably among the few tech demographics that still have to encounter it on a regular basis. Having written an entire game to the Win16 API and then later ported it to Win32 I lost a significant chunk of my life spent in drilling into GDI and DirectDraw (I think that is what it was called then) structures and entrypoi…
Back in the mid 90s I was learning how to program and understanding a Win32 "Hello world" was a royal pain compared to everything else I was doing. Functions with more than 8 parameters were the norm, structs with tens of members had to be manually initialised before calling them. And don't get me started on the WPARAM/LPARAM idiocy.
When you want to correlate events from your own code and OS events you use a tool like XPerf which knows the OS events and can read your application manifest to get strong typing on the events your application fires. This also lets you take traces on deployed software on customer machines.
If you want to roll your own event consumers you can do that too. But XPerf probably already does what you want.
This all existed back in like 2010 when I was using ETW. I'm sure the tooling has only gotten better since then. So yeah you can go write your own bad incomplete version of XPerf and not leverage your existing build process and MS tooling. But then is the API really bad? Or are you just not googling correctly?
ETW isn't supposed to be written like this at all. MS has entire codegen toolchain that lets you define events in an xml manifest as part of your build process. This codegens a C header file which lets you fire events in your own code with a simple function call. When you want to correlate events from your own code and OS events you use a tool like XPerf which knows the OS events and can read your application manifes…
Well, I don't know about the API, but that's certainly the worst blog software ever made, requiring me to enable JavaScript and execute code in order to read some simple HTML and CSS. Why‽
People still disable JS in 2016? I take it that 80%+ of the web is horribly broken for you guys.