>
> If go run is the primary starting point you wouldn't need the GOPATH
> configured.
>
> What I think would be interesting is the ability that most scripting
> languages provide which is to just start coding. No functions requiring
> definition and perhaps an auto-import of fmt, strings, io, etc. So you
> could write something like this:
>
> ''' hello.gos
> fmt.Println("hello world")
> '''
>
> And then type 'go runscript hello.gos'. I know this is horrible for all
> sorts of reasons but I'm reminded of what a friend said about writing: "get
> it writ, then right"
>
> For some one completely new to programming there's a reduced burden of the
> concepts to understand in the above. Thoughts?
>
>
Whilst I think the simpler something is the better it is for teaching, not
sure I'd advocate changing a language just to make it slightly easier for
beginners.
There are languages around which are ideal for getting people into the
mindframe of coding. What should really be encouraged is the attitude of
picking up multiple languages after you are comfortable.
Every course I've been on has always centered around how great coding is
and why the language they are using is ideal. Not sure I've ever heard
anyone at the end say "But you should really pick up x, y, z if you want to
do a, b, c".
I think it would be better to accept a certain place in the teaching
curriculum rather than try to cater for everyone - less code smell.
- from my thumbs to yours
>
You type with your thumbs? ;-)
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
