FF6 and earlier were all in a fantasy setting, with FF6 being the closest to modern, and in a way it foretold FF7's "mostly modern" setting. Then there was FF8 which really detracted from what Final Fantasy is about, but it still maintained that it belonged in the series, although it was too... "modern". Like the opening of 10, with the city of Zanarkand.
And you can't take money with you when you die. At least some belief systems will allow you to take open source with you (provided you learn the source code, which then, as part of your personal knowledge, is part of your soul.)
This would work only because then people would be forced to shop elsewhere, at higher prices, and thus able to buy less landfill-destined crap. Other than that, everything else will sadly stay the same.
My phone's "power off" is a suspend-to-RAM mechanism by default. HTC calls it "fast boot". Only by disabling "Fast boot" is power off really power off. Else yanking of the battery becomes a requirement.
960x540 QHD, eh? A lot of recently, and up-and-coming Android devices have that resolution, porting to them would require zero scaling, and porting to my current phone (HTC Desire HD), at 800x480, would only require minor downscaling.
Yes, Clear/Clearwire (who is partially owned by Sprint) runs a WiMAX network. All of Sprint's 4G is this Clear/Sprint co-ran WiMAX network. Also, it's probably worth noting that Clear tries to sell their WiMAX as "another home broadband" for use with home desktop PCs, as well as a mobile broadband network.
Here's a solution: Use Wi-Fi. I would think that the network in DC would be congested for all carriers, and each tower is like a Wi-Fi router, in that it is splitting up one single Internet connection with... oh, ballpark figure, 200 maximum active clients per cell? Now imagine all of the towers around you are loaded. Doesn't spell a good picture, does it? If you're really that hard hit for bandwidth, then, no joke, try dropping to the 2G GSM/EDGE network. As everyone's phones are clamoring to hit up the 3G UMTS/HSPA+ towers, they often ignore GSM/EDGE towers due to the lower maximum throughput that the older 2G systems provide. However, if the 3G system is so overloaded that the speeds have dropped to a crawl, going back to 2G can be an improvement in your case. You say you have an Aria around? Dial this into the Phone app: *#*#4636#*#* (You won't need to press Send, you will be automatically taken to a new menu upon dialing the last *). Hell, save that code as a contact. The menu presented varies across Android devices, but the code is the same for most, if not all Android phones. On my HTC Inspire 4G, go to Phone info -> Connection type, and one can select several options, even options for network types that probably make no sense for your phone (CDMA and EV-DO come to mind). Go from "WCDMA Preferred" to "GSM Only", and try to use the Internet. Your "3G" / "H" / "H+" icon should switch to an "E" (or "G" if you are unlucky or have low signal). Run a speed test. You might find improvements. You might not. At least, it's worth a shot. (Also, I have no instructions for iPhone, as I do not own one, nor know if the network type is even user-selectable on them)
Your imaginary deity called, it wants you to stop telling it to bless crap to your own ends. Oh, and he said that demanding a blessing upon your country still benefits you. It's a good imaginary deity, it is smart enough to protest your selfish demands of blessings that benefit you.
on a side note, I am aware that a person takes up a far smaller percentage of the broadcast sphere, I am still certain that the RF power your body absorbs from a TV or radio tower still exceeds 350 microwatts, unless you are significantly distant from the mast. Of course, that is totally ignoring every other TV and radio broadcast tower in range of you. And yes, I also considered that they broadcast continuously and not in TDMA/TDD bursts.
look, your standard GSM cellphone broadcasts at roughly 1mW in a nearly isotropic fashion. Your head take up roughly 35 percent (estimate) of the isotropic broadcast sphere. So, when you are on the phone, you are absorbing 350 microwatts of RF. Does it bother you at all that most TV and radio stations broadcast at 5 million to 50 million times the effective irradiated power of your cellphone, at 5kW-50kW?
Also, the "low frequency pulse" you describe is due to the use of TDMA (time division multiples access) in GSM and the failed D-AMPS, where LTE can also use similar time division schemes when there is not enough spectrum to have a separate downlink and uplink channels, so a single channel is used for both, by alternating between broadcasting and receiving on the same frequency (time division duplex). Look up TD-LTE. LTE only solves the problem if your carrier has enough spectrum to use FD-LTE.
Sounds like you didn't put a lot of thought into your take of the situation, and are trying to push a biased, uninformed opinion. Let me inform.
First of all, a fine-grained permission system like this is nothing new. BlackBerry OS has such a system, where permissions can be granted and revoked on-the-fly, and at any time. It's also worth noting that this is a feature currently unique to CyanogenMod, and not on most people's Android devices. This will thus have no effect for most Android users.
Secondly, it's not like average Joe Moron is going to be using this fine-grained permission control system. Most average users will never worry about fine-grained permission controls, nor will they ever worry about the security implications of the far-reaching permissions that apps ask for as it is, and on the rare occasion that they stumble into an unrecognizable screen or menu, average Joe Moron will have his usual reaction of shutting down his reasoning and logic skills, followed by mashing everything in sight on the phone until something recognizable appears. If anything broke during the course, the user would simply assume he broke it himself.
Thirdly, if an app has code to gracefully failed when permissions were no longer available, then the app would also be able to display an alert or dialog to the user indicating that the permissions required are absent and the ramifications to the user (such as what features are now disabled, or any new limitations arising from lack of permissions, etc.). They won't just "break" and have droves of average users turning in bad reviews and making apps not sell. Y'know, the average users that rooted their phones, installed CyanogenMod, and then started setting fine-grained permissions on their apps. Yeah, those average users.
Yes, but free TV's business model is the same as Google's - to sell eyes to advertisers, in turn, to make money for advertisers by having the eyes buy what the advertiser is selling.
In short, free TV depends on you running out to the store and buying everything in sight.
I am no graphics programmer, but I am going to stretch out my experience in other areas (audio APIs), and say that, while these are hardware-dependent in terms of features offered, I highly doubt the same low-level shaders that work on an ATI card will work on an NVIDIA card; in fact, I see HLSL and GLSL as wrappers, sorta of like Direct3D and OpenGL themselves a generation or two ago - certain Direct3D calls or OpenGL calls depended on what features are provided by the underlying hardware, and this also translates to bindings for interpreted languages (Python, for example). One graphics card might have you push 16-bit word 0xFEED to IO port 0x14f3, whereas another might have you put a 32-bit double-word to physical memory address 0xD4001337, while the program behind the high-level interface simply called the same exact function and arguments for both.
While this is an example describing purely native code, I believe it translates (maybe not so well) to interpreted things, like EMCA-262 (ISO/IEC 16262, aka JavaScript) and WebGL.
Let's say I want to send MPEG audio data directly to an MPEG-decoding sound card. With Open Sound System v4, I do this:
int dsp_fd = open("/dev/dsp", O_RDWR | O_ASYNC);
int format = AFMT_MPEG;
int ret = ioctl(dsp_fd, SNDCTL_DSP_SETFMT, &format);
If the underlying hardware supports decoding MPEG audio, it works, I can then write() all the MPEG audio data I want to my hearts content. If the hardware doesn't support decoding MPEG audio, I better hope the driver includes a licensed software decoder, or 'ret' there will contain the value -1, meaning I'm fucked.
When I see you idiots complaining about APIs that are essentially driving hardware functions lack certain functionality when the underlying hardware also lacks said functionality, and that you expect APIs to either "always work in full or completely break in full", I want to punch you in the face. From what I gather from a comment thrown around here (correct me if I am wrong), Silverlight's 3D APIs are intentionally crippled in the shader department to take the worry of hardware support away from developers (at the expense of being unable to use all of the features of the underlying hardware, I guess), and somehow that is the right thing to do. This AC here makes a pretty good point, in that, at the end of the day, it's all hardware-level code anyways. And I will direct you at, say, mpg123, which compiles in entirely different source files whether the target is x86 or PowerPC or whatever, if MMX or SSE or Altivec is to be used, etc., all hardware features of a CPU.
TL;DR: If you bitch because parts of an API used to drive hardware are unavailable in response to the hardware not supporting those features, and instead want an API that has all features always working no matter what the underlying hardware supports, either find an API that doesn't mind falling back to software rendering, or pull your head out of your ass and realize that the programming world (mostly) doesn't work that way.
Also, let me know how my knuckles taste, I'm going to punch you in the mouth for being stupid, while I'm at it.
Yes! Depending on your programming language, you can use conditional code compilation (this leads to different binary versions, I know, but all from the same exact code), or by checking OS and API versions (and optional APIs installed) and choose to conditionally enable code paths at runtime accordingly. Don't have an accelerometer API for the device? Don't use code that checks for device acceleration. User didn't install the Last.fm app (and thus it's optional third-party API)? Don't try to scrobble. Older OS version doesn't support libfoo? #ifdef out code that deals with libfoo. When doing development as official as possible, you should only need two code bases for your app to reach most users - one in Java for BlackBerry, Android, dumb phones, and one in C/C++ for iOS, Symbian, webOS (?), Playbook QNX, Mac OS X, Windows/WinMo and Bada.
Goes without saying that Apple will deliver a sub-par experience on older devices in order to "persuade" users to upgrade to newer devices, thus making Apples more money. Everyone does it.
This story was submitted by the very writer of the article linked in the story. Look at the username, then load the linked article and look at the author's name.
So essentially your data is just as subject to being lost forever as it was... hell, as it's always been?
Nothing has really changed in terms of data retention (or the lack thereof), aside from whose responsible for when it gets lost. Formerly you, now everyone but.
Slashdot Mirror
FF6 and earlier were all in a fantasy setting, with FF6 being the closest to modern, and in a way it foretold FF7's "mostly modern" setting. Then there was FF8 which really detracted from what Final Fantasy is about, but it still maintained that it belonged in the series, although it was too... "modern". Like the opening of 10, with the city of Zanarkand.
"You spin me right round, baby, right round, like a broken record, right round, right round, You spin me right round..."
And you can't take money with you when you die. At least some belief systems will allow you to take open source with you (provided you learn the source code, which then, as part of your personal knowledge, is part of your soul.)
This would work only because then people would be forced to shop elsewhere, at higher prices, and thus able to buy less landfill-destined crap. Other than that, everything else will sadly stay the same.
My phone's "power off" is a suspend-to-RAM mechanism by default. HTC calls it "fast boot". Only by disabling "Fast boot" is power off really power off. Else yanking of the battery becomes a requirement.
960x540 QHD, eh? A lot of recently, and up-and-coming Android devices have that resolution, porting to them would require zero scaling, and porting to my current phone (HTC Desire HD), at 800x480, would only require minor downscaling.
Yes, Clear/Clearwire (who is partially owned by Sprint) runs a WiMAX network. All of Sprint's 4G is this Clear/Sprint co-ran WiMAX network. Also, it's probably worth noting that Clear tries to sell their WiMAX as "another home broadband" for use with home desktop PCs, as well as a mobile broadband network.
Here's a solution: Use Wi-Fi. I would think that the network in DC would be congested for all carriers, and each tower is like a Wi-Fi router, in that it is splitting up one single Internet connection with... oh, ballpark figure, 200 maximum active clients per cell? Now imagine all of the towers around you are loaded. Doesn't spell a good picture, does it? If you're really that hard hit for bandwidth, then, no joke, try dropping to the 2G GSM/EDGE network. As everyone's phones are clamoring to hit up the 3G UMTS/HSPA+ towers, they often ignore GSM/EDGE towers due to the lower maximum throughput that the older 2G systems provide. However, if the 3G system is so overloaded that the speeds have dropped to a crawl, going back to 2G can be an improvement in your case. You say you have an Aria around? Dial this into the Phone app: *#*#4636#*#* (You won't need to press Send, you will be automatically taken to a new menu upon dialing the last *). Hell, save that code as a contact. The menu presented varies across Android devices, but the code is the same for most, if not all Android phones. On my HTC Inspire 4G, go to Phone info -> Connection type, and one can select several options, even options for network types that probably make no sense for your phone (CDMA and EV-DO come to mind). Go from "WCDMA Preferred" to "GSM Only", and try to use the Internet. Your "3G" / "H" / "H+" icon should switch to an "E" (or "G" if you are unlucky or have low signal). Run a speed test. You might find improvements. You might not. At least, it's worth a shot. (Also, I have no instructions for iPhone, as I do not own one, nor know if the network type is even user-selectable on them)
Neither does a full mailer, news reader, Web server, or BitTorrent client, but hey, who's counting?
Your imaginary deity called, it wants you to stop telling it to bless crap to your own ends. Oh, and he said that demanding a blessing upon your country still benefits you. It's a good imaginary deity, it is smart enough to protest your selfish demands of blessings that benefit you.
Since ::1 is the loopback address, and 1 is first, does that mean IPv6 is about putting yourself first?
Hey, now, not all trolling is bad, sometimes (rarely) it can be thought provoking. Take it as a compliment. I got a good laugh out of your statement.
on a side note, I am aware that a person takes up a far smaller percentage of the broadcast sphere, I am still certain that the RF power your body absorbs from a TV or radio tower still exceeds 350 microwatts, unless you are significantly distant from the mast. Of course, that is totally ignoring every other TV and radio broadcast tower in range of you. And yes, I also considered that they broadcast continuously and not in TDMA/TDD bursts.
look, your standard GSM cellphone broadcasts at roughly 1mW in a nearly isotropic fashion. Your head take up roughly 35 percent (estimate) of the isotropic broadcast sphere. So, when you are on the phone, you are absorbing 350 microwatts of RF. Does it bother you at all that most TV and radio stations broadcast at 5 million to 50 million times the effective irradiated power of your cellphone, at 5kW-50kW?
Also, the "low frequency pulse" you describe is due to the use of TDMA (time division multiples access) in GSM and the failed D-AMPS, where LTE can also use similar time division schemes when there is not enough spectrum to have a separate downlink and uplink channels, so a single channel is used for both, by alternating between broadcasting and receiving on the same frequency (time division duplex). Look up TD-LTE. LTE only solves the problem if your carrier has enough spectrum to use FD-LTE.
Sounds like you didn't put a lot of thought into your take of the situation, and are trying to push a biased, uninformed opinion. Let me inform.
First of all, a fine-grained permission system like this is nothing new. BlackBerry OS has such a system, where permissions can be granted and revoked on-the-fly, and at any time. It's also worth noting that this is a feature currently unique to CyanogenMod, and not on most people's Android devices. This will thus have no effect for most Android users.
Secondly, it's not like average Joe Moron is going to be using this fine-grained permission control system. Most average users will never worry about fine-grained permission controls, nor will they ever worry about the security implications of the far-reaching permissions that apps ask for as it is, and on the rare occasion that they stumble into an unrecognizable screen or menu, average Joe Moron will have his usual reaction of shutting down his reasoning and logic skills, followed by mashing everything in sight on the phone until something recognizable appears. If anything broke during the course, the user would simply assume he broke it himself.
Thirdly, if an app has code to gracefully failed when permissions were no longer available, then the app would also be able to display an alert or dialog to the user indicating that the permissions required are absent and the ramifications to the user (such as what features are now disabled, or any new limitations arising from lack of permissions, etc.). They won't just "break" and have droves of average users turning in bad reviews and making apps not sell. Y'know, the average users that rooted their phones, installed CyanogenMod, and then started setting fine-grained permissions on their apps. Yeah, those average users.
Actually, calling uses XMPP Jingle, with RTP being used as the transport, similar to SIP.
Yes, but free TV's business model is the same as Google's - to sell eyes to advertisers, in turn, to make money for advertisers by having the eyes buy what the advertiser is selling.
In short, free TV depends on you running out to the store and buying everything in sight.
I am no graphics programmer, but I am going to stretch out my experience in other areas (audio APIs), and say that, while these are hardware-dependent in terms of features offered, I highly doubt the same low-level shaders that work on an ATI card will work on an NVIDIA card; in fact, I see HLSL and GLSL as wrappers, sorta of like Direct3D and OpenGL themselves a generation or two ago - certain Direct3D calls or OpenGL calls depended on what features are provided by the underlying hardware, and this also translates to bindings for interpreted languages (Python, for example). One graphics card might have you push 16-bit word 0xFEED to IO port 0x14f3, whereas another might have you put a 32-bit double-word to physical memory address 0xD4001337, while the program behind the high-level interface simply called the same exact function and arguments for both.
While this is an example describing purely native code, I believe it translates (maybe not so well) to interpreted things, like EMCA-262 (ISO/IEC 16262, aka JavaScript) and WebGL.
Let's say I want to send MPEG audio data directly to an MPEG-decoding sound card. With Open Sound System v4, I do this:
int dsp_fd = open("/dev/dsp", O_RDWR | O_ASYNC);
int format = AFMT_MPEG;
int ret = ioctl(dsp_fd, SNDCTL_DSP_SETFMT, &format);
If the underlying hardware supports decoding MPEG audio, it works, I can then write() all the MPEG audio data I want to my hearts content. If the hardware doesn't support decoding MPEG audio, I better hope the driver includes a licensed software decoder, or 'ret' there will contain the value -1, meaning I'm fucked.
When I see you idiots complaining about APIs that are essentially driving hardware functions lack certain functionality when the underlying hardware also lacks said functionality, and that you expect APIs to either "always work in full or completely break in full", I want to punch you in the face. From what I gather from a comment thrown around here (correct me if I am wrong), Silverlight's 3D APIs are intentionally crippled in the shader department to take the worry of hardware support away from developers (at the expense of being unable to use all of the features of the underlying hardware, I guess), and somehow that is the right thing to do. This AC here makes a pretty good point, in that, at the end of the day, it's all hardware-level code anyways. And I will direct you at, say, mpg123, which compiles in entirely different source files whether the target is x86 or PowerPC or whatever, if MMX or SSE or Altivec is to be used, etc., all hardware features of a CPU.
TL;DR: If you bitch because parts of an API used to drive hardware are unavailable in response to the hardware not supporting those features, and instead want an API that has all features always working no matter what the underlying hardware supports, either find an API that doesn't mind falling back to software rendering, or pull your head out of your ass and realize that the programming world (mostly) doesn't work that way.
Also, let me know how my knuckles taste, I'm going to punch you in the mouth for being stupid, while I'm at it.
Not only that but the games also work on Xbox360 and mobile phones without such a major porting.
Know what else mobile phones have? The web.
Xbox 360 doesn't have the web. What do you recommend to get a game ported to a console?
PSN hack aside, the PLAYSTATION3 *does* have the web (WebGL support is another story). Without a PSN account, even! What say you now?
Yes! Depending on your programming language, you can use conditional code compilation (this leads to different binary versions, I know, but all from the same exact code), or by checking OS and API versions (and optional APIs installed) and choose to conditionally enable code paths at runtime accordingly. Don't have an accelerometer API for the device? Don't use code that checks for device acceleration. User didn't install the Last.fm app (and thus it's optional third-party API)? Don't try to scrobble. Older OS version doesn't support libfoo? #ifdef out code that deals with libfoo. When doing development as official as possible, you should only need two code bases for your app to reach most users - one in Java for BlackBerry, Android, dumb phones, and one in C/C++ for iOS, Symbian, webOS (?), Playbook QNX, Mac OS X, Windows/WinMo and Bada.
Goes without saying that Apple will deliver a sub-par experience on older devices in order to "persuade" users to upgrade to newer devices, thus making Apples more money. Everyone does it.
This story was submitted by the very writer of the article linked in the story. Look at the username, then load the linked article and look at the author's name.
So essentially your data is just as subject to being lost forever as it was... hell, as it's always been?
Nothing has really changed in terms of data retention (or the lack thereof), aside from whose responsible for when it gets lost. Formerly you, now everyone but.
Except the mafia usually did provide some protection, after all, a failed business can't pay it's protection monies.
Are you Daniel French, aka nirvgorilla?