Do you develop on GitHub? You can keep using GitHub but automatically sync your GitHub releases to SourceForge quickly and easily with this tool so your projects have a backup location, and get your project in front of SourceForge's nearly 20 million monthly users. It takes less than a minute. Get new users downloading your project releases today!
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.
I definitely disagree here. All features of C++ have their uses and it's possible and necessary to master them all. This language is focused on getting the job done. Thus some of its design decisions don't look very nice. But it's the most usable language in its niche.
If they're funded only by donations(with unrestricted "freeware" distribution) they don't have sales in strict sense. So I really want to know would donations be considered sales?
