genuinely interested in knowing why it is so. I quite like Go, but I also like Django, so I would like to know why a Django-like ORM would not be feasible.
The main reason, in my opinion, comes down to how Go as a language was designed. I have written some follow up posts to that, specifically this one: https://andrewpillar.com/programming/2022/10/24/a-simple-cru... wherein I explore creating an ORM-like library via generics in Go, this may be of interest to you if you want a better understanding of how some of these things would work in Go.
What is it about Go that prevents you from writing this complex logic?
Both actors and producers can benefit when access to talent is not held behind the gates of a few powerful entities. We've seen the damage such gatekeepers can wield with the Weinstein case and numerous subsequent claims, where vulnerable actors have their careers held hostage to avoid upsetting predators who wield all the power. If an actor can pay the bills by doing many short-term mocap jobs for independent producers armed with sophisticated software, everyone can benefit.
In addition, motion capture opens up opportunities for very talented but otherwise less conventionally attractive actors who traditionally are relegated to type-cast bit roles.
With the advent of motion-capture like this, actors will be reduced to a marionette of flesh to be puppeted around as the producers see fit. Perhaps Hollywood will be going towards a future where actors no longer act in movies, instead their likeness is simply licensed to a studio for a certain number of movies. Anyway, I'm a cynic when it comes to this, the industry itself is already plenty abusive and exploitive, and this could further that.
Hm, I have no knowledge or connection to the events, but "stomping out protests" made me expect a bit more dramatic events, than stopping someones speech, after his time was up.
"But Westenhofer’s speech was cut off mid-sentence after he used up his allotted time"
[1] - https://www.cnet.com/culture/entertainment/marvels-vfx-artis...
I know a guy that worked on StarTrek for years as a VR architect and general 3D modelling type of work. He worked longer hours than your average Torontonian, but nothing absolutely crazy. I've worked longer weeks.
He loved his job.
I'm not saying it is this way for everyone, but part of life is deciding if you want to work hard, have impact on things that matter, work on cool stuff, earn a lot of money, etc.
There are places where it truly gets exploitative, but in my humble opinion that's usually places where the people involved have almost no options other than to move to another town or country. I'm not against industries or companies where the up front expectation is hard work. Some people want that, at least some of the time.
VFX people in Hollywoord are some of the most underpaid workers in the industry. Sure, it's cool that you can be a part of a team that helps make a movie. No doubt it must be pretty cool to see your work on the big screen, or even the small screen, and know that you played a part in bringing it there. But I think something the workers would also value is having some autonomy over their work, and being paid for it.
I'm not easily convinced by the argument of, "you get to work on cool stuff", working on cool stuff doesn't make up for risking povery, debt, or unemployment when you're underpaid. Furthermore, there's a difference between hard work, and exhausting working. And being put under crunch is exhausting work, not hard work.