If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Might as well give up. That is the shittiest development speed I've ever seen. 20k LOC in 5 fucking years? My grandma codes faster than that and she's dead! 70k LOC from 100 devs? Hahahaha. Such a joke is wayland and weston. They code like they're just figuring out programming. They should just admit failure already.
Yeah, how dare they try to keep the keep base lean and focused.
Let me guess, if it was a lot of lines of code, you would be complaining about it being bloated.
When you're creating API and protocols, seems to me you spend most of the time designing, documenting and little time coding.
I don't know what you expected to look like by making such comment.
Roughly 1 million for the server, according to Ohloh. http://www.ohloh.net/p/xorg-server
There are two repository entries though, so migth be that its actually ~500K
2.5M for the whole project, though this also includes things that Wayland can/will make use of, like Mesa. http://www.ohloh.net/p/x
Thanks, that's an interesting comparison. I realise they're not directly comparable, but when the X server is many times the size in terms of codebase then it really hits home how much more streamlined Wayland is.
Roughly 1 million for the server, according to Ohloh. http://www.ohloh.net/p/xorg-server
There are two repository entries though, so migth be that its actually ~500K
2.5M for the whole project, though this also includes things that Wayland can/will make use of, like Mesa. http://www.ohloh.net/p/x
not really. but I often get the impression that people think that wayland needs a lot of work. not really. mesa, toolkits, cairo, WMs need lot of work. even the whole GDM/login issue thing is not resolved yet. wayland by itself is basically done.
wayland by itself is nothing. it's basically DRI on steroids. all rendering is directly from applications to the compositor. the hard work is porting the toolkits and WMs, not writing "wayland code". is mutter even wayland ready yet? i know gtk is basically done
I'm fully aware of that. Want Phoronix to check for every project that had plans on supporting Wayland? I'm not taking the time of doing so.
Leave a comment: