IS-136 is the successor to IS-54 "Digital AMPS" (D-AMPS, commonly referred to as "TDMA" in North America). IS-54 introduced multiplexed digital voice channels, providing three or six times the number of calls, while still using the same binary FSK control channels as AMPS. IS-136 switched to time division multiplexed control channels, and added support for text messages and circuit-switched data.
This is why CDMA services got 3G data about a year before GSM services. GSM ended up throwing in the towel, licensing CDMA, and amended the GSM spec to include wideband CDMA for data service. And this is why GSM phones could talk and use data at the same time - they had a TDMA radio for voice, and a CDMA radio for data. CDMA phones only had a single CDMA radio which could do voice or data, but not both simultaneously. It wasn't because GSM was superior, it was because GSM was inferior and needed a second radio to compete.
You post this at every opportunity, but it doesn't make it true. GSM phones did simultaneous voice/data using GPRS, which was nothing to do with CDMA. GPRS allocated one or more timeslots for packet data. Bandwidth in these timeslots could be divided up between all handsets on the channel with data enabled. Originally GPRS used GMSK modulation, but the later EDGE variant used higher-order QAM to increase data rates. It was always a bit of a hack, and it didn't work well for high-bandwidth applications or things that needed good uplink latency. But it was relatively quick/cheap to roll out using existing infrastructure and frequency allocations.
Some people have to carry their work when they travel, or work at client sites. Dell Precision Mobile Workstation is looking a lot like the last serious professional notebook.
If that's the case, just say you're dropping unmaintained architectures due to lack of interest or active maintainers. Talking about dropping "obsolete" architectures is somewhat misleading when the architectures being dropped are still in being manufactured or developed, but undeniably obsolete architectures are still being actively supported.
So they're dropping support for "obsolete" CPUs but somehow the first-generation Motorola 68000 in the PowerBook 100 doesn't qualify as obsolete? I mean, I was a Mac user in the '90s, and I still have some fondness for the some of the old hardware, but this is ridiculous. What kind of mental gymnastics do you have to go through to keep 68000 but drop the much newer Blackfin DSP, and the M32R that still seems to be manufactured for embedded applications?
Well, I'm not overly familiar with iOS, so I'd add a disclaimer if I was reviewing an iOS app. I'd expect someone who's primarily an iPhone user to give a similar disclaimer when reviewing an Android app. Same for a Mac user reviewing Windows software and vice versa.
Bullshit, at least in Australia. At a legal licensed brothel you'll probably pay $160 for half an hour or $200 for an hour, and it only goes up from there. At a massage parlour offering sex on the side, it might be $60/hour for the massage, plus another $50 for a handjob or $100 for sex. The vast majority of guys paying for sex are paying in the $100-$200 range for an appointment. Street workers taking $50 for a blowjob are very rare.
The typical prostitute is 30 years old,two kids, no husband, and no qualifications. They're fucking for their kids. The typical "massage" girl is trying to pay her way through university and maybe save a bit of money.
It depends on what your application's doing. One of the pitfalls is that it's LLP64, not LP64 like other platforms, so if you'd assumed sizeof(unsigned long) == sizeof(void*) you ran into problems. If you were using inline assembly with MSVC, you had to change it. If you're doing any kind of PC lifecycle management or application installation/inventory, or system configuration, you need to be aware of filesystem and registry redirection in 32-bit applications. It's not a huge issue for most applications. The enhanced security model for Vista and later required more changes.
It's someone who works providing sexual services. It includes prostitution, pornography, and a few other categories. It's a less specific umbrella term.
Steam fights piracy the same way the iTunes music store did: by making it easy/painless to buy the product so people have less incentive to pirate it. It doesn't have to have effective DRM to work.
Mixed Mode Manager was beautiful in a perverse way. The killer was that classic MacOS was tied to the 68k interrupt model - right up to MacOS 9 they were still dispatching interrupts through the 68k emulator. In early versions of System 7 for PowerPC you couldn't run native PowerPC code at interrupt time at all - anything that could be called from an interrupt handler had to run in the 68k emulator (this limitation was solved relatively quickly).
You had this structure called a Universal Procedure Pointer (UPP). On the PowerPC side it contained the address of the code and a description of the argument and return types. This allowed you to call 68k or PowerPC code from PowerPC code. For 68k code to call PowerPC code, there would be a prologue consisting of an _MixedMode A-line trap followed by the argument description. Mixed Mode Manager would detect the trap, break out of the emulator, and translate the stack frame.
You could probably translate COM between x86 and ARM. Microsoft already did this once when they supported 16-bit COM components in 32-bit applications and vice versa. The stack frames had to be translated for the differing calling conventions and pointer types. They probably don't want to though - the roll-out of x86_64 has encouraged people to write more portable code.
Kaspersky is disclosing a flaw their security researchers found in Telegram, which is not a Kaspersky product. The Telegram client code is open source, but that apparently hasn't stopped stupidity making it into the desktop client.
They'll probably have it in constant flux. You know, permanent beta culture, just like everything else Google does. They aren't very good at actual standards.
They didn't do their own web server. It was a pretty GUI for configuring Apache. Same for mail, originally OSX server used Cyrus, I think they switched to dovecot later. DNS was always implemented with BIND. A few of the services like DHCP/NetBoot used their own implementations, but most of it just a GUI for configuring open source services.
OSX Server used to be a compelling proposition for a small business, because it made configuring these services easy for someone who isn't a professional sysadmin. But once they changed it from being a separate OS spin to a feature pack in the app store, it was pretty clear they just didn't care.
I manage all my RHEL and CentOS servers with no GUI, and I've never had a problem. Also, privilege separation is a thing. The more stuff you run elevated, the more chance of an exploit. A UI toolkit is a huge attack surface. Better to just run the parts that need elevated privileges as root and keep the GUI running as a regular user.
But then you'd lose your artificially high buying power and massive profit margins on selling things built in low-cost labour markets. The "American dream" depends on this exploitation to exist at all.
In some games, they let you know about content you can otherwise miss. For example Psychonauts has a bunch of triggered events that you can miss if you just push through the game as fast as possible, and the achievements let you know that you've seen them. In the Steam version of Canabalt, there are achievements to let you know you've seen the entirety of the rearmost scrolling parallax layer.
The GMA950 was pretty bad. As well the performance being abysmal (sucking up RAM bandwidth from the already-starved CPU), it would cause kernel panics on and iBook running OSX when an external monitor was connected. They were terrible GPUs.
Slashdot Mirror
I've never seen "kmph" before, but "kph" seems to be an Americanism. Kilometres per hour is abbreviated to "km/h" in countries that use metric units.
IS-136 is the successor to IS-54 "Digital AMPS" (D-AMPS, commonly referred to as "TDMA" in North America). IS-54 introduced multiplexed digital voice channels, providing three or six times the number of calls, while still using the same binary FSK control channels as AMPS. IS-136 switched to time division multiplexed control channels, and added support for text messages and circuit-switched data.
You post this at every opportunity, but it doesn't make it true. GSM phones did simultaneous voice/data using GPRS, which was nothing to do with CDMA. GPRS allocated one or more timeslots for packet data. Bandwidth in these timeslots could be divided up between all handsets on the channel with data enabled. Originally GPRS used GMSK modulation, but the later EDGE variant used higher-order QAM to increase data rates. It was always a bit of a hack, and it didn't work well for high-bandwidth applications or things that needed good uplink latency. But it was relatively quick/cheap to roll out using existing infrastructure and frequency allocations.
Some people have to carry their work when they travel, or work at client sites. Dell Precision Mobile Workstation is looking a lot like the last serious professional notebook.
If that's the case, just say you're dropping unmaintained architectures due to lack of interest or active maintainers. Talking about dropping "obsolete" architectures is somewhat misleading when the architectures being dropped are still in being manufactured or developed, but undeniably obsolete architectures are still being actively supported.
So they're dropping support for "obsolete" CPUs but somehow the first-generation Motorola 68000 in the PowerBook 100 doesn't qualify as obsolete? I mean, I was a Mac user in the '90s, and I still have some fondness for the some of the old hardware, but this is ridiculous. What kind of mental gymnastics do you have to go through to keep 68000 but drop the much newer Blackfin DSP, and the M32R that still seems to be manufactured for embedded applications?
Well, I'm not overly familiar with iOS, so I'd add a disclaimer if I was reviewing an iOS app. I'd expect someone who's primarily an iPhone user to give a similar disclaimer when reviewing an Android app. Same for a Mac user reviewing Windows software and vice versa.
It emulates the Linux kernel system calls and loads Linux ELF binaries. You won't be able to run NetBSD binaries with this, only Linux binaries.
Bullshit, at least in Australia. At a legal licensed brothel you'll probably pay $160 for half an hour or $200 for an hour, and it only goes up from there. At a massage parlour offering sex on the side, it might be $60/hour for the massage, plus another $50 for a handjob or $100 for sex. The vast majority of guys paying for sex are paying in the $100-$200 range for an appointment. Street workers taking $50 for a blowjob are very rare.
The typical prostitute is 30 years old,two kids, no husband, and no qualifications. They're fucking for their kids. The typical "massage" girl is trying to pay her way through university and maybe save a bit of money.
It depends on what your application's doing. One of the pitfalls is that it's LLP64, not LP64 like other platforms, so if you'd assumed sizeof(unsigned long) == sizeof(void*) you ran into problems. If you were using inline assembly with MSVC, you had to change it. If you're doing any kind of PC lifecycle management or application installation/inventory, or system configuration, you need to be aware of filesystem and registry redirection in 32-bit applications. It's not a huge issue for most applications. The enhanced security model for Vista and later required more changes.
Two? I have half a dozen Opan, myki and Octopus cards used for different types of trips.
It's someone who works providing sexual services. It includes prostitution, pornography, and a few other categories. It's a less specific umbrella term.
If US was still part of the Commonwealth, they would've entered WWII in Europe sooner, not later.
Are you named after an Ubuntu release? The started using imaginary animals with J, so I wouldn't put using pokemon past them.
Steam fights piracy the same way the iTunes music store did: by making it easy/painless to buy the product so people have less incentive to pirate it. It doesn't have to have effective DRM to work.
Bochs x86_64 emulation works on an IBM POWER host.
Mixed Mode Manager was beautiful in a perverse way. The killer was that classic MacOS was tied to the 68k interrupt model - right up to MacOS 9 they were still dispatching interrupts through the 68k emulator. In early versions of System 7 for PowerPC you couldn't run native PowerPC code at interrupt time at all - anything that could be called from an interrupt handler had to run in the 68k emulator (this limitation was solved relatively quickly).
You had this structure called a Universal Procedure Pointer (UPP). On the PowerPC side it contained the address of the code and a description of the argument and return types. This allowed you to call 68k or PowerPC code from PowerPC code. For 68k code to call PowerPC code, there would be a prologue consisting of an _MixedMode A-line trap followed by the argument description. Mixed Mode Manager would detect the trap, break out of the emulator, and translate the stack frame.
You could probably translate COM between x86 and ARM. Microsoft already did this once when they supported 16-bit COM components in 32-bit applications and vice versa. The stack frames had to be translated for the differing calling conventions and pointer types. They probably don't want to though - the roll-out of x86_64 has encouraged people to write more portable code.
Kaspersky is disclosing a flaw their security researchers found in Telegram, which is not a Kaspersky product. The Telegram client code is open source, but that apparently hasn't stopped stupidity making it into the desktop client.
They'll probably have it in constant flux. You know, permanent beta culture, just like everything else Google does. They aren't very good at actual standards.
They didn't do their own web server. It was a pretty GUI for configuring Apache. Same for mail, originally OSX server used Cyrus, I think they switched to dovecot later. DNS was always implemented with BIND. A few of the services like DHCP/NetBoot used their own implementations, but most of it just a GUI for configuring open source services.
OSX Server used to be a compelling proposition for a small business, because it made configuring these services easy for someone who isn't a professional sysadmin. But once they changed it from being a separate OS spin to a feature pack in the app store, it was pretty clear they just didn't care.
I manage all my RHEL and CentOS servers with no GUI, and I've never had a problem. Also, privilege separation is a thing. The more stuff you run elevated, the more chance of an exploit. A UI toolkit is a huge attack surface. Better to just run the parts that need elevated privileges as root and keep the GUI running as a regular user.
I still wish Bugdom and Deimos Rising didn't stop working, even before Apple switched to x86. Stuff gets broken by OS updates all the time.
But then you'd lose your artificially high buying power and massive profit margins on selling things built in low-cost labour markets. The "American dream" depends on this exploitation to exist at all.
In some games, they let you know about content you can otherwise miss. For example Psychonauts has a bunch of triggered events that you can miss if you just push through the game as fast as possible, and the achievements let you know that you've seen them. In the Steam version of Canabalt, there are achievements to let you know you've seen the entirety of the rearmost scrolling parallax layer.
The GMA950 was pretty bad. As well the performance being abysmal (sucking up RAM bandwidth from the already-starved CPU), it would cause kernel panics on and iBook running OSX when an external monitor was connected. They were terrible GPUs.