Of course, but that doesn't equal the sound "moving around", the violin section will always remain in the same place for example, which is the feeling I get when listening to one of those 8D Audio videos on youtube. The sound moving around that is.
And I think your example of the plane is where this technique is applicable. In a cinema for example, imagine yourself watching a horror movie and you can hear the evil demon sneak up behind your back. shivers. In a concert setting however, the source of the sound is (usually) static, while I might move my head slightly from time to time and pick up the sound from different angles. If that could be simulated using headphones, that would be pretty cool! But again, I fail to see what purpose it would serve in a normal stereo setting where the sound is produced the same way, from stationary speakers. Then of course there are other factors like the venue layout, design and material. As well as speaker placement, mixing of the sound and even the crowd itself. Which all contributes to the sound and the "feeling" of listening to the music.
I have never understood what problem self-driving cars is trying to solve. I can, on the other hand, see that it could be more desirable to have self flying planes. But to even think that self flying = issue free and non crashable planes is beyond naive. Personally I believe that the best is to let humans do what they do best, and let computers do what they are good at. Without trying to force one into the other's shoes. (Computers has shoes, don't they?)
So you think that someone who's capable of building a system like this, has somehow missed the fact that you should store passwords safely? Nah, I don't buy that.
They should have been fined more than a measly €20k in my opnion. As a developer I'm deeply ashamed that people are still storing user passwords in plain text. There is no reason behind this behaviour what so ever, other than pure laziness ...
"... much of what is done is faux-agile, disregarding agile's values and principles." This. It feels so easy to get caught up in methods and tools, to not make a proper commitment (because it is tough to change the way you work) and to land in a sort of semi-agile state that no one likes.
I love the idea of having your actual users testing the software, rather a dedicated tester. A dedicated, employed, tester can never use the product like a normal user would. They have too much knowledge of how the system works and what it can and can't handle. In order to truly observe something, we must completely, or as much as is possible, remove ourself from that situation. A normal user however doesn't know that it's not possible to achieve task X within the system, and will try, and if enough users try to perform that task, it might be an indication that it is a task that should be implemented or looked over to see why they are trying to perform this. This is just an example, but I find the role of a tester pretty confusing and awkward. As a developer I build and test the code I'm writing. If something doesn't work within that code I want to know as quick as possible if something isn't right. So why should I hand over my code to someone else? And also, if a user doesn't find the bug, is it really a bug?
I don't think it's baffling at all. Facebook is the largest social media company, and what do they do to try to stop all of the propaganda, troll factories and hateful things going on there? Naught. They know that they are the largest company and therefore doesn't have to do anything as long as their position stays the same. Which it seems to be doing. Yes, there are people leaving the platform but where do they go? There is no real contender, therefore Facebook will remain number 1.
The surname is wrong in the title, it should be Klint, not Klimt. It's an interesting read however, although I'm no art expert by any means, I've always liked abstract paintings as they have a sort of liberating effect on my mind where the imagination in some cases can run completely it's own course.
Define "technical". But when it comes to programming I always enjoy Sandi Metz's talks. I can highly recomend this talk she made at the RailsConf in 2014, about taking an ugly beast of code and turning it to something more digestable and beautiful https://www.youtube.com/watch?v=8bZh5LMaSmE
Apparently it "ensures artists receive the compensation they are owed, encourages fair industry competition, and protects the intellectual property rights of studios nationwide—among other benefits."[0] However, I find it difficult to find anything about how this is actually implemented. Apart from this: "t changes the procedure by which millions of songs are made available for streaming on these services and limits the liability a service can incur if it adheres to the new process. It funds the creation of a comprehensive database with buy in from all the major publishers and digital service providers." [1] Which to me sounds very vague.
Found this also. "The MMA is a bill to be added to legislation with the goal of establishing a new collecting society, called the Mechanical Licensing Collective (MLC), that would be empowered to provide a blanket license for streaming services to companies, covering mechanical rights in any songs not otherwise covered by a digital company’s direct deals with music publishers."[2] So if I interpret this quote correctly, it basically means that there's going to be some sort of organisation chaperoning artist and music makers without a license to their music, collecting a license fee from streaming services and paying it to said musicians and music makers?
... "why even call it the "disgusting food"? Obviously anyone who connotates the exhibit with the items inside will be going in with a specific bias." Well, isn't that what they are trying to challenge? The 'whys' of disgusting food. I think it's an appropriate name considering that these items are usually presented as disgusting in the general public. So by giving it the name Disgusting Food Museum they create a mindset for the visitor that is saying 'you're now entering a museum of food you'll find disgusting', and then making the visitor quesiton that mindset; Why do they find Surstromming or Balut disgusting? You can't ask yourself such questions unless you think those dishes are disgusting in the first place. Why do you think chocolate is disgusting? Well, uh, I don't.
I own a KeyOne, released last year with Android instead of BB's own OS. I love it, only downside is that I had to import it as it isn't available in my country ... I'd mainly used Samsung flagship phones before and got really tired of all the bloatware as well as typing on a touchscreen. (Can't believe more people are questioning touchscreen typing on phones, I think it's horrible and I don't have the largest set of fingers in the world.)
I bought it for roughly $500 and this is what I make of it after one year of using it:
The camera on my KeyOne is superior to anything I've tried before, I'd even go as far as saying that it's up there and competing with the giants. The Sony Z2 Compact camera is a potato in comparison. The keyboard feels a bit cheap and some keys make a squeeking noise, but it's still better than touchscreen typing by far. I've dropped the phone on a number of occassions, it hasn't broken once. The backside tend to pop out, but it's easy to put it back in place again. My biggest complain about the hardware would be the screen, as I haven't access to any protective accessories my screen is pretty scratched by now. It doesn't affect what's displayed on the screen (yet) however, but yeah, I think it scratch too easily. Like I said, the OS is Android, and it's been fairly problem free for being Android. However, lately it has been a bit too agressive in shutting down apps in the background. But I don't know if that is BB's own build's fault or Android in general. There are some pre-installed "security" apps which gives the feeling of the phone being more secure than your other average Android phone. I don't use them though.
My over all impression of the KeyOne is 8 out of 10 I'd say, and I think I'll keep it until it literally fall apart.
Facebook give out a minimum of $500 for bugs and issues they deem worthy of rewarding. Last year they paid more than $880,000, and as of January this year they had paid a total amount of $6,300,000 to the people participating in their white hat program.
"That was risky, because Babel is open source—meaning it is freely available online, and users don’t have to pay for it."
I don't get why many seem to think that Open Source = No cost for the user. Now I haven't read up that much on the OS philosophy so that might be why, but I have read a bit about free software, like Free Software, Free Society:
Selected Essays of Richard M. Stallman[0] for example, how anyone could mistake free software as software at no cost is beyond me. You can of course make it available at no cost, but then, it's your problem if you're not getting paid. Free software basically means that you're free to review and edit the software as you wish, (with some other implications as well if you read up on the GPL-3.0 license) and as far as I know, that's basically the purpose of open source as well. I thought companies, or developers, made their code available to get feedback, find bugs and issues more quickly, show the rest of the world that they have nothing fishy to hide etc. But I had no idea that it also meant that code automatically became gratis for everyone.
I'm currently traversing through Linux From Scratch, http://www.linuxfromscratch.org/lfs/. Not necessarily because I wanted to build a Linux OS but because it was the best guide I could find. But at a first glance this looks promising to me, so I'd definitely check it out and try out a few "chapters" when time comes.