Nonetheless, if a firm has committed to Windows (which alone is a problem, but assume they've done that), it is perfectly fine to use ActiveX for systems. IE is simply a runtime, and having to use the IE runtime for some internal systems -- get the hell over it.
As others have said, blog posts like this are never professionally constructive. While some readers might sympathize with the writer, most will wonder if the problem is really with the writer (the old http://www.despair.com/dysfunction.html). There is an unavoidable smell that the writer might be toxic.
Which of course the writer can disregard. I've burned bridges and never had an ounce of concern because I understood that I was burning bridges and embraced that. If the author is doing that knowingly, then brilliant for them.
ActiveX is apparently still really big in South Korea for some reason - http://www.techdirt.com/articles/20120507/12295718818/south-...
Nonetheless, if a firm has committed to Windows (which alone is a problem, but assume they've done that), it is perfectly fine to use ActiveX for systems. IE is simply a runtime, and having to use the IE runtime for some internal systems -- get the hell over it.
As others have said, blog posts like this are never professionally constructive. While some readers might sympathize with the writer, most will wonder if the problem is really with the writer (the old http://www.despair.com/dysfunction.html). There is an unavoidable smell that the writer might be toxic.
Which of course the writer can disregard. I've burned bridges and never had an ounce of concern because I understood that I was burning bridges and embraced that. If the author is doing that knowingly, then brilliant for them.