6331
Off Topic / Re: US GOVERNMENT ISSUES EVACUATION
« on: April 01, 2013, 10:09:42 AM »
spoiler alert: us wins
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Hey um, is there a way i could take off the shades and the cigarette off the beret?why would you do this

I didn't say thatActually yes it does but he doesn't have the right software.
But the way marble presented us does not work
So wait...I didn't say anything about it
You guys are talking about extracting a .blb file from the cache.db?
You're all going to get into some deep trouble with the creators (permitting he allows you to release them)
They are private for a reason. May we let them stay that way?
Sorry but you're wrong. Java runs in a virtual machine; it interprets bytecode and converts it to object code (this is an oversimplification as it does many more optimizations but the abstraction works for my point). C++ compiles to object code and does not need any translation phase. Java's standard library might provide tools which speed up its programs to be faster than some C++ code but in raw benchmarks C++ will always win because there is no intermediary translation phase. To explain it from a different viewpoint, you can write faster algorithms in Python than in C++ if the Python implementation is more efficient. Whatever the case Java is indeed quite fast; there's no question about that.What about this?
Generally, C# and Java can be just as fast or faster because the JIT compiler -- a compiler that compiles your IL the first time it's executed -- can make optimizations that a C++ compiled program cannot because it can query the machine. It can determine if the machine is Intel or AMD; Pentium 4, Core Solo, or Core Duo; or if supports SSE4, etc.
A C++ program has to be compiled beforehand usually with mixed optimizations so that it runs decently well on all machines, but is not optimized as much as it could be for a single configuration (i.e. processor, instruction set, other hardware).
Additionally certain language features allow the compiler in C# and Java to make assumptions about your code that allows it to optimize certain parts away that just aren't safe for the C/C++ compiler to do. When you have access to pointers there's a lot of optimizations that just aren't safe.
Also Java and C# can do heap allocations more efficiently than C++ because the layer of abstraction between the garbage collector and your code allows it to do all of its heap compression at once (a fairly expensive operation).
Now I can't speak for Java on this next point, but I know that C# for example will actually remove methods and method calls when it knows the body of the method is empty. And it will use this kind of logic throughout your code.
So as you can see, there are lots of reasons why certain C# or Java implementations will be faster.
Now this all said, specific optimizations can be made in C++ that will blow away anything that you could do with C#, especially in the graphics realm and anytime you're close to the hardware. Pointers do wonders here.
So depending on what you're writing I would go with one or the other. But if you're writing something that isn't hardware dependent (driver, video game, etc), I wouldn't worry about the performance of C# (again can't speak about Java). It'll do just fine.
It is just as fast as C++.I just looked it up, looks like this is true.