My main point is that it is hard also when the source is available. At least I have found fixing even a small bug to take a few days. In the end, the fix can be trivial but it takes ages to get familiar with the codebase.
No, no, no. As an example, download Firefox source code and find where the code for linear interpolation of zoomed images is located. Before even modifying it, just locate it and try to roughly understand how it works. When you have done this, come back to the coffee table.
You only need to look at the stats - Metal on an iPad Air will manage to run 3000 draw calls per frame, OpenGL, only 200.
In all fairness, Metal is an optimized platform-specific API, like AMD Mantle. It is certainly true that OpenGL is slower, but it provides a common HAL for many platforms, making porting applications easier.
Just be aware that we are often talking about 100k+ lines of code projects these days. For fixing minor bugs it is okay, but adding new features means a lot of real work. Have you tried downloading the source code of some application and making even just small modifications to it?
The processor in the existing rpi is so slow compared to other (even similarly clocked) modern arm cores that one might seriously wonder if Intel isn't paying these folks to sabotage arm in the minds of developers.
Raspberry Pi is not a product that follows the latest computing advancements but it is about keeping a stable platform. A program written for C64 works on another C64. A program written for Raspberry Pi works on another Raspberry Pi.
It would make cooperative education and hobby projects more difficult if people had to continuously negotiate about "is this the 700MHz or 1000MHz version we are talking about". It's more straightforward to have a common ground.
Of course there's plenty of other ARM boards with the latest hot chips if that's what your project requires.:)
This seems to be how the human brain works, and it runs on less than 100 watts (100 watts corresponds to 2000 Calories per day).
A whole woman consumes 100 watts. Of that brain is about 20 watts. Also, watt represents momentary consumption and calories are a fixed mass of energy, so you can't directly compare them.
When Debian pushed Gnome3 and the community didn't like it they moved forward with it as the default desktop anyway. Now there is the systemd debacle. A large number of people have voiced their disapproval, but No, Debian is going to go down that route anyway.
GNOME3 and SystemD are a natural choice because the developer community behind them is so large. Hopefully that leads to software which has less glitches, less vulnerabilities, new features are implemented faster, documentation is up to date, and quality assurance works. These days open source projects are so complex that you really need the pure manpower. This is probably the direction which we are even more heading towards in the future.
On Haswell architecture there is some special bit that has to be set for the hardware samplers to work at maximum performance. There seems to be no details regarding what this specifically means. The original LunarG post seems to contain the best information. What is quite cool is that they claim to have plugged LLVM into the Mesa shader compiler.
To what standard do you hold the US government as opposed to other governments? You can be damn sure that every other intelligence agency is doing exactly the same thing... but you're criticizing NSA why exactly?
Most of the big web services that we are using are located in USA.
Exactly. They need only a handful of the most juicy vulnerabilities.
Besides, that we are having this whole discussion is ridiculous. "Yeah, know a bunch of secrets that we could use to crack into your computer...but we do reveal most of them -- honest!"
Now you are talking about programming. C64 had a BASIC interpreter ready when you turned the machine on. The commands were relatively simple and you had no APIs but direct hardware access. Sure, you still required lots of skill to make cool things, but it was more easy to get in to. With couple of lines you get your first program which fills the screen with "I am awesome". If we make apps for Android, the first pot of coffee goes just when setting up the development environment. So things are quite more complex on that front too.
Actually from Fedora I get least the beta feeling. They have a good amount of developers working on the components and fixing bugs, and they at least pretend to have some kind of real quality assurance.
Slashdot Mirror
My main point is that it is hard also when the source is available. At least I have found fixing even a small bug to take a few days. In the end, the fix can be trivial but it takes ages to get familiar with the codebase.
No, no, no. As an example, download Firefox source code and find where the code for linear interpolation of zoomed images is located. Before even modifying it, just locate it and try to roughly understand how it works. When you have done this, come back to the coffee table.
You only need to look at the stats - Metal on an iPad Air will manage to run 3000 draw calls per frame, OpenGL, only 200.
In all fairness, Metal is an optimized platform-specific API, like AMD Mantle. It is certainly true that OpenGL is slower, but it provides a common HAL for many platforms, making porting applications easier.
Yep, that should be doable by one man.
Just be aware that we are often talking about 100k+ lines of code projects these days. For fixing minor bugs it is okay, but adding new features means a lot of real work. Have you tried downloading the source code of some application and making even just small modifications to it?
And why would it do any of these things? I'm sure it would not be good business for a hardware manufacturer to include such malicious features.
Huh? How does UEFI violate one's privacy?
I just missed the "per day" for calories, that's all. Yep, I agree with you.
Just to tune that even further, a proper link would not read "a proper link" but XKCD #1437. :)
Well played.
Hmm, C6 seems to indeed be the main smoothing cap.
The processor in the existing rpi is so slow compared to other (even similarly clocked) modern arm cores that one might seriously wonder if Intel isn't paying these folks to sabotage arm in the minds of developers.
Raspberry Pi is not a product that follows the latest computing advancements but it is about keeping a stable platform. A program written for C64 works on another C64. A program written for Raspberry Pi works on another Raspberry Pi.
It would make cooperative education and hobby projects more difficult if people had to continuously negotiate about "is this the 700MHz or 1000MHz version we are talking about". It's more straightforward to have a common ground.
Of course there's plenty of other ARM boards with the latest hot chips if that's what your project requires. :)
Oh, good point. Then it makes sense indeed.
Of course they are. I simply meant to use the word "human" instead of "woman". The word "human" still encompasses women.
A whole woman consumes 100 watts.
D'oh! Human, not woman.
This seems to be how the human brain works, and it runs on less than 100 watts (100 watts corresponds to 2000 Calories per day).
A whole woman consumes 100 watts. Of that brain is about 20 watts. Also, watt represents momentary consumption and calories are a fixed mass of energy, so you can't directly compare them.
When Debian pushed Gnome3 and the community didn't like it they moved forward with it as the default desktop anyway. Now there is the systemd debacle. A large number of people have voiced their disapproval, but No, Debian is going to go down that route anyway.
GNOME3 and SystemD are a natural choice because the developer community behind them is so large. Hopefully that leads to software which has less glitches, less vulnerabilities, new features are implemented faster, documentation is up to date, and quality assurance works. These days open source projects are so complex that you really need the pure manpower. This is probably the direction which we are even more heading towards in the future.
On Haswell architecture there is some special bit that has to be set for the hardware samplers to work at maximum performance. There seems to be no details regarding what this specifically means. The original LunarG post seems to contain the best information. What is quite cool is that they claim to have plugged LLVM into the Mesa shader compiler.
That's the new excuse of an alcoholic buying copious amounts of booze.
To what standard do you hold the US government as opposed to other governments? You can be damn sure that every other intelligence agency is doing exactly the same thing... but you're criticizing NSA why exactly?
Most of the big web services that we are using are located in USA.
Exactly. They need only a handful of the most juicy vulnerabilities.
Besides, that we are having this whole discussion is ridiculous. "Yeah, know a bunch of secrets that we could use to crack into your computer...but we do reveal most of them -- honest!"
Now you are talking about programming. C64 had a BASIC interpreter ready when you turned the machine on. The commands were relatively simple and you had no APIs but direct hardware access. Sure, you still required lots of skill to make cool things, but it was more easy to get in to. With couple of lines you get your first program which fills the screen with "I am awesome". If we make apps for Android, the first pot of coffee goes just when setting up the development environment. So things are quite more complex on that front too.
You seem to be one of those guys who post angry messages day after day. Whatever, thanks for the correction.
It's quite easy to type LOAD"GAME",8,1. The UI of a smartphone is more friendly-looking, but the feature set is way larger.
Actually from Fedora I get least the beta feeling. They have a good amount of developers working on the components and fixing bugs, and they at least pretend to have some kind of real quality assurance.