Oh it doesn't happen all the time, it's relatively rare in the scale of things. Most prostitutes in Australia are single mothers fucking for their kids, students trying to make a few bucks on the side, or people who have fallen through the gaps in society. Legalisation/regulation of prostitution is far better than the alternative - it makes it safer for everyone involved, allows government to tax it, lets police focus on actual crimes rather than prosecuting vulnerable women, etc.
I just think it's interesting that when human trafficking does happen, it's invariably connected to licensed brothels rather than unlicensed ones.
Prostitution is legal and regulated in Australia, but you still get human trafficking cases. Interestingly, it's usually legal, licensed brothels that are involved in human trafficking/sex slavery. The illegal unlicensed businesses are usually just students or people on tourist visas (who shouldn't be working) trying to make some money on the side.
That's not completely true - Mandarin Chinese has stricter grammar than Cantonese. There are different conventions for how things are phrased. They're definitely mutually intelligible and very similar when written, but they end up sounding odd if you try to read one as the other.
Bourne shells pass as literal on failure to match glob. This has always irritated me as commands like "find . -name *.c" do radically different things depending on whether there are any.c files in the current directory. C shells don't pass on a literal glob if it doesn't match - they return an error without running the command.
Yeah, but Audacity is a sound file editor, not a DAW. It simply doesn't have the functionality a lot of people need. You could have recommended Reaper, BitWig or something else that runs on Linux, but suggesting Audacity as a replacement for a DAW just makes you looks ignorant.
360 degree video would't be much use for porn unless you dropped the camera in the middle of a group sex orgy or something. In most porn, all the action is happening in one spot. You might want multi-angle video where you can view the action from different locations (also useful for sports footage, dance instruction videos and other stuff), but that's completely different to 360 degree video that lets you look in any direction from a single location.
I have kids (currently 8 and 4) and a Wii U and have not suffered any mishaps. They know not to do stupid shit because my wife and I have had high expectations of them from when they were very young.
People have been using vulnerabilities in CMS and forum software (and their plugins) to attack web and mail servers with this ransomware. I know it's hit some schools and small companies.
If you just want to play NAOMI/Atomiswave games, you're better off using DEmul. It attempts to map PowerVR onto D3D and has a recompiling SH4 core. MAME doesn't come close to that performance. However DEmul uses the MAME CHD format for GDROM images and uses MAME-documents disc/ROM dumps, and the DEmul developers share findings with the MAME team and vice versa. MAME research/technology contributes to non-MAME emulators all the time.
There are issues with encryption/protection blocking progress on some of the later Namco games. There has been some progress behind the scenes, but it hasn't got as far as making anything playable.
There are dedicated Sega Model 2/3 emulators which, once again, are heavily dependent on the documentation from MAME.
As for MAME emulating things you've never heard of, that's one of the big benefits of MAME: ensuring these things aren't lost to future generations. Without MAME's preservation efforts, a lot more of our digital heritage would be lost.
MAME was never BSD-licensed: it was BSD plus additional restrictions. This made it impossible to use MAME code in a GPL project, or to use [L]GPL code in MAME, without first securing a license exception for the code in question. The vast majority of the code in MAME is now BSD-licensed. However since some code is now [L]GPL-licensed, binary distributions of the entire project fall under the GPL.
Most of the source is BSD-licesnsed while parts are [L]GPL. The entire emulation/scheduling core is BSD, so if you want to take advantage of that to make your own emulator, go right ahead. However if you're in it for the games, some rather widely used sound cores in MAME are under GPL, so you can't go closing them up.
We're doing plenty to improve the user experience of MAME. We recently integrated the MEWUI user interface code, giving better system selection and configuration from within MAME. MAME now supports UI localisation. We added "autofire" features.
New APIs are supported depending on your host OS including CoreAudio, Xaudio2 and Xinput, for lower latency and support for newer peripherals.
The Direct3D renderer has supported CRT simulation for a while, and the OpenGL renderer supports pluggable filters. But the new cross-platform BGFX renderer will support all that and more with a clean, data-driven approach in an upcoming release. We're also looking to integrate code from GroovyMAME to support people using MAME in arcade-style cabinets and with CRT monitors.
But most importantly, the emulation keeps getting better, leading to more playable games and usable emulated computers. For example recently MAME became the first emulator to properly support the Zaccaria classics Cat and Mouse and Laser Battle (licensed to Midway as Lazarian) with correct colours, full video effects and sound. MAME also recently added the very rare Korean games 96 Flag Rally and Philko Lock On. MAME's support for the historically significant Osborne 1 computer got a lot better last year, including proper memory banking and support for the SCREEN-PAC add-on.
MAME's slot system allows emulation of many peripherals and add-ons that other emulators can't handle. Things like add-on procesor cards for the Apple II, or the IBM PGC.
This is only possible because MAME has a flexible emulation core and a huge library of well-tested cores for emulating CPUs, video hardware, sound chips, and other devices.
Yeah, ten months of tracking people down and wrangling agreements. In the end a small amount of code had to be removed for the rare cases where authors couldn't be contacted. However we think it's effort well spent.
It was previously a license based on the BSD-3-Clause license with additional terms prohibiting commercial use, distribution alongside unauthorised ROM images, and certain kinds of derivative builds. This caused it to fall afoul of OSI and FSF rules. It also tended to hurt potential legitimate users (e.g. rights holders wanting to re-release classics) while doing nothing to stop software pirates and arcade game bootleggers.
This change also makes it easier for other F/L/OSS projects to leverage MAME code, and may help get MAME accepted by F/L/OSS software distribution services (such as main package repositories for major Linux distributions).
Note that MAME is a registered trademark, and the are still restrictions on use of the MAME name, logo and wordmark.
Oh the Aborigines definitely have been known to screw with white people. There's a place in Victoria called Wendouree, which comes from the local Aboriginal for "piss off" (as in an impolite way to tell someone to go away). They asked a local Aboriginal woman what the name of the swamp was, and that's what she said. There are other cases where people have asked the local Aborigines what something should be called and they've given an ironic or less-than-flattering name that's been adopted because the people asking don't know enough about the language to know the joke's on them.
If you time it right, you can duck and punch a magpie when it attempts to dive-bomb you. I've pulled this off a few times, and in each case the magpie in question has remembered me from then on and not tried to attack me again (they still attacked other people). They aren't particularly quiet in a dive, so if you're actually listening you can hear them on the way down. Most people just don't have any situational awareness.
I've got wild emus on the run, too. You can also scare off most Australian snakes, including the infamous eastern brown snake. The Australian animals you really don't want to fuck with are the eastern grey kangaroo, Sydney funnelweb spider, blue-ringed octopus and saltwater stonefish.
That's not true at all. The huge majority of C/J/K characters in common use are in the Basic Multilingual Plane (BMP) and therefore take two bytes in UTF-16, compared to three bytes in UTF-8. The characters outside the BMP are all infrequently user or included for historical reasons but not in modern usage.
On your second point, Microsoft couldn't change the existing APIs to expect UTF-8, as they need to use the current ANSI codepage for compatibility. They correctly convert the current ANSI codepage to/from the encoding used by the underlying filesystem. If you want to use UTF-8 with these APIs, you can change the ANSI codepage to UTF-8 for your application.
Slashdot Mirror
Oh it doesn't happen all the time, it's relatively rare in the scale of things. Most prostitutes in Australia are single mothers fucking for their kids, students trying to make a few bucks on the side, or people who have fallen through the gaps in society. Legalisation/regulation of prostitution is far better than the alternative - it makes it safer for everyone involved, allows government to tax it, lets police focus on actual crimes rather than prosecuting vulnerable women, etc.
I just think it's interesting that when human trafficking does happen, it's invariably connected to licensed brothels rather than unlicensed ones.
Prostitution is legal and regulated in Australia, but you still get human trafficking cases. Interestingly, it's usually legal, licensed brothels that are involved in human trafficking/sex slavery. The illegal unlicensed businesses are usually just students or people on tourist visas (who shouldn't be working) trying to make some money on the side.
You might not think you were impaired but you were. Alcohol is nasty that way.
That's not completely true - Mandarin Chinese has stricter grammar than Cantonese. There are different conventions for how things are phrased. They're definitely mutually intelligible and very similar when written, but they end up sounding odd if you try to read one as the other.
Bourne shells pass as literal on failure to match glob. This has always irritated me as commands like "find . -name *.c" do radically different things depending on whether there are any .c files in the current directory. C shells don't pass on a literal glob if it doesn't match - they return an error without running the command.
Yeah, but Audacity is a sound file editor, not a DAW. It simply doesn't have the functionality a lot of people need. You could have recommended Reaper, BitWig or something else that runs on Linux, but suggesting Audacity as a replacement for a DAW just makes you looks ignorant.
360 degree video would't be much use for porn unless you dropped the camera in the middle of a group sex orgy or something. In most porn, all the action is happening in one spot. You might want multi-angle video where you can view the action from different locations (also useful for sports footage, dance instruction videos and other stuff), but that's completely different to 360 degree video that lets you look in any direction from a single location.
I have kids (currently 8 and 4) and a Wii U and have not suffered any mishaps. They know not to do stupid shit because my wife and I have had high expectations of them from when they were very young.
People have been using vulnerabilities in CMS and forum software (and their plugins) to attack web and mail servers with this ransomware. I know it's hit some schools and small companies.
Doesn't require me to hit shift on my Japanese keyboard, and I like it that way (it's on the key to the right of P)!
We failed to contact people who contributed under these names:
Edgardo E. Contini Salvan
insideoutboy
Ralf Schaefer
If you just want to play NAOMI/Atomiswave games, you're better off using DEmul. It attempts to map PowerVR onto D3D and has a recompiling SH4 core. MAME doesn't come close to that performance. However DEmul uses the MAME CHD format for GDROM images and uses MAME-documents disc/ROM dumps, and the DEmul developers share findings with the MAME team and vice versa. MAME research/technology contributes to non-MAME emulators all the time.
There are issues with encryption/protection blocking progress on some of the later Namco games. There has been some progress behind the scenes, but it hasn't got as far as making anything playable.
There are dedicated Sega Model 2/3 emulators which, once again, are heavily dependent on the documentation from MAME.
As for MAME emulating things you've never heard of, that's one of the big benefits of MAME: ensuring these things aren't lost to future generations. Without MAME's preservation efforts, a lot more of our digital heritage would be lost.
Hey in my day job I'm a CEO of a financial services company, so I get paid per buzzword. Gimme a break!
MAME was never BSD-licensed: it was BSD plus additional restrictions. This made it impossible to use MAME code in a GPL project, or to use [L]GPL code in MAME, without first securing a license exception for the code in question. The vast majority of the code in MAME is now BSD-licensed. However since some code is now [L]GPL-licensed, binary distributions of the entire project fall under the GPL.
MAME doesn't dynamically link to the code under emulation. It's not an issue.
Most of the source is BSD-licesnsed while parts are [L]GPL. The entire emulation/scheduling core is BSD, so if you want to take advantage of that to make your own emulator, go right ahead. However if you're in it for the games, some rather widely used sound cores in MAME are under GPL, so you can't go closing them up.
We're doing plenty to improve the user experience of MAME. We recently integrated the MEWUI user interface code, giving better system selection and configuration from within MAME. MAME now supports UI localisation. We added "autofire" features.
New APIs are supported depending on your host OS including CoreAudio, Xaudio2 and Xinput, for lower latency and support for newer peripherals.
The Direct3D renderer has supported CRT simulation for a while, and the OpenGL renderer supports pluggable filters. But the new cross-platform BGFX renderer will support all that and more with a clean, data-driven approach in an upcoming release. We're also looking to integrate code from GroovyMAME to support people using MAME in arcade-style cabinets and with CRT monitors.
But most importantly, the emulation keeps getting better, leading to more playable games and usable emulated computers. For example recently MAME became the first emulator to properly support the Zaccaria classics Cat and Mouse and Laser Battle (licensed to Midway as Lazarian) with correct colours, full video effects and sound. MAME also recently added the very rare Korean games 96 Flag Rally and Philko Lock On. MAME's support for the historically significant Osborne 1 computer got a lot better last year, including proper memory banking and support for the SCREEN-PAC add-on.
MAME's slot system allows emulation of many peripherals and add-ons that other emulators can't handle. Things like add-on procesor cards for the Apple II, or the IBM PGC.
This is only possible because MAME has a flexible emulation core and a huge library of well-tested cores for emulating CPUs, video hardware, sound chips, and other devices.
Yeah, ten months of tracking people down and wrangling agreements. In the end a small amount of code had to be removed for the rare cases where authors couldn't be contacted. However we think it's effort well spent.
It was previously a license based on the BSD-3-Clause license with additional terms prohibiting commercial use, distribution alongside unauthorised ROM images, and certain kinds of derivative builds. This caused it to fall afoul of OSI and FSF rules. It also tended to hurt potential legitimate users (e.g. rights holders wanting to re-release classics) while doing nothing to stop software pirates and arcade game bootleggers.
This change also makes it easier for other F/L/OSS projects to leverage MAME code, and may help get MAME accepted by F/L/OSS software distribution services (such as main package repositories for major Linux distributions).
Note that MAME is a registered trademark, and the are still restrictions on use of the MAME name, logo and wordmark.
Oh the Aborigines definitely have been known to screw with white people. There's a place in Victoria called Wendouree, which comes from the local Aboriginal for "piss off" (as in an impolite way to tell someone to go away). They asked a local Aboriginal woman what the name of the swamp was, and that's what she said. There are other cases where people have asked the local Aborigines what something should be called and they've given an ironic or less-than-flattering name that's been adopted because the people asking don't know enough about the language to know the joke's on them.
If you time it right, you can duck and punch a magpie when it attempts to dive-bomb you. I've pulled this off a few times, and in each case the magpie in question has remembered me from then on and not tried to attack me again (they still attacked other people). They aren't particularly quiet in a dive, so if you're actually listening you can hear them on the way down. Most people just don't have any situational awareness.
I've got wild emus on the run, too. You can also scare off most Australian snakes, including the infamous eastern brown snake. The Australian animals you really don't want to fuck with are the eastern grey kangaroo, Sydney funnelweb spider, blue-ringed octopus and saltwater stonefish.
It's a bloke who stole a sheep, note a dude. Get it right at least!
You can't spell an imported word the same way it's spelled in the original language if your alphabets don't line up.
Look how well the Arab Spring ended in Libya.
That's not true at all. The huge majority of C/J/K characters in common use are in the Basic Multilingual Plane (BMP) and therefore take two bytes in UTF-16, compared to three bytes in UTF-8. The characters outside the BMP are all infrequently user or included for historical reasons but not in modern usage.
On your second point, Microsoft couldn't change the existing APIs to expect UTF-8, as they need to use the current ANSI codepage for compatibility. They correctly convert the current ANSI codepage to/from the encoding used by the underlying filesystem. If you want to use UTF-8 with these APIs, you can change the ANSI codepage to UTF-8 for your application.