Scaevolus 15 hours ago
link |
The static analysis features are exciting: http://golang.org/lib/godoc/analysis/help.html
"Because concurrent Go programs use channels to pass not just values but also control between different goroutines, it is natural when reading Go code to want to navigate from a channel send to the corresponding receive so as to understand the sequence of events.
Godoc annotates every channel operation—make, send, range, receive, close—with a link to a panel displaying information about other operations that might alias the same channel."
Understanding large concurrent programs is significantly easier with a precise pointer analysis to help you track objects.
reply
---
some notes from this discussion on Haskell's homepage:
https://news.ycombinator.com/item?id=8006997
"Speaking of tutorials, the old page links to like 500 of them or so. I have no clue how to figure out which one to start with."
Torn 1 day ago
link |
Also typing in their code example (the one right at the top, pride of place) into their 'Try it' repl throws an error:
primes = sieve [2..] where sieve (p:xs) = p : sieve [x | x <- xs, x `mod` p /= 0]
<hint>:1:8: parse error on input `='" error
Now I have almost no knowledge of Haskell, so I'm probably making some really basic mistake, but I figure most visitors will try that and then get put off
---
wtetzner 1 day ago
link |
The site feels too flashy, and the giant photo feels distracting. It would be nice if it felt "cleaner." As it is, I feel like a newcomer would find it somewhat overwhelming visually.
I think something nice and simple like Rust's homepage[1] would be nice. Or maybe something like Racket's homepage[2].
[1] http://www.rust-lang.org/ [2] http://racket-lang.org/
(bayle: see also pietrust/webdesign)
---
(copied from pietrust/webdesign):
http://www.libelium.com/products/waspmote/
https://developer.apple.com/swift/ https://developer.apple.com/library/prerelease/ios/documentation/Swift/Conceptual/Swift_Programming_Language/ https://developer.apple.com/library/prerelease/ios/referencelibrary/GettingStarted/LandingPage/index.html
--
http://www.mozilla.org/en-US/firefox/30.0/releasenotes/
--
io's web page style looks nice:
http://iolanguage.org/scm/io/docs/IoTutorial.html
http://iolanguage.org/scm/io/docs/IoGuide.html
--
also the Flask web page style looks nice:
---
the official Python tutorial is wonderful
here's a pretty haskell tutorial: http://yannesposito.com/Scratch/en/blog/Haskell-the-Hard-Way/
incidentally, the asm.js spec formatting is pretty.
---
equivalent to python PEP 8, and to Golang gofmt
---
http://www.inf.ethz.ch/personal/wirth/Oberon/Oberon07.Report.pdf has some good, concise text for defining basics such as 'scope' in an informal spec
---
the Rust Guide (not tutorial) is good in that it covers many of the little things that a first-time (or second-time) programmer might not know: http://doc.rust-lang.org/master/guide.html . it's a little verbose, though; if you took out some of the informality, it would be less verbose yet still easy. i'd prefer to assume a level of expertise / provide the level of density that the Python tutorial does, though.
--
lnanek2 1 day ago
link |
I'm not really a fan of having a second source of truth compared to in depth material already on php.net. The two will invariably start to disagree and php.net is much, much better than any spec or documentation I have ever read. Using Android is a nightmare compared to php.net because every single thing on php.net has extensive user generated documentation whereas Android is just some broken official docs. I submitted a bug report with a fix for the Android docs telling people to make dialogs in a way that simply crashed and didn't work and it was never merged in for years and years. So official specs tend to suck.
reply
--