I'm a software engineer so my knowledge is rather limited, but I'd have assumed that the orbits of planets would tend to be in the same plane as the spinning of the galaxy, so if you look at a mostly flat galaxy, you'll find mostly aligned orbits, and if a galaxy was more... "chaotic", the orbits would be likewise less aligned in respect with each other.
From he article: The high power charging will require special, electronically detectable and very clever “USB Power Delivery” certified cables, which will be backwards compatible with all types of USB 2.0 and 3.0.
So yeah, if resistance > X, its not a proper cable and you can't use it for > 4.5W (standard USB3 charging power)
I always forget this site ignores line feeds in comments and expects me to add <br>s to the comment myself.
This is how it was meant to look like (if I had noticed my failing before I pressed submit):
I know you can set up an x86 userland on a x64 kernel (although it can be somewhat annoying to do it right sometimes). The X32 ABI is meant to replace the x86 ABI in that situation, because it offers advantages without any drawbacks.
Without X32, you either use the full x64, including the pointer bloat and long-integer-is-64bit issue (when compiling unaware code), or you stick to plain old x86, with only 6 integer general-purpose registers and only 8 FP/SIMD registers.
The idea of X32 is to get all the advantages of x64 (extra registers, most notably) into a 32bit process, avoiding pointers and longs growing unnecessarily in size, which is not ideal for database daemons and similar software with high memory usage, but can be a really nice boost for applications that do intensive work on small data sets (specially apps that have a lot of references to data/virtual methods/callbacks).
I know you can set up an x86 userland on a x64 kernel (although it can be somewhat annoying to do it right sometimes). The X32 ABI is meant to replace the x86 ABI in that situation, because it offers advantages without any drawbacks.
Without X32, you either use the full x64, including the pointer bloat and long-integer-is-64bit issue (when compiling unaware code), or you stick to plain old x86, with only 6 integer general-purpose registers and only 8 FP/SIMD registers.
The idea of X32 is to get all the advantages of x64 (extra registers, most notably) into a 32bit process, avoiding pointers and longs growing unnecessarily in size, which is not ideal for database daemons and similar software with high memory usage, but can be a really nice boost for applications that do intensive work on small data sets (specially apps that have a lot of references to data/virtual methods/callbacks).
I assumed the idea of x32 was to run it on top of a 64bit kernel? so that you could mix x64 apps with x32 and use pointers as big as necessary and not always 64bit, maybe I should read more on it to confirm...
Major tier domains (expensive, requiring proof of organization/trademark):
<name>.global
<name>.<country>
<name>.<culture> (in cases where one country coudl have more than one culture with specific languages, etc)
(certain names mult be disallowed when they collide with lower-tier codes and reserved words)
Middle tier domains (affordable, requiring proof of organization existence and that it's valid for the class):
<name>.<class>.global
<name>.<class>.<country>
(where <class> could be 'co', 'org', etc.)
Personal domains (cheaper, requiring valid ID):
<name>.people.global
<name>.people.<country>
Sub-domains of those could be sold by their owners, and certain major domains should be banned. the global namespace should be managed by a non-profit international organization, country namespaces shoudl be managed by the respective governments.
Because they all run off X11, and I hate the whole concept of a socket-based windowing protocol. I also have a great dislike for POSIX, which is the whole reason why I'm stuck on Windows still... at least until (if) Metro becomes the norm, then there will be something I hate more than X11 and I may switch.
This has existed in Spain for many months.
The Spanish version also includes piracy and other illegal activities in the list, in case you didn't look at child porn.
It scares the shit out of people, and I suppose it works more times than it doesn't.
Slashdot Mirror
I'm a software engineer so my knowledge is rather limited, but I'd have assumed that the orbits of planets would tend to be in the same plane as the spinning of the galaxy, so if you look at a mostly flat galaxy, you'll find mostly aligned orbits, and if a galaxy was more... "chaotic", the orbits would be likewise less aligned in respect with each other.
See http://goo.gl/MPjHT
From he article: The high power charging will require special, electronically detectable and very clever “USB Power Delivery” certified cables, which will be backwards compatible with all types of USB 2.0 and 3.0. So yeah, if resistance > X, its not a proper cable and you can't use it for > 4.5W (standard USB3 charging power)
I always forget this site ignores line feeds in comments and expects me to add <br>s to the comment myself.
This is how it was meant to look like (if I had noticed my failing before I pressed submit):
I know you can set up an x86 userland on a x64 kernel (although it can be somewhat annoying to do it right sometimes). The X32 ABI is meant to replace the x86 ABI in that situation, because it offers advantages without any drawbacks.
Without X32, you either use the full x64, including the pointer bloat and long-integer-is-64bit issue (when compiling unaware code), or you stick to plain old x86, with only 6 integer general-purpose registers and only 8 FP/SIMD registers.
The idea of X32 is to get all the advantages of x64 (extra registers, most notably) into a 32bit process, avoiding pointers and longs growing unnecessarily in size, which is not ideal for database daemons and similar software with high memory usage, but can be a really nice boost for applications that do intensive work on small data sets (specially apps that have a lot of references to data/virtual methods/callbacks).
I know you can set up an x86 userland on a x64 kernel (although it can be somewhat annoying to do it right sometimes). The X32 ABI is meant to replace the x86 ABI in that situation, because it offers advantages without any drawbacks. Without X32, you either use the full x64, including the pointer bloat and long-integer-is-64bit issue (when compiling unaware code), or you stick to plain old x86, with only 6 integer general-purpose registers and only 8 FP/SIMD registers. The idea of X32 is to get all the advantages of x64 (extra registers, most notably) into a 32bit process, avoiding pointers and longs growing unnecessarily in size, which is not ideal for database daemons and similar software with high memory usage, but can be a really nice boost for applications that do intensive work on small data sets (specially apps that have a lot of references to data/virtual methods/callbacks).
I assumed the idea of x32 was to run it on top of a 64bit kernel? so that you could mix x64 apps with x32 and use pointers as big as necessary and not always 64bit, maybe I should read more on it to confirm...
Major tier domains (expensive, requiring proof of organization/trademark):
<name>.global
<name>.<country>
<name>.<culture> (in cases where one country coudl have more than one culture with specific languages, etc)
(certain names mult be disallowed when they collide with lower-tier codes and reserved words)
Middle tier domains (affordable, requiring proof of organization existence and that it's valid for the class):
<name>.<class>.global
<name>.<class>.<country>
(where <class> could be 'co', 'org', etc.)
Personal domains (cheaper, requiring valid ID):
<name>.people.global
<name>.people.<country>
Sub-domains of those could be sold by their owners, and certain major domains should be banned. the global namespace should be managed by a non-profit international organization, country namespaces shoudl be managed by the respective governments.
Because they all run off X11, and I hate the whole concept of a socket-based windowing protocol. I also have a great dislike for POSIX, which is the whole reason why I'm stuck on Windows still... at least until (if) Metro becomes the norm, then there will be something I hate more than X11 and I may switch.
This has existed in Spain for many months. The Spanish version also includes piracy and other illegal activities in the list, in case you didn't look at child porn. It scares the shit out of people, and I suppose it works more times than it doesn't.