so in other words instead of writing your task in a few lines of straight C, you'd write it in a bunch of straight C in an extension library and then use python to glue it together.
tis strange how virtually none of the widely used python applications do this though.
of course if you care to submit a mandelbrot which uses native libraries to do better, i'd love to see it.
They would have had to bolt on multiple user and filesystem permissions, which would be a fundamental change to BeOS. It lacked both.
BeOS is/was also advanced in terms of file meta data. That situation is still quite messy in MacOS X.
File metadata is a big pile of doggie poo, especially when your OS is totally dependent on them. Apple struggled with that problem for 10 years in MacOS, then the internet came along and ripped them a new asshole -- metadata travels poorly on the internet, especially between different architectures.
OSX handles metadata in a portable way with bundles and property lists. It's messy, but it's better than the alternative (non portable resource/data forks)
In the end BeOS was really no choice at all. A few nifty features couldn't compensate for the huge pile of glaring flaws.
the problem of storing metadata that way is that its non portable. it's exactly the same problem that plagued macos classic. great when you only deal with macs but bad when the internet comes around and suddenly you have no simple way to transport files around.
also bad when you need to talk eg nfs or smb.
storing metadata in bundles and the whole bundle system allows macos to be transparenly "native" on just about any filesystem.
linux and nt have the ability to attach metadata to files, but nobody uses it. it would be a huge pain if anyone did start, because it would then suffer from again being non portable.
osx bundles are a sort of compromise between having metadata available, but in a way thats portable. its a bit ugly, but it works.
if you get a monetary judgement against him, then for a small fee you can have the local sheriff seize his property / bank accounts / etc. in order to pay the judgement.
doesnt matter if he doesn't want to pay, when law enforcement shows up with firearms and takes the decision out of his hands.
Slashdot Mirror
try this one?
AGP cards have different notches in them to prevent you from plugging a card into the wrong voltage slot.
you can buy fanless geforce 6800's btw.
I have a Shuttle SB52G2 with a 2.6ghz Celeron and the HSF is _silent_. The loudest thing in it by far is the WDC WD2000JB-00EVA0.
Sorry you had bad experiences with Shuttles, unless you're expecting 0db or something...
FWIW the quietest drives i've ever had are Maxtor 6Y200P0's. You cant even tell theyre on unless you hold them.
sounds like you speak from experience.
C is slower in water. This is what causes the cerenkov effect (blue glow) in nuclear reactors as particles are accelerated beyond C (in water).
so in other words instead of writing your task in a few lines of straight C, you'd write it in a bunch of straight C in an extension library and then use python to glue it together.
tis strange how virtually none of the widely used python applications do this though.
of course if you care to submit a mandelbrot which uses native libraries to do better, i'd love to see it.
the mandelbrot test isnt recursive.
care to try again?
it was also missing users and permissions. a big no-no for modern multitasking systems.
NextSTEP was still a better choice.
BeOS would also have been a cleaner start.
Not really.
They would have had to bolt on multiple user and filesystem permissions, which would be a fundamental change to BeOS. It lacked both.
BeOS is/was also advanced in terms of file meta data. That situation is still quite messy in MacOS X.
File metadata is a big pile of doggie poo, especially when your OS is totally dependent on them. Apple struggled with that problem for 10 years in MacOS, then the internet came along and ripped them a new asshole -- metadata travels poorly on the internet, especially between different architectures.
OSX handles metadata in a portable way with bundles and property lists. It's messy, but it's better than the alternative (non portable resource/data forks)
In the end BeOS was really no choice at all. A few nifty features couldn't compensate for the huge pile of glaring flaws.
i don't know about that. an OS without filesystem or user permissions of any kind doesnt cut it these days.
if you feel you have better python code to perform a task on the benchmark, feel free to submit it.
r k.php?test=mandelbrot&lang=all&sort=fullcpu=all for example.
try http://shootout.alioth.debian.org/sandbox/benchma
producing code speaks louder than complaining that the benchmark is useless.
no, i do understand.
the problem of storing metadata that way is that its non portable. it's exactly the same problem that plagued macos classic. great when you only deal with macs but bad when the internet comes around and suddenly you have no simple way to transport files around.
also bad when you need to talk eg nfs or smb.
storing metadata in bundles and the whole bundle system allows macos to be transparenly "native" on just about any filesystem.
linux and nt have the ability to attach metadata to files, but nobody uses it. it would be a huge pain if anyone did start, because it would then suffer from again being non portable.
osx bundles are a sort of compromise between having metadata available, but in a way thats portable. its a bit ugly, but it works.
its also all xml, woo woo.
osx metadata still exists, only it's now called property lists and lives inside bundle files.
...for apple to make mac mini socks...
actually I was thinking more like "they call me the d-d-d-d-doctor"...
matt frewer as the doctor
:))
john de lancie as the master
let the flames begin
http://slashdot.org/~dcam/foes
lol. looks like you have some serious problems you need to sort out.
their track record speaks for itself, so the answer would be: highly unlikely
its not hard at all -- if MS would actually write decent solid code then I would have no problem crediting them.
as long as they continue to pump out rubbish code, they will be continue to be criticized for it.
don't forget... microsoft didn't write mssql -- they bought sybase and relabeled it.
if you get a monetary judgement against him, then for a small fee you can have the local sheriff seize his property / bank accounts / etc. in order to pay the judgement.
doesnt matter if he doesn't want to pay, when law enforcement shows up with firearms and takes the decision out of his hands.
be glad they didn't move tech support out to new delhi or bangalore.
congratulations.
your're living proof that video games corrupt youth, leaving horrible mental scars that remain for life.
if you have an extremely pedantic personality and enjoy nitpicking things to death, then game QA is certainly for you.
...
however this personality type describes many programmers
doom3 was a tech demo, nothing more.