saving time?
but unreadable...
thanks for the speech
file compressor?
come on thousands of library available...
why do you want to create a new wheel?
if you are doing sth new...
the problem isn't the time to write the code...
its more like debugging, thinking, and understanding the problem...
and that is much easier for some beginner if the code is readable
without an native understanding of the language
Quote:SAVING a good amount of TIME. In Software Engineering time is a high priority.
made me laugh
thats why 80% of work is done in the planning phase/iteration...
(12-13-2011, 12:29 PM)dannzen Wrote: [ -> ]saving time?
but unreadable...
thanks for the speech
file compressor?
come on thousands of library available...
why do you want to create a new wheel?
if you are doing sth new...
the problem isn't the time to write the code...
its more like debugging, thinking, and understanding the problem...
and that is much easier for some beginner if the code is readable
without an native understanding of the language
Quote:SAVING a good amount of TIME. In Software Engineering time is a high priority.
made me laugh
thats why 80% of work is done in the planning phase/iteration...
you make me laugh even more if you are making a planning phase for an small casual project. You do that with AGILE methodologies when you have a big team and a project that should be modular and maintainable, not otherwise.
Learn to get into context.
!!!WARNING. THE FOLLOWING IS ONLY MY OPINION!!!
I don't see the point in haskell as a first or even as an early language. It's difficult to learn (unless you're obsessed with math) and utterly useless for most programmers. It's so different from conventional programming languages that if you were to learn it first then go off and learn a more common language like java or C you would feel like you're learning everything all over again.
That's the advantage of starting with something like C++. It eases your transition into other languages. Imperative languages are also much easier for a beginner to use.
Ruby on the other hand I do think would make a decent first language.
(12-13-2011, 02:29 PM)NaturalViolence Wrote: [ -> ]I don't see the point in haskell as a first or even as an early language. It's difficult to learn (unless you're obsessed with math) and utterly useless for most programmers. It's so different from conventional programming languages that if you were to learn it first then go off and learn a more common language like java or C you would feel like you're learning everything all over again.
Depends. If you have someone teaching you (in school for example) starting with Haskell might not be a bad idea because it makes it easier to think in terms of complex types, implement algorithms and work with data structures, etc. My school teaches OCaml as the first language, MIT used to teach Scheme with a really good book (SICP, you can find it online), and although it's not as "practical" as C++/Java, it teaches you good practices.
Saying that "imperative languages is easier" is wrong, btw. Neither imperative or functional is the "natural" way of thinking. However, talking about paradigms, recommending Java/C# as a first language is seriously fucked up IMHO. You have two choices : copy pasting stuff you don't understand ("public class Main { public static void main(String[] args) { } }"), or scratching your head for one month trying to understand OOP while learning to program.
My advice to learn programming on your own would be Python as a first language, with a book like Learn Python the Hard Way (it's not that hard, and it teaches stuff in an interesting way), then C/C#/Java (it doesn't really matter, most of the stuff you'll have learned with Python can be done in the same way in these three languages).
Quote:scratching your head for one month trying to understand OOP while learning to program.
öhm? serious?
i see you are a math genius...
there are people who understand the relations of OOP really fast
and there are people who suck at math
Actually no, I fail at maths really hard.
OOP can be easy to understand assuming you already have some programming background. When you don't, learning it at the same time as basic programming concepts is a very good way to completely fail to learn both. Obviously some people can do both at the same time, but I wouldn't bet on it.
i fail at maths too ;>
in school A
in university D
! ;D
its just not my world ö_Ö
@BlinkHawk
I didn't call Haskell old, I said the teaching methods used in schools all over the world are old and out of date.
(12-14-2011, 03:48 AM)Runo Wrote: [ -> ]@BlinkHawk
I didn't call Haskell old, I said the teaching methods used in schools all over the world are old and out of date.
well my links weren't college courses, just internet tutorials which helped me a lot on learning these languages, I didn't learn any of those 2 at university but at work
. I was also suggesting haskell for good mathematicians since it's just one step from math.
Anyways, some guy there mentioned Python. Python is another great choice, just like Ruby. It's as quite useful and focuses on what is important rather than confusing you with system-related resources like types, memory, bindings, etc. It also has many practical uses like Shell scripting, web programming, plugin programming for software packages. Quite a good choice.