Things you (probably) don't know about Go(nf.wh3rd.net)
nf.wh3rd.net
Things you (probably) don't know about Go
http://nf.wh3rd.net/10things/
11 comments
You can watch Andrew's talk, along with a talk from Rob Pike and one from Evan Shaw here: https://www.youtube.com/watch?v=JE17r3n1kz4
It's broken on Chrome 19.0.1084.56 on OS X if you open it in a new tab in the background with middle click. Plain black page, arrow keys/space changes the number indicator in the URL, but shows no content.
Edit: and on a related note, personally I really dislike the trend of posting slides for review outside of the context of a presentation. As something to click on from the front page here, or to bookmark/print for future reference, a plain page with a list that you'd just scroll up/down normally instead of separate slides would be much handier.
Edit: and on a related note, personally I really dislike the trend of posting slides for review outside of the context of a presentation. As something to click on from the front page here, or to bookmark/print for future reference, a plain page with a list that you'd just scroll up/down normally instead of separate slides would be much handier.
Go is the new Esperanto: Slightly nicer, slightly more regular but it's not clear what problem it solves.
Check out langalot.com. Python (for example) is a nice language but I doubt it could be used to create as brisk a similar site.
That is actually incredibly fast!
I was at this talk. It was the best meetup I've ever gone to. So many people and so much enthusiasm. I only hope it will translate into Go's success.
11. The gopher's name
No. His name is not Gordon.
I see, so his name used to be Gordon[1] but he changed his name so that now he has no name.
[1]: http://reneefrench.blogspot.com/2009/10/gordon.html
[1]: http://reneefrench.blogspot.com/2009/10/gordon.html
`luriel`, isn't 'cat-v.org' your site?
Gordon is the mascot for Google's Go programming language.
Also was also created by Renée French.It has no name.
That’s correct. Source: http://www.youtube.com/watch?v=JE17r3n1kz4&t=1h25m45s (1:25:45 in). (via http://news.ycombinator.com/item?id=4148148)
[deleted](1)
It would be nice if it didn't hijack my attempts to zoom in and read on my phone. And some indication that swiping changes slides depending which way you swipe.
I got to the landing page and didn't know how to progress either. Why not just add some visible buttons/overlays for next/previous?
Gosh darn gopher. Does anyone know its name? I tried Googling it but couldn't find anything.
The recording of this talk, and two more, are here: https://www.youtube.com/watch?v=JE17r3n1kz4
It's revealed at the end.
It's revealed at the end.
For those who don't want to watch the whole thing, it's said just after 1:25:45. The gopher has no name.
Things I still don't know because the site is just a solid black page with nothing on it.
I got the title slide and was stuck. Took me a while to find out that the space bar skips to the next page. Then I found the invisible 100px wide buttons left and right of the slide area.
Very annoying but I guess it looks better as a presentation. At least the mouse wheel should work, that was my instinctive reaction to skip forward and you could add that without affecting the visuals.
Very annoying but I guess it looks better as a presentation. At least the mouse wheel should work, that was my instinctive reaction to skip forward and you could add that without affecting the visuals.
I'm on chrome on a mac, the pagedown/up buttons worked.
It's an HTML5 presentation. I apologize if it doesn't work in your browser of choice. Try viewing it in Chrome, instead.
I viewed it in Chrome on Linux and it took me quite a while to figure out that you advance by clicking the solid black bars on the side of the slides (which don't even show if your browser window is too narrow). More of a UX issue than a technical one, I guess.
Same here. Arrow buttons of some sort would help.
I hadn't even noticed how I was going through the presentation until you mentioned it.
The problem in Opera is your feature test in slide-deck.js line 762. At the time this part of the code executes, the DOM is not ready yet, so document.body is just null and the whole thing fails.
It does however work perfectly after executing window.slidedeck = new SlideDeck(); manually.
It does however work perfectly after executing window.slidedeck = new SlideDeck(); manually.
I used chrome and almost just exited the page until I accidentially clicked on the black part next to the slide. That's not a browser issue.
Well, if you could see the first slide you could use the arrows to navigate.
But you'd have to guess that. It's not standard behavior.
You are right. I just wanted to let people know how to use it (I closed the site and reopened it because I didn't know either).
You probably need an HTML5 compliant browser.
You also need to make sure your screen is wide enough. Running your browser on half of a 1920px screen isn't a supported configuration either.
I have one. Perhaps the site needs HTML5 compliant markup?
FAIL - apparently the presentation does not work properly for half the commentators here. The world is clearly not ready for HTML5 (not everyone uses chrome's flavor of it either) yet so make it work with other browsers as well.
Well, a big problem is that you're got a pretty huge sampling bias there. The people that it works for aren't going to comment to say "it works!" because that's the state that they expect it to be in.
It works fine for me -- Firefox 13.0.1, so it's not just Chrome-flavoured html5.
It works fine for me -- Firefox 13.0.1, so it's not just Chrome-flavoured html5.
As well as the sampling bias pointed out by jdpage, the breakage is also the fault of this particular HTML5 presentation framework – it is not necessarily the fault of HTML5 as a whole. The page’s user interface could make it clearer that there are more slides and show you how to go to them – for instance, by showing the invisible buttons along the side on page load. And it’s possible that the JavaScript could be written more compatibly, and have better fallbacks for when the browser doesn’t support certain things.