- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Ah, so the problem is that those nazi security guys shouldn't be looking at YOUR code, they should be looking at someone else's. That's a WTF in itself and not a comment I'd expect from someone with the, uh, cahones, to read this site.
Let's create an analogy for your comment: "who cares that my abstraction layer has no exception handling and a bunch of buffer overflows, the layer above it will always send it valid data. Always. I know this. I am brillant!".
Uh, yeah. If you seriously believe you're exempted from writing strong, secure code that is not vulnerable to one of the top security flaws in web apps just because it's not directly published outside your infrastructure (today, just wait for that last minute project requirement where it gets put out there), you need to take a sabbatical and do some reading.
If, on the other hand, your rebuttal is that your slightly amibiguous post meant the security guy found a non-existent issue, I just typed all that for no reason.
Cheers!
Admin
This is why MSFT is so bloated, every SDE and SDET must make "frameworks" (usually by taking an existing framework and wrapping it into their own New Framework) in order to get a level increase when it comes to their annual review based on their CSP's (Career Stage Profiles).
Admin
Oh sure, it's all about annual reviews. Not about F-head programmers in the field who won't do what the API documentation says and have to be protected from themselves with another layer.
*roll eyes*
Admin
The problem was that Corel Draw for Windows was written in a mixture of MFC and direct Win32, so porting at the Win32 API level was the best solution.
They did do some very nifty stuff as they ported MFC on top of their Win32 port. A CWnd was derived from an LWindow, and an HWND was defined as an LWindow*. Since the CWnd simply wraps an HWND, the CWnd was always wrapping itself. The Win32 API port and the MFC port were tied together in a mobius strip.
This was something that caused everyone who touched the code to eventually lose a day of productivity as they just stared dumbly at their monitor upon realizing all the implications.
Admin
The real WTF is that not a single person who posted on this thread noticed the misspelling of "cojones".
Admin
As someone who develops desktop apps, I can say, Java was not up to the task a few years ago, but now it is the only solution that makes sense. I routinely do all my development and testing in a pure Linux environment. I put the jar file on a CD and show up at the client's site and run it on their Windows machines. I don't do any Windows testing before I do this. These are heavy Swing apps with complicated layout and design and whatever. And it's almost flawless. I don't even need an installer. You just double-click the jar file. No other system can do this today. On top of that you have all the memory protection and safety inherent in Java.
I realize the parent topic is set in the late 90s, when Java wasn't ready, but today, we have a solution.
Admin
Tell me it was Lernout&Hauspie?
Admin
Admin
pharmacie en ligne france fiable https://kamagraenligne.shop/# pharmacie en ligne