Because basically grandparent sayd: "DGA would fix the mouse issue, but unfortunately some numbnuts think the entire DGA is obsolete, but it's really only the write-directly-to-the-framebuffer part that is obsolete, the rest of it is fine".
And then a numbnut promptly crawls out of the woodwork to respond with "errr, but didn't you hear that DGA is obsolete because it allows apps to write directly to the framebuffer".
And mods happily mod it up to 5 Insightful, rather than 5 Funny (or -1 Reading Comprehension).
It's hard enough to translate source code from one language to another and end up with a maintainable code base
Indeed, this is mostly for device drivers, browser plugins, middlewares, rather than full-blown applications.
....there you have all comments, high level control structures, classes, and templates or macros intact.
It's surprising how much info C++ leaves in compiled code. You have the type of function parameters, names of classes, and even templates. Templates are fun because they are re-compiled, not linked, and this code allows even further inference about the application's own classes. But it's true, templates do make the decompiler more complex (more advanced pattern matching needed than for decompiling normal code).
You are right about the comments though, these are indeed lost.
Decompilation, even if you reverse-engineer the low level control structures and detect unrolled loops and other optimizations
It's probably all a matter of the optimization level with which the code has been compiled. Most code is surprisingly easy to decompile, and the "funny" parts are often not due to loop unrolling, but rather inline assembler macros (strlen, etc), which once recognized can be easily replaced by the decompiler with their name.
doesn't leave you with something that you can take forward long term... and I don't see that changing.
But it's golden if all you want is have a 64 bit version of a middleware of which you only have a 32 bit binary.
...because someone somewhere decided that DGA was "deprecated" and never mind that the deprecation was ONLY concerning its graphic component.
DGA sucks. It's a painful kludge. When you use DGA, you are asking both X and the kernel to stand back and respect your right to draw whatever you like on the framebuffer. This is a hell of a lot harder than it sounds, and is just simply fail in modern setups.
Hehe. Why is the above modded Insightful, rather than Funny?
Hehe, a colleague of mine is ambulance nurse, and he loves to "entertain" us during lunchtime with his very graphic descriptions of accident victims and other yucky stuff. Has occasionally netted him an extra desert too:-)
Things may have changed since the banking crisis, but until very recently, CSSF has indeed been very lax about enforcing its regulations.
The goal here is to not upset banks, so that we can attract more banks to our lovely country. Until last year, the CSSF had only shut down one single bank, and only because they really overdid it a teeny little bit.
Smaller fraudsters (such as Dresdner Bank, which offloaded Argentinia obligations to unsuspecting investors in the late nineties) were being ignored by the CSSF. The fact that the manager of CSSF and the manager of the Luxembourgish branch of the Dresdner were good personal friends probably helped somewhat too.
And forget about the courts. If you hire a Luxembourgish attorney to attack a bank, the bank will pay him double behind your back to lose your case. Moreover, many of the defrauded customers tried to hide the invested money from their tax administration, which makes them wary about raising too big a fuss about it, and the banks know that.
Well, many users use LaTeX because they are concerned about viruses. And will probably continue to use LaTeX, unless this article turns out to be workable.
For most small businesses cash flow is critical. If you don't have a record of who paid you in the last month then you can't invoice the rest and you are dead.
Hasslesome (and costly), yes. But not a death sentence.
Indeed, for most businesses, customers pay via a bank, rather than cash. So you can "just" go over your bank statements, and re-enter the data.
I had once tried the other hole, but the banana just refused to enter, and got squished instead. Even leaving the peel on didn't help, it just burst open.
If you want something else than oral sex, use a harder fruit instead, such as a cucumber.
Or a potato, if really nothing better is available.
A couple of years back, they managed to get a Slashdot comment censored that quoted OT VIII verbatim.
No other organization has so more managed to make Slashdot cave.
And even Scientology regretted it, because in the wake of that censorship, OT VIII was reposted so frequently that their lawyers wore out their pens attempting to catch up with take-down notices.
It will eventually expire from google's cache on its own. But it won't expire from Slashdot. Unless Pearson is somehow involved with the clams, then even Slashdot caves.
So, if you get a take down notice, perform the following steps:
Take the offending work down.
Post an "Ask Slashdot" story (with enough detail to allow people to locate the work from google cache).
keep reloading slashdot until you see somebody post the stuff from google stuff (or alternatively, if everybody is too dumb to figure it out, or too coward to do it, just fricking post it yourself, from an anonymous account)
rejoice, as nobody except the clams is foolish enough to sue Slashdot...
And more importantly, can they prove that you received it (the post office can and does lose letters occasionally, or you might be on an extended trip...)
Well, now that you posted to Slashdot, you can unfortunately forget about that part.
So better take it down, it's been safely backed up anyways by now:-)
This is Slashdot . Everyone around here knows that ActiveX must be married to the OS in order to have plausible cause to bundle the browser with the OS. If it could be sandboxed to easily, a judge might get the idea to force Microsoft to dissociate both products.
You'd still need to get the data back to the site. What if at the datacenter, nodoby is reachable, or what if all faxes and phones of the school (needed to receive the list back from the datacenter) are submerged in water too?
Unfortunately, I don't think I clarified what I meant by "crossing that bridge." The point I was trying to make was that from a user standpoint, it is unreasonable to stop using a piece of software solely because vulnerabilities may present themselves.
O, and I naively thought that by the "bridge" you meant a cure for AIDS. Silly me...
I am not advocating that nothing be done to address the vulnerabilities before viruses are written, nor do I advocate doing nothing to protect yourself from said viruses.
Hmmm, but what can we do to protect ourselves, if LaTeX doesn't?:-)
Slashdot Mirror
And then a numbnut promptly crawls out of the woodwork to respond with "errr, but didn't you hear that DGA is obsolete because it allows apps to write directly to the framebuffer".
And mods happily mod it up to 5 Insightful, rather than 5 Funny (or -1 Reading Comprehension).
It's hard enough to translate source code from one language to another and end up with a maintainable code base
Indeed, this is mostly for device drivers, browser plugins, middlewares, rather than full-blown applications.
....there you have all comments, high level control structures, classes, and templates or macros intact.
It's surprising how much info C++ leaves in compiled code. You have the type of function parameters, names of classes, and even templates. Templates are fun because they are re-compiled, not linked, and this code allows even further inference about the application's own classes. But it's true, templates do make the decompiler more complex (more advanced pattern matching needed than for decompiling normal code).
You are right about the comments though, these are indeed lost.
Decompilation, even if you reverse-engineer the low level control structures and detect unrolled loops and other optimizations
It's probably all a matter of the optimization level with which the code has been compiled. Most code is surprisingly easy to decompile, and the "funny" parts are often not due to loop unrolling, but rather inline assembler macros (strlen, etc), which once recognized can be easily replaced by the decompiler with their name.
doesn't leave you with something that you can take forward long term... and I don't see that changing.
But it's golden if all you want is have a 64 bit version of a middleware of which you only have a 32 bit binary.
Are we just afraid of negative feedback from anti-forking people?
Or maybe we are afraid of some knifing (backstabbing) by the pro-knife people?
Most commercial software houses of any size are extremely loathe to release source for their products,
If that is the case, why then are they then so eagerly giving out a license to legally decompile their program?
Indeed, in the European Union, according to articles 5.3 and 6 of the European "copyright" directive of May 14th 1991, it is allowable to reverse engineer a program in circumstances where this is necessary to achieve interoperability.
Right now, decompilation is a pretty rare occurrence due to lack of appropriate tools, but this is changing...
...because someone somewhere decided that DGA was "deprecated" and never mind that the deprecation was ONLY concerning its graphic component.
DGA sucks. It's a painful kludge. When you use DGA, you are asking both X and the kernel to stand back and respect your right to draw whatever you like on the framebuffer. This is a hell of a lot harder than it sounds, and is just simply fail in modern setups.
Hehe. Why is the above modded Insightful, rather than Funny?
And then if they merge back together, it'll be a blush!
Or just add some Sprite to the white wine, and you'll have some nice Champagne.
Let's just hope it's not fizzy Lambrusco.
No, for that you also need to add an Alka Seltzer...
Surely everyone here on slashdot know that Rosé is not simply a mix of red and white wines... Don't they...
Not if the airheads in Brussels have their way...
Hehe, a colleague of mine is ambulance nurse, and he loves to "entertain" us during lunchtime with his very graphic descriptions of accident victims and other yucky stuff. Has occasionally netted him an extra desert too :-)
The goal here is to not upset banks, so that we can attract more banks to our lovely country. Until last year, the CSSF had only shut down one single bank , and only because they really overdid it a teeny little bit.
Smaller fraudsters (such as Dresdner Bank, which offloaded Argentinia obligations to unsuspecting investors in the late nineties) were being ignored by the CSSF. The fact that the manager of CSSF and the manager of the Luxembourgish branch of the Dresdner were good personal friends probably helped somewhat too.
And forget about the courts. If you hire a Luxembourgish attorney to attack a bank, the bank will pay him double behind your back to lose your case. Moreover, many of the defrauded customers tried to hide the invested money from their tax administration, which makes them wary about raising too big a fuss about it, and the banks know that.
Well, many users use LaTeX because they are concerned about viruses. And will probably continue to use LaTeX, unless this article turns out to be workable.
... with a hat on.
For most small businesses cash flow is critical. If you don't have a record of who paid you in the last month then you can't invoice the rest and you are dead.
Hasslesome (and costly), yes. But not a death sentence.
Indeed, for most businesses, customers pay via a bank, rather than cash. So you can "just" go over your bank statements, and re-enter the data.
But boy, what a tall and handsome chap! And such a nice tan!
I see the relevance of cucumbers, but cheese tacos? Aren't they way to squishy for sex?
banana... oral
Well, that's usually how I eat a banana.
I had once tried the other hole, but the banana just refused to enter, and got squished instead. Even leaving the peel on didn't help, it just burst open.
If you want something else than oral sex, use a harder fruit instead, such as a cucumber.
Or a potato, if really nothing better is available.
(Sorry really couldn't resist...)
No other organization has so more managed to make Slashdot cave.
And even Scientology regretted it, because in the wake of that censorship, OT VIII was reposted so frequently that their lawyers wore out their pens attempting to catch up with take-down notices.
Why balls? Pearson is not involved with the clams, so what does he have to fear?
So, if you get a take down notice, perform the following steps:
Was it certified? Can they prove they sent it?
And more importantly, can they prove that you received it (the post office can and does lose letters occasionally, or you might be on an extended trip...)
Well, now that you posted to Slashdot, you can unfortunately forget about that part.
So better take it down, it's been safely backed up anyways by now :-)
This is Slashdot . Everyone around here knows that ActiveX must be married to the OS in order to have plausible cause to bundle the browser with the OS. If it could be sandboxed to easily, a judge might get the idea to force Microsoft to dissociate both products.
You'd still need to get the data back to the site. What if at the datacenter, nodoby is reachable, or what if all faxes and phones of the school (needed to receive the list back from the datacenter) are submerged in water too?
Unfortunately, I don't think I clarified what I meant by "crossing that bridge." The point I was trying to make was that from a user standpoint, it is unreasonable to stop using a piece of software solely because vulnerabilities may present themselves.
O, and I naively thought that by the "bridge" you meant a cure for AIDS. Silly me...
I am not advocating that nothing be done to address the vulnerabilities before viruses are written, nor do I advocate doing nothing to protect yourself from said viruses.
Hmmm, but what can we do to protect ourselves, if LaTeX doesn't? :-)
That's indeed a more natural form of Word processing. Whether it is better at protecting against viruses than LaTeX is open for debate.