The most honest answer is that studios can't extend the software without violating the GPL.
Maya is outrageously extensible in a variety of ways and really set the standard for being "open" in this way. A lot of the big studios have toolsets that radically transform parts of Maya, shaping it into the tool needed for the work.
Maya is also pretty crusty, plenty of other applications do a better job at it's core competency, but they simply aren't dug into studio pipelines like a tick in the way that Maya is.
Blender has to limit itself to Python, or at least, I'm not aware of the ability to create native plugins. I'm all for Python, but a lot of interesting work is done in C++ building native operators for the application or embedding custom viewports for gamedev which I don't think is remotely possible in Blender yet.
Additionally, licensing prevents many integrations from getting off the ground.
So what you are saying is that there is no benefit of using Maya if you are not specifically a commercial software company who want to sell derivative tool-kits made from open source projects.
Or... should I sum it up as Maya is used by studios who already has c++ experience, and Blender is used by studios that has python experience?
The trouble though comes about once you have to start working with a UI library. It's a mess and a half unless you use C++. I'd like to try using Elm, or Purescript for UI work using atom-shell or nw.js. That opens almost the same can of worms (how easy it might be to 'bind' your engine to your UI/view).
I've written a non-trivial application using QtWebkit entirely for the UI and it was a very agreeable experience. The engine of this app was C++ but it got my gears turning.
My comment was in reference to using native toolkits from a language other than C++ and not the status of using native toolkits in general. <friendly-joke>I have a hard time believing that you've been using native UI toolkits using Haskell since the mid-90s.</friendly-joke> :)
No, but I was using Turbo Pascal followed by Delphi. Also played with C++ Builder, but by then Visual C++ had taken over as Borland was going through their Inprise phase.
This has been what I've been worried about during all of this. I'm not entirely sure why Germany has to be "damned if they do and damned if they don't". It's as if people forget that the country has had to learn how to recover from total catastrophe and might be offering realistic and practical solutions to the problem.
My limited understanding is that this help came with a lot of stipulations as to how the money was to be used and these stipulations were enormously unpopular.
Personally, I can find some understanding of both sides to this. On one hand, if I were greek I'd be utterly and totally committed to replacing every member of the government that so royally screwed me and I'd be insulted by the entities who are offering bail outs at the expense of my quality of life (I don't fully understand the details of how this impacted people on individual levels, this is only my attempt to epathize). On the other hand, if I had a lot of money to help people in need, and someone came to me asking to pay their loan sharks after an epic binge I would certainly have a number of stipulations placed on this and would in no way consider handing them a check without some extensive scaffolding around that exchange.
As I learn more about this situation I might feel differently about either side, so please understand I'm just sharing my opinion given what little I know about it so far.
I imagine he just hasn't implemented them yet--they're not incredibly difficult and can usually be added later, as I did for Plan 9's rio WM at some point.
Using two monitors on Linux and running XMonad changed the game for me. Very organized, productive and efficient interactions with the system grew organically out of it. Even though I tend to use KDE (and KWin) these days on a laptop, that experience helped me drill down into a workflow that I apply anywhere I can. The best thing is that, everybody comes to their own "most efficient" workflow using these tools.
Interacting with OSX/Quartz after that felt something akin to giving up <insert code editor or IDE of choice here> and writing all your code in [TextEdit.app | Notepad.exe | nano].
Also, scratch terminal windows are solved by TMUX and a single terminal.
wtftw is very interesting. I can't wait to give it a shot.
Terminal.app supports tabs, I'm not sure why tmux would be any better (well, tmux can do splits, but transient windows don't need splits).
The problem is if I create a tab, I want it to be at least somewhat related to the other tabs in the window. And even then, I usually use new windows for scratch terminals because I want to see multiple different terminals side-by-side. I could use a vertical tmux split except that shrinks the original terminal, and I want both the original and new terminal to be at their natural size.
TMUX is a transferable implementation of terminal session and "tab" organization. It's also scriptable if you aren't happy with some aspect of it's default presentation or interaction.
For me, that is enormously valuable.
Sounds like your use case could be mapped by TMUX windows acting like Terminal tabs, and TMUX sessions acting like multiple Terminal windows. Except the benefit is that now you can use this workflow on any system with a posix compliant shell and a tmux binary (which I'm pretty certain is practically all the things at this point). Sessions and windows can be given labels which is a nice touch too.
If you are an Emacs user, it's also worth noting that TMUX totally works well with ansi-term. :) I normally have a TMUX session dedicated to an ansi-term buffer in Emacs. Even if I have iTerm or Konsole using another session.
"..but transient windows don't need splits"; well, in my universe transient windows are splits. :)
Anyway, I don't want you to think I'm trying to persuade you into adopting what I consider awesome and useful. Just clarifying my statement. It sounds like you already have a workflow, are happy with it, and don't see any need for alteration.
I use tmux over mosh on my Linode. I've just never found it to be particularly useful on my local machine. Especially because it removes the ability for my terminal to manage history and requires using a keyboard shortcut in order to scroll backwards in history.
I believe Terminal.app handles mouse events differently, so the standard tmux config doesn't work right. Maybe see if https://bitheap.org/mouseterm/ improves matters for you.
Terminal.app doesn't handle mouse events at all. I filed a radar for that a while ago. But I don't consider that good enough reason to use iTerm2 as the programs that actually support CLI mouse events are very rare.
I close the browser tab immediately when an ad starts or hit the back button on my phone. I'd love to be able to support content creators without subjecting my mind to advertisements. Hopefully they find a solution to the issues you've mentioned here.
Some content creators enable a donation button on youtube (which was officialized a few weeks back). Hit that for the creators you like, and install adblock. At this point, I don't see any other choice.
Bob Ross was a national treasure who dedicated his life to helping others see that it is wonderful to make or create for the sake of it.
Anyone I've met who thinks he's a joke have been illustrators who hadn't yet come to terms with the reality that they were craftspeople and not fine-artists. As if there is some dishonor for being a dedicated and skilled craftsperson. Having a passion for and love for a craft at any skill level is a beautiful thing.
I live in a country where Bob Ross isn't really known at all, and I spend a lot of my free time doing illustration or painting (http://ultimatehurl.tumblr.com is where I post stuff, to give an idea). Having relatively recently learned of him and his show I think it's amazing and encouraging. I have no formal training yet frequently have people say to me 'I could never do something like that!', Bob Ross worked to prove that's not true, because it's really not.
