I also bought two OLPC, using the "give one, get one" program, and gave the one sent to me as a Christmas gift to my nephew.
He used it and is still using it, but the main problem is: it is painfully slow.
The CPU in the XO-1 is an AMD / 433 Mhz and integrated graphics, with 64K Level 1 and 128K Level 2 Cache: I think that it simply cannot keep up with the amount of computation that its software components require.
And I do not think that Python is necessarily to blame here. I cannot say for sure without profiling, but I think that for most interactive uses the perceived performance problems are not in tight Python logic loops, but in rendering and other basic stuff which mainly happens in C libs.
Great news for me, I'll be able to continue using my favorite distribution even in the 64 bit environment. After a brief initial experience with SuSe, I went with Slack and never looked back.
I am happy of course to see that having a Linux native version is a priority at least for some developers. Too bad I really don't like Quake-like games, or any FPS. If only the RPG companies would have Linux in their mind. Like Bioware, which delivered Neverwinter Nights (thanks!), but now turned its back on us with Dragon Age.
I bought SUSE Linux together with a new computer in a small shop near my home. I specifically asked for it, since I was going to go to the university, and I needed a Unix-like system for my studies, to practice at home and work on assignments, without having to always go to the computer labs, where DEC machines and terminals were available.
The guys in the shop installed the OS for me, so I had everything already working. No network connection btw. I started messing around, and soon discovered that a game called "nethack" was installed. It blew my mind.
"With South Park's senior citizens behind the wheel, more than a few farmer's markets have been mowed down. Unwilling to surrender their driver's licenses, the elderly fight back."
My slackware 12.1 (with kernel 2.6.26 though) boots in 30 seconds, from Loading Linux to the login prompt. Then I'd go emacs -nw, but since you ruled it out, try the other already suggested simple editors (nano seems a good choice).
Just want to inform you that threads nor any other multiprogramming mechanisms are necessary for responsive user interfaces, and that IO multiplexing in particular does not require threads at all.
You can solve both with threads, but you don't have to. And in most common cases it is much better not to; it seems that threads continue to be one of the most misused and misunderstood of the programming concepts.
I agree, and in addition there is currently no context when creating a new article. It's maybe just too soon, but the process seems to make it more difficult to reach critical mass.
I wanted to start writing something, but desisted, because I found no contextual information.
On wikipedia I would read some article, see a dangling link with no page associated, and create one from there. Or read an existing one, and just add additional information, or correct some detail.
Otherwise it is hard to just start writing general, context-free articles about "what I know". Maybe they should have started with wikipedia content, applying the new process for further edits and new articles, in order to already have a lot of context already.
Premise: I was a very hopeful wine user, and even tried to contribute some small improvements to the project that never went anywhere (support for the undocumented INI empty section and empty keyname features of the profile kernel32 API), partly since I had no real windows to test on, partly since I could not establish a good dialog with the developers, partly because the applications using this undocumented behavior are not the big known apps.
Question: Currently wine strategy seems to be (correct me if I am wrong), to target one application at a time, privileging the big known apps, with less interest in supporting the smaller apps, or in breaking them with new versions: is there any chance that after getting most of the big apps working, the current strategy will be changed to focus on a more generic solution, matching the win32 API as closely as possible, in order to support most if not all of the small programs, and thus enabling much more migrations to free software-only solutions and thus achieving world domination? (http://www.catb.org/~esr/writings/world-domination/world-domination-201.html)
codeweavers _are_ the main wine developers. There are no real boundaries between the company and the free software project; this is in my opinion the cause of the divergence between the community-perceived goals of wine, and the real ones, which are far less far-reaching than I would like.
I quote the relevant part that makes me think that:
[quote] The encumbered binaries tarball contains complete binaries (libraries, kernel modules, commands) that are compatible with the source. These are binaries that cannot be built using only the source tarball for one reason or another. If you wish to build the kernel (or some portion of it), or if you wish to build a complete set of installable archives, you will want the encumbered binaries. [/quote]
The OpenSolaris project does convey code under a free software license, but there are core components which are only available as binary blobs, under non-free licenses. They are necessary to successfully run a Solaris system.
This is the OpenSolaris binary license under which most of these non-free components are distributed:
Slashdot Mirror
I find some of the features interesting, but until these problems are solved, I will not try it out.
https://btrfs.wiki.kernel.org/index.php/Gotchas
I never rated > 0;
I got either the ogres, or some sort of male or genderless body with tits.
The population is greatly decreased,
and now the odds are greatly increased,
that I may someday get a chance
to kiss your lips.
I thank the Lord each day,
for the Apocalypse.
Folks are mostly disfigured or dead,
but sugar I won't let it go to my head
My Mammas face has dripped down into the dirt,
but I'm still chasing chittlins, whiskey and skirt.
"A programmer who doesn't know C is like a doctor who doesn't know anatomy".
I will remember this; this is a very insightful comment.
Too bad I have no mod points, as I mostly do not bother to login anymore.
Missing the ground is fundamental in learning how to fly
http://www.urbandictionary.com/define.php?term=flying
See 3.
I also bought two OLPC, using the "give one, get one" program,
and gave the one sent to me as a Christmas gift to my nephew.
He used it and is still using it, but the main problem is: it is painfully slow.
The CPU in the XO-1 is an AMD / 433 Mhz and integrated graphics, with 64K Level 1 and 128K Level 2 Cache: I think that it simply cannot keep up with the amount of computation that its software components require.
And I do not think that Python is necessarily to blame here.
I cannot say for sure without profiling, but I think that for most interactive uses the perceived performance problems are not in tight Python logic loops, but in rendering and other basic stuff which mainly happens in C libs.
http://video.google.com/videoplay?docid=7951038502689013454
Great news for me, I'll be able to continue using my favorite distribution even in the 64 bit environment. After a brief initial experience with SuSe,
I went with Slack and never looked back.
I am happy of course to see that having a Linux native version is a priority at least for some developers.
Too bad I really don't like Quake-like games, or any FPS.
If only the RPG companies would have Linux in their mind. Like Bioware, which delivered Neverwinter Nights (thanks!), but now turned its back on us with Dragon Age.
To Somalia! Clear blue waters with skull islands...
http://www.southparkstudios.com/episodes/220764/
I bought SUSE Linux together with a new computer in a small shop near my home.
I specifically asked for it, since I was going to go to the university, and I needed a Unix-like system for my studies, to practice at home and work on assignments, without having to always go to the computer labs, where DEC machines and terminals were available.
The guys in the shop installed the OS for me, so I had everything already working. No network connection btw.
I started messing around, and soon discovered that a game called "nethack" was installed.
It blew my mind.
We need a poll. I vote for the penguin doctor video
The penguin doctor video was much better. Btw, the linuxfoundation.org site is already /.ed, so
http://www.youtube.com/watch?v=svaHnha-PXs
I did:
http://www.niceties.it/google_tags_google_as_malware.png
"With South Park's senior citizens behind the wheel, more than a few farmer's markets have been mowed down. Unwilling to surrender their driver's licenses, the elderly fight back."
http://www.southparkstudios.com/episodes/103856/
My slackware 12.1 (with kernel 2.6.26 though) boots in 30 seconds, from Loading Linux to the login prompt.
Then I'd go emacs -nw, but since you ruled it out, try the other already suggested simple editors
(nano seems a good choice).
Reading these comments I am distracted by a loud "whooooosh!" of a great joke passing over everybody's head.
Just want to inform you that threads nor any other
multiprogramming mechanisms are necessary for
responsive user interfaces,
and that IO multiplexing in particular does not require
threads at all.
You can solve both with threads, but you don't have to.
And in most common cases it is much better not to;
it seems that threads continue to be one of the most
misused and misunderstood of the programming concepts.
I agree, and in addition there is currently
no context when creating a new article.
It's maybe just too soon, but the process seems
to make it more difficult to reach critical mass.
I wanted to start writing something, but
desisted, because I found no contextual information.
On wikipedia I would read some article, see a
dangling link with no page associated, and create
one from there. Or read an existing one, and
just add additional information, or correct
some detail.
Otherwise it is hard to just start writing
general, context-free articles about
"what I know". Maybe they should have started
with wikipedia content, applying the new process
for further edits and new articles, in order
to already have a lot of context already.
Premise:
I was a very hopeful wine user, and even tried to contribute
some small improvements to the project that never went anywhere
(support for the undocumented INI empty section and empty keyname
features of the profile kernel32 API), partly since I had
no real windows to test on, partly since I could not establish
a good dialog with the developers, partly because the applications
using this undocumented behavior are not the big known apps.
Question:
Currently wine strategy seems to be (correct me if I am wrong),
to target one application at a time, privileging the big known
apps, with less interest in supporting the smaller apps,
or in breaking them with new versions:
is there any chance that after getting most of the big apps
working, the current strategy will be changed to focus on a
more generic solution, matching the win32 API as closely as
possible, in order to support most if not all of the small
programs, and thus enabling much more migrations to free
software-only solutions and thus achieving world domination?
(http://www.catb.org/~esr/writings/world-domination/world-domination-201.html)
Thank you -
codeweavers _are_ the main wine developers.
There are no real boundaries between the company and the free software project;
this is in my opinion the cause of the divergence between
the community-perceived goals of wine, and the real ones, which are far
less far-reaching than I would like.
No.
When hiring, take your best developers into the process.
They recognize people like them in a very short time,
with very few questions.
That was a good answer. Specifically, I would follow the examples of firefox,
thunderbird (free), acrobat reader for unix (proprietary), and go GTK+.
NexentaOS includes an OpenSolaris kernel in its installable images,
which means it must contain some proprietary code as far as I
understand.
See the OpenSolaris README:
http://dlc.sun.com/osol/on/downloads/20071203/README.opensolaris
I quote the relevant part that makes me think that:
[quote]
The encumbered binaries tarball contains
complete binaries (libraries, kernel modules, commands) that are
compatible with the source. These are binaries that cannot be built
using only the source tarball for one reason or another. If you wish
to build the kernel (or some portion of it), or if you wish to build a
complete set of installable archives, you will want the encumbered
binaries.
[/quote]
The OpenSolaris project does convey code under a free software
license, but there are core components which are only available as
binary blobs, under non-free licenses. They are necessary to
successfully run a Solaris system.
This is the OpenSolaris binary license under which most of these
non-free components are distributed:
http://opensolaris.org/os/licensing/opensolaris_binary_license/