What Perens is saying is that is own consulting company will offer support for KDE as a service provider. Gnome is still the only chosen GUI for UserLinux.
The next release of Evolution will be 1.6, not 2.0. In fact, Ximian's bugzilla shows 1.6 as a possible target milestone, and the evolution-hackers mailing list has messages regarding the improvements in the next 1.6 release.
Well, if you are into Test Driven Development, you test your code as often as possible. In my current project (based on Smalltalk) I run my tests every couple of minutes: In a C++ project, this could be impossible, due to longer compilation time. And precompiled header and incremental linking do not help in this case.
His issue is not with compilation per se, but with the traditional edit-compile-debug cycle which has limited scalability (as your code grows larger, the wait time to see if your code works increases). Both C and C++ have this problem. Some languages like Smalltalk and Common LISP, due to their incremental compilation system, are not affected by this problem.
AFAIK, KJS is based on ECMAScript Edition 3 (implemented in JavaScript 1.5 and JScript 5.5). QSA is based on the forthcoming Edition 4, which is way different from the previous version. (Edition 4 is implemented in JScript.NET and the yet-to-be-released JavaScript 2.0). To learn more on ECMAScript v. 4, see here.
Why should I have to write a unit test suite that implements defacto type checking when I can offload that to the compiler vendor?
But you still have to write a unit test suite to test the behaviour of your types, and that is a thing that you can't offload to the compiler. And if these tests implement the type checking, well, thats a plus:-)
A compiler vendor has far more resources to bring to the problem, and can often go to the extent of using formal methods to insure correctness.
But these methods can insure syntax correctness only, not the semantic correctness.
If you are going the Wiki route, I suggest you evaluate ZWiki. Zwiki is a Zope product that adds Wiki capabilities to Zope. this gives you the flexibility of a Wiki with the power of the Zope framework.
Then use Smalltalk. It is fast, expressive, easy (it has just six grammar rules). It has a state-of-the-art garbage collector, an advanced JIT engine , and many other useful features.
On the other hand, the police seemed to act more like 15-year-old hackers than police. They "...used a suspect's computer and password to reach across the ocean and replace the offending images with the insignia of the special police unit that tracked him down." That really doesn't seem very professional to me.
Actually, they were following Italian laws provisions, which require the police to put their seal on materials which are under investigation.
Actually, I was a little pissed at first that the GNOME hackers had decided to remove viewports, but after using GNOME 2.0 snapshots for a while, I think that they were right in removing them.
The GNOME guys had realized that most people were using either viewports or workspaces, not both. They decided to remove such a code duplication, unifying the two things. They could have called them viewports, but maybe they thought that more people would have bitched for that:-).
So please don't file a bug asking for viewports return before having tried the GNOME 2 desktop. Try it first, and if you think that something is still missing, then, and only then, file a report.
The GNOME 2 guys have made great strides in term of usability and simplicity. Give them a little trust.
Re:.NET is overall a good thing.
on
Java v. .Net?
·
· Score: 1
FYI, Mono has become self hosting on Linux since yesterday (Mar 27)
It is absolutelly useless, and dangerous too, to choose a development platform before addressing the nature of the problem. There is no language and development platform suitable for every class of problem, no matter what MS, Sun etc. are saying. Another issue you should address your development process, and how the various development platforms suit in the process.
That said, I suggest you may investigate also SmallTalk. Once you get the hang on the language, you'll find it has one of the most productive IDEs ever created.
I'm not sure how much mainstream acceptance is possible for any paradigm that incorporates a faddish name like 'extreme'
There are signs that the name will change from 'Extreme' to 'Agile'. This for two reasons:
1) It's easier to sell to the management an 'agile' development process than an 'extreme' one.
2) There are plans for melding the many agile development techniques in just one discipline.
These two things give me nightmares remembering customers who have had cute ideas at the last minute. Other than that is looks like the waterfall model.
Each and every model looks like waterfall. The difference between the various models is the amount of feedbask between phases that the models allow (I'm simplifying, of course). Extreme Programming takes the feedback to the limit, by use of methods like continuous integration, on site customer, minumum bureaucracy. The goal here is to give the customer something valuable ASAP.
I can't but confirm the initial impressions on the IDE. I haven't used it for long, but I have read some of the tutorials on eclipse.org. It seems that by using their own widget toolkit (SWT? - can't remember the name now) they have obtained something faster than a Swing app, and prettier than an AWT one. Writing a plug-in for the framework doesn't seem too difficult, too.
I was also thinking about trying to fetch the source code to gcj, in order to have a more responsive app. Has anyone tried this yet?
The overturning of Marconi's patent was due to the fact that Marconi's company had sued the US Government for patent infringement during World War I. The quickest way of solving the problem was overturning the patent, and so they did.
I think that they are going to attract users in the 'corporate desktop' market. Sun is going to replace CDE with GNOME 2.0. HP will be shipping GNOME 2.0 with HP-UX, too. I feel that focusing on this market niche is The Right Thing To Do.
KDE has focused more on the 'home/small office desktop' market, but it is going to compete with Windows (and maybe MacOS X) there. Once GNOME 2.0 has reached the same integration of CDE (and this will happen soon), it will easily win the competion with CDE.
To all who complain about the too many features of GNOME (compared with CDE):
You can strip GNOME down to resemble CDE. It doesn't take much time to set your enviroment this way. Hey, you can even have your window manager look like olvwm, if you like.
So, all this comments 'GNOME has too many graphical features, I'm afraid of it' are just nonsense, IMHO.
Slashdot Mirror
What Perens is saying is that is own consulting company will offer support for KDE as a service provider. Gnome is still the only chosen GUI for UserLinux.
That's what they're doing: Linux leaders offer education discounts
Using the Workspace Switcher, just drag & drop the window you want to move into the other workspace, the switch to that workspace
The next release of Evolution will be 1.6, not 2.0. In fact, Ximian's bugzilla shows 1.6 as a possible target milestone, and the evolution-hackers mailing list has messages regarding the improvements in the next 1.6 release.
Well, if you are into Test Driven Development, you test your code as often as possible. In my current project (based on Smalltalk) I run my tests every couple of minutes: In a C++ project, this could be impossible, due to longer compilation time. And precompiled header and incremental linking do not help in this case.
So, basically, it has to be compiled (duh)
His issue is not with compilation per se, but with the traditional edit-compile-debug cycle which has limited scalability (as your code grows larger, the wait time to see if your code works increases). Both C and C++ have this problem.
Some languages like Smalltalk and Common LISP, due to their incremental compilation system, are not affected by this problem.
AFAIK, KJS is based on ECMAScript Edition 3 (implemented in JavaScript 1.5 and JScript 5.5). QSA is based on the forthcoming Edition 4, which is way different from the previous version. (Edition 4 is implemented in JScript.NET and the yet-to-be-released JavaScript 2.0).
To learn more on ECMAScript v. 4, see here.
In GPL's mindframe, each user is potentially a developer. And this is both a strength and a weakness of the GPL.
Why should I have to write a unit test suite that implements defacto type checking when I can offload that to the compiler vendor?
:-)
But you still have to write a unit test suite to test the behaviour of your types, and that is a thing that you can't offload to the compiler. And if these tests implement the type checking, well, thats a plus
A compiler vendor has far more resources to bring to the problem, and can often go to the extent of using formal methods to insure correctness.
But these methods can insure syntax correctness only, not the semantic correctness.
You forgot one:
78) Profit.
If you are going the Wiki route, I suggest you evaluate ZWiki. Zwiki is a Zope product that adds Wiki capabilities to Zope. this gives you the flexibility of a Wiki with the power of the Zope framework.
Then use Smalltalk. It is fast, expressive, easy (it has just six grammar rules). It has a state-of-the-art garbage collector, an advanced JIT engine , and many other useful features.
You may try Kannel. Its is a free open source WAP and SMS gateway.
I dunno, man. You can't get stoned with an Internet Phone.
On the other hand, the police seemed to act more like 15-year-old hackers than police. They "...used a suspect's computer and password to reach across the ocean and replace the offending images with the insignia of the special police unit that tracked him down." That really doesn't seem very professional to me.
Actually, they were following Italian laws provisions, which require the police to put their seal on materials which are under investigation.
Actually, I was a little pissed at first that the GNOME hackers had decided to remove viewports, but after using GNOME 2.0 snapshots for a while, I think that they were right in removing them.
:-).
The GNOME guys had realized that most people were using either viewports or workspaces, not both. They decided to remove such a code duplication, unifying the two things. They could have called them viewports, but maybe they thought that more people would have bitched for that
So please don't file a bug asking for viewports return before having tried the GNOME 2 desktop. Try it first, and if you think that something is still missing, then, and only then, file a report.
The GNOME 2 guys have made great strides in term of usability and simplicity. Give them a little trust.
FYI, Mono has become self hosting on Linux since yesterday (Mar 27)
It is absolutelly useless, and dangerous too, to choose a development platform before addressing the nature of the problem. There is no language and development platform suitable for every class of problem, no matter what MS, Sun etc. are saying. Another issue you should address your development process, and how the various development platforms suit in the process.
That said, I suggest you may investigate also SmallTalk. Once you get the hang on the language, you'll find it has one of the most productive IDEs ever created.
There are signs that the name will change from 'Extreme' to 'Agile'. This for two reasons:
1) It's easier to sell to the management an 'agile' development process than an 'extreme' one.
2) There are plans for melding the many agile development techniques in just one discipline.
These two things give me nightmares remembering customers who have had cute ideas at the last minute. Other than that is looks like the waterfall model.
Each and every model looks like waterfall. The difference between the various models is the amount of feedbask between phases that the models allow (I'm simplifying, of course). Extreme Programming takes the feedback to the limit, by use of methods like continuous integration, on site customer, minumum bureaucracy. The goal here is to give the customer something valuable ASAP.
I was also thinking about trying to fetch the source code to gcj, in order to have a more responsive app. Has anyone tried this yet?
The overturning of Marconi's patent was due to the fact that Marconi's company had sued the US Government for patent infringement during World War I. The quickest way of solving the problem was overturning the patent, and so they did.
KDE has focused more on the 'home/small office desktop' market, but it is going to compete with Windows (and maybe MacOS X) there. Once GNOME 2.0 has reached the same integration of CDE (and this will happen soon), it will easily win the competion with CDE.
To all who complain about the too many features of GNOME (compared with CDE):
You can strip GNOME down to resemble CDE. It doesn't take much time to set your enviroment this way. Hey, you can even have your window manager look like olvwm, if you like.
So, all this comments 'GNOME has too many graphical features, I'm afraid of it' are just nonsense, IMHO.