32 bit COM objects and 64 bit COM objects can both be used in a
You've added 12 really lame anti
I'm in Australia and my average is 237ms, and they say that we don't need the NBN
The NBN will reduce the time between you and your ISP, so at most will shave 20ms off your latency - provided they don't screw it up and increase the latency with the equipment.
Here's a full tracert from a 19Mbit link on Internode:
Tracing route to slashdot.org [184.108.40.206]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.254
2 29 ms 29 ms 29 ms lns20.adl6.on.ii.net [220.127.116.11]
3 29 ms 29 ms 30 ms te3-3.cor1.adl6.on.ii.net [18.104.22.168]
4 29 ms 29 ms 29 ms xe-11-0-0.cr1.adl6.on.ii.net [22.214.171.124]
5 49 ms 48 ms 49 ms ae4.br1.syd7.on.ii.net [126.96.36.199]
6 204 ms 205 ms 206 ms te0-2-0-3.br2.sjc2.on.ii.net [188.8.131.52]
7 204 ms 204 ms 203 ms xe-11-0-1.edge1.SanJose3.Level3.net [184.108.40.206]
8 204 ms 203 ms 204 ms Savvis-Level3.Dallas3.Level3.net [220.127.116.11]
9 206 ms 225 ms 209 ms cr2-tengig0-7-3-0.sanfrancisco.savvis.net [18.104.22.168]
10 266 ms 266 ms 266 ms cr1-ten-0-4-0-1.chd.savvis.net [22.214.171.124]
11 259 ms 258 ms 258 ms hr1-te-12-0-1.elkgrovech3.savvis.net [126.96.36.199]
12 268 ms 265 ms 264 ms das5-v3029.ch3.savvis.net [188.8.131.52]
13 258 ms 268 ms 256 ms 184.108.40.206
14 257 ms 265 ms 265 ms slashdot.org [220.127.116.11]
Wow... these comments make up a lot of assumptions about my character. What's with all the hostility? One guy called me a cunt! What's next, threats?
You made a logical and totally reasonable suggestion, but it went against his religion. His internal conflict caused him to lash out at you the messenger.
for single people its $90 a month for the carrier bill
Holy shit, that's a lot of money for cellphone service.
Bloody oath! I pay $10/month for 1GB of 3G + about $5 worth of calls and SMS, so $15 total per month for me.
I already had a customer balking about installing java. Now it seems certain we'll have to port everything away, a huge undertaking. (Even though we'll end up porting it to C++ and have multiple times more vulnerabilities when we're done, but I guess at least they'll be specific to our application).
There is no way in hell I could recommend taking a team of Java developers and getting them to port their application to C++. Actually I've seen this attempted back in 2003, and it ended up generating a bunch of C++ code that had to be trashed and rewritten by a team of competent C++ programmers. The problem was mainly all these design patterns that Java programmers use that are based on garbage collection being present, and all the weird and wonder hacks that were introduced to try to add some kind of memory manangement scheme on top of a bunch of code that was written without any thought about object lifetime management. What about other languages like C#/mono? that will at least allow a basic like for like translation of everything below the GUI layer?
Barium is an element does not vanish and can certainly be sterilized to any degree desired. So, why do they apparently not recycle the stuff?
Because not much is used in medical practice, so it's not worth it. The main use of Barium is Barite which is a Drilling Fluid for drilling bore holes. You may have heard of white mud?
you'd have to be particularly crazy to develop a game that requires DirectX 11.1 any time soon
Given a pragmatic developer I can't see how that would happen, unless they were doing a tech demo. Most of the DirectX utility and sample code sets up the device like this:
- Try initializing Directx9
- Try initializing Directx10
- Try initializing Directx11
so now you add:
- Try initializing Directx11.1
All the fixed function stuff is gone now. You do your own object-local-to-word transform in the vertex shader, and then the world-to-view transform using the projection matrix. If you have stereoscopic rendering, then you have 2 projection matricies in the shaders.
Thus in the above tests you get back what version of DirectX is running, and load the corresponding set of shaders for your world, lighting and material renderers. You'd need the option to turn on or off stereoscopic rendering anyway, so it makes having an exclusive Directx11.1 renderer highly implausible.