The trouble with all this is they still need people to create the content for iPad users to consume. Web content can be published from Windows/Linux easily enough with just some testing on target devices, but they still need a viable app development platform. If they alienate developers badly enough, no-one will want to use a Mac even to develop for iOS. What do they do then? Release tools for targeting iOS while developing on Windows or Linux? Part of their sales pitch has always been the "whole ecosystem" argument. Could they really kill that and still survive? They'd probably be reduced to receiving poorly ported Android apps.
No, "whore" implies receiving payment, while "slut" (or "manslut" if you want to make it explicit you're talking about a dude) doesn't. Calling someone a "whore" means you think they're compromising their morals in exchange for payment while calling them a "slut" just means you believe they're being immoral/promiscuous without necessarily receiving payment for it. "Prostitute" is a bit different, it isn't really as much of an insult, and it's rarely used when the services in question aren't sexual.
I'd still say "whore" - anyone, male or female, who sells out is a whore in my book. Some of the biggest whores I've had the displeasure of knowing are men.
Kilograms per minute makes no sense, its joules per second, aka watts, and the typical denomination is kilowatts (kW). At least kilowatts are the same everywhere unlike horsepower that are different in different countries.
Check the tires on your car. The diameter is specified in Inches.
This is a really weird one though, the spec like 205/55/R16 means 205mm tread width, 55% aspect (sidewall is 55% of tread width) for 16 in rims. It has both millimetres and inches in it, just to be confusing.
COBOL really isn't such a bad language. It has some nice features, like native variants that map very well onto hierarchical data like XML. The biggest problem with COBOL is shitty COBOL programmers. The language makes it easy for idiots to make code that doesn't crash, so bad programmers can get poorly written code into production. Java has much the same problem, it isn't that Java's a bad language per se, just that it makes life too easy for bad programmers, so you get stuff that uses too much memory, allocates all the time, doesn't perform, and can't be maintained.
Fedora is a lot like CentOS/RHEL, so if you're developing for one of those, it's a good desktop environment to use. It also gives you a preview of what might go into future releases of CentOS/RHEL and gives you a chance to adapt to it or complain about it. (CentOS/RHEL are relatively well-supported by software and hardware vendors and hence popular in environments where stuff has to "just work".)
You've completely sidestepped the question. How do you use MongoDB and its ilk in situations where you need transactional consistency or fine-grained permissions?
No, just because it was a B36 - it would've been more surprising if at least one engine didn't catch fire. The B36 had propellers in pusher configuration on the trailing edges of the wings to reduce turbulence in the leading edges and improve lift. This required the radial engines be flipped front-to-back relative to how they were designed to be installed. This meant that the carburettors had cold air passing over them rather than air that had been warmed by passing over the engine, leading to ice build-up. This caused fuel to somehow come out of the carburettors the wrong way, make its way onto hot parts of the engines, and catch fire. The B36 was infamous for engine fires thanks to this highly questionable piece of engineering.
In the early days of SElinux on Fedora I got alerts all the time, but it's never been a problem on RHEL7. They seem to have fixed the misbehaving tools and problematic policies some time in between. (I still think SElinix is a horrible hack - adding a layer to fake role-based privileges with massive black/whitelists. It all comes back to POSIX permissions being far too couarse-grained for what they're forced to protect.)
So he can run a text editor on a Mac. Wow, I'm really impressed, I couldn't imagine editing text on a machine that isn't a Mac. His whole boast about high-frequency trading was irrelevant.
I call bullshit. I actually do work in market making. None of the serious network cards (SolarFlare, Chelsio, etc.) support OSX. The industry standard is to use Linux with various hacks to reduce context switching. Also, there's no Apple server hardware that you can install in a rack at a colocation or proximity site. You can't do low-latency trading from home, the latency of your connection to the exchange will swamp any advantages you can get by tuning your software; you need to have your stuff running on a box on-site. IBM's Intel-based servers were a popular choice until they offloaded that unit to Lenovo. Dell PowerEdge has risen in popularity since then. Yes, I've edited trading system code on a Mac, but only over SSH to a Linux server.
Not true with Australian carriers - receiving text messages when roaming overseas is free. Only sending text message cost money. (Receiving calls when roaming overseas costs money, but receiving calls within Australia is free.)
I dunno. Tesla seems to be doing pretty well selling to rich people in Shanghai, but electric cars are heavily subsidised there. They're ridiculously expensive in Australia and apparently not very popular.
Yeah, US badly needs an "advertised price is actual total cost" law. We take these kinds of laws for granted in the rest of the world, but I for one only really learned to appreciate it after visiting the US (for IEEE 802.11 working group). Hotels want a "resort fee" on top of the advertised room rates, lots of things have sales tax added on top of the listed price, there's the dreaded tipping game, i.e. underpay workers so we can list artificially low prices, and count on customers paying extra. It really needs to stop, as it creates anything but an open and transparent market.
Because the English requirement comes in when you're providing drivers for hire. The test that was allowed to be done in Urdu was for getting a personal, non-commercial driver's license.
In casual speech in Hong Kong and Taiwan, astronauts are often called "taikong ren" (literally "space people") - this is probably where "taikonaut" comes from, a weird portmanteau of that with "astronaut". But no-one actually uses the word "taikonaut" besides novelists as far as I can tell. English releases from Chinese companies always use "astronaut".
Can you stop posting this bullshit on every article about the Chinese space program? The Chinese for astronaut is "yuhang yuan" (literally "space-navigating personnel") and official English-language media releases from the Chinese space program use the word "astronaut". "Taikonaut" is some bastardised Chinglish abomination invented by English-speaking novelists during the cold war.
HK Octopus predates London Oyster. The name comes from the Chinese name of the card "Baat Daaht Tung", literally "Eight-Arrived Passage" but figuratively "Access All Areas", eight referring to the cardinal and semicardinal points of the compass. Octopus is a catchy English name with a reference to eight in it.
Trouble is, whatever I get with pkg never has the options I need enabled, so I have to go back to using ports, then I get messy dependency issues "X needs Y to be newer than version B, but Z needs Y to be older than version A". With RHEL and similar, the binary packages tend to have kitchen sink enabled by default, which is better suited for my use cases.
Yeah, but it's like "90% of people use 10% of features" - everyone uses a different 10%, so 100% of features are used. Similarly, everyone needs a different combination of languages, so if you're going to use one family of fonts, you want to have massive coverage.
It's for situations where you allow user input, and don't want to limit them to entering text in a single language. Or if you want to display filenames, or the contents of e-mails, or whatever.
The trouble with all this is they still need people to create the content for iPad users to consume. Web content can be published from Windows/Linux easily enough with just some testing on target devices, but they still need a viable app development platform. If they alienate developers badly enough, no-one will want to use a Mac even to develop for iOS. What do they do then? Release tools for targeting iOS while developing on Windows or Linux? Part of their sales pitch has always been the "whole ecosystem" argument. Could they really kill that and still survive? They'd probably be reduced to receiving poorly ported Android apps.
No, "whore" implies receiving payment, while "slut" (or "manslut" if you want to make it explicit you're talking about a dude) doesn't. Calling someone a "whore" means you think they're compromising their morals in exchange for payment while calling them a "slut" just means you believe they're being immoral/promiscuous without necessarily receiving payment for it. "Prostitute" is a bit different, it isn't really as much of an insult, and it's rarely used when the services in question aren't sexual.
I'd still say "whore" - anyone, male or female, who sells out is a whore in my book. Some of the biggest whores I've had the displeasure of knowing are men.
Kilograms per minute makes no sense, its joules per second, aka watts, and the typical denomination is kilowatts (kW). At least kilowatts are the same everywhere unlike horsepower that are different in different countries.
This is a really weird one though, the spec like 205/55/R16 means 205mm tread width, 55% aspect (sidewall is 55% of tread width) for 16 in rims. It has both millimetres and inches in it, just to be confusing.
COBOL really isn't such a bad language. It has some nice features, like native variants that map very well onto hierarchical data like XML. The biggest problem with COBOL is shitty COBOL programmers. The language makes it easy for idiots to make code that doesn't crash, so bad programmers can get poorly written code into production. Java has much the same problem, it isn't that Java's a bad language per se, just that it makes life too easy for bad programmers, so you get stuff that uses too much memory, allocates all the time, doesn't perform, and can't be maintained.
Fedora is a lot like CentOS/RHEL, so if you're developing for one of those, it's a good desktop environment to use. It also gives you a preview of what might go into future releases of CentOS/RHEL and gives you a chance to adapt to it or complain about it. (CentOS/RHEL are relatively well-supported by software and hardware vendors and hence popular in environments where stuff has to "just work".)
Google seems to be completely random. When I travel internationally I get locked out of Google talk until I log in to Gmail to "verify" myself.
Yeah, sixteen registers is actually quite a lot - for a long time you were lucky to get eight general-purpose registers.
You've completely sidestepped the question. How do you use MongoDB and its ilk in situations where you need transactional consistency or fine-grained permissions?
No, just because it was a B36 - it would've been more surprising if at least one engine didn't catch fire. The B36 had propellers in pusher configuration on the trailing edges of the wings to reduce turbulence in the leading edges and improve lift. This required the radial engines be flipped front-to-back relative to how they were designed to be installed. This meant that the carburettors had cold air passing over them rather than air that had been warmed by passing over the engine, leading to ice build-up. This caused fuel to somehow come out of the carburettors the wrong way, make its way onto hot parts of the engines, and catch fire. The B36 was infamous for engine fires thanks to this highly questionable piece of engineering.
In the early days of SElinux on Fedora I got alerts all the time, but it's never been a problem on RHEL7. They seem to have fixed the misbehaving tools and problematic policies some time in between. (I still think SElinix is a horrible hack - adding a layer to fake role-based privileges with massive black/whitelists. It all comes back to POSIX permissions being far too couarse-grained for what they're forced to protect.)
Not any more - they barely last two years together.
So he can run a text editor on a Mac. Wow, I'm really impressed, I couldn't imagine editing text on a machine that isn't a Mac. His whole boast about high-frequency trading was irrelevant.
I call bullshit. I actually do work in market making. None of the serious network cards (SolarFlare, Chelsio, etc.) support OSX. The industry standard is to use Linux with various hacks to reduce context switching. Also, there's no Apple server hardware that you can install in a rack at a colocation or proximity site. You can't do low-latency trading from home, the latency of your connection to the exchange will swamp any advantages you can get by tuning your software; you need to have your stuff running on a box on-site. IBM's Intel-based servers were a popular choice until they offloaded that unit to Lenovo. Dell PowerEdge has risen in popularity since then. Yes, I've edited trading system code on a Mac, but only over SSH to a Linux server.
Not true with Australian carriers - receiving text messages when roaming overseas is free. Only sending text message cost money. (Receiving calls when roaming overseas costs money, but receiving calls within Australia is free.)
I dunno. Tesla seems to be doing pretty well selling to rich people in Shanghai, but electric cars are heavily subsidised there. They're ridiculously expensive in Australia and apparently not very popular.
Yeah, US badly needs an "advertised price is actual total cost" law. We take these kinds of laws for granted in the rest of the world, but I for one only really learned to appreciate it after visiting the US (for IEEE 802.11 working group). Hotels want a "resort fee" on top of the advertised room rates, lots of things have sales tax added on top of the listed price, there's the dreaded tipping game, i.e. underpay workers so we can list artificially low prices, and count on customers paying extra. It really needs to stop, as it creates anything but an open and transparent market.
Because the English requirement comes in when you're providing drivers for hire. The test that was allowed to be done in Urdu was for getting a personal, non-commercial driver's license.
In casual speech in Hong Kong and Taiwan, astronauts are often called "taikong ren" (literally "space people") - this is probably where "taikonaut" comes from, a weird portmanteau of that with "astronaut". But no-one actually uses the word "taikonaut" besides novelists as far as I can tell. English releases from Chinese companies always use "astronaut".
Can you stop posting this bullshit on every article about the Chinese space program? The Chinese for astronaut is "yuhang yuan" (literally "space-navigating personnel") and official English-language media releases from the Chinese space program use the word "astronaut". "Taikonaut" is some bastardised Chinglish abomination invented by English-speaking novelists during the cold war.
HK Octopus predates London Oyster. The name comes from the Chinese name of the card "Baat Daaht Tung", literally "Eight-Arrived Passage" but figuratively "Access All Areas", eight referring to the cardinal and semicardinal points of the compass. Octopus is a catchy English name with a reference to eight in it.
Trouble is, whatever I get with pkg never has the options I need enabled, so I have to go back to using ports, then I get messy dependency issues "X needs Y to be newer than version B, but Z needs Y to be older than version A". With RHEL and similar, the binary packages tend to have kitchen sink enabled by default, which is better suited for my use cases.
Yeah, but it's like "90% of people use 10% of features" - everyone uses a different 10%, so 100% of features are used. Similarly, everyone needs a different combination of languages, so if you're going to use one family of fonts, you want to have massive coverage.
It's for situations where you allow user input, and don't want to limit them to entering text in a single language. Or if you want to display filenames, or the contents of e-mails, or whatever.