What I said is that it's not just a.NET knockoff. Note the 'just'.
Part of it sure is reimplementation of.NET Framework (and/not/ the.NET Framework itself). The rest is support for the GNOME (and Linux in general) -specific parts. This includes Gtk#, DBUS and HAL support, Apache support.
In other words, Mono is.NET, embraced and extended. With generics already working in CVS (as far as I know).
Mono is currently focused on properly wrapping Gtk and GNOME functionality (pure wrappers, without going through Forms). There are already a few apps that use this, and at least one is IMHO a potential killer app (namely Dashboard).
It goes without saying that both Gtk and Gtk# (Gtk wrapper for Mono) work on Windows, too. So you don't lose cross-platform angle, but this does show that Mono is *not* just a.NET knockoff.
> And all of these either have either costs, drawbacks, or don't really solve the problem (i.e. Bayesian filter on MUAs don't avoid the traffic etc.), while I can't for the life of me find anything bad on the thoughts of spammer rotting in jail.
In addition to this, suggestions that the end-users take the burden neglects the basic moral principle. Spammers/should/ go to jail.
(if you haven't read Vernor Vinge's Deepness in the Sky, do so now;) )
It's really funny how the end-of-civilisation scenarios mentioned in the book become reality. In particular, this is a case of his over-efficiency scenario: as the automation and control systems become more efficient, the margin for error gets narrower, until even a minor glitch can escalate to affect a large proportion of the planet. This happens in part because no single person fully understands the structure of the control mechanisms, so the catastrophic scenarios can't be predicted.
(the other scenario I remembered was ubiquitous law enforcement. Things like RFID tags, smart dust, and ubiquitous surveilance are all becoming possible)
That said, I don't think we're going to have the end of the world. But there will have to be some fundamental changes in the way we design and use the technology.
Actually open the mixer (in GNOME, it's right-click on the speaker in the panel, select it from the menu). Then lower the PCM slider from the max. Then also lower the master volume off from the max.
SB Live! likes to distort the sound when either slider is topped, which AFAIK is not the linux' fault.
> Brooks said it took some time to convince Disney attorneys that he wanted to pay for the development of the porting solution but did not want to own it. However, Disney's legal department has developed a policy that enables Disney to protect its intellectual property while keeping within the statutes of the GNU General Public License, he said.
> I'd also appreciate RenderMan-style shaders. While I have yet to find a material I can't emulate fairly convincingly using Blender's materials, the ugly hacks I've had to do to get them make me think shaders would be a tad easier for some of the stranger materials.
Renderman export is in Tuhopuu tree already. Somebody also wrote a new connect-the-boxes material editor and is interested into integrating it into Blender (check the forums on blender.org for details).
Open your computer, and read the 'Made in...' stickers. Most of them don't say Taiwan any more.
Now go around your house and read more 'Made in...' stickers.
It's not the technology, it's the finance and (cheap) workforce and know-how and willingness to use the technology. US may get there in 20 years, you know...
--
Re:Too bad it's only a case-mod
on
Ant Farm PC
·
· Score: 2, Funny
Just to stress the main feature of the Hex: ANTHILL INSIDE.:)
> Most of them don't know or even consider that it IS stealing. DON'T STEAL MUSIC was part of the message sent buy the RIAA (Apple is still innovating the industry, in more ways than one. Remember when the iPod first came out....) and this is something we should really think about.
It is NOT stealing. It's copyright infringement. And RIAA is guilty of the crime of abusing the language. Think about it for a second: they made people rename a very abstract crime (which in fact used to be a misdemeanor in 70's and 80's) into an emotionally loaded word. That is something we should really-really think about.
Indeed. It comes out of the factory with builtin liquid cooling. I wouldn't mind more memory bandwidth, either... damn, where did I put those keys again?!
I strongly disagree with the article. I can tell you for *sure* that neither my C nor my C++ code suffer from buffer overflows. How do I know? Because I don't use buffers. For a lot of my C code I don't even allocate my memory by hand (I'm a proponent of garbage collection, and yes, it can be done in C); for a lot of my C++ code, I don't even bother - STL handles most of my memory management needs, some strategically placed magic classes handle the rest. Furthermore, most experienced C/C++ programmers also do these kinds of things.
What's becoming the real issue is that more and more subsystems are getting integrated into larger chunks. On Windows, the integration is a major marketing point, and also an endless source of nightmares, since the systems that work just fine on their own begin to interact in unpredictable and dangerous ways when linked. This is beginning to happen on Linux, with the similar effects; however, most programmers are smart enough to know when the integration gets dangerous.
Basically, most modern OSes are becoming more complex than we can fathom. Hence the breakage, regardless of the programming language.
The comics you mention are all spandex - in that sense, American comics are a failure, as they can't seem to come up with real plots about real people and still become household names. Not to mention that the actual *numbers* on the Japanese Manga sales put any publishing industry (except Holywood) to shame. The article mentions $2 bil.
When I asked about my literary preferences, I generally refer to SF as SF&F - I tend to read SF and fantasy in about equal ammounts. That said, my favorites on the SF side are David Brin (anything written by him), William Gibson, and Peter F. Hamilton. On the fantasy side, Tolkien (need you ask?) and Ursula LeGuin.
I guess what attracts me is bold imagination/and/ quality writing. I do require both interesting story and interesting characters to get into a book.
Incidentally, my favorite world is Larry Niven's Smoke Ring... It's a pure childhood dream-of-flight. I wish the characters he put in there weren't so flat.
--
Re:Why do they all go to GTK/GNOME?
on
Mozilla 1.2 Unleashed
·
· Score: 5, Interesting
In the case of Mozilla, they needed a lightweight windowing system abstraction (on top of which they built their own set of widgets), and gdk was the right choice. GDK is a layer underneath Gtk, and it provides a lightweight portability system sitting directly on Xlib. Qt (AFAIK) has something similar, but Qt's portability layer is canvas-like (again AFAIK), which isn't so convenient if all you want is simplified drawing primitives.
OO.O is benefitting from Ximian work, and that naturally involves GNOME.
Sun/HP/the rest of the CDE people wanted something that can easily replace Motif in all the places where Motif appears. Since this means a lot of legacy pure-C apps, Gtk seemed a natural choice, too.
So in each case, it was a different issue, rather than a single, obviously decisive feature.
As for the technical differences, yes, Gtk and Qt are different, but not as much as the advocates of either like to think (personally I prefer Gtk/GNOME, but the only strong technical reasons I can name are bonobo-activation, atk and gstreamer systems, which I consider uber-cool, but not absolutely essential).
It still beats Sailor Moon dubbed in Croatian that they're playing here. The language path, as far as I could tell, was Japanese->English->German->Croatian. If you ever read Vernor Vinge's Fire Upon the Deep, it's just as bad as long language path translations found in the book.
Of course, Sailor Moon is bad to begin with, but this got downright ridiculous.
Slashdot Mirror
What I said is that it's not just a .NET knockoff. Note the 'just'.
.NET Framework (and /not/ the .NET Framework itself). The rest is support for the GNOME (and Linux in general) -specific parts. This includes Gtk#, DBUS and HAL support, Apache support.
.NET, embraced and extended. With generics already working in CVS (as far as I know).
Part of it sure is reimplementation of
In other words, Mono is
--
Mono is currently focused on properly wrapping Gtk and GNOME functionality (pure wrappers, without going through Forms). There are already a few apps that use this, and at least one is IMHO a potential killer app (namely Dashboard).
.NET knockoff.
It goes without saying that both Gtk and Gtk# (Gtk wrapper for Mono) work on Windows, too. So you don't lose cross-platform angle, but this does show that Mono is *not* just a
--
> And all of these either have either costs, drawbacks, or don't really solve the problem (i.e. Bayesian filter on MUAs don't avoid the traffic etc.), while I can't for the life of me find anything bad on the thoughts of spammer rotting in jail.
/should/ go to jail.
In addition to this, suggestions that the end-users take the burden neglects the basic moral principle. Spammers
--
(if you haven't read Vernor Vinge's Deepness in the Sky, do so now ;) )
It's really funny how the end-of-civilisation scenarios mentioned in the book become reality. In particular, this is a case of his over-efficiency scenario: as the automation and control systems become more efficient, the margin for error gets narrower, until even a minor glitch can escalate to affect a large proportion of the planet. This happens in part because no single person fully understands the structure of the control mechanisms, so the catastrophic scenarios can't be predicted.
(the other scenario I remembered was ubiquitous law enforcement. Things like RFID tags, smart dust, and ubiquitous surveilance are all becoming possible)
That said, I don't think we're going to have the end of the world. But there will have to be some fundamental changes in the way we design and use the technology.
--
You didn't bother looking into the packages they distribute, did you? Their .display files are XML.
--
What follows is the patch to change all the occurences of the word flamewar with flamewaur. ;)
--
Actually open the mixer (in GNOME, it's right-click on the speaker in the panel, select it from the menu). Then lower the PCM slider from the max. Then also lower the master volume off from the max.
SB Live! likes to distort the sound when either slider is topped, which AFAIK is not the linux' fault.
--
> Brooks said it took some time to convince Disney attorneys that he wanted to pay for the development of the porting solution but did not want to own it. However, Disney's legal department has developed a policy that enables Disney to protect its intellectual property while keeping within the statutes of the GNU General Public License, he said.
Does anybody know that the problem was?
--
> I'd also appreciate RenderMan-style shaders. While I have yet to find a material I can't emulate fairly convincingly using Blender's materials, the ugly hacks I've had to do to get them make me think shaders would be a tad easier for some of the stranger materials.
Renderman export is in Tuhopuu tree already. Somebody also wrote a new connect-the-boxes material editor and is interested into integrating it into Blender (check the forums on blender.org for details).
--
Nah, this one only uses NT to manage the reactor control rods. :)
--
1'v h33rd dat g0v7's l15t3|\|1|\|g. Wh4ts 4ll di5 54r5 th1|\|g? 4nyw3y, l3t d3m c3n5or th15!
;)
Although I suspect this might be tad more difficult with Chinese letters.
--
Open your computer, and read the 'Made in...' stickers. Most of them don't say Taiwan any more.
Now go around your house and read more 'Made in...' stickers.
It's not the technology, it's the finance and (cheap) workforce and know-how and willingness to use the technology. US may get there in 20 years, you know...
--
Just to stress the main feature of the Hex: ANTHILL INSIDE. :)
--
SCO seems to continue the tried and true tradition. See the relevant Jargon File entry.
--
> Most of them don't know or even consider that it IS stealing. DON'T STEAL MUSIC was part of the message sent buy the RIAA (Apple is still innovating the industry, in more ways than one. Remember when the iPod first came out....) and this is something we should really think about.
It is NOT stealing. It's copyright infringement. And RIAA is guilty of the crime of abusing the language. Think about it for a second: they made people rename a very abstract crime (which in fact used to be a misdemeanor in 70's and 80's) into an emotionally loaded word. That is something we should really-really think about.
--
Indeed. It comes out of the factory with builtin liquid cooling. I wouldn't mind more memory bandwidth, either... damn, where did I put those keys again?!
--
Toroids do arise more naturaly in 4 dimensions, where they're simply S^1 x S^1.
;)
As for your second comment, FTL travel is physics and therefore trivial.
--
I strongly disagree with the article. I can tell you for *sure* that neither my C nor my C++ code suffer from buffer overflows. How do I know? Because I don't use buffers. For a lot of my C code I don't even allocate my memory by hand (I'm a proponent of garbage collection, and yes, it can be done in C); for a lot of my C++ code, I don't even bother - STL handles most of my memory management needs, some strategically placed magic classes handle the rest. Furthermore, most experienced C/C++ programmers also do these kinds of things.
What's becoming the real issue is that more and more subsystems are getting integrated into larger chunks. On Windows, the integration is a major marketing point, and also an endless source of nightmares, since the systems that work just fine on their own begin to interact in unpredictable and dangerous ways when linked. This is beginning to happen on Linux, with the similar effects; however, most programmers are smart enough to know when the integration gets dangerous.
Basically, most modern OSes are becoming more complex than we can fathom. Hence the breakage, regardless of the programming language.
--
They used Visual Basic. *gag*
Read the article.
The comics you mention are all spandex - in that sense, American comics are a failure, as they can't seem to come up with real plots about real people and still become household names. Not to mention that the actual *numbers* on the Japanese Manga sales put any publishing industry (except Holywood) to shame. The article mentions $2 bil.
--
Surely you mean Kylix.NET and #Builder. :)
--
Ah, right. They have one of those on NCC-1701-D's holodeck. :)
--
When I asked about my literary preferences, I generally refer to SF as SF&F - I tend to read SF and fantasy in about equal ammounts. That said, my favorites on the SF side are David Brin (anything written by him), William Gibson, and Peter F. Hamilton. On the fantasy side, Tolkien (need you ask?) and Ursula LeGuin.
/and/ quality writing. I do require both interesting story and interesting characters to get into a book.
I guess what attracts me is bold imagination
Incidentally, my favorite world is Larry Niven's Smoke Ring... It's a pure childhood dream-of-flight. I wish the characters he put in there weren't so flat.
--
In the case of Mozilla, they needed a lightweight windowing system abstraction (on top of which they built their own set of widgets), and gdk was the right choice. GDK is a layer underneath Gtk, and it provides a lightweight portability system sitting directly on Xlib. Qt (AFAIK) has something similar, but Qt's portability layer is canvas-like (again AFAIK), which isn't so convenient if all you want is simplified drawing primitives.
OO.O is benefitting from Ximian work, and that naturally involves GNOME.
Sun/HP/the rest of the CDE people wanted something that can easily replace Motif in all the places where Motif appears. Since this means a lot of legacy pure-C apps, Gtk seemed a natural choice, too.
So in each case, it was a different issue, rather than a single, obviously decisive feature.
As for the technical differences, yes, Gtk and Qt are different, but not as much as the advocates of either like to think (personally I prefer Gtk/GNOME, but the only strong technical reasons I can name are bonobo-activation, atk and gstreamer systems, which I consider uber-cool, but not absolutely essential).
--
It still beats Sailor Moon dubbed in Croatian that they're playing here. The language path, as far as I could tell, was Japanese->English->German->Croatian. If you ever read Vernor Vinge's Fire Upon the Deep, it's just as bad as long language path translations found in the book.
Of course, Sailor Moon is bad to begin with, but this got downright ridiculous.
--