D2 is a very nice language. The standard library situation is a total mess, but then again a completely insane standard library never stopped C++ from taking over the world (I mean "push_back", seriously guys?).
D2 should take over the world. There are absolutely no places in which it is a worse language than C++ and about a million places in which it's better. In practice it probably won't for the same reasons I spend my days writing Java and C++, both languages that are practically Sanskrit in computer terms these days but have very mature toolchain support, big libraries, and lots of developers who know them.
It's been broken in a way that probably does not allow it to be used to decrypt phone traffic - big difference. That said, it's unfortunate that KASUMI has this weakness, even though it appears to be the result of new cryptographic research, given the speed with which new ciphers can be rolled out.
The (open source) Chrome updater doesn't "refuse to install". Wait an hour or two after the last Google program using it has been uninstalled, it'll wake up to do an update check, discover it has nothing to do and remove itself.
When you install an Android app it says very clearly "Access your location data". It is not buried in legalese. You really cannot compare a screen that contains a handful of bullet points to a EULA, they aren't even in the same league.
You're trolling, right? Speed Limit is a tool that uses GPS to check your car speed and inform you if you went over the limit. Of course it requires GPS.
Well, the whole reason DRM exists is because the legal system doesn't scale to the number of law violators that exist. If copyright violation could be prosecuted quickly and efficiently enough to target everyone who did it, you wouldn't need DRM. You could just rely on the law as is. However there are too many violators and the law is too slow and heavy to do that, so you get DRM, and then it kind of makes sense to make breaking DRM illegal because not many people do that, so the law scales to it.
Of course, this does lead to contradictions with other parts of the law, eg fair use and expiration of copyrights. Some DRM schemes do attempt to address these. For example the design of BluRay DRM allows for copyright expiry as the title keys can be (are?) placed in eskrow to be released on the due date. Of course this doesn't actually have any impact because most keys leak long before that. AACS also has this concept of "managed copy" which attempts to address some parts of fair use, but fair use is deliberately vaguely defined so some people will never be happy with whatever compromise is worked out.
The real solution would be a lightweight and efficient legal process for punishing copyright violators. The various attempts to introduce 3-strikes laws are an example of that. Unfortunately these have been running around too, as lots of people are happy with the status quo where they can break the law daily without any real risk of punishment so there's no incentive to support such changes, although in the long run they could result in less or even no DRM being applied.
Gah, you're an idiot, as is the person who submitted the article. Why don't you go actually invest your own time and money into creating something and then deal with pirates who turn up and ask for tech support for a product they didn't buy? Do you really think everyone is a dispassionate number crunching machine? Do you really think your ridiculous rationalizations about "bugs" gives you the right to simply not pay for someone. Do you steal shoes on the grounds that until you've worn them for six months you don't know if they'll be comfortable or not?
Last year, my brother put together a high end strings sample library with a partner. He wanted some protection against piracy, but didn't want to invest in high end sample library DRM because he believed it'd get quickly cracked anyway. Instead he wanted some watermarking on the samples so he could find who uploaded it. I cautioned him that this was a bad idea, but he insisted so I went ahead and created an installer for his library which watermarked the samples. It launched, got good reviews and sold some copies.
Needless to say, eventually somebody did upload it to torrent sites. The watermark worked fine, but my brother concluded he did not have the time or legal muscle to actually file a suit against the uploader. In other words, his work had no protection at all, pretty much. This is a product that isn't useful without high end audio gear, so the people pirating it could definitely afford to pay. And for people who wanted to learn, he'd definitely have given some free copies out if they'd asked nicely.
Before a copy appeared on torrent sites, he was thinking about making another one. Afterwards, he's not. The reason is that doing contract work is more reliable and generally pays better than creating products that are susceptible to piracy. Whilst the pirates uploaded it after a few months, so he did make some sales and thus by your logic he should do it again, in practice it could have occurred at any time leaving him significantly out of pocket. The risk is just too high, so no sequel will be forthcoming. Of course I suspect these sorts of stories are not enough for the poster of TFA who will say it cannot be "proven" that the subsequent dropoff in sales was due to piracy, but who cares? My brother isn't making more products, end of story.
And passwords. Better hope nobody on TPB re-uses the same password for every website (hint: lots of people do). And before you tell me they're MD5 hashed, take a walk over to antichat and take a look at the people reversing hashes using high end video cards there. These guys don't give a crap about hashing anymore.
No they don't. Most bad guys aren't skilled enough to find new exploits. They typically prefer to reverse engineer the patches and then exploit people who don't update. Most exploit packs are exploiting flaws that are old and well known. So this "MSRC" or whatever will definitely make things worse, and they're arguing from the worst kind of academic viewpoint if they claim it won't.
This report does seem to agree with you. In particular I note things like this:
- In terms of debugging, ourbenchmarking shows that Android has the fastest debugging process, compared with iPhone, Symbian and Java ME. Debugging in Symbian takes up more than twice the time it takes on Android.
This isn't surprising. I am naturally a C++ developer - though I move between languages frequently, currently, I get paid to write mostly in C++. I've also done some J2ME in the past. So when I heard that Android was Java based, I was very skeptical. How could it compete with an interpreter for a language so bloated that simply representing the constant string "Hello World" took many multiples of the storage space C++ did. Then I sat down and wrote an Android app.
It's really easy to forget how much more productive a managed environment makes you, if you don't use one for a while. No memory corruptions. No leaks. The debugger always works. You can put together a simple crash reporter in 10 lines of code. Sure, the APIs can be a bit over-engineered, and Eclipse is a pig, but it still beats the crap out of C++ and a text editor.
Not to mention that many people don't even know C++ these days.
Yeah, that's a real killer. Samsungs Bada is the same - dev environment is Windows only. As soon as I saw that I knew it was dead in the water. I know a lot of really great, passionate software developers. The sort who obsess over the details of their software and make great things. None of them use Windows as their primary OS.
The general trend towards laptops over desktops also hurts PC gaming quite significantly. I used to play a lot of PC games. These days I use a macbook + xbox. It works well.
Exceptions in a language like Java are a whole other issue than exceptions in C++. I think you'd have to be crazy to try and use C++ exceptions because writing exception safe code in that language is very hard. There are reasons Google C++ is exception free. It's kind of like writing thread safe code in that bugs tend to be invisible and hard to test.
There was a bug in Firefox for a long time (think it's fixed now? not sure) that didn't correctly update the status bar, so it would say it was waiting on Analytics when it actually wasn't. The Google Analytics servers are really fast. This story is about how Google is investing in making the web as fast as possible - if Analytics was really a common cause of slowdown, don't you think it'd get fixed?
Re:Multitasking complaint is kind of bogus
on
iPhone 4 News Roundup
·
· Score: 3, Informative
Well, on Android all apps support multi-tasking out of the box. And it's not just because it's been there since v1. It's because the framework practically forces you into supporting the suspend/resume model of multi-tasking (though you have the option of "the real thing" if you want it). Android apps are built up out of activities, and each activity suspends its state to what is basically a small file when it leaves the screen and reads back from it when it comes back. To move between screens, you pass the OS another little bundle of data. It's quite an interesting system once you get used to it, though like most of Android it's optional.
IPhone apps do not have access to email or text messages or the data in any other app except through a very well defined API
That's not correct. iPhone apps have access to a far larger amount of data than you might expect. For instance they can all read the "keyboard cache" which records all keystrokes save for passwords. This iPhone Privacy study may prove interesting.
Slashdot Mirror
D2 is a very nice language. The standard library situation is a total mess, but then again a completely insane standard library never stopped C++ from taking over the world (I mean "push_back", seriously guys?).
D2 should take over the world. There are absolutely no places in which it is a worse language than C++ and about a million places in which it's better. In practice it probably won't for the same reasons I spend my days writing Java and C++, both languages that are practically Sanskrit in computer terms these days but have very mature toolchain support, big libraries, and lots of developers who know them.
It's been broken in a way that probably does not allow it to be used to decrypt phone traffic - big difference. That said, it's unfortunate that KASUMI has this weakness, even though it appears to be the result of new cryptographic research, given the speed with which new ciphers can be rolled out.
Defending Europe from itself? Like what? Who is going to invade Europe these days??
No, the JavaScript is in an attachment. It's not being rendered by any email product.
The (open source) Chrome updater doesn't "refuse to install". Wait an hour or two after the last Google program using it has been uninstalled, it'll wake up to do an update check, discover it has nothing to do and remove itself.
When you install an Android app it says very clearly "Access your location data". It is not buried in legalese. You really cannot compare a screen that contains a handful of bullet points to a EULA, they aren't even in the same league.
You're trolling, right? Speed Limit is a tool that uses GPS to check your car speed and inform you if you went over the limit. Of course it requires GPS.
Well, the whole reason DRM exists is because the legal system doesn't scale to the number of law violators that exist. If copyright violation could be prosecuted quickly and efficiently enough to target everyone who did it, you wouldn't need DRM. You could just rely on the law as is. However there are too many violators and the law is too slow and heavy to do that, so you get DRM, and then it kind of makes sense to make breaking DRM illegal because not many people do that, so the law scales to it.
Of course, this does lead to contradictions with other parts of the law, eg fair use and expiration of copyrights. Some DRM schemes do attempt to address these. For example the design of BluRay DRM allows for copyright expiry as the title keys can be (are?) placed in eskrow to be released on the due date. Of course this doesn't actually have any impact because most keys leak long before that. AACS also has this concept of "managed copy" which attempts to address some parts of fair use, but fair use is deliberately vaguely defined so some people will never be happy with whatever compromise is worked out.
The real solution would be a lightweight and efficient legal process for punishing copyright violators. The various attempts to introduce 3-strikes laws are an example of that. Unfortunately these have been running around too, as lots of people are happy with the status quo where they can break the law daily without any real risk of punishment so there's no incentive to support such changes, although in the long run they could result in less or even no DRM being applied.
Gah, you're an idiot, as is the person who submitted the article. Why don't you go actually invest your own time and money into creating something and then deal with pirates who turn up and ask for tech support for a product they didn't buy? Do you really think everyone is a dispassionate number crunching machine? Do you really think your ridiculous rationalizations about "bugs" gives you the right to simply not pay for someone. Do you steal shoes on the grounds that until you've worn them for six months you don't know if they'll be comfortable or not?
Last year, my brother put together a high end strings sample library with a partner. He wanted some protection against piracy, but didn't want to invest in high end sample library DRM because he believed it'd get quickly cracked anyway. Instead he wanted some watermarking on the samples so he could find who uploaded it. I cautioned him that this was a bad idea, but he insisted so I went ahead and created an installer for his library which watermarked the samples. It launched, got good reviews and sold some copies.
Needless to say, eventually somebody did upload it to torrent sites. The watermark worked fine, but my brother concluded he did not have the time or legal muscle to actually file a suit against the uploader. In other words, his work had no protection at all, pretty much. This is a product that isn't useful without high end audio gear, so the people pirating it could definitely afford to pay. And for people who wanted to learn, he'd definitely have given some free copies out if they'd asked nicely.
Before a copy appeared on torrent sites, he was thinking about making another one. Afterwards, he's not. The reason is that doing contract work is more reliable and generally pays better than creating products that are susceptible to piracy. Whilst the pirates uploaded it after a few months, so he did make some sales and thus by your logic he should do it again, in practice it could have occurred at any time leaving him significantly out of pocket. The risk is just too high, so no sequel will be forthcoming. Of course I suspect these sorts of stories are not enough for the poster of TFA who will say it cannot be "proven" that the subsequent dropoff in sales was due to piracy, but who cares? My brother isn't making more products, end of story.
And passwords. Better hope nobody on TPB re-uses the same password for every website (hint: lots of people do). And before you tell me they're MD5 hashed, take a walk over to antichat and take a look at the people reversing hashes using high end video cards there. These guys don't give a crap about hashing anymore.
No they don't. Most bad guys aren't skilled enough to find new exploits. They typically prefer to reverse engineer the patches and then exploit people who don't update. Most exploit packs are exploiting flaws that are old and well known. So this "MSRC" or whatever will definitely make things worse, and they're arguing from the worst kind of academic viewpoint if they claim it won't.
This report does seem to agree with you. In particular I note things like this:
This isn't surprising. I am naturally a C++ developer - though I move between languages frequently, currently, I get paid to write mostly in C++. I've also done some J2ME in the past. So when I heard that Android was Java based, I was very skeptical. How could it compete with an interpreter for a language so bloated that simply representing the constant string "Hello World" took many multiples of the storage space C++ did. Then I sat down and wrote an Android app.
It's really easy to forget how much more productive a managed environment makes you, if you don't use one for a while. No memory corruptions. No leaks. The debugger always works. You can put together a simple crash reporter in 10 lines of code. Sure, the APIs can be a bit over-engineered, and Eclipse is a pig, but it still beats the crap out of C++ and a text editor.
Not to mention that many people don't even know C++ these days.
Yeah, that's a real killer. Samsungs Bada is the same - dev environment is Windows only. As soon as I saw that I knew it was dead in the water. I know a lot of really great, passionate software developers. The sort who obsess over the details of their software and make great things. None of them use Windows as their primary OS.
As a Brit living in Switzerland, I disagree. Nobody cares about Symbian in Europe either.
The general trend towards laptops over desktops also hurts PC gaming quite significantly. I used to play a lot of PC games. These days I use a macbook + xbox. It works well.
Exceptions in a language like Java are a whole other issue than exceptions in C++. I think you'd have to be crazy to try and use C++ exceptions because writing exception safe code in that language is very hard. There are reasons Google C++ is exception free. It's kind of like writing thread safe code in that bugs tend to be invisible and hard to test.
How is this different to Windows Update?
Yes. So? You can't expect HTC or whomever to give you tech support if you reflash the OS to something else.
You can install custom ROMs on a Nexus One, it's supported by the bootloader. No "jailbreaking" necessary.
There was a bug in Firefox for a long time (think it's fixed now? not sure) that didn't correctly update the status bar, so it would say it was waiting on Analytics when it actually wasn't. The Google Analytics servers are really fast. This story is about how Google is investing in making the web as fast as possible - if Analytics was really a common cause of slowdown, don't you think it'd get fixed?
Well, on Android all apps support multi-tasking out of the box. And it's not just because it's been there since v1. It's because the framework practically forces you into supporting the suspend/resume model of multi-tasking (though you have the option of "the real thing" if you want it). Android apps are built up out of activities, and each activity suspends its state to what is basically a small file when it leaves the screen and reads back from it when it comes back. To move between screens, you pass the OS another little bundle of data. It's quite an interesting system once you get used to it, though like most of Android it's optional.
That's not correct. iPhone apps have access to a far larger amount of data than you might expect. For instance they can all read the "keyboard cache" which records all keystrokes save for passwords. This iPhone Privacy study may prove interesting.
I imagine he'd want to add you to his Wave-letter. So go get an account and sign up ;)
Here are some interesting case studies
You can get email notifications of changes to your Wave inbox now. Use the little drop down next to the Inbox label.