Copyright isn't bad. What's bad is how it's implemented.
Programmers aren't academics. So, there's still really no reason to join the ACM for most programmers.
Because the vast majority of all H1Bs go to IT jobs.
Page breaks in word processors existed long before Word.
lol...the Mac Pro doesn't use gamer cards, moron. Come back when you know wtf you're talking about.
I challenge you to build a PC with the same hardware for a cheaper price.
They CAN provide the information requested but they have to shutdown the system to do it. Otherwise, they don't have space and the system will auto delete everything over a certain age. There's just no room to keep the system running without delete functionality active. You could argue that they should shut it down until it's audited but that would require you actually read instead of rant.
Yep. It's not really about the NSA or its activities. It's about hating on America. Nobody gives a shit if a dozen other countries do the exact same thing.
What difference does it make? The NSA doesn't need warrants to tap phones in other countries.
Actually my number is low but it depends on where you live. In large cities, about 97% of all cases are plea bargained. That said, I don't understand how this makes people unaccountable for their actions. Accepting a plea IS accepting guilt. They go hand in hand.
Actually for all crimes, regardless of severity, plea bargains are the order of the day. The legal system couldn't come close to handling even 10% of the cases if they were to go to court.
One doesn't always get to choose their language. I spend most of my time in Java but it doesn't mean I don't apply functional paradigms where I can.
Sorry, I should have been more clear. I meant mutability in the sense that while the values in an array can change, the structure cannot.
As for how bad it is, I'm not that concerned. If you're using functional paradigms regarding values, this just isn't an issue at all. Functions shouldn't be modifying passed in structures in the first place. That's just a horrible, albeit common, coding practice.
So they're only allowed to do things that other languages have done? Also, given that there's literally thousands of languages, you can be certain that at least one other language has done this.
As for CoW semantics, there's no such thing as a mutable array. Even languages that offer such a construct (like Ruby) are just hiding the mechanics they use to reallocate memory. Swift is essentially exposing this to the developer. I agree it's a bit odd but not the end of the world. There are a millions worse things in languages that are very popular.
I don't see what the big deal is. If you modify the size of an array, regardless context, you get a different array. Not exactly a brain buster.