Magnussoft has explained their side of the story concering the recent split between them and Bernd Korz and the Zeta development team. "The archived sales figures of Zeta were far below Magnussoft's expectations. Continuation of financing the project is economically no longer viable. For the time being, Magnussoft discontinued funding of the Zeta development team on March, 16th 2007. The exclusive distribution agreement will remain unaffected. The existing contract is valid until the end of 2007."
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2006-06-26
Member since:2005-07-27
This "feature" is commonly known as the ability to copy files. You know, that thing you do in BeOS, Zeta, MacOS X, Minix, TOS/GEM (Atari ST), Amiga OS (every version since the Amiga 1000), and even DOS. Not to mention, probably every other OS and OS derivative you can possibly imagine!
Oh, sure, you can copy files, but you'll eat up all your RAM (and likely KDL Haiku in the process), in doing so.
Here's how to test Haiku's "feature" (this example assumes you have 512Mb of RAM; the more RAM you have the less this will affect you):
1) Take haiku.image (100Mb file) and duplicate it. Put them into a folder. I call mine "XferTest". This is now a 200Mb folder. Once you have an install of Haiku on a partition, copy the folder from BeOS into the Haiku partition from within BeOS. Attempting to copy this folder from BeOS to Haiku, from within Haiku, will KDL Haiku almost immediately.
2) Boot into Haiku.
3) Copy (not move) that folder from it's current directory to another directory (I use /home). And watch as your memory allocation (shown in the Deskbar via ProcessController (or whatever it's called)) slowly climb. If you have 512Mb of RAM, it will eat up all of it. And you CAN'T recover it! Well, you can recover HALF of it, if you throw away the folder you just copied and empty the trash, but that's the best you'll get. The other 50% of your RAM is still holding it's copy of your 200MB folder. How do you purge that? I dunno. But why copy the folder in the first place, if the only way to reclaim, even 50% of your memory, is to delete the file you just copied?
If try to copy another file, of almost any size (once you've eaten up all your RAM), you will *instantly* KDL Haiku. Or, if you try to copy a 250Mb file/folder, it will KDL Haiku before the copy is even finished..
What is happening: Haiku is loading the file/folder into RAM and then DUPLICATING ("copying") that file in RAM. In other words, a 200Mb file takes up 400Mb of RAM! The file looks like it's on the drive, elsewhere (wherever you've supposedly copied it to), but it isn't. If you KDL Haiku and type reboot and go back to Haiku and look, you'll see the file isn't where you supposedly copied it to... because it was only in RAM the whole time! Only if you shutdown or reboot while Haiku is still functional, will it ACTUALLY copy the file to the hard drive where it needs to be.
Try it. And see how long you can imagine having to live with this "missing feature" in an OS you really enjoy (or at least WANT to enjoy) using otherwise...
I've said this before and I'll say it again... this "feature" should have been implemented a long time ago, back when the Terminal/Tracker were first functional. And yet, how many years has it been since then? And, more importantly, how much *longer* will it be before it's implemented?
The closer we get to the capability to actually COPY large files (USB and Networking support), the more urgently this "feature" is going to be needed.
People can shout "It's pre-Alpha!" til the earth ends, but it does not change the simple fact that this is something Haiku NEEDS implemented NOW, not later!
Member since:2005-06-30
Oh my god.
Please stop with this!
Haiku is still in development:
1. even if this "features" is implemented you won't have a fully functiona OS (Haiku R1 will still be BeOS R5 with some more drivers, nothing like Windows + Microsoft Office and other applications or let's say Ubuntu or Mac OS X).
2. there are many bugs left and the developers are working hard on it, so don't worry, take some months a year, study C/C++ programming and help Haiku developers instead of waste your time writing the same things all the time.
Member since:
2005-07-27
There is a "feature" that I have been wanting (and harping about) ever since I noticed the lack of this "feature" causes the entirety of Haiku to go straight to KDL (Kernel Debugging Land; i.e. OS crash).
I started a log (in BeOS, mind you) concerning Haiku's progress. I started it in Sept. of 2006. It is now March of 2007. It's been 6 months and this "feature" has YET to be implemented!
Mind you, this one "feature" is a critical element to *ALL* OS's. In fact it's so basic and critical, you can't function without it in MacOS X! Yet, for some odd reason, it gets put off endlessly in Haiku! While this and that developer adds new filesystems, or fixes something inside an app, or changes documentation, or adds a new device driver, etc.
Mind you, this one solitary feature is ALL that keeps me from using Haiku on a regular basis! I could be USING it, instead of talking ABOUT it.
If I focus on this one "missing feature", it will ruin my appreciation for the potential this OS has. But "potential" is intangible. Potential must be REALIZED for it to have any meaning.
And Haiku's potential is, thus far, still just... potential. It has yet to be realized.
Edited 2007-03-27 17:57