Did they do any serious research on how much their choice of cartridge over cd-rom, and that mini-cd-thingy over DVD have cost them?
I think they repeated the same mistake, in a market full with gurus....
They fought piracy and they lost, obviously. Yes I think Sony won a lot, by leaving a small space for piracy.
Many people I know, bought several pirated CDs, and few original. Yet they bought nothing of Nintendo.
I was hurt when you said I should seek a non-technical job.
But since you was nice enough to notice my post and reply. I have to return the favor.
I am not saying I am good, but I honestly want to be good (in term of programming skills). I whole heartdely believe that the best way is to have a broad view of the issue, when it comes to programming this translate to learning different languages that implement the multitude of programming paradigms ever invented.
I do believe, that solve a problem, in terms of OOP is not simple, I wasn't saying it's beyond me, I am just saying it's hard. And honestly most book, dump down this fact.
To solve a problem you need a plan, to execute a plan (in OOP) you need actors, actions in the plan, will be the responsibility of specifice actor.
I was being quick in representing my view of OOP, but the bottom line, tryin to solve many problems this way, complicated the solution, you don't always need actors and responsibility assignement.
Of course there is more to OO, but the problem is the same. OO can easily be an overkill.
Maybe I am being irrational, and not fair, maybe problem solving does depend on the problem solver taste and way of thinking, I feel more comfortable with dealing with C, Perl and Tcl (I love Tcl). And think of problems in terms, of Input, Process, Output. Instead of actor and responsibilities.
I am learning Perl using Beginning Perl
And I am really satisfied with it, it's free, it's comprehensive and it's author is a skilled Perl hacker.
I would like to know, what more does Learning Perl have to offer? (For one it's not free!)
If it's depth, I plan to use the perldoc and perlmonks.org for the depth. And beginning perl just for the big picture (not that it doesn't offer depth, it does to a great degree).
Python, not anymore. Ruby, maybe but doubt it
on
Learning Perl, 4th Ed.
·
· Score: 2, Insightful
Why? Mainly the OO paradigm, big turn off
Okay, I am one of those, generalists, prgrammer wannabe.
I have spent time with, C, C++, Objective-C, OCaml, Python, Java, Bash scripting, Perl, Tcl, Sql and maybe others.
And even thought Python was kind sometime, my main pick, I had to give up on it.
Python is hard, harder to learn than even C.
Learning how to program in OO, is hard, and python, regardless of what you say doesn't make it easier.
To really understand the different programming paradigm, you have to learn more than one language, an programmer who haven't look on at least 5 languages shoul question his own skills.
Anyway, Perl biggest assets in my opinion, are
The wealth of it's literature, you can find a Perl book covering almost any programming corner and topic.
That Perl book, will be effectively teaching you a CPAN library
Python, will never have that, mainly because no other language have that, Perl is unique in this. Plus OO programming, is just tuff to swallow, in theory, I would say OO offer a very nice level of uniformity and abstraction to any program, but in real life, it's just easier to deal with the mess of procedurla programming. And don't think of data, and behavior owners.
Good luck with your Pythonic dreams, but... honestly, I wouldn't recommend Python, well not anymore.
The first thing I like to check in a new book is the table of contents, yet the book homepage doesn't seem to have it.
I hate it when they do that, I'll have to look for it in the publisher 's website.
Re:Rails, great for those fed up with J2EE.
on
Ajax On Rails
·
· Score: 2, Insightful
You should probably read this paper on scripting
The moral is, no matter how complex a system build on Ruby will get, it will always be more simple to use than a system build on Java, just because Java carries the characteristics of a systems programming language while Ruby carries the characteristics of a scripting programming language.
Is an elephant bigger or a girafe taller?
on
mod_perl 2.0.0 Released
·
· Score: 5, Insightful
It's not that Perl is good or bad by itself, the question is more like, you still that Perl is still good/better in comparision to Ruby, Tcl, Python, Haskell, OCaml, Mozart/Oz and others more.
I do realize, that sometimes comparing two languages is more like asking, is an elephant bigger or a girafe taller?
But honestly, if you are still to start learning would you still have picked Perl.
I picked Tcl and I have my reasons. (Tcl/Tk, Sqlite, event driven programming and OpenAcs).
And my second choice would be ruby, I strongly like the OOP paradigm and as far as I know Ruby got better support for this paradigm, I'll probably learn ruby next, I believe one should learn a new language every now and then (it's a common advice, I didn't come up with it).
Supporting old system is good enough reason to learn Perl, but beside taking advantage of availbe libraries (and this is a HUGE good reason) I dont see any other reason to get excited over Perl.
Are they delivered on it, and how much of the delay is in IT projects is IT related.
For example a project may be delayed because, the programs are busy working on multiple project, this is not directly related to IT, but could mean, that finding more programmers is an issue
And most importantly, is this problem IT specific, and the emphasis here is ont the I, how much of the delay can be blamed on the T
How many of high tech project is delayed? Maybe managers just can't forcast how much time and effort high-tech jobs take, this is not exaclty the fault of engineer, but actually a failure in the management domain! If the job is simple they succeed to predict how long it will take to finish, if not, they fail, kinda sounds obvious.
When I here statics like this, I remember statics like, 60% of people in jail are black, is it really because they are black, or more because they are poor, and it just happens that more black people are poor, know what I mean! We can reduce poverty, but we can't (at least not desirable) to change peoples color, and even if we can, that won't guaranty reduce the jail population.
I think new consoles should comes with screens
or anything like a screen i.e. a projectors
One of the biggest console drawbacks is that you have to take over a TV to play a game, usually someone else in the house might also have some interest in using the TV, morale, make it easier and cheaper to play games
Well I am mostly just thinking loudly!
Does anyone see the link here, OpenOffice or
WhateverOffice will just be a WYSIWYG editor
or an XSL Stylesheet, since an office word processor, is also What You See!
I think the people of OpenOffice or OpenFormat and DocBook/DebianDoc/TEI people, need to acknowledge the conflict of interest and offer a comprimise
after I install some software on thw windows-NT it asks for a reboot! How will that work, without taking down the other systems. And what about system shutdown, which OS will be allowed to shut the power down?
I think such a system will require some sort of an OS manager ! a layer downwards between the OS(es) and the hardware.
It's a popular advice (wisdom) that to be a good
programmer one needs to learn a new programming
language every now and then.
Also another good and popular advice that a programmer
should introduce himself to many programming paradigms
like OOP, AOP, Procedural, Static, Dynamic, Generic, Strongly typed, Weakly typed, Un-typed, etc...
I think choosing to learn O'caml achieves both advices.
So in other words, you might want to learn O'caml, not just because it's a good language, but because by learning O'caml you might become a better programmer!
Personally I am very disapointed
The logo is not cool, not artistic, not insipiring, not anything...
I really like what OpenBSD did, they know how to play with their logo, I believe this speaks a lot about the attitude of the people behind the project.
And it says, that they like and want to have fun!
NetBSD have made a terrible statement by this logo, this logo declares in my opinion that the NetBSD is not about fun anymore!
I seriously can't imagine a worst logo...
So we know that OpenBSD is a Libra, what about the other OSes
Anyway, I think it's a shame that the OpenBSD doesn't release official ISO. I have no idea how hard it is to make one, but I think it might encourage more people to try OpenBSD.
OpenBSD does seem to have a cool collection of Hackers/Developers (hackers slash developers) and a special community. And opensource software is all about community.
if you need to make a piece of software, and can't work alone, because it's too much work for you, or because you don't everything about everything
taking your project online as a free project might help!
or if you can do it alone, taking is online might help improve it, more hands, eyes, legs, bugs, and everything you can imagine
another reason to make a software free, is increasing it's chance of adoption, so if more adoptions have more value to you, then maybe making your program free, is a good idea
moral is, there is a chance that making a sw project open source, is the only way to make use or money out of it
the internet, and the millions and millions of the net citizens, increases the chances that you will get what you want from makin a project free
more volunteers who share similar interests
cheap distribution
more adoption
so evaluate the situation, and choose
free or close
don't forget, that making closed source software, costs a lot, companies likes Redhat, mandrake, suse, would have never existed if the main software component they work on (linux-kernel) wasn't free, because at one point in their life, paying for the development and marketing and distribution for a new OS was way bigger then their pocket.
so it can be very practical and economic to make a sotware free...
Attracking the right volunteers, in my opinion, remains the make it or break it
so one should not set his hopes too high
maybe you will make a piece of code free, but no one will bother
or maybe the skilled volunteer poll will be satured, all the skilled ppl are busy and taken
but then of course, i am sure, many many many, closed source sw maker, bankrupt for less then that
So are we now supposed to congratulate the wealthiest company ever for doing what it should have been doing far better for a while longer and a lot cheaper?
Slashdot Mirror
Did they do any serious research on how much their choice of cartridge over cd-rom, and that mini-cd-thingy over DVD have cost them?
....
I think they repeated the same mistake, in a market full with gurus
They fought piracy and they lost, obviously. Yes I think Sony won a lot, by leaving a small space for piracy.
Many people I know, bought several pirated CDs, and few original. Yet they bought nothing of Nintendo.
I was hurt when you said I should seek a non-technical job.
But since you was nice enough to notice my post and reply. I have to return the favor.
I am not saying I am good, but I honestly want to be good (in term of programming skills). I whole heartdely believe that the best way is to have a broad view of the issue, when it comes to programming this translate to learning different languages that implement the multitude of programming paradigms ever invented.
I do believe, that solve a problem, in terms of OOP is not simple, I wasn't saying it's beyond me, I am just saying it's hard. And honestly most book, dump down this fact.
To solve a problem you need a plan, to execute a plan (in OOP) you need actors, actions in the plan, will be the responsibility of specifice actor.
I was being quick in representing my view of OOP, but the bottom line, tryin to solve many problems this way, complicated the solution, you don't always need actors and responsibility assignement.
Of course there is more to OO, but the problem is the same. OO can easily be an overkill.
Maybe I am being irrational, and not fair, maybe problem solving does depend on the problem solver taste and way of thinking, I feel more comfortable with dealing with C, Perl and Tcl (I love Tcl). And think of problems in terms, of Input, Process, Output. Instead of actor and responsibilities.
I am learning Perl using Beginning Perl
And I am really satisfied with it, it's free, it's comprehensive and it's author is a skilled Perl hacker.
I would like to know, what more does Learning Perl have to offer? (For one it's not free!)
If it's depth, I plan to use the perldoc and perlmonks.org for the depth. And beginning perl just for the big picture (not that it doesn't offer depth, it does to a great degree).
Okay, I am one of those, generalists, prgrammer wannabe.
I have spent time with, C, C++, Objective-C, OCaml, Python, Java, Bash scripting, Perl, Tcl, Sql and maybe others.
And even thought Python was kind sometime, my main pick, I had to give up on it.
Python is hard, harder to learn than even C.
Learning how to program in OO, is hard, and python, regardless of what you say doesn't make it easier.
To really understand the different programming paradigm, you have to learn more than one language, an programmer who haven't look on at least 5 languages shoul question his own skills.
Anyway, Perl biggest assets in my opinion, are
- The wealth of it's literature, you can find a Perl book covering almost any programming corner and topic.
- That Perl book, will be effectively teaching you a CPAN library
Python, will never have that, mainly because no other language have that, Perl is unique in this. Plus OO programming, is just tuff to swallow, in theory, I would say OO offer a very nice level of uniformity and abstraction to any program, but in real life, it's just easier to deal with the mess of procedurla programming. And don't think of data, and behavior owners.Good luck with your Pythonic dreams, but
The first thing I like to check in a new book is the table of contents, yet the book homepage doesn't seem to have it.
I hate it when they do that, I'll have to look for it in the publisher 's website.
You should probably read this paper on scripting
The moral is, no matter how complex a system build on Ruby will get, it will always be more simple to use than a system build on Java, just because Java carries the characteristics of a systems programming language while Ruby carries the characteristics of a scripting programming language.
It's not that Perl is good or bad by itself, the question is more like, you still that Perl is still good/better in comparision to Ruby, Tcl, Python, Haskell, OCaml, Mozart/Oz and others more.
I do realize, that sometimes comparing two languages is more like asking, is an elephant bigger or a girafe taller?
But honestly, if you are still to start learning would you still have picked Perl.
I picked Tcl and I have my reasons. (Tcl/Tk, Sqlite, event driven programming and OpenAcs). And my second choice would be ruby, I strongly like the OOP paradigm and as far as I know Ruby got better support for this paradigm, I'll probably learn ruby next, I believe one should learn a new language every now and then (it's a common advice, I didn't come up with it).
Supporting old system is good enough reason to learn Perl, but beside taking advantage of availbe libraries (and this is a HUGE good reason) I dont see any other reason to get excited over Perl.
Are they delivered on it, and how much of the delay is in IT projects is IT related.
For example a project may be delayed because, the programs are busy working on multiple project, this is not directly related to IT, but could mean, that finding more programmers is an issue
And most importantly, is this problem IT specific, and the emphasis here is ont the I, how much of the delay can be blamed on the T
How many of high tech project is delayed? Maybe managers just can't forcast how much time and effort high-tech jobs take, this is not exaclty the fault of engineer, but actually a failure in the management domain! If the job is simple they succeed to predict how long it will take to finish, if not, they fail, kinda sounds obvious.
When I here statics like this, I remember statics like, 60% of people in jail are black, is it really because they are black, or more because they are poor, and it just happens that more black people are poor, know what I mean! We can reduce poverty, but we can't (at least not desirable) to change peoples color, and even if we can, that won't guaranty reduce the jail population.
I think new consoles should comes with screens or anything like a screen i.e. a projectors
One of the biggest console drawbacks is that you have to take over a TV to play a game, usually someone else in the house might also have some interest in using the TV, morale, make it easier and cheaper to play games
Well I am mostly just thinking loudly!
Does anyone see the link here, OpenOffice or
WhateverOffice will just be a WYSIWYG editor
or an XSL Stylesheet, since an office word processor, is also What You See!
I think the people of OpenOffice or OpenFormat and DocBook/DebianDoc/TEI people, need to acknowledge the conflict of interest and offer a comprimise
And there is also tmk at http://tmk.sourceforge.net/
Why doesn't SUN offer to pay IBM to port those applications to solaris!
Pay just like a customer for IBM
after I install some software on thw windows-NT it asks for a reboot! How will that work, without taking down the other systems. And what about system shutdown, which OS will be allowed to shut the power down?
I think such a system will require some sort of an OS manager ! a layer downwards between the OS(es) and the hardware.
Just PostSQL,
...
post as in after or even better beyond !!
beyond sql
and it can be pronounced postsequel
postsequel is definitly easier on the tongue and easier to remember, but then I am not sure if it's smart to change names now
Does linux have fewer bugs than the freebsd, netbsd, openbsd kernels, the hurd and more?
That would also be interesting.
I expect the openbsd kernel to win!
But I'd still choose GNU/Debian for many other different reasons
It's a popular advice (wisdom) that to be a good
...
programmer one needs to learn a new programming
language every now and then.
Also another good and popular advice that a programmer
should introduce himself to many programming paradigms
like OOP, AOP, Procedural, Static, Dynamic, Generic, Strongly typed, Weakly typed, Un-typed, etc
I think choosing to learn O'caml achieves both advices.
So in other words, you might want to learn O'caml, not just because it's a good language, but because by learning O'caml you might become a better programmer!
Personally I am very disapointed ... ...
The logo is not cool, not artistic, not insipiring, not anything
I really like what OpenBSD did, they know how to play with their logo, I believe this speaks a lot about the attitude of the people behind the project.
And it says, that they like and want to have fun!
NetBSD have made a terrible statement by this logo, this logo declares in my opinion that the NetBSD is not about fun anymore!
I seriously can't imagine a worst logo
So we know that OpenBSD is a Libra, what about the other OSes Anyway, I think it's a shame that the OpenBSD doesn't release official ISO. I have no idea how hard it is to make one, but I think it might encourage more people to try OpenBSD. OpenBSD does seem to have a cool collection of Hackers/Developers (hackers slash developers) and a special community. And opensource software is all about community.
if you need to make a piece of software, and can't work alone, because it's too much work for you, or because you don't everything about everything
...
taking your project online as a free project might help!
or if you can do it alone, taking is online might help improve it, more hands, eyes, legs, bugs, and everything you can imagine
another reason to make a software free, is increasing it's chance of adoption, so if more adoptions have more value to you, then maybe making your program free, is a good idea
moral is, there is a chance that making a sw project open source, is the only way to make use or money out of it
the internet, and the millions and millions of the net citizens, increases the chances that you will get what you want from makin a project free
more volunteers who share similar interests
cheap distribution
more adoption
so evaluate the situation, and choose
free or close
don't forget, that making closed source software, costs a lot, companies likes Redhat, mandrake, suse, would have never existed if the main software component they work on (linux-kernel) wasn't free, because at one point in their life, paying for the development and marketing and distribution for a new OS was way bigger then their pocket.
so it can be very practical and economic to make a sotware free
Attracking the right volunteers, in my opinion, remains the make it or break it
so one should not set his hopes too high
maybe you will make a piece of code free, but no one will bother
or maybe the skilled volunteer poll will be satured, all the skilled ppl are busy and taken
but then of course, i am sure, many many many, closed source sw maker, bankrupt for less then that
So are we now supposed to congratulate the wealthiest company ever for doing what it should have been doing far better for a while longer and a lot cheaper?