micmil

"Switching between 3d modellers" undersells the issue.

COMPLETELY ALTERING YOUR PRODUCTION PIPELINE TO ACCOMMODATE ONE PACKAGE gets the point across a little bit better.

There are studios out there that have decades of in-house scripts and programs built around a given set of software. If you do a lot of architectural rendering you may have your own outdoor lighting systems. If you focus primarily on title sequences you may have certain effects that you developed. Having to completely rewrite all of that in-house code would be a MASSIVE undertaking.

It has nothing to do with "employee vanity" and that's one of the stupidest things I've ever heard.

There's a simple reason Blender doesn't see much use in film production: Support. There is no way the Blender Foundation could provide the level of support that a company like Autodesk does. When you run into problems you call your enterprise support team and get it fixed. This is why you pay them the big bucks. Their support staff does nothing but fix problems, where anyone that you could hire to do the same would necessarily spend most of their time sitting on their ass doing nothing since stuff just doesn't go wrong all that often. That alone will keep Blender out of a LOT of shops, especially those that are just large enough to be working on major projects.

The idea that a company should just hire a programmer they don't otherwise need just so they can make some software work is asinine. That's like saying a home builder should hire a full time auto mechanic instead of taking their work vehicles to the shop when they break down. No, hiring a guy will not offset the cost of purchasing licenses and support. This is especially true when you hit one of those moments where things get so shredded that the cost of enterprise support seems like a bargain.

There are other, more technical, issues that keep Blender from being used much. Chief among them is that it isn't really exceptional at anything. It's not uncommon for things to be modeled in one program, textured in another, then imported into another for animation, and then brought into a final one for lighting and rendering. There are better programs for modeling than Blender. There are better programs for rendering, texturing, animation. Blender is oatmeal. It's there, it works, but it's not really great at anything and as a result has never found a niche.

Because, ultimately, that's what it's all about.

Any GOOD smart lock that you'd want to put on your house will have key backup. You basically have to be a complete douche to install a keyless system in a residential application.

It depends entirely on the type of locks involved.

The majority of residential homes in the US have semi-standardized lock bore and setback sizes so most anything you pick up for dirt cheap at your local home improvement retailer will bolt right on. I'm not sure if there's the same level of standardization in the UK, but in most of Europe locks are of a design that allows you to replace the cylinder with a couple of screws from the inside. The locks themselves typically cost more but the labor is pretty much nonexistent.

The only way you'd need to pay that much to have locks changed is if you're needing to do actual physical work on the door or jamb itself.

Or if your locksmith is overcharging you because you don't know any better.

Notice how almost all of those cite "suspected fraud"? The bank will always be paranoid about fraud and if you do anything to freak them out, you're done. They're worse than cats when it comes to flipping out and skittering away. In the cases where resolutions are cited the customer receives their money back. This is due to federal laws regarding banking.

Contrast this with PayPal who needs no reason to freeze your funds and will hold them as long as they damn well please please federal banking law (for the most part) does not apply to them.

This even though they're regulated as a bank nearly everywhere else in the world. But then again this is the US and when do we ever do anything that makes sense?

"If you told a C64 user back in the day his machine would break in two years..."

That was pretty much expected. Hardware upgrades were just as fast and furious as they are now, if not moreso. Backwards compatibility with years-old systems at the consumer level was a byproduct, not a plan.

Because your post was utterly irrelevant in every possible way. A lot of things a lot more expensive than Macs get EOL on a much more regular basis.

Have fun running brand new Android on a seven year old tablet.

Why would it be? There are specific things you have to do for your code to be considered "integrated" with GPL code and as long as you avoid that there's no issue.

That seems likely. What's funny is how Edge (and eventually IE) became even more entrenched in the system than before, yet nobody cares anymore. Almost like the whole thing was a bunch of arm-waving by nerds and regulators that wanted to pretend they knew what was going on.

No, you cannot. Federal law sets out how all banking must be done. There is always reciprocity. Since PayPal isn't regulated as a bank there is no directly applicable federal law. Instead, it's regulated on a state-by-state basis and the majority of the time you'd be hard pressed to figure out exactly who within your state you would have to file a complaint with. PayPal wants it both ways. It wants to act like a bank when it's good for them, but avoid all of the regulations. It's the worst of both worlds for the customer.

Anecdotally speaking, I know multiple people that have had funds frozen by PayPal after months or years of use. I know exactly nobody that has had a bank account frozen.

The federal definition is essentially irrelevant unless you're traveling across state lines or live in DC. Such things are handled by the states in all other cases.

I'm not a database guy so have no clue, but why are there so many versions receiving support? Is there just that much legacy crap they can't get away from, like Python?