I used to advocate for piracy in my 20s, when I could barely afford anything, but then changed my mind. For more than a decade I advocated for respecting copyrights, because even if the copyright system is truly skewed towards American financial interests, there are ways to profit from it even for poorer countries. I convinced a lot of people that copyright is a good thing, even with its flaws, even when hiding academic content and knowledge behind paywalls and high markups.

Now, it's impossible for me to argue for copyright anymore. All my arguments fall flat in the face of the way the US abuses now the terms of copyright. Basically, the judge says that theft is fine if you can't reproduce the thing that you stole, so that's perfect. I will not be able to reproduce blockbusters either, nor books, nor other forms of content. if these are the new terms of copyright, then so be it.

Excellent! Now that's an awesome defense next time I'll pirate anything: the knowledge of the things I pirated is so thoroughly distilled in me that it's ridiculous to consider my act illegal.

It's pure data theft. Not only does Microsoft grab the files and uploads them to their servers, but they also *delete* them from your local workstation. It basically holds your data hostage.

Now, quoting from the guy, the developers chose Rust as technology, and the company went to developers and *asked them how productive they feel* in a technology they chose. Now, Google is not the ideal workplace that people thought it was 15 years ago. Google is a company that prepares itself for the next firing round. Their work is probably not AI related, because if it was they would've done something in python. What will the answer be? What would you answer, especially knowing that your productivity isn't measured in the quality of what you release because *there's nobody to measure that*!!!

I really hate the trend of strong-arming Rust as if it was safe. It isn't. You can mess up just like in C++ or C, the unsafe keyword doesn't change the accessibility of ways of messing things up. It is possible that a lot of the code that you have out there written in Rust is better because Rust was adopted by more senior developers because they are the only ones who accept fighting with the compiler so much. Plus, Rust codebases don't have to struggle with 80s, 90s and 00s mindsets in the libraries they use because, well, it didn't exist back then. So I get what's going on there. I wish Rust developers would do more work with their code than with their mouths, because their choir is cacophonously deafening.

They *asked* to switch to Rust. Now, listen, in a company where people are thrown out if they don't do AI, if you go and ask how productive they feel” (which is how they measure) with a tech *they chose*, what sort of answers do you think you'll be getting?

Being a google product, Go is abandoned by the creators, because that's what Google does.

It made sense for Hemingway, since his first draft was on paper and there's so little space to modify that draft that was on paper. You could make sidenotes, cut words, but how much editing can you do on paper? Not much. So after you did the work on the first draft you'd start rewriting - mind you, not rewriting something else entirely, but the thing you worked on.

But now we have infinitely-refreshable paper. No need to throw away your drafts. But perhaps this piece of advice deserves to be thrown away.

/me replies in Eastern European white male privilege

... she brought attention to herself and her company. Which is great. People who are interested in astrology will talk about her fierce attitude, the rest will either applaud her or point out that she's hypocritical. She's the talk of the town, go her. It's always good to see privileged people succeed in life. Sexism sometimes works, and I love how tone-deaf people ignore the fact that they defend a privileged woman taking advantage of her gender, while complaining that segregated conferences, stuff like women-in- conferences that sprung up all over the place, make her feel left out.

To those that ask themselves: but what if she discovers that being a woman is not the reason why people ignored her?” - don't fret. She sounds like a smart woman, she already knows that. She decided to play the gender card, and I bet it wasn't an easy choice - it's not the choice you make when you have too much business to take care of. And for those that insist that what she says is pure BS - remember, she's a *founder*, of course everything she says is BS, regardless of her gender, race, or sexual orientation.

You do realize that founders”, be them male or female, are privileged people, right?

Duuude, that's so wrong. First of all, your C code runs in C++. Period. Second of all, whatever C can do, C++ can do better because templates can actually let compilers optimize based on the data type, as well as a few other things. And that thing about someone using the STL which call new and malloc” is like saying that the standard C library has malloc, so someone might call it.

No, wherever you have C, C++ can do a better job. This is already proven time and time again in the past 20 years, there's no need to debate this.

You can also write C# without pissing on your own hands. Depending on what the system wants to do, C# might be a good option. I still would lead people towards C++, but C# might work in certain situations.

If people paid for products, there would be no need for ads. But would people pay the podcaster? Not really. People are too much used to free stuff to actually pay for the things they consume.

Or they will show you why code comments are a bad idea.

Code comments are usually unmaintainable artifacts; misleading at best.

The best kind of documentation is architectural description of the solution. Everything else is just rubbish. I want to see code comments WHEN they are needed - and the fewer the better. If you write your code in such a manner that it needs documentation, then you might have done a bad job ad writing code.

Example of moments when you NEED to document code: module boundaries, interfaces and implementation hints for when the code needs extension. But by no means should one document EVERY call; but the most important ones. Code samples would help.

Just some programmer's opinion

The title looks like an excerpt from slashdot article, cca 2014

EMail has qualities that no other means will ever have: it can be archived, you can search for information in it, and the conversations are logically organized. Good luck to the manager, I think he will need it, soon

You know that what you said has nothing in common with the idea of God and spirituality, and also nothing to do with the 'debate' that we're discussing? This is pretty much what the science dude said too, but that was not the subject matter of the discussion, and you're very, very, very offtopic.