.. and 5> much better developement tools 6> easier API's and libraries 7> better documentation
Symbian is really pain in the ass for developers.
Build system documentation tells how to compile hello world but there is no documentation that helps to understand it if you want to do more things than just compile C/C++ files during your build process.
And the build tools are bunch of windows.cmd scripts and perl scripts wrapped together, and a few symbian's own exe files doing some binary conversion things. total mess.
All API's are done very differently than on all other platforms. For example there are things like 7 different string classes for more efficient memory usage. And even "hello world" program requires 4 classes.
>> (2) Most of the marine life (including seaweed, >> etc) stays relatively close to the surface. >> Great, you say -- makee the thing travel >> deeper to avoid skewering whales, etc. >> Well, that'd be nice, but it's a *lot* >> harder to cavitate at depth due to the >> increased pressure (and reduced temperature) -- >> and the relationship is not a proportional one. >> Besides being harder to cavitate in the first >> place, it'd be harder to maintain the bubble >> around the vehicle (because sea pressure >> would be trying to collapse it). > > a compromise depth of around 40m should do the > trick.
how are you going to stay on 40m?
if you're travelling at some 500km/h speed, it's about 150m/s.
if your direction is going only 1% too up or too down, you will still end up on the surface or be twice as deep in 30 seconds.
And, while your blind, you don't know your direction and depth very presicely, (conventional depth meter wont work in a bubble) you may even not know your going too up until you find yourself flying ten meters above the surface.
And, even if you knew your direction is too up or too down, how do you turn in the bubble?
There is also one very big problem: fuel capasity.
The russioan torpedo runs only few, maybe few tens of kilometers. And the engine and fual already take very big part of it.
To use it on longer (>100km) distances, over 100% of the mass of the sub would have be fuel. Or then we need multi-phase rockets, just like on space rockets. And that's _very_ expensive, as the payload is usually about 1%or less of the mass of the whole rocket
I think too "easy" tools help help people to write little "dirty" programs easily, but that don't help them to learn programming, instead, it may work just the otherwise.
with those tools it's very easy to make "gui-hanger"-programs, which are mess and explode on bigger programs, when model-controller-view is much better for "real work"
Re:not at all real info about the chip
on
K8 Details
·
· Score: 1
everything about the K8 architechture there is just 100% rumor and speculation. Somebody thinks "64bits is better than 32 bits, intel is desgning 64 bit chip (merced), so of cource AMDs next chip should also be 64bit. But this has nothing to do with reality. the register said this same hoax first, when they understood they were wrong, they posted "amd has changed their k8 architechture...". But too many people read the hoax, and didn't read the "correction" extending x86 to 64 bits - nonsense. noone would support it, and the lack of registers, not the size, is the major problem. When AMD does the announcement, We'll all see, that it's just a nother normal (3/x)86 processor. The futrher the rumors get before that, the more false information is on the move.
Slashdot Mirror
.. and
.cmd scripts and perl scripts wrapped together, and a few symbian's own exe files doing some binary conversion things. total mess.
5> much better developement tools
6> easier API's and libraries
7> better documentation
Symbian is really pain in the ass for developers.
Build system documentation tells how to compile hello world but there is no documentation that helps to understand it if you want to do more things than just compile C/C++ files during your build process.
And the build tools are bunch of windows
All API's are done very differently than on all other platforms. For example there are things like 7 different string classes for more efficient memory usage.
And even "hello world" program requires 4 classes.
... and these today-released mobile duron chips have NO power steppings.
I think intel's way is much better than nothing at all.
AMD is designing a new "morgan" duron core,
which will have PowerNow and ther power-draw-
orientated enchantments too.
But that chip is not yet ready,
so they just lowered the voltage of current duron
from 1.6 to 1.4 V, and added a "mobile"-sticker on it.
It has too big power requireemnts to be a real good mobile part, and I think k6-2+ and k6-III+
are still AMD's mest mobile parts.
We will have to wait a few months until
AMD releases truly mobile palomino and morgan-cored athlons.
AMD's copper fab(fab30) is in dresden, ;)
which belonged to DDR before the merger.
So system with DDR memory and CPU made in DDR
>> (2) Most of the marine life (including seaweed,
>> etc) stays relatively close to the surface.
>> Great, you say -- makee the thing travel
>> deeper to avoid skewering whales, etc.
>> Well, that'd be nice, but it's a *lot*
>> harder to cavitate at depth due to the
>> increased pressure (and reduced temperature) --
>> and the relationship is not a proportional one.
>> Besides being harder to cavitate in the first
>> place, it'd be harder to maintain the bubble
>> around the vehicle (because sea pressure
>> would be trying to collapse it).
>
> a compromise depth of around 40m should do the
> trick.
how are you going to stay on 40m?
if you're travelling at some 500km/h speed,
it's about 150m/s.
if your direction is going only 1% too up or
too down, you will still end up on the surface
or be twice as deep in 30 seconds.
And, while your blind, you don't know your
direction and depth very presicely,
(conventional depth meter wont work in a bubble)
you may even not know your going too up until
you find yourself flying ten meters above the surface.
And, even if you knew your direction is too up or too down, how do you turn in the bubble?
There is also one very big problem:
fuel capasity.
The russioan torpedo runs only few, maybe few
tens of kilometers.
And the engine and fual already take very big
part of it.
To use it on longer (>100km) distances,
over 100% of the mass of the sub would have be
fuel. Or then we need multi-phase rockets,
just like on space rockets. And that's
_very_ expensive, as the payload is usually
about 1%or less of the mass of the whole rocket
I think too "easy" tools help help people to
write little "dirty" programs easily,
but that don't help them to learn programming,
instead, it may work just the otherwise.
with those tools it's very easy to make
"gui-hanger"-programs, which are mess and
explode on bigger programs,
when model-controller-view is much better
for "real work"
everything about the K8 architechture there is
just 100% rumor and speculation.
Somebody thinks "64bits is better than 32 bits,
intel is desgning 64 bit chip (merced),
so of cource AMDs next chip should also be 64bit.
But this has nothing to do with reality. the register said this same hoax first, when they understood they were wrong, they posted "amd has changed their k8 architechture...". But too many people read the hoax, and didn't read the "correction"
extending x86 to 64 bits - nonsense.
noone would support it, and the lack of registers, not the size, is the major problem.
When AMD does the announcement, We'll all see, that it's just a nother normal (3/x)86 processor. The futrher the rumors get before that, the more false information is on the move.