We had a class in the first semester of uni where we had to create a static html page based on a screenshot.
There was this one textbox at the top of the site, where the only way you could recreate the screenshot was by using a <br/> in the middle of the text.
The prof was very picky about your HTML being semantically thorough and correct, so that was super weird that that was necessary.
I don't think it's okay to be toxic to newbies but there certainly are cases where the solution to problems was a google search and 10 minutes of reading away.
There are a lot of community heroes out there, that spend their days supporting users in forums, without having any monetary benefit from it, that in my opinion may have a reason to be upset if someone does not want to spend any effort on their own in trying to solve their problem.
It's very strange to have North Korean refugees send balloons up north with the state responding to it and also accusing Seoul of propaganda. Seems like they can hardly fathom that individuals have freedom to decide what they may do on their own.
Not really. Exceptions are a controlled way of indicating something went wrong in an application.
The only point where you wouldn't know about the possibility of one is when you don't know enough about the language features you're using or when you use a badly documented library or framework.
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.
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.
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.
Oh boy.
We had a class in the first semester of uni where we had to create a static html page based on a screenshot.
There was this one textbox at the top of the site, where the only way you could recreate the screenshot was by using a
<br/>in the middle of the text.The prof was very picky about your HTML being semantically thorough and correct, so that was super weird that that was necessary.