OK, an airline isn't a military institution, but still. The 'chain of command' theory of management is hardly unique to Asia.
It depends.
In North America, a lot of pilots are civilians who enter the airlines - because in North America, we have an affordable air system (General Aviation). In Europe, it's expensive, so only the rich can afford to fly GA. In Asia, it's unheard of (China's pretty much only got a handful of GA allowed airports).
As civilian pilots, it's a lot easier to be "flat" and say that everyone is responsible for the safety of the flight above all - the captain is just whoever occupies the left seat, but all is responsible. This is the basis of what we call today "Cockpit Resource Management", aka CRM. In any emergency, a skillful pilot flying (captain, copilot, whoever) will delegate tasks to everyone else (which also includes ATC and everyone who can help). The "Miracle on the Hudson" is a very stunning recent example of this.
But in Asia, this is not the case. In fact, the only way to fly in most countries is to join the military. As such, the national airlines are almost all pulled from ex-military pilots (they do poach a few civilian pilots from other countries). So now, you have established a military hierarchy in the cockpit. So the captain may have been a captain before leaving, and the copilot may be a Lt., and even though the copilot may have more experience in the plane, Captain trumps Lt., and military rank trumps all. The captain is "untouchable" for the flight and what he says is law.
EVEN. IF. HE. IS. WRONG.
It wasn't too long ago that even North American pilots were like this - the left seater trumps all. However, a brilliant set of realizations 50 years ago brought forth CRM and it took a few years to retrain everyone into this new line of thinking. It still did happen now and then, but frequency dropped significantly. These days, it's expected and taught, even to the single engine Cessna pilot - because the "C" can also mean "crew" - if you have passengers, have them keep a look out as well to ensure safety of flight.
That was what iIwas thinking, this would only effect people downloading apk files from third party sites or android users downloading files that they think are free version of a $$$ app. If you stick to the Google play app store then you should be fine for now.
And eliminate useful third party legit sites?
Like say, Amazon App Store? Or Humble Bundle apps?
Sure, you tend to trust these apps as they're from legitimate sites, but are you ABSOLUTELY certain that Amazon and Humble Bundle are checking their files? Google Play only implemented the check when they were told about it, as well. Who knows if they've checked every existing app?
The biggest strength of Android is also its biggest weakness. Once you check the box, Android will not differentiate between Google Play, Amazon App Store, Humble Bundle, Appslib, Random Chinese App Store, etc.
Of course, for the places where there is no Google Play...
I heard the usual "we need to make sure it's a good fit" deal, but my attitude is you either believe me at my skills or don't.
Well, in your case it was obvious. But temp-to-hire is extremely common for the "fit" problem - just because you have the skills doesn't mean you have the right "fit" to the team. There's a lot of interpersonal dynamics at play. Sometimes you may be the expert at what you do, but either the way you act, or the way you react, to everyone else makes it difficult to fully utilize your skills.
Of course, if it was temp-to-hire, they won't use a third party to hire you. They'd put you on contract first.
I don't have to worry about getting patches pushed out that I can't opt out of.
I thought you were talking about Android being better than iOS?
iOS has never required you to update if you didn't want to. This is true way back since 2007 when Jobs introduced it.
Now, iTunes back then prompted you (and still does) that there's an update, but you can click "Cancel" and check "Do not ask me again" and it won't bug you again until there's another update. Which you can decline as well.
In fact, when people were hacking the first iPhone to unlock it, Apple specifically told them to NOT update because it wouldn't work. Of course, when Apple releases a new version, everyone daftly clicked "Update".
At no point has an update ever been forced on someone while they had a working phone. The only time an update is "forced" is if you clicked "Restore" to restore the phone back to factory settings. But if you were happy with what you had and things worked, you did zilch - you have to click update to perform the update.
ISTR that forced updates was more of an Android thing... mostly perpetuated by carriers.
2. A decent on-screen keyboard. Personally I like the sliding-style ones like Swype and Swiftkey and iOS doesn't do that eithre, but one of my biggest annoyances with iOS is that Apple's keyboard does not change the state of letters on-screen when the shift key has been pressed.
Fair comment about the shift key state (though I suppose one reason why is caps gives readability).
Though I wonder if the reason why Android keyboard alternatives are plentiful is because the default Android keyboard is... well, terrible. Mostly because the touchscreens are terrible which gives a horrendous typing experience on Android. Entering passwords I find extremely tedious on Android purely because it takes many attempts to do it properly.
I've tried keyboards like Swype and the like and hated them, and then reverted back to the default because they just got annoying.
On iOS, I can enter my password in the first time every time.
Also even if the bot has 1 failed attempt a day using some discretionary attack, at some point a server should realize that there is no human stupid enough to fail to enter a password properly on a regular basis. I mean once you enter your password in most browser or on the Wii console, you don't even have to type it in again, so 3 failed attempts in any given period of time should lock you out of your account, period.
Except Club Nintendo is NOT tied to anything you already have. It's a separate account and everything.
In fact, it's sort of useless because all it's good for is entering those codes you get with the system and games, which gives you access to prizes. There's very little personal information (you only need an email address to sign up), and there's absolutely no financial information at all - the rewards of Club Nintendo are paid for completely by Nintendo - no shipping, etc.
Heck, even shipping addresses may not be all that special, if they're retrievable. And Nintendo only asks for those when they need it.
I have lots of easy to guess passwords if they allow 15 million attempts on an account.
More like they tried 15M attempts at logging in with various username-password combinations, of which 24,000 of them were successful.
Though, given how little information Nintendo asks, one wonders what the whole point is - I don't think Nintendo even asks for an address until they absolutely need it, so if it was an account created but not really used, there's no information at all. Maybe a few coins, but you can't take them from one account and consolidate them to another...
Of course, Nintendo's entire online thing is a bit iffy to begin with - there's at least three different logins for three different systems, none of which are combined - you have a support account, a Nintendo Network account (Wii U) and a Club Nintendo account.
I suppose a lot of the separation is because well, all the child privacy and protection laws really make it hard to even get something like an email address...
The "real price" of something is exactly determined by each transaction where it is sold. This is the realest price you can get. A MSRP printed on the book is not "real".
Exactly. The MSRP is just a "suggested" price, like what the manufacturer thinks it should cost, but it isn't what you necessarily pay.
And it's just like the stock market in the end - the price is what two people agreed upon to do the trade. The next one may be higher or lower.
If the gap between what buyers are willing to pay and what sellers are willing to sell is too big, it, like a thinly traded stock, will not be very liquid and sales will be low.
Of course, an opportunity comes in where a middleman may be able to talk the seller into going lower (but not as low as the highest buyer), and asking the buyer to go higher (but not as high as what the seller is willing to sell) and thus facilitating a trade. Which causes trades to happen and adds liquidity in the system..
However, I don't mind Sony doing it so much since I can play online there for free. It's also less intrusive than Xbox. Microsoft, on the other hand, charges $60 a year for their services and spams the shit out of the home screen with ads.
PS4 requires PS+ to play online. Sony has already stated this. PS3 will however retain ability to play for free online.
You mean "what's new" which shows the last 3 games you played, and 3 panels above and below that with promotional tiles. You can set it so that the PS3's XMB doesn't go to it after boot.
System Settings> Display [What's New]
Turn it to off. That setting only applies if you have your PS3 connected to the Internet, if you don't it can't show it. Either way you have the option of not automatically showing it, though I find it useful to check for new releases on PSN.
That doesn't remove that ticker that shows up below the login details that scrolls ads. I don't know why, but I find that way more annoying that how Microsoft does it (though that advertising tile comes close - the one that says "advertising" on it). The other stuff seems fairly static and somewhat relevant and interesting.
That said, I think the PS4 will have to include it as well - an advertising API because games will demand it for in-game ads. (Which are here now, no matter what the platform)
Why does it still take fucking drivers, patches, and voodoo to fucking hook up a regular printer and make it function?
Because printer manufacturers want it to be this way. Although there's also a tone of stuff that's not standardized - e.g., computer-printer communication protocol (e.g., how is a printer supposed to announce its capabilities? Remember that the old parallel interface (emulated by USB) consists of 8 data lines and 5 return status lines. It was assumed back then that printer drivers knew everything. It's also why printers have a set of "defaults" that exist in the printer driver and on the printer itself.
I also can't understand why it's so complicated? Isn't PCL supposed to be standard?
PCL is a page description language and a bit of printer control protocol. A page description language describes how to put things on paper, while a printer control protocol describes how the printer should work.
The former describes what's on the page, the latter how the pages are laid out. So something like duplexing, paper type, which tray, color settings, color correction, etc., are printer control while things like what font to use and how to rasterize it are page description.
It's only recently have full two-way communications between computer and printer been available that let us query printers for capabilities and such and actually lead us to one universal driver because printer control is typically a two-way protocol while page description is one-way.
In fact, Apple's been trying to push driverless printing through AirPrint to allow devices to print to printers directly (if they support AirPrint) or through an intermediary (legacy printers).
It looks like it's actually a modified version of CUPS since Linux can support it natively.
What's even more ironic is that inexpensive monitors only have VGA. they would be even less expensive if they had DVI (or HDMI) since they could skip the A/D part. But they want you to buy the more expensive ones for digital inputs.
Except it's generally an all-in-one chip that does it all - A/D, scaling, and panel interfacing.
Also, DVI gets complicated with stuff like HDCP (which requires keys and such) and layout (DVI does require high-speed layout since the bits are coming at it fairly fast). VGA can be fairly tolerant as long as the three lines reach the chip at around the same time.
In _real_ languages like Ada and Verilog you can use the underscore as an optional thousand unit separator.
I wonder why more programming languages don't incorporate a separator that is ignored on number parsing. Like underscores. They're extremely handy (and very useful if you could use it arbitrarily in case you need to break the number into oddly shaped groups). Especially when you're dealing with 64-bit numbers which are starting to get a bit long to type out and missing a digit is a likely possibility.
no. People don't practically care plus they have the memory of a fish.
That, and the fact that encrypting the body of your content doesn't do jack with the metadata. If you encrypt your e-mail, they know when you sent it and to whom. If you access a web page, they know which server you connected to and when.
If violent games don't impact behaviour, then the military can save millions on all of those desensitizing programs (games) that they use. Of course their research probably differs from this study as they, the military aren't trying to show that violent games don't impact "pro" social behaviour. Wouldn't the proper study have been that violent video games impact anti-social behaviour? But then, maybe I missed the frames in GTA where you have to pick up pens from the ground?
That's the problem with violence in videogame studies. There's so many subtle differences between each that none really answer the question. And many are NOT mutually exclusive, either.
This study simply says if you have a well adjusted person, letting them onto video games will not affect friendships and other positive social behaviors.
The military studies say that exposing soldiers to violence desensitizes people to the violence so when they're exposed to it in real life they won't flinch and run away. Or when they've trained their sights on the enemy, they won't hesitate to shoot.
In fact, the two are completely compatible with each other - you can have healthy relationships with people and still be able to pick up and gun and shoot an enemy.
And then there are studies to see if violent video games promote antisocial behavior, another orthogonal question.
One says there's no impact to existing social relationships, the other says it helps desensitize people to the violence (so they don't react as strongly), and the third asks if promotes the use of violence.
Very different questions. No wonder the research is all over the map. And when you mean to measure one, you may be inadvertently measuring something else.
If we are going to teach our kids computer science, shouldn't one of the first subjects be on how they can best train their replacements in other countries when their jobs are outsourced?
Why would a kid want to pursue a career in computer science? Wouldn't it be a better career choice to become a lawyer, marketing insultant, MBA or politician?
No. Stop laughing. I am serious.
Coding is not computer science. Coding is a trade job like plumber, electrician, etc. Comparing coding to computer science or computer engineering is like comparing an electrician to an electrical engineer.
They're separate and quite different occupations. An EE is not an electrician unless they also choose to take up the trade, just like an electrician is not an EE unless they decided to study it. They both have different licensing criterion, as well.
You have the science (the study of the subject), the engineering (the application of the subject), and the trade (the hands on skill).
I'm quite sure, given the "free" license of QT is based on LGPL, that a developer will need a commercial license from Digia to publish an iOS app on the App Store:(
Not really. It's triple licensed - GPLv3, LGPLv2, and commercial.
LGPLv2 means that it's perfectly compatible with App Stores - just you have to release the source to the QT library. The App Store effectively "TiVoizes" the app, but for the most part, there is no license issues between (L)GPLv2 and app stores.
(A|L)GPLv3 is incompatible though.
And you may ask why GPLv3 and LGPLv2 - that's because GPLv2 and GPLv3 are incompatible licenses. If QT remained LGPLv2, you couldn't use it in a GPLv3 project (it's not LGPLv2+).
In fact, there are many GPLv2 apps in the App Store. There were some unfortunate incidents with some GPLv2 apps due to the copyright holders differing interpretations (usually between the spirit vs. the letter), but for the most part, it's compatible.
Of all the app stores, only Microsoft calls out the GPLv3 - most usually just say you either hold copyright to, or have permission from copyright holders to redistribute. And yes, GPLv3 is fundamentally incompatible because of the Anti-TiVoization clause. (It is this clause that also makes it GPLv2 incompatible).
So the further from the station the less effectively accurate the signal is (people don't measure the exact distance they are from the source so they can't know the real time when they get the signal). The time to receive could be a second or two behind the real time for someone receiving on the far side of the earth. So how does touting their supreme accuracy reflect on actuality? Not well. I wonder if it is worth creating a super duper accurate time keeping service that can't be received accurately.
You know, if you wanted, you could compensate for the propagation delays - given your location is fixed relatively to the station, you can just add or subtract the difference.
The famous Heathkit WWV (not WWVB) clock, the GC-1000, actually has dip-switches that sets propagation delays. Though, granted, when it's in "Hi-Spec" mode (meaning the internal oscillator and the receiver are in sync) you only get sub-100ms accuracy. (It tunes its internal oscillator around 3.6MHz until the CPU runs at precisely a multiple of the received signal, given a damn accurate 3.6MHz signal)
Well, they could, but apps provide stuff that websites don't, and sometimes stuff doesn't make it in the spec. Like DRM support in HTML5. Since that seems to be a huge non-starter, it just means if you want DRM, you don't put it on the web, you release it as an app.
Whether or not HTML5 DRM is a good idea or not, or whether app-ificiation of the web is a good thing or not, is a debate for another day.
What's the advantage of integrating it into the TV, other than increasing the TV manufacturer's profit margin?
Exactly. TVs are a commodity - there's very little that differentiates one TV from another, and most consumers will go for the cheapest. There's very little money to be made in TVs (which is why Apple's rumored TV is most peculiar).
It comes about because the processors used in TVs are getting very powerful for what they're used for - these days you're talking about single or dual core ARM processors with 256+MB or more of RAM and a decent amount of ROM. The pace of technological development has pretty much meant that there's no point using a lower-powered processor (like an ARM9), less memory or Flash - it costs just as much anyways. So you just stick in a Cortex A8 or A9 based chip, some RAM that's supported and cheap and NAND flash, and the chip works just fine. Of course, the whole TV part is pretty low-resource since most people don't go fiddling with the menus often, and the scaling is handled by a bog-standard video processor core you'd probably recognize.
So you have a powerful chip with a powerful GPU and you're barely using 10% of it. What do you do? You start adding easy software features - a NIC chip or WiFi chip is fairly cheap. Linux is easy to get on (yes, a lot of these TVs run Linux), and now you have a wide open platform for adding stuff to make the TV "smart". The power's there, so why not use it?
I realize that I probably can't count on my next TV lasting 25 years
Given how cheap TVs are these days, you're paying far less for a TV of equivalent size to your old CRT one than your CRT one ever costed, not counting inflation. Add in inflation and you'll find your CRT TV probably cost many times more. Enough so that over 25 years of buying replacements, you probably would still spend less than on that CRT TV you bought in the late 80s.
So you can only get infected if you side load apks from sketchy sources. Play store users are safe.
How is this any different if you side load apps on iOS devices?
Play store apps are safe NOW since Google was alerted to this in February and had a chance to update their scanners.
But there's still plenty of ways of sideloading apps and who knows if they're sketchy? The problem is Android does not allow sideloading apps from certain alternative stores - it's either Play Store only or everyone.
E.g., if you use Amazon, Humble Bundle, your "Allow non-Play store apps" checkbox is checked and you're vulnerable to sketchy APKs.
And APKs can be installed without your knowing - there exist several lockscreen hacks for many phones that let you get enough access to install a lockscreen bypass app from the Play store. Someone doing that can install their sketchy app and then reset your phone back to normal.
And you can't sideload iOS apps - they must come through the App Store. The only way is to either jailbreak, or install a developer certificate provisioning file that lets you install developer-signed apps. Or enterprise signed apps. Unlike Android, most iOS users don't have these installed, though if you can bypass the lock screen, you can install it. (Though since these certs are signed by Apple, Apple could revoke them if that's their use).
Did you notice that the corps have you fighting with the Union workers to lower your standard of living? They've got you asking: "Why do those guys get to live well?" instead of "Why am I struggling to retire?".
That's the entire point of the anti-union narrative we see non-stop. It's what progressives mean when they say 'a race to the bottom'....
Pay close attention to your views on workers rights and what a reasonable quality of life should be. Then ask yourself who's really shaping them and why...
That's a good point. Think about the IT field and what happens. Like people being "on call" or working more than 40 hour workweeks being common. Or unpaid internships.
Note that in most other fields, such things are unheard of. Hell, the lowly electronics tech managing the stockroom, after 40-odd (40-50 hours depending on location) they get mandatory overtime pay. But if you do a 60 hour workweek? Zilch.
Unpaid interships? Unheard of in most other fields - some are extremely poorly paid (e.g., residents in medical), but most others at least get minimum wage.
On call? Hell, that's often paid as well - it may be poorly paid, but "wearing the pager" means you're still on the clock and billing out hours. Most IT admins do it, willingly or not.
And we in IT think we're superior. All employers have seen is someone who really doesn't have much of a social life, who wants to be with computers 24/7, and who sees much of "normal life" as irrelevant. In the end, they let us be exploited because we let them.
If you don't have anything to report, then don't report. Enough with worthless speculation.
The problem is, Apple is newsworthy. VERY newsworthy. If Tim Cook farts in public, it'll be reported. If he blinks his eyes, they'll report it.
Why? The public pretty much ensures ANY Apple news gets a ton of eyeballs. And thus, ad views and thus, revenue.
Look at the crowds of people Apple attracts. Any Apple story. You get Apple fanbois. Apple haters. Android fanbois. Microsoft fanbois. Windows fanbois. Google fanbois, etc.
Take any Android article - you'll get your usual Android fanbois and haters. And only a tiny smattering of Apple fanbois. Android articles just don't stir up enough people.
Basically, Apple hating has always been a trend since Apple started - it doesn't matter what, it's "always been cool" to hate Apple. And every Apple story attracts these folks who bring up the click count.
Apple can announce NOTHING and still probably get 300+ comments on/. easily. Or more.
Android manages to exist on multiple CPUs. But then it's also one of the most fragmented systems there is, with developers deciding not to develop for it as a result. So that's no advert.
Android supports 3 architectures - ARM, x86, and MIPS.
Of the three, ARM is most prevalent on practically all smartphones out there. x86 is pushed heavily by Intel, but exists on a tiny miniscule amount of phones (one from Motorola for Asia, and a couple of other bit players), and Intel has to bundle in an ARM emulator to at least run a decent number of apps.
MIPS is a curiosity done more so as a platform - MIPS supporting Android for set-top boxes and the like.
But make no mistake, Android is best supported on ARM.
With the traditional CNC machine, the method of material removal works the same irrespective of the stock material, with minor exceptions. A CNC mill can make parts from materials as soft as waxes to as hard as steel with little more than a bit change, and perhaps the addition of cooling lubricant.
A 3d printer, by contrast, is a deposition method which depends to a very large degree on the properties of the feed stock. Even at their best, they'll do no better than a mill.
And 3 hours to make a part is ridiculously long, especially given the failure rate. A trained machinist would instead choose the best tool(s) for the job and turn it out in short order.
Just for perspective: I spent one and a half hours building a molding machine from scratch. Rather than print out the part with a 3d printer, he could have made the molding machine and molds in the same amount of time, with the added advantage that he could make an almost arbitrary number of copies. Sometimes the old ways are just faster.
CNCs are great. However, they're complementary to a 3D printer. 3D printers produce the workpiece by addition, while mills produce the workpiece by subtraction. There's some things you can do better/easier with an additive process, others you can do better/easier with a subtractive one.
Generally for big pieces where you want to remove small bits, a mill is faster. For complex pieces, additive can be easier (as well as able to print "impossible" things a mill cannot easily replicate).
For high-speed mass production, a mill is still preferable to produce the molds that are then used for injection molding. For small one-offs, the whole thing is rather excessive
There are places for both.
Hell, the next-generation manufacturing techniques may make extensive use of both processes.
Writing the code before the spec (i.e., what you are intending to have the code do) means that whatever buggy-ass shit the coder writes as his version 0.1 ends up being the "spec". Which means that when the bugs are fixed (if they are ever fixed, as they're part of the spec now!), it breaks the spec.
The other thing I notice is missing besides the spec is industry co-operation. Without specs, the industry will simply do what's necessary to get the features they want.
No video support? Guess what? Yamaha will introduce it! As will Pioneer, Onkyo, Marantz, etc. Oh, did I mention they were all incompatible with each other because they all went and did their own thing?
Without a clear roadmap of when support will be added and clear industry contacts, "take the code and use it" doesn't get very far because each company wants to add their own "special sauce" to the mix.
And yes, this work is boring and un-sexy and is akin to documentation, UX design and other skills that are often way undervalued amongst FLOSS programmers (I didn't say software engineers on purpose). Valuing code over everything else does not get acceptance.
So to even get started, someone needs to be an industry liason and seek input - what do THEY want out of it? And when can they expect an implementation. And nothing wishy-washy - product cycles are short, lead times long and deadlines far closer than you think (e.g., if you want to make Holiday 2013, you must be ready with hardware and software now).
Given it came out now, the earliest product will be ready is Holiday 2014. Maybe summer 2014 if everyone gets their act together and figures out how to talk to industry and how to handle their demands.
And don't forget qualification testing. Some no-name Chinese brand may add it as a feature point if it compiles nicely into the code (if it doesn't, they'll chop stuff out until it does). But without a way to enforce quality standards and a test suite, these crap implementations may simply result in everyone going "Oh, it supports MagicCrap" because everyone sees stuttering, choppy playback as the result, or it not working at all because some vital bit is missing. (What, you expect testing?)
Just because it's BSD doesn't mean it's accepted. It just means the license is acceptable. Industry knows what their customers (consumers to high end A/V professionals) want, and if there's demand, they'll provide it. And to do that they need to know how they can ask for improvements, help, assistance, qualification tests, etc.
Slashdot Mirror
It depends.
In North America, a lot of pilots are civilians who enter the airlines - because in North America, we have an affordable air system (General Aviation). In Europe, it's expensive, so only the rich can afford to fly GA. In Asia, it's unheard of (China's pretty much only got a handful of GA allowed airports).
As civilian pilots, it's a lot easier to be "flat" and say that everyone is responsible for the safety of the flight above all - the captain is just whoever occupies the left seat, but all is responsible. This is the basis of what we call today "Cockpit Resource Management", aka CRM. In any emergency, a skillful pilot flying (captain, copilot, whoever) will delegate tasks to everyone else (which also includes ATC and everyone who can help). The "Miracle on the Hudson" is a very stunning recent example of this.
But in Asia, this is not the case. In fact, the only way to fly in most countries is to join the military. As such, the national airlines are almost all pulled from ex-military pilots (they do poach a few civilian pilots from other countries). So now, you have established a military hierarchy in the cockpit. So the captain may have been a captain before leaving, and the copilot may be a Lt., and even though the copilot may have more experience in the plane, Captain trumps Lt., and military rank trumps all. The captain is "untouchable" for the flight and what he says is law.
EVEN. IF. HE. IS. WRONG.
It wasn't too long ago that even North American pilots were like this - the left seater trumps all. However, a brilliant set of realizations 50 years ago brought forth CRM and it took a few years to retrain everyone into this new line of thinking. It still did happen now and then, but frequency dropped significantly. These days, it's expected and taught, even to the single engine Cessna pilot - because the "C" can also mean "crew" - if you have passengers, have them keep a look out as well to ensure safety of flight.
And eliminate useful third party legit sites?
Like say, Amazon App Store? Or Humble Bundle apps?
Sure, you tend to trust these apps as they're from legitimate sites, but are you ABSOLUTELY certain that Amazon and Humble Bundle are checking their files? Google Play only implemented the check when they were told about it, as well. Who knows if they've checked every existing app?
The biggest strength of Android is also its biggest weakness. Once you check the box, Android will not differentiate between Google Play, Amazon App Store, Humble Bundle, Appslib, Random Chinese App Store, etc.
Of course, for the places where there is no Google Play...
Well, in your case it was obvious. But temp-to-hire is extremely common for the "fit" problem - just because you have the skills doesn't mean you have the right "fit" to the team. There's a lot of interpersonal dynamics at play. Sometimes you may be the expert at what you do, but either the way you act, or the way you react, to everyone else makes it difficult to fully utilize your skills.
Of course, if it was temp-to-hire, they won't use a third party to hire you. They'd put you on contract first.
I thought you were talking about Android being better than iOS?
iOS has never required you to update if you didn't want to. This is true way back since 2007 when Jobs introduced it.
Now, iTunes back then prompted you (and still does) that there's an update, but you can click "Cancel" and check "Do not ask me again" and it won't bug you again until there's another update. Which you can decline as well.
In fact, when people were hacking the first iPhone to unlock it, Apple specifically told them to NOT update because it wouldn't work. Of course, when Apple releases a new version, everyone daftly clicked "Update".
At no point has an update ever been forced on someone while they had a working phone. The only time an update is "forced" is if you clicked "Restore" to restore the phone back to factory settings. But if you were happy with what you had and things worked, you did zilch - you have to click update to perform the update.
ISTR that forced updates was more of an Android thing... mostly perpetuated by carriers.
Fair comment about the shift key state (though I suppose one reason why is caps gives readability).
Though I wonder if the reason why Android keyboard alternatives are plentiful is because the default Android keyboard is... well, terrible. Mostly because the touchscreens are terrible which gives a horrendous typing experience on Android. Entering passwords I find extremely tedious on Android purely because it takes many attempts to do it properly.
I've tried keyboards like Swype and the like and hated them, and then reverted back to the default because they just got annoying.
On iOS, I can enter my password in the first time every time.
Except Club Nintendo is NOT tied to anything you already have. It's a separate account and everything.
In fact, it's sort of useless because all it's good for is entering those codes you get with the system and games, which gives you access to prizes. There's very little personal information (you only need an email address to sign up), and there's absolutely no financial information at all - the rewards of Club Nintendo are paid for completely by Nintendo - no shipping, etc.
Heck, even shipping addresses may not be all that special, if they're retrievable. And Nintendo only asks for those when they need it.
More like they tried 15M attempts at logging in with various username-password combinations, of which 24,000 of them were successful.
Though, given how little information Nintendo asks, one wonders what the whole point is - I don't think Nintendo even asks for an address until they absolutely need it, so if it was an account created but not really used, there's no information at all. Maybe a few coins, but you can't take them from one account and consolidate them to another...
Of course, Nintendo's entire online thing is a bit iffy to begin with - there's at least three different logins for three different systems, none of which are combined - you have a support account, a Nintendo Network account (Wii U) and a Club Nintendo account.
I suppose a lot of the separation is because well, all the child privacy and protection laws really make it hard to even get something like an email address...
False. Computrace (LoJack) actually survives OS reinstallation, provided the new OS is compatible (i.e., WIndows).
It does it by relying on a BIOS component that checks for it to be installed and if not, patches itself back in on the hard drive.
Of course, it lacks a lot of authentication and can easily be hijacked if you modifiy the BIOS...
Exactly. The MSRP is just a "suggested" price, like what the manufacturer thinks it should cost, but it isn't what you necessarily pay.
And it's just like the stock market in the end - the price is what two people agreed upon to do the trade. The next one may be higher or lower.
If the gap between what buyers are willing to pay and what sellers are willing to sell is too big, it, like a thinly traded stock, will not be very liquid and sales will be low.
Of course, an opportunity comes in where a middleman may be able to talk the seller into going lower (but not as low as the highest buyer), and asking the buyer to go higher (but not as high as what the seller is willing to sell) and thus facilitating a trade. Which causes trades to happen and adds liquidity in the system..
PS4 requires PS+ to play online. Sony has already stated this. PS3 will however retain ability to play for free online.
That doesn't remove that ticker that shows up below the login details that scrolls ads. I don't know why, but I find that way more annoying that how Microsoft does it (though that advertising tile comes close - the one that says "advertising" on it). The other stuff seems fairly static and somewhat relevant and interesting.
That said, I think the PS4 will have to include it as well - an advertising API because games will demand it for in-game ads. (Which are here now, no matter what the platform)
Because printer manufacturers want it to be this way. Although there's also a tone of stuff that's not standardized - e.g., computer-printer communication protocol (e.g., how is a printer supposed to announce its capabilities? Remember that the old parallel interface (emulated by USB) consists of 8 data lines and 5 return status lines. It was assumed back then that printer drivers knew everything. It's also why printers have a set of "defaults" that exist in the printer driver and on the printer itself.
PCL is a page description language and a bit of printer control protocol. A page description language describes how to put things on paper, while a printer control protocol describes how the printer should work.
The former describes what's on the page, the latter how the pages are laid out. So something like duplexing, paper type, which tray, color settings, color correction, etc., are printer control while things like what font to use and how to rasterize it are page description.
It's only recently have full two-way communications between computer and printer been available that let us query printers for capabilities and such and actually lead us to one universal driver because printer control is typically a two-way protocol while page description is one-way.
In fact, Apple's been trying to push driverless printing through AirPrint to allow devices to print to printers directly (if they support AirPrint) or through an intermediary (legacy printers).
It looks like it's actually a modified version of CUPS since Linux can support it natively.
Except it's generally an all-in-one chip that does it all - A/D, scaling, and panel interfacing.
Also, DVI gets complicated with stuff like HDCP (which requires keys and such) and layout (DVI does require high-speed layout since the bits are coming at it fairly fast). VGA can be fairly tolerant as long as the three lines reach the chip at around the same time.
I wonder why more programming languages don't incorporate a separator that is ignored on number parsing. Like underscores. They're extremely handy (and very useful if you could use it arbitrarily in case you need to break the number into oddly shaped groups). Especially when you're dealing with 64-bit numbers which are starting to get a bit long to type out and missing a digit is a likely possibility.
That, and the fact that encrypting the body of your content doesn't do jack with the metadata. If you encrypt your e-mail, they know when you sent it and to whom. If you access a web page, they know which server you connected to and when.
That's the problem with violence in videogame studies. There's so many subtle differences between each that none really answer the question. And many are NOT mutually exclusive, either.
This study simply says if you have a well adjusted person, letting them onto video games will not affect friendships and other positive social behaviors.
The military studies say that exposing soldiers to violence desensitizes people to the violence so when they're exposed to it in real life they won't flinch and run away. Or when they've trained their sights on the enemy, they won't hesitate to shoot.
In fact, the two are completely compatible with each other - you can have healthy relationships with people and still be able to pick up and gun and shoot an enemy.
And then there are studies to see if violent video games promote antisocial behavior, another orthogonal question.
One says there's no impact to existing social relationships, the other says it helps desensitize people to the violence (so they don't react as strongly), and the third asks if promotes the use of violence.
Very different questions. No wonder the research is all over the map. And when you mean to measure one, you may be inadvertently measuring something else.
Coding is not computer science. Coding is a trade job like plumber, electrician, etc. Comparing coding to computer science or computer engineering is like comparing an electrician to an electrical engineer.
They're separate and quite different occupations. An EE is not an electrician unless they also choose to take up the trade, just like an electrician is not an EE unless they decided to study it. They both have different licensing criterion, as well.
You have the science (the study of the subject), the engineering (the application of the subject), and the trade (the hands on skill).
Not really. It's triple licensed - GPLv3, LGPLv2, and commercial.
LGPLv2 means that it's perfectly compatible with App Stores - just you have to release the source to the QT library. The App Store effectively "TiVoizes" the app, but for the most part, there is no license issues between (L)GPLv2 and app stores.
(A|L)GPLv3 is incompatible though.
And you may ask why GPLv3 and LGPLv2 - that's because GPLv2 and GPLv3 are incompatible licenses. If QT remained LGPLv2, you couldn't use it in a GPLv3 project (it's not LGPLv2+).
In fact, there are many GPLv2 apps in the App Store. There were some unfortunate incidents with some GPLv2 apps due to the copyright holders differing interpretations (usually between the spirit vs. the letter), but for the most part, it's compatible.
Of all the app stores, only Microsoft calls out the GPLv3 - most usually just say you either hold copyright to, or have permission from copyright holders to redistribute. And yes, GPLv3 is fundamentally incompatible because of the Anti-TiVoization clause. (It is this clause that also makes it GPLv2 incompatible).
You know, if you wanted, you could compensate for the propagation delays - given your location is fixed relatively to the station, you can just add or subtract the difference.
The famous Heathkit WWV (not WWVB) clock, the GC-1000, actually has dip-switches that sets propagation delays. Though, granted, when it's in "Hi-Spec" mode (meaning the internal oscillator and the receiver are in sync) you only get sub-100ms accuracy. (It tunes its internal oscillator around 3.6MHz until the CPU runs at precisely a multiple of the received signal, given a damn accurate 3.6MHz signal)
Exactly. TVs are a commodity - there's very little that differentiates one TV from another, and most consumers will go for the cheapest. There's very little money to be made in TVs (which is why Apple's rumored TV is most peculiar).
It comes about because the processors used in TVs are getting very powerful for what they're used for - these days you're talking about single or dual core ARM processors with 256+MB or more of RAM and a decent amount of ROM. The pace of technological development has pretty much meant that there's no point using a lower-powered processor (like an ARM9), less memory or Flash - it costs just as much anyways. So you just stick in a Cortex A8 or A9 based chip, some RAM that's supported and cheap and NAND flash, and the chip works just fine. Of course, the whole TV part is pretty low-resource since most people don't go fiddling with the menus often, and the scaling is handled by a bog-standard video processor core you'd probably recognize.
So you have a powerful chip with a powerful GPU and you're barely using 10% of it. What do you do? You start adding easy software features - a NIC chip or WiFi chip is fairly cheap. Linux is easy to get on (yes, a lot of these TVs run Linux), and now you have a wide open platform for adding stuff to make the TV "smart". The power's there, so why not use it?
Given how cheap TVs are these days, you're paying far less for a TV of equivalent size to your old CRT one than your CRT one ever costed, not counting inflation. Add in inflation and you'll find your CRT TV probably cost many times more. Enough so that over 25 years of buying replacements, you probably would still spend less than on that CRT TV you bought in the late 80s.
Play store apps are safe NOW since Google was alerted to this in February and had a chance to update their scanners.
But there's still plenty of ways of sideloading apps and who knows if they're sketchy? The problem is Android does not allow sideloading apps from certain alternative stores - it's either Play Store only or everyone.
E.g., if you use Amazon, Humble Bundle, your "Allow non-Play store apps" checkbox is checked and you're vulnerable to sketchy APKs.
And APKs can be installed without your knowing - there exist several lockscreen hacks for many phones that let you get enough access to install a lockscreen bypass app from the Play store. Someone doing that can install their sketchy app and then reset your phone back to normal.
And you can't sideload iOS apps - they must come through the App Store. The only way is to either jailbreak, or install a developer certificate provisioning file that lets you install developer-signed apps. Or enterprise signed apps. Unlike Android, most iOS users don't have these installed, though if you can bypass the lock screen, you can install it. (Though since these certs are signed by Apple, Apple could revoke them if that's their use).
That's a good point. Think about the IT field and what happens. Like people being "on call" or working more than 40 hour workweeks being common. Or unpaid internships.
Note that in most other fields, such things are unheard of. Hell, the lowly electronics tech managing the stockroom, after 40-odd (40-50 hours depending on location) they get mandatory overtime pay. But if you do a 60 hour workweek? Zilch.
Unpaid interships? Unheard of in most other fields - some are extremely poorly paid (e.g., residents in medical), but most others at least get minimum wage.
On call? Hell, that's often paid as well - it may be poorly paid, but "wearing the pager" means you're still on the clock and billing out hours. Most IT admins do it, willingly or not.
And we in IT think we're superior. All employers have seen is someone who really doesn't have much of a social life, who wants to be with computers 24/7, and who sees much of "normal life" as irrelevant. In the end, they let us be exploited because we let them.
The problem is, Apple is newsworthy. VERY newsworthy. If Tim Cook farts in public, it'll be reported. If he blinks his eyes, they'll report it.
Why? The public pretty much ensures ANY Apple news gets a ton of eyeballs. And thus, ad views and thus, revenue.
Look at the crowds of people Apple attracts. Any Apple story. You get Apple fanbois. Apple haters. Android fanbois. Microsoft fanbois. Windows fanbois. Google fanbois, etc.
Take any Android article - you'll get your usual Android fanbois and haters. And only a tiny smattering of Apple fanbois. Android articles just don't stir up enough people.
Basically, Apple hating has always been a trend since Apple started - it doesn't matter what, it's "always been cool" to hate Apple. And every Apple story attracts these folks who bring up the click count.
Apple can announce NOTHING and still probably get 300+ comments on /. easily. Or more.
Android supports 3 architectures - ARM, x86, and MIPS.
Of the three, ARM is most prevalent on practically all smartphones out there. x86 is pushed heavily by Intel, but exists on a tiny miniscule amount of phones (one from Motorola for Asia, and a couple of other bit players), and Intel has to bundle in an ARM emulator to at least run a decent number of apps.
MIPS is a curiosity done more so as a platform - MIPS supporting Android for set-top boxes and the like.
But make no mistake, Android is best supported on ARM.
CNCs are great. However, they're complementary to a 3D printer. 3D printers produce the workpiece by addition, while mills produce the workpiece by subtraction. There's some things you can do better/easier with an additive process, others you can do better/easier with a subtractive one.
Generally for big pieces where you want to remove small bits, a mill is faster. For complex pieces, additive can be easier (as well as able to print "impossible" things a mill cannot easily replicate).
For high-speed mass production, a mill is still preferable to produce the molds that are then used for injection molding. For small one-offs, the whole thing is rather excessive
There are places for both.
Hell, the next-generation manufacturing techniques may make extensive use of both processes.
The other thing I notice is missing besides the spec is industry co-operation. Without specs, the industry will simply do what's necessary to get the features they want.
No video support? Guess what? Yamaha will introduce it! As will Pioneer, Onkyo, Marantz, etc. Oh, did I mention they were all incompatible with each other because they all went and did their own thing?
Without a clear roadmap of when support will be added and clear industry contacts, "take the code and use it" doesn't get very far because each company wants to add their own "special sauce" to the mix.
And yes, this work is boring and un-sexy and is akin to documentation, UX design and other skills that are often way undervalued amongst FLOSS programmers (I didn't say software engineers on purpose). Valuing code over everything else does not get acceptance.
So to even get started, someone needs to be an industry liason and seek input - what do THEY want out of it? And when can they expect an implementation. And nothing wishy-washy - product cycles are short, lead times long and deadlines far closer than you think (e.g., if you want to make Holiday 2013, you must be ready with hardware and software now).
Given it came out now, the earliest product will be ready is Holiday 2014. Maybe summer 2014 if everyone gets their act together and figures out how to talk to industry and how to handle their demands.
And don't forget qualification testing. Some no-name Chinese brand may add it as a feature point if it compiles nicely into the code (if it doesn't, they'll chop stuff out until it does). But without a way to enforce quality standards and a test suite, these crap implementations may simply result in everyone going "Oh, it supports MagicCrap" because everyone sees stuttering, choppy playback as the result, or it not working at all because some vital bit is missing. (What, you expect testing?)
Just because it's BSD doesn't mean it's accepted. It just means the license is acceptable. Industry knows what their customers (consumers to high end A/V professionals) want, and if there's demand, they'll provide it. And to do that they need to know how they can ask for improvements, help, assistance, qualification tests, etc.