The Streisand effect applies when you're trying to avert attention from something but inadvertently attract attention to it in doing so. I don't think it applies here. Nobody is trying to avert attention from anything. In fact, I'd expect their government to be pleased as punch with so much free publicity for a simple policy change.
If your point is that telling people about illegal currency only makes them want to use it more, I think you're overestimating the general appeal of bitcoin. Main reason for bitcoin's popularity is that it's both difficult to trace and not illegal. One of those is no longer true in Thailand and I don't think that will improve its popularity with criminals in Thailand, nor with most others valuing the former.
Don't mistake my point for agreement with their policy though. I don't think bitcoin as it stands has lasting potential, but that doesn't mean I agree with a decision like outlawing it.
You could also argue that, if you need a modern GPU to be able to render the graphics for a fun game, you're doing it wrong! What's wrong with Pacman and Space Invaders, right?
More space allowing for more data and faster calculation in a spreadsheet allows for more uses. Just the fact that you'd pick another set of tools, doesn't mean someone able to do it quickly and effectively with a spreadsheet is doing anything "wrong".
Like most people, I'm mostly interested in the capability to stream audio to all kinds of devices. And people have already pointed out some key differences with DLNA that explain why there is reason to be happy with something like MagicPlay.
But Airplay offers streaming of audio, as well as video, photo's and screen mirroring. I haven't looked into the source yet, but going by the description, it looks like MagicPlay doesn't offer any of that and sofar nobody is planning to add it. Has anyone looked at the source and are they able to refute this?
Calling MagicPlay "open source AirPlay" seems a bit of a stretch then. That's like calling AbiWord "open source Office". Of course the marketing department won't like it, but MagicPlay seems more like "open source RAOP" (Remote Audio Output Protocol, see the Unofficial AirPlay Protocol Specification ) with the added stuff required to nicely hook up sinks to sources.
Because you know what is right, unlike the people telling you, right?
The truism you present always sounds nice, but it doesn't mean anything if the whole point of a discussion is about what's right and what's not. Your post skirts the issue of what is right; in fact, you seem to assume that everyone already knows that what Snowden did was right and he just had to act upon it.
We can all agree that Snowden broke the rules and let's just hope that he broke the rules doing something he believed was right (and not just to impress his gf). So, he followed your maxim there. But whether he's a hero or a villain is up to the public and their sense of what is right. Just opposing government doesn't cut it, unless you're a particular brand of anarchist.
Your question is valid, but the research doesn't appear to favor one of the answers - though it's clear which one will sell more ads. (Found myself replacing "papers" with "ads" there, how sad)
Although this is in the article: 'Appelbaum said that with time and experience, the gamer apparently gets better at doing this. "They need less information to arrive at a probabilistic conclusion, and they do it faster."' And of course you could actually determine this by looking at how long and how much people have been playing games up to the point of the study.
Nicely put. I agree, Linux is for survivalist, literate hippies with no interest in digital entertainment and Windows is for pretty much everyone else.
The parent made their point about games, but it is equally true for business software, creative software and pretty much any software that's not back end stuff. Sure, there's great software for other OSes. Steam for Linux, the move to the web and into the cloud and all that jazz. But don't pretend that Windows isn't still the premier platform for nearly all commercial software developers.
Perhaps the better question would be directed at developers: what keeps you developing for Windows? And when might those arguments stop being valid?
When I first learned to program, I didn't own a computer, nor did I have access to one at home. I wrote GFA Basic programs in a lined paper notebook, saving it up for the rare time I did have access to an Atari 1040 STF at a friend's house. Learning GFA Basic was nice, learning to think about code and imagining how it would work without a compiler on hand taught me much more.
The first system I had continual access to was a 8086 XT with DOS 4.01. Learning GW Basic was nice, learning how to juggle around code to get the most out of the limited space afforded by the language taught me much more.
Running out of options on Basic, I started playing around with debug.com. Learning machine code was nice, learning about microcomputer architecture by manipulating it up close taught me much more. In the end, replacing command.com with my own is one of my fondest programming memories.
You get the idea. MASM taught me assembler, but also the value of a good build and deployment process and the pain of multi-threading in the form of TSR's. Then Borland Turbo Pascal 5.0 taught me Pascal, but also object-orientation and modular software design in the first glimpse of an IDE. Then AutoLisp in AutoCAD 2.something taught me LISP, but also the functional programming paradigm and how math and programming had more in common than I ever suspected. A few more languages got me through the first year of college, finally bringing it all together in a coherent story; filling in the blanks and allowing me for the first time to understand the computer in its entirity, from semi-conductors all the way up through machine code, parsers, compilers, higher level languages and beyond.
Then Delphi followed and introduced me to rapid application development and visual interface design and I don't think a year has passed since in which I didn't learn at least one new programming language (the latest being Scala). Because if teaching myself how to program (and getting a little help at university later) taught me one thing, it's that you're never done learning in the field of software development. And the true lessons aren't in learning how to code, they're in understanding why someone designed a language and what it tells you about systems, software and their purpose.
Anyone can make an omelet with eggs. The trick is to make one with none.