I have one of those "Optimum" laptops with combined Intel graphics and discrete Nvidia graphics. Unfortunately Dell implemented it with all the external monitor ports hooked up to the Nvidia chip, which means that if I want to drive external monitors I need to fire up the power-hungry Nvidia chip even though the integrated graphics could do it perfectly well.
Also, the Nvidia chip supposedly supports three external monitors, but it actually doesn't work, and the added performance over the integrated graphics is pointless if you're not gaming.
Finally, throw in the fact that the Intel drivers are open source and actively supported by Intel.
The desktop/laptop processors are easy...single socket, relatively small number of cores.
It takes effort to add the bits to allow the processors to scale to 10/12 cores, huge caches, and multiple sockets. They also use more complicated memory modules, different motherboards, etc.
Also, large companies are able to get their hands on limited quantities of these cpus well before they're generally available for large-scale ordering to allow their engineers to build products on them and test how they'll behave.
According to the WHO, malaria (spread by mosquitoes) killed between 473000 and 789000 people in 2012. Add in a few more similar diseases and it could plausibly be "millions of people".
I've been working for over a decade on the server side of things. Linux kernel customization, device drivers, high-availability, fault-tolerance, etc. Mostly in C, more than a little bit of assembly, some shell scripting.
There's a lot of that stuff still being done, and it's a pretty good living since there aren't all that many people who are comfortable in that environment.
If you need to take passengers somewhere, rent a car for the day.
I used to live with no car, and I could rent a small hatchback for $15/day on the weekends, with unlimited distance allowed.
Now I've got kids and I'm in a city with worse public transit, so it'd be a lot harder to live without a car. But it's not a large car, and if we need more capacity then I borrow a trailer or rent a truck/minivan.
The useful comments are often not *what* the code is doing, but the other information about the code:
Why we're doing something this particular way. (Maybe the option that might seem obvious at first blush has issues that only show up in certain wierd circumstances.)
The overall goal of the function? Maybe it's doing some impenetrable higher math, in which case it can be useful to summarize the general intent.
Expected usage. Not all languages support design by contract, in which case it can be useful to have a comment giving expected ranges for inputs, valid bit flags, etc.
Basically anything that might be useful for the next person that looks at the code to help them get up to speed. You never know, that person could be you 10 years later. (It happened to me...I wrote some code, it got farmed out to outsourced labor to maintain, then a decade later I got called in to help debug some issues. Turned out to be flaws in the code that the subcontractors had added...but my earlier comments were useful in getting familiar with the code again.)
If you take your old system and convert it to a VM you can then shut down all but the necessary services and add a stateful firewall on the host. This will go a long way towards reducing the security risk.
For the paper masks in question you need to fit the metal nose-piece properly to your nose.
I agree, for the rubber/silicone masks with filter(s) and exhalation valves there's no real fitting involved, but most people in China apparently aren't wearing those.
The stated goal of the patent system was to improve technology by making stuff public in return for a limited monopoly. (The alternative was having everyone keep their stuff as trade secrets, which could get lost if the right people died at the wrong time.)
If you have two people independently invent the same thing then that seems to indicate that it wasn't in danger of being lost and so therefore shouldn't be eligible for protection.
In the real world once a patented idea has been made public it becomes very difficult to prove independent invention, so the window for this sort of thing to happen would be very small--basically from the time someone starts working on something until the time that someone files for a patent on it.
The ISP should be able to shape traffic between subscribers based only on their relative bandwidth and SLA, not the traffic type. The ISP should only do traffic-type-based shaping if the subscriber asks them to, and the shaping should only affect that subscriber.
They don't own the dealerships, but they do set the prices.
All Toyota dealerships within 2000km of my house had the same prices when I was car shopping. And they didn't dicker. If you were really good you could get a couple of accessories thrown in, but the price on the car itself does not go below Toyota's suggested price.
And Toyota parts in Canada cost double what they cost in the USA.
There is no group with a lower aggregate IQ then new car buyers. Not even 'audiophiles'.
Have to quibble a little bit. I bought a new Toyota Matrix in 2005 even knowing the downsides of buying new. I had a couple primary reasons that I still think are valid:
1) At the time there were few hatchbacks available used anywhere within 1000km. Well-used Civics were going for 10K. 2) I have every intention of driving my vehicle into the ground, in another decade or so.
Now there are hatchbacks/crossovers from everyone all over the place, so when we add a second vehicle I'll probably go used.
ISPs can still throttle torrents to ensure voip traffic moves through.
No! If I dedicate all my bandwidth to torrents and you dedicate all yours to VoIP why should you get preferential treatment?
The only fair solution is for an ISP to do per-subscriber shaping within their network. Each subscriber gets throughput relative to the bandwidth that they paid for. Traffic type shouldn't matter when comparing traffic for two different subscribers.
If an individual subscriber wants to prioritize VoIP over torrents they can do that on their own equipment (or have the ISP do it for them). But that should affect only the traffic for that subscriber, and should have ZERO impact on any other subscriber's traffic.
You could let the municipality own the last mile and bill to cover maintenance, since that is pretty much a natural monopoly.
Then the ISPs could compete for the connection to the outside world and tie into neighbourhood switches. This would be far fairer to ISPs since it would limit the amount of infrastructure necessary to get started. And the municipality often already owns water/sewer/etc. so they're used to digging in people's yards.
A basic monthly cost to cover the act of having a wire connected to the house, and a separate usage-based component to cover bandwidth costs and infrastructure upgrades.
We did all the right stuff (breastmilk, good food, have a cat, play in dirt, etc.)
However, both my kids are sensitive (not allergic) to soy protein and cow-based dairy products, and my older kid seems to react to gluten.
We discovered the dairy issue while he was still breastfeeding...he got really bad gas/bloating when my wife consumed dairy products. Took us months to realize what was going on.
"Because the pediatricians tell us that if we give peanuts to a child under 2 years old, he will die (ok... they really just strongly advise against it)."
That's just it, that *used* to be the recommendation, but now there are multiple studies coming out showing that the above advice may not be the best course of action. If your medical professionals are staying on top of things they may start to change their recommendations...
I've got an iron constitution and can eat anything. Both my kids are sensitive to cow's milk and soy protein (not allergic, but it gives them stomach pains and bad gas). Nuts are totally fine.
When my wife was breastfeeding our first kid we noticed that *he* got symptoms when *she* consumed cow's milk. So whatever is problematic in the dairy was being transmitted through the breastmilk.
The problem is when you move on and your replacement needs to get up to speed, or you need to go back two years later to fix a corner case.
Assembly code in particular can be hard to follow. Among other things, if I'm writing assembly that ties into higher-level language code I find it helpful to include human-readable descriptions of what the various registers are on entry and on exit. I'll also break up the code into logical blocks and include a comment describing at a high level what is happening in each block.
Slashdot Mirror
I have one of those "Optimum" laptops with combined Intel graphics and discrete Nvidia graphics. Unfortunately Dell implemented it with all the external monitor ports hooked up to the Nvidia chip, which means that if I want to drive external monitors I need to fire up the power-hungry Nvidia chip even though the integrated graphics could do it perfectly well.
Also, the Nvidia chip supposedly supports three external monitors, but it actually doesn't work, and the added performance over the integrated graphics is pointless if you're not gaming.
Finally, throw in the fact that the Intel drivers are open source and actively supported by Intel.
The desktop/laptop processors are easy...single socket, relatively small number of cores.
It takes effort to add the bits to allow the processors to scale to 10/12 cores, huge caches, and multiple sockets. They also use more complicated memory modules, different motherboards, etc.
Also, large companies are able to get their hands on limited quantities of these cpus well before they're generally available for large-scale ordering to allow their engineers to build products on them and test how they'll behave.
According to the WHO, malaria (spread by mosquitoes) killed between 473000 and 789000 people in 2012. Add in a few more similar diseases and it could plausibly be "millions of people".
I've been working for over a decade on the server side of things. Linux kernel customization, device drivers, high-availability, fault-tolerance, etc. Mostly in C, more than a little bit of assembly, some shell scripting.
There's a lot of that stuff still being done, and it's a pretty good living since there aren't all that many people who are comfortable in that environment.
If you need to take passengers somewhere, rent a car for the day.
I used to live with no car, and I could rent a small hatchback for $15/day on the weekends, with unlimited distance allowed.
Now I've got kids and I'm in a city with worse public transit, so it'd be a lot harder to live without a car. But it's not a large car, and if we need more capacity then I borrow a trailer or rent a truck/minivan.
The useful comments are often not *what* the code is doing, but the other information about the code:
Why we're doing something this particular way. (Maybe the option that might seem obvious at first blush has issues that only show up in certain wierd circumstances.)
The overall goal of the function? Maybe it's doing some impenetrable higher math, in which case it can be useful to summarize the general intent.
Expected usage. Not all languages support design by contract, in which case it can be useful to have a comment giving expected ranges for inputs, valid bit flags, etc.
Basically anything that might be useful for the next person that looks at the code to help them get up to speed. You never know, that person could be you 10 years later. (It happened to me...I wrote some code, it got farmed out to outsourced labor to maintain, then a decade later I got called in to help debug some issues. Turned out to be flaws in the code that the subcontractors had added...but my earlier comments were useful in getting familiar with the code again.)
If you take your old system and convert it to a VM you can then shut down all but the necessary services and add a stateful firewall on the host. This will go a long way towards reducing the security risk.
The message has been, if you want privacy, use your mobile device (and don't vote for Democrats and their spy programs).
Do you honestly think that a Republican government wouldn't do just as much spying?
http://www.3m.com/product/info...
Which needs to have the little metal piece fitted to the bridge of the nose.
And of course this type of mask is nowhere near as nice as a half/full silicone mask with separate filters.
For the paper masks in question you need to fit the metal nose-piece properly to your nose.
I agree, for the rubber/silicone masks with filter(s) and exhalation valves there's no real fitting involved, but most people in China apparently aren't wearing those.
The stated goal of the patent system was to improve technology by making stuff public in return for a limited monopoly. (The alternative was having everyone keep their stuff as trade secrets, which could get lost if the right people died at the wrong time.)
If you have two people independently invent the same thing then that seems to indicate that it wasn't in danger of being lost and so therefore shouldn't be eligible for protection.
In the real world once a patented idea has been made public it becomes very difficult to prove independent invention, so the window for this sort of thing to happen would be very small--basically from the time someone starts working on something until the time that someone files for a patent on it.
The ISP should be able to shape traffic between subscribers based only on their relative bandwidth and SLA, not the traffic type. The ISP should only do traffic-type-based shaping if the subscriber asks them to, and the shaping should only affect that subscriber.
They don't own the dealerships, but they do set the prices.
All Toyota dealerships within 2000km of my house had the same prices when I was car shopping. And they didn't dicker. If you were really good you could get a couple of accessories thrown in, but the price on the car itself does not go below Toyota's suggested price.
And Toyota parts in Canada cost double what they cost in the USA.
There is no group with a lower aggregate IQ then new car buyers. Not even 'audiophiles'.
Have to quibble a little bit. I bought a new Toyota Matrix in 2005 even knowing the downsides of buying new. I had a couple primary reasons that I still think are valid:
1) At the time there were few hatchbacks available used anywhere within 1000km. Well-used Civics were going for 10K.
2) I have every intention of driving my vehicle into the ground, in another decade or so.
Now there are hatchbacks/crossovers from everyone all over the place, so when we add a second vehicle I'll probably go used.
There are many parts of the USA where the "Deep Winter" is more like -40. So your overall range is roughly either -40-100 in F or -40-38 in C.
ISPs can still throttle torrents to ensure voip traffic moves through.
No! If I dedicate all my bandwidth to torrents and you dedicate all yours to VoIP why should you get preferential treatment?
The only fair solution is for an ISP to do per-subscriber shaping within their network. Each subscriber gets throughput relative to the bandwidth that they paid for. Traffic type shouldn't matter when comparing traffic for two different subscribers.
If an individual subscriber wants to prioritize VoIP over torrents they can do that on their own equipment (or have the ISP do it for them). But that should affect only the traffic for that subscriber, and should have ZERO impact on any other subscriber's traffic.
The only fair solution is for the ISP to shape traffic per-subscriber.
If the subscriber wants to prioritize different traffic types then they can do that internally once it hits their equipment.
You could let the municipality own the last mile and bill to cover maintenance, since that is pretty much a natural monopoly.
Then the ISPs could compete for the connection to the outside world and tie into neighbourhood switches. This would be far fairer to ISPs since it would limit the amount of infrastructure necessary to get started. And the municipality often already owns water/sewer/etc. so they're used to digging in people's yards.
A basic monthly cost to cover the act of having a wire connected to the house, and a separate usage-based component to cover bandwidth costs and infrastructure upgrades.
We did all the right stuff (breastmilk, good food, have a cat, play in dirt, etc.)
However, both my kids are sensitive (not allergic) to soy protein and cow-based dairy products, and my older kid seems to react to gluten.
We discovered the dairy issue while he was still breastfeeding...he got really bad gas/bloating when my wife consumed dairy products. Took us months to realize what was going on.
"Because the pediatricians tell us that if we give peanuts to a child under 2 years old, he will die (ok... they really just strongly advise against it)."
That's just it, that *used* to be the recommendation, but now there are multiple studies coming out showing that the above advice may not be the best course of action. If your medical professionals are staying on top of things they may start to change their recommendations...
I've got an iron constitution and can eat anything. Both my kids are sensitive to cow's milk and soy protein (not allergic, but it gives them stomach pains and bad gas). Nuts are totally fine.
When my wife was breastfeeding our first kid we noticed that *he* got symptoms when *she* consumed cow's milk. So whatever is problematic in the dairy was being transmitted through the breastmilk.
Back then the mobile space hadn't exploded yet.
The problem is when you move on and your replacement needs to get up to speed, or you need to go back two years later to fix a corner case.
Assembly code in particular can be hard to follow. Among other things, if I'm writing assembly that ties into higher-level language code I find it helpful to include human-readable descriptions of what the various registers are on entry and on exit. I'll also break up the code into logical blocks and include a comment describing at a high level what is happening in each block.