Comment Re:stop going to reddit (Score 1) 125
Get off your high horse. I've been on
Instead of complaining about the community what are _you_ doing to improve it?
Get off your high horse. I've been on
Instead of complaining about the community what are _you_ doing to improve it?
The problem is AT&T would rather bill the person then actually look into an anomaly. The average person spends what, max $100 / month on long distance? And $15K _didn't_ set off any alarms that _maybe_ something was wrong?!?! Nope, they just billed the person with the attitude "Not our problem"
It's called "Having respect for your customers",
not
"Let's fuck them over any chance we get -- not our problem until it is our problem"
I concur. Visually it is mildly interesting but it ignores the elephant in the room:
* Modern game design spends more time focusing on form then function
Grind-Grind-Grind!
When your refer to your customers as whales attempting to suck as much money out of them as possible, the industry of shovelware is fucked
While there is some truth to that, you haven't been keeping up to date with Orgre's design and architecture changes:
Orgre 2.0 Pitfalls and Design Proposal
* http://www.mediafire.com/downl...
They ditched OOP and incorporated DOD (Data-Orientated-Design) for a 5x performance increase!
* http://www.yosoygames.com.ar/w...
Mike Acton is a respected programmer in the video game industry, and he's right. In fact, if you were paying attention I listed his famous Typicall C++ Bullshit as reference in my Ogre 2.0 proposal.
OgreNode.cpp was written 13 years ago when OO programming was all the rave (still is?) everyone had a single core, caches didn't matter and most efficient way to cull the world was to use an Octree or a BSP. The world believed that "if( dirty )" was a magical, no-cost expression that is immediately a performance improvement wherever used to avoid the execution of more than 3 instructions.
13 years later, Moore's law kicked us in the butt and everyone is multicore. You probably know that story already.
Mike Acton reviewed the 1.9 version. Perhaps it would've been more interesting to see a review of the 2.0 file which has been refactored to better fit Data Oriented Design principles (and I'm sure there are things I wrote to criticize). Many of the things he criticizes of 1.9 have been fixed. Nevertheless there are things we can learn. Note that if he weren't right, then it would be hard to explain why there was a 5x performance increase between 1.9 and 2.0.
Mike Acton's DOD comments
* http://bounceapp.com/116414
... over on Reddit. It keeps getting rehashed:
* Game Engine Design
* UE4 is now completely free
* wishlist game engine from scratch
* differences between Unity and Unreal
* UE4 vs Unity Faceoff
* More AAA games using unity?
* AAA are all free
There are still 2 reasons to "roll your own" game engine:
- To learn. i.e. See this uber diagram of all the components of a modern game engine!
and
- The popular engines still do a terrible job of dynamic terrain management, instancing, meshing, etc. Rolling your own such as Proc World, say using dual contouring, etc., means it is easier to fit into your rendering pipeline instead of trying to figure out someone else's architecture.
Yup, Vim FTW! I particularly like this VIM Cheat Sheet
MS forgot the first rule of programs:
"Those who forget the past are condemned to re-implement it, badly."
Which MMO was this?
That's a good point about USB. The FAT32 4GB file size limit is probably the technical reason why the files are spilt into 3 archives.
That's good question. Looks like they were too lazy to optimize it for the ~4.5 GB DVD / layer
[ ] debian-hurd-2015-i386-DVD-1.iso 24-Apr-2015 07:24 1.7G
[ ] debian-hurd-2015-i386-DVD-2.iso 24-Apr-2015 07:28 1.7G
[ ] debian-hurd-2015-i386-DVD-3.iso 24-Apr-2015 07:32 1.8G
The "typical" excuse would be to help with downloads but seriously who is using a downloader that can't resume in this day and age?
Since the total is 5.2GB I wonder if they could re-compress the files down to 4.5 GB to fit on one DVD with say something like LZMA
TFA has a broken link. This is the fixed one:
I've noticed several design suggestions in your code.