|
Movie Studios Ask Google To Censor Their Own Films, Facebook and Wikipedia
Based on an update to the article, it seems some unknown third party requested the films be taken down. Example take down notices:
- Cabin in the Woods was asked to be taken down from Blockbuster, iTunes, Amazon, and others.
- How I Met Your Mother was asked to be taken down from CBS.
- Take down notices were also issued for film reviews and Wikipedia articles.
|
|
|
|
|
|
|
|
Quote: Still waiting for an ad-free Code Project
Somebody has to pay the bills. I'd suffer the advertising clutter, rather than paying for CP membership, (or membership for any other social network, in that matter)
|
|
|
|
|
I'd happily pay to avoid ads. Though, I'm probably in the extreme minority.
|
|
|
|
|
|
Did they try it in a vacuum? Did they have a really good source of Brownian Motion?
|
|
|
|
|
Every new version of JavaScript adds some extra goodies that make programming easier. EcmaScript 5 added some much needed methods to the Array data type, and, while you can find resources which teach you how to use these methods, they typically omit a discussion on using them with anything other than a boring, custom function. The new array methods added in ES5 are usually referred to as Array Extras. They ease the process of working with arrays by providing methods to perform common operations. Tips, tricks and the unknown second argument.
|
|
|
|
|
Now don’t get me wrong. C++11 is fantastic! I am in just about 100% agreement with all of the changes that have been made. C++ has definitely become much easier to use and it has even become more powerful. There is one thing it didn’t become though—and this is the most important—more simple. It seems that many of the seasoned developers have forgotten why we stopped using C++ and moved on to Java, C# and other modern languages. But there is still some value in learning C++.
|
|
|
|
|
I love C++. Yeah, C++11 made it a lot better than what it was for sure. C# has some simplicity. I keep going back to C++ for gui work simply because WPF is just too insane. It requires a lot of "do it your damnself" rather than offering some simplistic stuff like (enable tab closing, no multiline tabbing, drag and drop previewing), etc. No C# book I have shows how to do sockets properly. I have yet to find decent documentation on C# sockets, especially with non-blocking event sockets.
I love programming, even if I have to deal with pointers. C++ offers a lot of gui frameworks like Qt, wxWidgets, etc. I prefer Qt, because win32, MFC, etc. just doesn't offer simplicity when designing gui applications in C++. I can easily have a nice gui program in way less time than I would in win32 and MFC. Microsoft's documentation is just piss poor on win32. COM is just horrible in C++ unlike in C#. That's another good thing about C# is COM development.
My only gripe about C++ is Microsoft's slow arse at adding features of C++11. It is so far behind it ain't funny. GCC, Clang, etc. are almost done with the implementation of C++. Microsoft doesn't offer continuous updates of their C++ compiler for C++11. You have to wait for the next major release of Visual Studio to find more features. I can almost use all of C++11 when I'm developing a C++ application in Linux. I wouldn't be able to port it to Windows for use.
This is how I see the Windows platform. If you are going to develop for it use C#. Don't even bother with C++. If you want C++ development switch to Linux.
|
|
|
|
|
xComaWhitex wrote: No C# book I have shows how to do sockets properly. I have yet to find decent documentation on C# sockets, especially with non-blocking event sockets.
I found the help and MSDN to be more than adequate, if you understand the basics of socket communications.
We have a TCP/IP socket-based tracing tool we developed for debugging our distributed application. It requires several complex classes, including threading and pool support, in our C++ applications. I replicated all of the functionality in C# in less than a day.
Software Zen: delete this;
|
|
|
|
|
xComaWhitex wrote: C# has some simplicity. I
my app complicated enough, i don't need any further complexity to delete(thisshit)
xComaWhitex wrote: <layer> I keep going back to C++ for gui work simply because WPF is just too insane
yea think WPF sucks sh*t but why not just use Winform?
xComaWhitex wrote: My only gripe about C++ is Microsoft's slow arse at adding features of C++11
I started my career doing MFC/WIN32/C++ - but I wish C++ just die and everything just .NET/C# so I can only focus on real application logic/capability
xComaWhitex wrote: If you want C++ development switch to Linux.
I don't switch to another platform because it's cool or that I want to do C++
(I would if it *PAYS*)
xComaWhitex wrote: That's another good thing about C# is COM development.
Gosh, they used to say "COM is Love". WTF just hype ... all this complexity to for just a god damn procedure call? I remember one whole book just on DCOM while I can wire down any sh*t with C# in binary format with existing library or build new one for RPC in two days.
All in all, I wish C++ is dead and whole world just do one single language C# and one single API - .NET
dev
|
|
|
|
|
Thanks. Good stuff. Unfortunatley cannot vote. 
|
|
|
|
|
As a programmer, have you ever had to work with multithreaded code? It's horrible. You might as well give up on unit testing and quality; concurrency bugs usually aren't very reproducible. Hence the old adage: "Some people see a problem and say 'I know, I'll use threads.' Now they have two problems...." We need a language where we can write code as we normally do (single threaded) and have the compiler transform it into multithreaded code automatically. Such a compiler could weigh the benefits of multithreading against the overhead of creating threads and optimize accordingly. This is the only solution to our long-term dilemma. Hardware will only get you so far. Better software is the answer.
|
|
|
|
|
I imagine this to also be the only practical way of writing code for multicore chips too.
=====
\ | /
\|/
|
|-----|
| |
|_ |
_) | /
_) __/_
_) ____
| /|
| / |
| |
|-----|
|
=====
===
=
|
|
|
|
|
|
OOP is great - I try use it as much as I could. But for some demanding scenario I revert to functional programming
For example, if you have a large number of "trades" to import/export, instead of doing it trade by trade, import them by bcp then in SQL update/add relevant fields to already imported records the relational/functional way
dev
|
|
|
|
|
Definately the next major step. We got memory management with Java and C#, now need to let the framework handle the threading. I know that a lot of my time is spent with threading, even if I do not exactly work with the threading class. I am sure there are issues with my threading, but things work. The future is not have to worry about threading, like we no longer worry about memory management.
|
|
|
|
|
That sounds like what the CPU is already doing automatically. (I mean The CPU pipeline tries to execute several instructions in parellel)
|
|
|
|
|
The coffers of Unix hold many simple tools, which by themselves are powerful, but when chained together facilitate complex data manipulations. Unix's use of functional composition eliminates much of the tedious boilerplate of I/0 and text parsing found in scripting languages. This design creates a simple and succinct interface for manipulating data and a foundation upon which custom tools can be built. Although languages like R and Python are invaluable for data analysis, I find Unix to be superior in many scenarios for quick and simple data cleaning, idea prototyping, and understanding data. This post is about how I use Unix for EDA. read | learn | pipe | rule!
|
|
|
|
|
Compared to any of the popular tablets—the various iPads, the Nexus 7, Amazon's range—the Surface Pro is absurdly overpriced and its battery life is pathetic. Compared to an Ultrabook, it's not that bad: a little ahead in some ways, a little behind in others. The thing is, in spite of its pricing, the Surface Pro isn't an Ultrabook.... This makes Surface Pro an awkward sale. Surface RT was difficult to categorize, and Surface Pro, if anything, exacerbates that difficulty.
|
|
|
|
|
Here are some technologies that have such strong "street cred", they are effectively untouchable. Anyone who dares imply that they are deficient in any way is instantly labelled an uneducated moron. It is impossible to have a realistic conversation about these technologies, and it's not very common for enthusiasts of these technologies to admit their failings. Why your pet technology sucks.
|
|
|
|
|
Clearly Linux isn't the best operating system, because OpenVMS is. And any lack of drivers for OpenVMS is a benefit, not a shortcoming.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
