Agreed with the general lack of algorithm experience. However, this knowledge can still be obtained professionally. I think, if you can't say "look at my degree", you should be able to say "look at all this software I've built over the past four years, it proves I know a thing or two".
I haven't actually dumped an open source application in favour of a proprietary alternative because it was difficult to install. I could, however, completely understand why some users after attempting to install and configure open source applications would make the move. The installation and initial configuration experience is the first impression and is important to get right. It is the first impression the software gives as to how good/usable/stable it really is. How can you get feedback regarding other aspects of the software if they can't get past step one?
Our flexible hours have come in handy on more than one occasion. Our leaders realize that it doesn't matter when during the the day it gets done as long as deadlines are met.
It comes down to irresponsible end users. If they are able to successfully sue an open source developer for a bug is besides the point. If the end user cannot comprehend use at your own risk, they are in much deeper trouble and the resulting lawsuit victory will not help them in the long run.
Submit a bug report and be helpful about it. With bugs in open source software you can become the number one enemy of the developer(s) you sue, or you could potentially be credited in the subsequent release. Seems like a no-brainer to me...
We used to use Zimbra until about three years ago when we migrated to Gmail. I haven't used it since but I always loved the UI. It sounds like it is worth playing with again.
Pascal is a great teaching language. I was taught Pascal in high school and it served as a great introduction to recursion. Our instructor walked us through the steps to drawing Sierpinski triangles on the screen. I suppose it is a combination of both language and teaching methodology.
Slashdot Mirror
"Hard disks are banned" seems like it would be a show-stopper for many folks.
Agreed. If the comment is difficult to follow, odds are the code will also be difficult to understand.
Agreed with the general lack of algorithm experience. However, this knowledge can still be obtained professionally. I think, if you can't say "look at my degree", you should be able to say "look at all this software I've built over the past four years, it proves I know a thing or two".
I wonder if these code improvements lead to overall usability. That seems to be the biggest stumbling block for open source, not stability.
They fade away.
The usefulness of such technology simply isn't there. So why bother with it? I guess it just sounds cool.
Within programmer month, a day is dedicated to developers for a certain language. Except, of course, Java developers.
I haven't actually dumped an open source application in favour of a proprietary alternative because it was difficult to install. I could, however, completely understand why some users after attempting to install and configure open source applications would make the move. The installation and initial configuration experience is the first impression and is important to get right. It is the first impression the software gives as to how good/usable/stable it really is. How can you get feedback regarding other aspects of the software if they can't get past step one?
I guess the next best thing would be a library that handles the thread pooling and figures out how to manage things.
Agreed. There is no need to feel shame for getting something functional out the door.
I concur in that there really shouldn't be a need for an external library outside of the browser in order to maintain a server connection.
Supporting it is not an option.
Canada isn't any better than the US. Any time I browse available jobs, the ones that interest me the most seem to be in the EU.
Although, these tools will slowly decline in use as well once former Windows users are forced to use alternatives.
Our flexible hours have come in handy on more than one occasion. Our leaders realize that it doesn't matter when during the the day it gets done as long as deadlines are met.
It comes down to irresponsible end users. If they are able to successfully sue an open source developer for a bug is besides the point. If the end user cannot comprehend use at your own risk, they are in much deeper trouble and the resulting lawsuit victory will not help them in the long run. Submit a bug report and be helpful about it. With bugs in open source software you can become the number one enemy of the developer(s) you sue, or you could potentially be credited in the subsequent release. Seems like a no-brainer to me...
Perhaps this should be known as the twitter effect.
Any javascript could potentially drain the CPU if it is computationally hungry.
OSS is only expensive in terms of effort. This search is seriously flawed.
I think exploring some various state machine configurations would help here.
Indeed. This is a rather important piece of software historically. Nice to see it still being released.
One of the few downsides to open source software.
We used to use Zimbra until about three years ago when we migrated to Gmail. I haven't used it since but I always loved the UI. It sounds like it is worth playing with again.
I tend to like the brief, developer-only meetings. As a developer, everything else seems to be unnecessarily long and irritating.
Pascal is a great teaching language. I was taught Pascal in high school and it served as a great introduction to recursion. Our instructor walked us through the steps to drawing Sierpinski triangles on the screen. I suppose it is a combination of both language and teaching methodology.