prof

Since witches are generally agreed upon to be nasty bitches, I'd argue they don't care.

Well, you can only win against big corpo if you shoot them with their own guns.

Or literal guns.

Thanks for explaining. I was not arguing the point that closures happen, just expanding on why it's not easy for the studios to get back on their feet again as independents.

There will likely be non-disclosure agreements, non-competes or simply IP rights to take into consideration if we want to argue why these studios can't continue their work. In the end it comes down to legal stuff and money. The IP rights even for unreleased products very likely are with the parent corporation. The same goes for the codebase.

So yeah. The studios are left with nothing, except a severance pay if they're lucky.

Why even engage if you're not interested in discussion?

Misrepresenting what I'm saying is not nice of you.

If the studios had the resources they could easily become independent. But the corporate side owns the rights to their works, so the now independent studio doesn't have any incoming revenue.

The average employee won't work for scraps or nothing. So it's effectively over if big corpo cuts them off.

You better hope the sound is baffling when you're at a concert!

Thanks for the response. Seems like I can't assume other CS degrees are comparable.

We definitely have a strong focus on security in my degree, but I still believe that awareness of what you're running on your machine and potential dangers of those programs fall into the category of common sense. Mishandling secrets, having bad authentication or not knowing how to setup SSL is definitely experience stuff though.

Neither young or naive. Just assuming others share my experience.

Makes sense, I feel bad for the guys that were happy for a chance and got screwed over. (By the hackers, not you, haha)

It's sad that this works. You'd think especially software professionals would be the most vigilant about running unknown code.