Personally, I'd rather we spent the $trillions on known, well-understood issues where we can see sizable concrete benefits that help billions of people
I suggest we spend the money on finding an alternative to fossil fuels before they run out. Dependable energy is more important than the climate.
You can call it unethical, but if the ROI on the treatment is 200% but only 80% for the cure then you're not going to stay in business making cures all the time.
Why not simply charge more for the cure so that ROI is 210 % ?
the final mix is down-sampled to 44.1 kbps at 16-bit resolution (the CDA standard)
If you don't think that's enough, you don't understand signal theory. Higher rates earlier in the chain are useful for digital filtering and mixing, but 44 ksps is plenty for hearing.
They offer measurably-better resolution than CDA
Apart from being able to reproduce frequencies which we can't hear, please show the measurements where vinyl is better.
Insulin is needed for a few percent of the diabetics. And even then, most insulin dependents can benefit from having a low-carb diet in combination with much less insulin.
But I knew somebody would immediately come back with corner cases, ignoring the big picture of millions of people who can get better by fixing their diet.
Diabetic retinopathy occurs when the high levels of blood sugar in the bloodstream cause damage to your retina's blood vessels
An obvious way to fix the root cause is to switch to a low-carb diet, where you avoid high levels of blood sugar. Too bad there's more money to be made prescribing insulin and gadgets.
The problem with microkernel performance is not due to latency for process switching and message passing.
The problem is the synchronization between different parts. Imagine for instance a multi-threaded filesystem. A filesystem as whole has a certain state. That state describes all the files and directories, file sizes and contents. Now imagine that one of the threads makes a change to the state. The problem is how to get that state update to all the other threads with a minimum of a delay.
In a monolithic kernel, the problem is solved by getting a lock, update the state, and releasing the lock. It's a very simple and efficient operation.
In a microkernel, you need to send messages around. You can optimize the message passing itself, but you'll still have the problem that the receiving thread is doing other things, and only handles the messages at certain points. While it is doing those other things, it's working with an outdated version of the state. Basically you're getting into the design of distributed filesystems/computing, and this is a very hairy subject. The complexity of the problem is much larger than just sticking to simple locking.
The traditional solution is to keep the filesystem (and similar parts of the OS) in a single thread. This may be a viable solution on some platforms (perhaps a phone or tablet), but it will quickly run into scalability problems on a large, general purpose computer.
The energy in the system comes from the Sun. There's about 170000 TW of solar energy hitting the atmosphere. The 20 TW of human-generated energy is nothing compared to that.
Why would you compare the 2.5TW change in solar output with our energy production, which is a totally unrelated variable ?
You should compare it to the average solar output, which is about 1360 W/m^2. So we're talking about 0.7% variation.
Now compare your solar graph to the global temperature graph, and you'll see they don't match. Especially after about 1980, when solar output starts to go back down, and global temperature goes through fastest rise.
All depends on the ARM core and how hard you can bargain. Probably less than $1 per core. But keep in mind that you could easily have 100 individual CPU cores in a car.
I think the biggest reason for these companies is flexibility to make their own custom designs.
Modifying a stop sign with the purpose of fooling a self-driving car is similar to someone tampering with a stop sign to fool human drivers, and can be handled with existing laws.
So where are they? I mean this is open source right, and they aren't just throwing that around as a buzzword so where is the website for it, where are the specs, where is the 'how to' articles or anything else.
That is before you get to manufacturing. Who will fab them? In what technology? Who will qualify parts? Who will stock the inventory? Who closes the loop between hardware defects and design?
These cores will not be used as standalone CPU devices. They will be integrated in an application-specific SoC design that each company will have fabbed for themselves according to their own needs.
Take a look at how big companies develop Linux kernel modifications. It's not that hard. You do the things you want for yourself, and then you share those with the others.
Slashdot Mirror
Not all poor people have cooking facilities for turnips, or capital, transport and safe storage for those soybeans.
Plenty of poor people do, but they still are not buying them.
More people look better when you show the org chart to investors. That's all.
The problem is that they tried to save money and ended up spending more.
It's not exactly a problem if the real goal is spending money.
Personally, I'd rather we spent the $trillions on known, well-understood issues where we can see sizable concrete benefits that help billions of people
I suggest we spend the money on finding an alternative to fossil fuels before they run out. Dependable energy is more important than the climate.
I wouldn't want to explain to them how this wasn't my fault and I'm not sharing.
No worries, you'll be dead before that happens.
Fair enough.
How about this: the insurer funds the development of the cure, and happily takes the 80% profit margin, instead of paying for the 200% ?
You can call it unethical, but if the ROI on the treatment is 200% but only 80% for the cure then you're not going to stay in business making cures all the time.
Why not simply charge more for the cure so that ROI is 210 % ?
the final mix is down-sampled to 44.1 kbps at 16-bit resolution (the CDA standard)
If you don't think that's enough, you don't understand signal theory. Higher rates earlier in the chain are useful for digital filtering and mixing, but 44 ksps is plenty for hearing.
They offer measurably-better resolution than CDA
Apart from being able to reproduce frequencies which we can't hear, please show the measurements where vinyl is better.
Insulin is needed for a few percent of the diabetics. And even then, most insulin dependents can benefit from having a low-carb diet in combination with much less insulin.
But I knew somebody would immediately come back with corner cases, ignoring the big picture of millions of people who can get better by fixing their diet.
Diabetic retinopathy occurs when the high levels of blood sugar in the bloodstream cause damage to your retina's blood vessels
An obvious way to fix the root cause is to switch to a low-carb diet, where you avoid high levels of blood sugar. Too bad there's more money to be made prescribing insulin and gadgets.
The problem with microkernel performance is not due to latency for process switching and message passing.
The problem is the synchronization between different parts. Imagine for instance a multi-threaded filesystem. A filesystem as whole has a certain state. That state describes all the files and directories, file sizes and contents. Now imagine that one of the threads makes a change to the state. The problem is how to get that state update to all the other threads with a minimum of a delay.
In a monolithic kernel, the problem is solved by getting a lock, update the state, and releasing the lock. It's a very simple and efficient operation.
In a microkernel, you need to send messages around. You can optimize the message passing itself, but you'll still have the problem that the receiving thread is doing other things, and only handles the messages at certain points. While it is doing those other things, it's working with an outdated version of the state. Basically you're getting into the design of distributed filesystems/computing, and this is a very hairy subject. The complexity of the problem is much larger than just sticking to simple locking.
The traditional solution is to keep the filesystem (and similar parts of the OS) in a single thread. This may be a viable solution on some platforms (perhaps a phone or tablet), but it will quickly run into scalability problems on a large, general purpose computer.
Graph of solar variation on top of global temperature.
http://www.woodfortrees.org/pl...
Doesn't seem to be much correlation.
there are about 5.1*10^12 square meters
Surface area of the Earth, as seen from the Sun, is 127*10^12 square meters.
The energy in the system comes from the Sun. There's about 170000 TW of solar energy hitting the atmosphere. The 20 TW of human-generated energy is nothing compared to that.
Why would you compare the 2.5TW change in solar output with our energy production, which is a totally unrelated variable ?
You should compare it to the average solar output, which is about 1360 W/m^2. So we're talking about 0.7% variation.
Now compare your solar graph to the global temperature graph, and you'll see they don't match. Especially after about 1980, when solar output starts to go back down, and global temperature goes through fastest rise.
I want to see a drone ring my doorbell, hand me my package, and then ask for my signature.
That is not the same as disguising a stop sign, and probably not illegal under current law.
Current law also considers intent of your actions. If you purposefully create a situation where people end up in danger, then it is illegal.
All depends on the ARM core and how hard you can bargain. Probably less than $1 per core. But keep in mind that you could easily have 100 individual CPU cores in a car.
I think the biggest reason for these companies is flexibility to make their own custom designs.
Modifying a stop sign with the purpose of fooling a self-driving car is similar to someone tampering with a stop sign to fool human drivers, and can be handled with existing laws.
So where are they? I mean this is open source right, and they aren't just throwing that around as a buzzword so where is the website for it, where are the specs, where is the 'how to' articles or anything else.
I don't know. Impossible to find anything.
https://riscv.org/
That is before you get to manufacturing. Who will fab them? In what technology? Who will qualify parts? Who will stock the inventory? Who closes the loop between hardware defects and design?
These cores will not be used as standalone CPU devices. They will be integrated in an application-specific SoC design that each company will have fabbed for themselves according to their own needs.
anyone any idea what that number is ?
Billions and billions...
Take a look at how big companies develop Linux kernel modifications. It's not that hard. You do the things you want for yourself, and then you share those with the others.
License fees, plus you're stuck with what ARM gives you. Having your own core means you can customize it.
Radio waves penetrate deeper, though.