SkyOS Development Team Quizzed 83
Hexydes writes "TechIMO recently interviewed the SkyOS Development Team about SkyOS. The developers were asked questions regarding SkyOS 5.0, what a typical development day is like, and why they decided to work on SkyOS, which is 'a free operating system written from scratch for x86 PC's'. Included in the interview are pictures from the most recent beta build of SkyOS 5.0"
Stay away from this! (Score:5, Funny)
Once SkyOs merges with
Free eh? (Score:5, Informative)
1: Eats at GPL programs and does not follow GPL
2: Has no source to examine
3: No "Open Source" type license
4: Pissy developers when you mention Open Source
Real free. Want speech with that?
Re:Free eh? (Score:2, Insightful)
As for "something that eats at GPL programs and does not follow GPL" - would you care to back that accusation up, please?
Re:Free eh? (Score:2)
Figuring how SkyOS is made for public dissemination (anybody can download/install it), they're breaking the GPL.
As for references, there's a stir on the SkyOS message boards occaisionally, but the admins delete them. I'm pretty sure they're listed also with the FSF as GPL breakers too....
Re:Free eh? (Score:5, Informative)
We have talked to the FSF, and they are perfectly fine with our project. We also talked to any developers whose code we used in included applications, and any ones we were able to contact were also fine with the situation.
In fact, the ONLY people who have had a problem with things regarding the GPL are a few random users on Slashdot. The FSF is fine with us. Developers are fine with us. 99% of users are fine with us. Why do you have such a problem with our project? We aren't breaking any part of the GPL purposely. Robert accidentally does not have the source for the 4.0 applications available any more (as he uses them to develop to the 5.0 applications), and we've already cleared all of that up with the developers and the FSF. When we release 5.0, we will also be releasing the source to GPL applications.
As far as the kernel and underlying parts of the system go, 95% of that is code that Robert has written, the rest uses BSD.
I really wish a few people would stop looking for ways to attack our project.
Re:Free eh? (Score:2)
NOT [L]GPL!!! KILL!! KILL!!!! MY COUSIN VINNY SAID A FRIEND OF A FRIEND OF A FRIEND TOLD HIM THE SKYOS TEAM EAT CHILDREN WITH TABASCO SAUCE!!! OK, MOD ME UP!!!1! NEXT FUD ARTICLE!!! LOOK, SHINY!!! OOOOHHHHH!!!
Just keep doing what you're doing and ignore the warts - especially here. The warts in th
Re: (Score:1)
Re:Free eh? (Score:2)
Re:Free eh? (Score:1)
As far as I understand it, this is perfectly valid under the terms of the GPL. All you need to do is allow any recipient of the derived code to have the source. You don't have any obligation to provide it to the person you got it from.
Re:Free eh? (Score:5, Insightful)
BeOS was free as in beer for personal use, too -- then, when Be's money dried up, the OS was neatly packed up in Palm's back pocket. Sure, there have been a few runs at trying to keep the OS alive, but they are far too disorganized to be of any worth.
When SkyOS's development team disintegrates, what will happen to its users, and its source code? Forking is a healthy thing for operating systems, from the point of view of its users, because it means the OS will continue to exist, independant of a few individual developers' whims.
The only actual reason for keeping the kernel source closed is the ego of the developers. It's a cute OS from the screenshots, but anyone who is really looking for a desktop replacement should think long and hard about what happens when this project folds.
They don't get OSS (Score:5, Insightful)
And yet, on their main page [skyos.org]:
WTF? I didn't know the market was so bad people took s/w positions in exchange for access to toy operating systems. Well it isn't. And you can't get people to work for free while you make all the money. Choose open source or closed source, but play by the rules...Comment removed (Score:5, Insightful)
Re:They don't get OSS (Score:2)
Fact of the matter is, a LOT of people/companies (including me) make closed source free software, but if you want the code, you pay me a licensing fee.
Don't like it? Write your own damn code.
Re: (Score:2)
Re: (Score:1)
Re: (Score:2)
Re:They don't get OSS (Score:2)
fail. In many cases, esp. if they care about GUI
giving users choice is abject failure. So for
instance a big failure of Linux is the user having
a choice between the looks and feels provided by
different distros as opposed to one look and feel
for Windows or OSX. This of course refers to
system defaults since everyone allows you to
customize.
Similar fragmentation exists further down, so for
instance users do not have ONE WAY of laying out
their directory structure. N
Re:They don't get OSS (Score:2, Insightful)
You said it yourself:
> Having one standard is often better.
I'm not sure having projects fork makes standard more difficult to achieve, even if it seems counterintuitive.
Re:They don't get OSS (Score:1)
a bunch of forks in the sense that they take same
code and package it to their liking. Sometimes
even their Linux trees are a bit different. So
I'd call that situation a fork.
Re:They don't get OSS (Score:2, Insightful)
I wouldn't consider different distros using different patchsets to Linux forks. The kernels used by most distros swarm around vanilla - they get upgraded at the same time and have mostly the same code. Often the only difference is which features are applied. A fork would involve having two vanilla Linuxes, each evolving in a different direction, and some core developers going to Fredix while some stay with Linux.
That's the kernel. Certainly many distros fork, for example Mandrake w
Re:They don't get OSS (Score:4, Insightful)
All I can say is keep plugging a way at it guys but I do not have the time or any compleing reason to help, I am too busy learning my way around the Linux Kernel.
Re:They don't get OSS (Score:3, Funny)
You mean they don't believe the proprietary software is evil?
I say thank God.
Re:They don't get OSS (Score:2)
Since, I am happily married with children(3) and get out quite often.
The first post, jumped all over the guy for not being true OSS. I must admit I assumed he was referring to GNU and the RMS type of thinking.
1) I get tired of people slamming other folks because it doesn't fit into their ideal of what OSS is or is not.
2) RMS would say SkyOS is evil, with this I have problems. Yes, I may have jumped the gun.
I didn't post ac why did you?
Re:They don't get OSS (Score:1)
Re:They don't get OSS (Score:2)
He slammed the guy saying he doesn't get OSS.
I said I thank God. Why? because I have alot of problems with GNU/RMS type of thinking and some of the OSS type of thinking.
This is what RMS says of non-"FREE" software:
"Proprietary software is antisocial, so developing it is wrong."
Evil may be a strong word, but so are RMS statements about non-"FREE" software.
> 2. GNU and RMS have nothing to do with OSS. OSS is the ESR/P
Re:They don't get OSS (Score:1)
Re:They don't get OSS (Score:1)
Re:They don't get OSS (Score:1)
Re:They don't get OSS (Score:1)
Are you an end user? On what would you or RMS base your objection to how we treat our end users? We don't really have any end users at this point, the only thing that comes close really is our beta testing team. We have had no complaints from any of them about our "treatment" towards them. In fact, we make a point to look at the feedback from them numerous times a day and try to help them w
Re:They don't get OSS (Score:2)
Re:They don't get OSS (Score:4, Informative)
How many DIFFERENT operating systems is out there?
I count all these unix-like as only one because they are not so different and inovative from each other.
So there are (in no particular order):
-Windows
-UNIX and UNIX-like (Linux, BSD, ect)
-OSX (UNIX-like but don't use X)
In the somewhat-usable-for-the-desktop market, i think that's all. There is many other specialised OS but SkyOS want to be a desktop OS. Only three...
And don't count these os that are no longer maintained or don't have a significative market share:
-Amiga
-BeOS
-OS/2
-put your favorite unknown desktop os here
Re: (Score:2)
Re:They don't get OSS (Score:1)
Isn't it obvious? (wink) It's because they're afraid they might've misappropriated SCO's "intellectual property." (grin) I can already see it... Daryl ranting about "million and million of lines of code misappropriated by SkyOS" after their suit against the Rest of the Planet (TM) goes to pieces.
Minimize, Maximize & Close ? (Score:2, Insightful)
Re:Minimize, Maximize & Close ? (Score:1, Funny)
Re:Minimize, Maximize & Close ? (Score:2, Informative)
Re:Minimize, Maximize & Close ? (Score:1)
Re:Minimize, Maximize & Close ? (Score:2)
UI elements should immediately convey their intended purpose and function (in most cases) rather than force the user to hilight them before telling exactly what it does. Purists would say right-clicking is bad for just
Re:Minimize, Maximize & Close ? (Score:1)
Tech Support A: Click the yellow button.
vs
Tech Support B: Click the button that looks like 2 squares overlapping.
Granted, most "close window" icons are the X but what about the mini
Re:Minimize, Maximize & Close ? (Score:2)
Sounds like it was brought to us by the same committee that decided to not "clutter up" the display with underscores letting you know which Alt+letter keys did what; instead, the underscores don't appear until you hit Alt (and how would you know that hitting Alt would have any effect without the underscores to guide you?).
I'm all for advanced interface development but I do
Re:Minimize, Maximize & Close ? (Score:2, Interesting)
My findings are that the GUI is very basic and not very intuitive. I understand that a lot of work has been put into the project, but it hasn't come very far in a couple years. IIRC, most of the actions were buried in places I wouldn't think to look. I seriously doubt this OS w
Re:Minimize, Maximize & Close ? (Score:1)
Second, I really take offense to you saying that we (the developers) have poor attitudes. We have tri
Re:Minimize, Maximize & Close ? (Score:1)
Re:Minimize, Maximize & Close ? (Score:1)
I can't really say much as far your conversation with whoever you talked to, because I wasn't a part of it. If it was Robert, you would have to remember 1) he is very limited on time and doesn't generally have a whole lot of time for chit-chat (he gets many, many e-mails every day, and tons of suggestions and offers for help), and 2) his first language is not English, so he
Re:Minimize, Maximize & Close ? (Score:1)
Re:Minimize, Maximize & Close ? (Score:1)
FWIW, the text is tiny in IE6, as well.
Team? (Score:2, Funny)
knee jerk (Score:4, Insightful)
But it might not be as crazy as it sounds. Reading between the lines, it sounds like they're trying to take this closed-source hobby OS and turn it into a closed-source commercial OS. Slashdotters might have a hard time believing it, but many people are both (a) disgusted with Windows, and (b) scared to attempt Linux. Even if they succeed in capturing only 2% of the x86 market, that's still more CPUs than Apple has! Heck, with 0.2% of the x86 market they could still be quite a big, profitable company.
The Apple analogy is also interesting, because Apple has already shown how easy it is to write a proprietary OS while taking advantage of open-source tools. This could be digital miscegenation in the eyes of the Stallmanites, but it seems to have worked pretty well.
Of course, their market would always be limited. Like MacOS X, it's never gonna run the games you see on the shelf at a retail store. But plenty of people have old x86 machines running Windows 3.1 or Windows 95 that they only use for web surfing and e-mail. Those people might balk at the price of upgrading Windows, or the price of buying a Mac, but an OS that Just Works, priced at $60 or something, might be very appealing to them.
<flamebait> Maybe we should admit that no system based on shared libraries and X11 is ever going to be really easy for a naive user to install and use. </flamebait>
And let's not forget that we can't fight the Windows monoculture by poo-poohing people who want to create or use an alternative OS.
Re:knee jerk (Score:1)
I disagree. Most games on Windows are developed on DirectX, OpenGL, or SDL. The last two will become more popular in the future due to the extreme portability of the libraries. OpenGL and SDL can interact directly with the framebuffer bypassing the OS layer for graphics meaning more portability. The only real obstacle is the OS reading the binary formats or the developers writing it with portability in mind. It is not that hard to g
Re:knee jerk (Score:1)
SDL intereacts with DirectX or the Win32 API if DX isn't available.
see here [libsdl.org]
If it could bypass the OS it would have to have a driver level component. Something that runs in ring 0 (i.e. at the kernel level).
Re:knee jerk (Score:1)
I disagree. Most games on Windows are developed on DirectX, OpenGL, or SDL.
Maybe you're right, although the game developers would, e.g., have to decide it was worth their while to print "Sky OS" on the box as a system it runs on, and to offer support. (If they can't be bothered to support Mac Classic or MacOS X, I have a hard time believing they'd support SkyOS.)
But in a broader sense, what you're saying is an example of a valid res
Re:knee jerk (Score:1)
Re:knee jerk (Score:2, Informative)
Its the open and decentralized nature of Linux that allows it to succeed so well. Linux's success so far relies on one thing really, *drivers*. Linux supports a lot of hardware because hundreds of peopl
Re:knee jerk (Score:1, Informative)
That's because you're short-sighted. Who says that the SkyOS team
Re:knee jerk (Score:1)
You know, most people at least manage to say a few on-topic things before they get to the business of personal insults, yet this is your very first sentence. So, you were just tired and wanted to cut to the chase? :)
I believe the second sentence answers the question of the first sentence in the affirmative. Indeed, "of course". :)
Accelerated 3d graphics (Score:1)