What I really don't understand is why so many people have dogs, and not just any dogs, but big dogs. There's no way you can get away when you have one of those things.
As a person with (some) big dogs, I feel I have it easier than people with children...
Even if they were studied, it's worth keeping in mind that the current Canadian government appears (according to many Canadian scientists) to have a habit of suppressing or even altering scientific research that doesn't support its political goals. And it's election season; take any Canadian government PR with an extra large dose of sodium chloride.
And sadly, unless you're buying the device well into its shelf life, you don't know about major flaws until they're discovered.
I bought it well into the shelf life in spite of the known problems. The pros at the time outweighed the cons. But I didn't really consider the longevity of the community support. There are still people working on it, but not part of CM, and there are far fewer such projects than many other devices.
CM is obviously looking for a business model for monetizing their work.
I kind of thought that myself, until they screwed OnePlus with the Micromax deal. I understand the details are a bit more complicated, but alienating your most enthusiastic and visible client like that doesn't exactly strike me as something a company trying to make money would do.
selling out to Microsoft is a pretty lousy choice
If the goal is to ensure that many (most?) of the current "free" CM users don't turn into "paying" users through Cyanogen OS phone purchases, they certainly hit it out of the park with that decision.
So much for expecting to have a longer phone support through CM
It's hit or miss...
CM is pretty up-front about this; support for specific devices typically depends on a volunteer/champion who's willing to do the grunt work of testing and patching for that device. If that individual or team loses interest (or their devices croak or they just can't figure out how to work around critical bugs) and nobody is willing to step up and take over maintenance, the device can't be supported.
Generally speaking, it seems that robust and popular devices get longer support, and devices with major flaws drop support sooner. That's happened to one of mine (the tf700t is a nice device with infuriatingly shitty I/O performance), while my other (purchased a year prior) still gets decent support with CM12.1.
It's still better software support than what the manufacturer gives you.
It would be far cheaper to manufacture the stethoscopes in China.
Then you have a whole bunch of cheap stethoscopes in China. Great place for them.
The problem they're trying to solve isn't the lack of stethoscopes, it's the lack of simple but important medical supplies like stethoscopes in times and places where you can't just order a palette from Aliexpress with overnight shipping.
I'll grant that leaves them with the chicken and egg problem of getting a 3D printer, a supply of plastic and other parts, and the necessary object files into that same location... It's possible to repstrap a printer, if necessary, but there's still challenges.
Just sayin', regardless of reality or fantasy, when your policy suggestion is basically the exact thing the devil does during the "end times," you might have a tough sell there.
The obvious question being, how relevant is this particular bit of mythology to Finnish society? I don't have any strong insight into this... I understand that they're predominantly Christian, but I'd also expect that nations with a heavy socialist bent wouldn't be quite as ready to call their government an agent of the devil. How does the typical Finn interpret this particular passage of the bible?
It would only have to be available in French to be sold in Quebec or used by some governments (who are unlikely to even allow Android on their networks, making the question of Cortana on Android in French entirely irrelevant).
And even then, I don't believe most online stores enforce the French-for-Quebec restriction.
He sits down in your living room and shows you and your wife the list of hundreds of copyright infringements you have committed, and asks you wouldn't it be a shame if your wife and kids were put out on the street because you were languishing in jail for longer than someone who committed manslaughter
One of the problems with threatening someone with a certain sentence longer than they'd get for manslaughter is that they might do the math and decide it's less risky to just kill you and dispose of the evidence...
they totally messed up on the whole android build/deploy/update system.
From what I understand, a significant chunk of the problem with mobile device "longevity" is that closed source drivers for the SoC's used in phones are typically provided by chipset vendors, and if the driver model used by the O/S ever changes then the SoC vendor needs to provide a newer set of drivers. Which they aren't going to do when they are no longer selling the chipsets.
Still, I have no problems with the efforts to make programming easier. Anything that helps will not only make it easier for novices, but will also aid professional programmers.
Sometimes that's true. Sometimes, the things that make it easier for novices get in the way of the pros and often necessitate workarounds.
Granted, sometimes the pros are just being stuck-in-the-mud reactive twits. You gotta take it case by case.
I'd use Watson as a great example of how deep learning systems won't make coding go away too soon. From the Wikipedia entry:
Watson uses IBM's DeepQA software and the Apache UIMA (Unstructured Information Management Architecture) framework. The system was written in various languages, including Java, C++, and Prolog, and runs on the SUSE Linux Enterprise Server 11 operating system using Apache Hadoop framework to provide distributed computing.
Any guesses as to how many lines of code and development hours are behind that stack? How about a guess as to how long it'll be before Watson is able to make useful contributions to a significant part of that software stack? Is it worth thinking about the hardware stack, or the effort put into curating the database?
Watson is, basically, a sophisticated search engine built upon a massive mountain of human effort.
Experience says that the more complex systems become and the more ubiquitously they're deployed, the more you need people who can build them, expand them, bend them and glue them into place. It doesn't seem to follow a curve like agriculture where productivity can continuously increase while labour contracts. It probably will turn that way, eventually, but I don't expect to be around for it.
Coding is likely to be obsolete in a few years - replaced by deep learning systems as those systems increase in capability, and so the last thing we should do is steer kids away from math and toward coding.
One of my computer science profs said that, pretty much word for word, when I suggested I wasn't interested in grad school. Except at the time "CASE" was the big buzzword.
From the rate of progress I've seen with these "make coding obsolete" initiatives, I expect I'll be well retired before that happens. And, even if they get something working, there's still going to be a job market for coders in gluing all these deep learning systems together.
But the US population isn't their hiring pool, people qualified to do the job are their hiring pool.
We're specifically talking about people interviewing at Google, not the general US population. These are people who are, by definition, in their hiring pool.
I can entirely understand that the demographics of Google employees won't match that of the more general population. But if the demographics going into the interview process consistently and noticeably fail to match the demographics actually being hired, then it looks like there might be a problem. Which exact problem, I don't know. Poor pre-interview screening? There's many other potential reasons than rampant age discrimination, but I think there's also enough merit to the complaint for someone to start digging.
We don't really know what the facts of the case are, but I wonder what it is about people that lead them to believe they're being discriminated against based on a particular factor, like age, race, etc?
Haven't read the article, but repeated "good" interviews from the same company could be taken as meaning that either HR records suck, or the company is going out of their way to not accurately tracking the reason they didn't hire her in those records.
Now, happening to a relatively small number of people wouldn't be a huge deal. But one might get a bit suspicious if this consistently happens to people in an under-represent demographic within the company.
I don't know the facts, either, but it strikes me as something worth digging into a bit more.
Unattended instrumentation in the Canadian arctic... to put the bandwidth constraints/costs in context, we're in the process of upgrading the gear to use TCP/IP over 2400 baud. It's tight.
Slashdot Mirror
As a person with (some) big dogs, I feel I have it easier than people with children...
I'm surprised she still managed to get $13,000 worth of love from the tech industry.
Even if they were studied, it's worth keeping in mind that the current Canadian government appears (according to many Canadian scientists) to have a habit of suppressing or even altering scientific research that doesn't support its political goals. And it's election season; take any Canadian government PR with an extra large dose of sodium chloride.
Well, that and the whole "a bullet through Googleâ(TM)s head" nonsense.
Android is a big pool, but people still don't want to swim close to the guy who's pissing in it...
I bought it well into the shelf life in spite of the known problems. The pros at the time outweighed the cons. But I didn't really consider the longevity of the community support. There are still people working on it, but not part of CM, and there are far fewer such projects than many other devices.
I kind of thought that myself, until they screwed OnePlus with the Micromax deal. I understand the details are a bit more complicated, but alienating your most enthusiastic and visible client like that doesn't exactly strike me as something a company trying to make money would do.
If the goal is to ensure that many (most?) of the current "free" CM users don't turn into "paying" users through Cyanogen OS phone purchases, they certainly hit it out of the park with that decision.
It's hit or miss...
CM is pretty up-front about this; support for specific devices typically depends on a volunteer/champion who's willing to do the grunt work of testing and patching for that device. If that individual or team loses interest (or their devices croak or they just can't figure out how to work around critical bugs) and nobody is willing to step up and take over maintenance, the device can't be supported.
Generally speaking, it seems that robust and popular devices get longer support, and devices with major flaws drop support sooner. That's happened to one of mine (the tf700t is a nice device with infuriatingly shitty I/O performance), while my other (purchased a year prior) still gets decent support with CM12.1.
It's still better software support than what the manufacturer gives you.
The Martians might consider us sending Trump to Mars as an act of war.
I only say "might" because while most humans would, we don't entirely understand the alien mind.
Then you have a whole bunch of cheap stethoscopes in China. Great place for them.
The problem they're trying to solve isn't the lack of stethoscopes, it's the lack of simple but important medical supplies like stethoscopes in times and places where you can't just order a palette from Aliexpress with overnight shipping.
I'll grant that leaves them with the chicken and egg problem of getting a 3D printer, a supply of plastic and other parts, and the necessary object files into that same location... It's possible to repstrap a printer, if necessary, but there's still challenges.
The obvious question being, how relevant is this particular bit of mythology to Finnish society? I don't have any strong insight into this... I understand that they're predominantly Christian, but I'd also expect that nations with a heavy socialist bent wouldn't be quite as ready to call their government an agent of the devil. How does the typical Finn interpret this particular passage of the bible?
This was my standard shell/Unix tool environment. At least until I upgraded to L...
It would only have to be available in French to be sold in Quebec or used by some governments (who are unlikely to even allow Android on their networks, making the question of Cortana on Android in French entirely irrelevant).
And even then, I don't believe most online stores enforce the French-for-Quebec restriction.
Yes, but are you willing to take the risk of hackers changing the radio to a country and western station?
One of the problems with threatening someone with a certain sentence longer than they'd get for manslaughter is that they might do the math and decide it's less risky to just kill you and dispose of the evidence...
From what I understand, a significant chunk of the problem with mobile device "longevity" is that closed source drivers for the SoC's used in phones are typically provided by chipset vendors, and if the driver model used by the O/S ever changes then the SoC vendor needs to provide a newer set of drivers. Which they aren't going to do when they are no longer selling the chipsets.
Sometimes that's true. Sometimes, the things that make it easier for novices get in the way of the pros and often necessitate workarounds.
Granted, sometimes the pros are just being stuck-in-the-mud reactive twits. You gotta take it case by case.
The real money is in short usernames... I hope.
I'd use Watson as a great example of how deep learning systems won't make coding go away too soon. From the Wikipedia entry:
Any guesses as to how many lines of code and development hours are behind that stack? How about a guess as to how long it'll be before Watson is able to make useful contributions to a significant part of that software stack? Is it worth thinking about the hardware stack, or the effort put into curating the database?
Watson is, basically, a sophisticated search engine built upon a massive mountain of human effort.
Experience says that the more complex systems become and the more ubiquitously they're deployed, the more you need people who can build them, expand them, bend them and glue them into place. It doesn't seem to follow a curve like agriculture where productivity can continuously increase while labour contracts. It probably will turn that way, eventually, but I don't expect to be around for it.
One of my computer science profs said that, pretty much word for word, when I suggested I wasn't interested in grad school. Except at the time "CASE" was the big buzzword.
From the rate of progress I've seen with these "make coding obsolete" initiatives, I expect I'll be well retired before that happens. And, even if they get something working, there's still going to be a job market for coders in gluing all these deep learning systems together.
In her particular case, yes. That's why I said:
We're specifically talking about people interviewing at Google, not the general US population. These are people who are, by definition, in their hiring pool.
I can entirely understand that the demographics of Google employees won't match that of the more general population. But if the demographics going into the interview process consistently and noticeably fail to match the demographics actually being hired, then it looks like there might be a problem. Which exact problem, I don't know. Poor pre-interview screening? There's many other potential reasons than rampant age discrimination, but I think there's also enough merit to the complaint for someone to start digging.
Haven't read the article, but repeated "good" interviews from the same company could be taken as meaning that either HR records suck, or the company is going out of their way to not accurately tracking the reason they didn't hire her in those records.
Now, happening to a relatively small number of people wouldn't be a huge deal. But one might get a bit suspicious if this consistently happens to people in an under-represent demographic within the company.
I don't know the facts, either, but it strikes me as something worth digging into a bit more.
Unattended instrumentation in the Canadian arctic... to put the bandwidth constraints/costs in context, we're in the process of upgrading the gear to use TCP/IP over 2400 baud. It's tight.
We still have operational gear running at 110 baud.
Granted, it's being emulated over 2400 baud satellite networks, but the physical hardware can't go any faster than 110.
Well, in his defence, streaming quality on dial-up is rather poor. Maybe even worse than AM radio.