[Prev][Next][Index][Thread]
Re: GPL Liscensing on New Release: What Gives?
Licensing...UGH....
the reason I checked out oskit was so I could write an OS without worrying
about this person and that...whose code ya got....
ugh....I thought writing an OS with the kit would alieviate licensing
problems.
I'm just going to continue writing my OS from scratch.
I'm a professional developer who got into computers as a hobby, and writing
an OS is a HOBBY thing for me...(for now)....anyway, I'm not going to use
the OSKIT simply because of the licensing and some other issues.
NOTE: To the oskit developers: You guys are awesome...and I think I'm pretty
good too...so as you must enjoy the OSKIT project...I'm just enjoying Mine.
I think your stuff will be more marketable, support more hardware, and much
more "RealWorld" usable because of your UNIX ties. Keep up the good work as
we can't let Microsoft be the only ones who know what Assembly Language and
OS development really are!
I want to write my own for the following reasons:
#1: Do not want anyone being able to say I stole thier code
#2: I want to benchmark (My) OS whose main kernal and support programs and
libraries are written in PURE Assembly Language against a C\C++ counterpart
like Win98
#3: I want to write an OS that is not obscure for users. That is, I want an
operating system thats fast like linux, but easy to setup like win95/98(on a
good day).
#4: I want to try my hand at writing my own assembler, my own C compiler,
and eventually a C++ compiler.
#5: I want an operating system that utilizes Parallel processing to its
fullest potential....from the very core of the operating system...so even
the operating system can share workload across processors...and networked
machines.
Note: So Far I have a Decent Filesystem that is not FAT based, does not use
a BAM, and can read files quickly both forward and backwards
But that's just me :)
Jason Sage
Follow-Ups: