Mostly "Turks" are of Armenian and Greek ancestry, their ancestors being Armenians and Greeks converted to Turkish culture, either voluntarily using economic incentives or enslaved in young age and grown as Turks. So any Armenians and Greeks that don't want to be Turks are considered existential threat by Turkish nationalists..

Unless they assume they already pay more than needed. The main problem here isn't money. The point is changing requirements make project significantly later no matter how much money is spent on it. This economy cargo cult idea that money automatically make things happen is one of underlying reasons of all messes like that. Religious belief in power of money often makes people forget about doing actual work.

OK. If government can't determine what is religion and what isn't then any corporation can declare itself a religious organization and take tax break. No justification is needed whatsoever because government can't determine this. So just make it a blanket tax exemption for everyone to avoid wasting time on paperwork that will result in them all declaring themselves religion.

It's obvious that the reason for those changing requirements is that they lack understanding of how development process works, so they just need technical background to understand what requirements make sense and what don't. Just being good at "management" is not enough.

No, it's not GPL that is PITA but closed specs and NDA requirements. They're PITA no matter whether you're using BSD or GPL. So who cares if GPL prevents you from doing things in lawyer approved OCD way those companies want? It just won't work. At most you'll end up with some BLOB nobody maintains and which gets obsolete within a year.

Jade Empire still existed alongside proper RPGs. Could be considered a side project.

Bioware mostly remembered for RPG games like Baldur's Gate and Neverwinter Nights. Those were before ME. And ME was the turning point when Bioware finally abandoned RPG core gameplay and switched to FPS/TPS core gameplay. That's the reason many people consider it dead. Because it's no longer doing what gave it worldwide fame, namely RPGs.

You don't make things clearer if you add more verbosity. It's the other way around. People will get lost in details without any job getting done. Copy/pasting boilerplate is boring and error prone(because you need to plug it into your code after all and may modify some bits). Better make api more powerful so there will be no need to have boilerplate in the first place.

Well, you're getting too excited about something that is evolutionary step backward and such hasty statements are a proof of this. I myself have some opengl experience and I can tell you getting to lower level is NOT what I would want. Yet I don't want to be locked into using an engine either with their often suspect design decisions. I consider opengl to be in sweet spot in this regard, though shaders are kinda pushing it.

Then it's not replacement for opengl and shouldn't be considered one, but an api one level below. And I don't really think it's such a good idea. Like switching from C back to assembly.

It's really hard to prove that this 10-20% comes from api alone, if it exists at all. Sounds like random ass pull to me. (But a person who is paid per line of code will have no trouble proving this with a powerpoint presentation that'll absolutely convince anyone ignorant about graphics) Anyway right now we don't need more fps, but rather more stability. And having less code helps with that. Statistically bug count is proportional to line count and obviously shifting some code from drivers to be repeated by every application raises line count drastically.

600 lines to write a program that renders a triangle? Such apis are obsolete in 21th century period. Don't care what cowboy coders do on their game consoles. There's no need for line of code count maximization techniques in opensource.

Well, not having them designed for easier repair is objectively economically harmful. So it's an example of market failure. And forget about "looking good". It's all bogus, there's no contradiction between ergonomics and repairability. They're just making up excuses but real motives are "strategic", that is getting rid of competitors and making entry into market harder.

I'm not yet familiar with gnome's implementation, but wouldn't you still see scrollbar along with progress indication if you mouse over scrollable area?

I don't even remember when I directly interacted with a scrollbar last time. Only when interacting with crappy custom GUIs that don't support mouse scrollwheel maybe.