115 karma · joined January 25, 2012
function SUM() { var sum = 0; for (var i = 0; i < arguments.length; i++) { sum += arguments[i]; } return sum; }
Now you can do stuff like =SUM(A1, B1, C2) and it works like expected.
Kudos to both, dynamic lighting on 2D art looks great.
For raw 720p RGBA you'd send: 1280 * 720 * 32 = 29,491,200 bits but obviously you're not going to do that. Suddenly you're not only sending data but also encoding / decoding it.
It's quite possible that one could stream into any other machine including tablets, laptops and even phones. This would enable playing your full Steam library from anywhere with decent enough connection (on both sides), especially games where input lag is not that big issue.
Main reason seems to be that while SteamOS can only handle games that have Linux support the streaming allows you to have "HTPC" SteamOS connected to TV and play anything that Windows machine would be able to play.
Of course there's the input lag etc which might be an issue in some FPS games etc (which they mention that they're trying to "reduce in operating system level")
I did call them today and they couldn't even find the order, even though it was still fine couple weeks ago. (This is an international order btw)
Anyways, the product still looks great and the customer support has been fast to reply so I have no complaints about that either. I was just quite eager to start developing some projects for it.
I've tried bunch of possible candidates to replace Reader and this is the first one that actually feels responsive enough for daily use.
And the fact that it's open source and written in Go is just icing on the cake.
For actual answer to your question, there was a comment about it yesterday: https://news.ycombinator.com/item?id=5842769
Here's Go 1.1 vs 1.0.3 on a bit beefier machine: https://gist.github.com/errnoh/5320784
Next benchmark will have Go 1.1 running, can't promise that it'll scale as well as on this server but it'll be significant change anyways.
And most of all, main part of the language is that it's intuitive to write and comes with a clear and readable spec and standard library.
edit: updated gist with Netty using the same configuration
I don't think they have anything against C#, probably no one just has committed C# version to be benched.
(edit: whops, linked fork first)
OpenGL bindings are at https://github.com/go-gl
For 2D graphics there's promising project at https://github.com/skelterjohn/go.wde which provides interface that you can use together with http://golang.org/pkg/image/draw
(Issue worth noting is that none of the platforms specific parts in go.wde yet have hardware acceleration so it's not yet ready for game development etc. It's quite possible that that'll change in the future though :) )
And for ascii graphics we have https://github.com/nsf/termbox-go
There are bunch of other libraries as well but these are the ones that I'm more or less constantly using. go.wde is probably closest to what you were looking for but also the one that still requires hardware acceleration before it can properly be used as fast canvas for experimenting with games etc.
Note: None of these count as "standard library", all of them are third party projects by gophers around the world.
I opened the thread first thing after waking up this morning, commented before having cup of coffee and resulted in misreading the whole point of that comment.
I'll try to drink more coffee from now on. Sorry knotty66.
bench old_ns/op new_ns/op delta
"BenchmarkHTTPClientServer 373216, 52646 -85.89%"
That bench is 7 times faster in Go 1.1 than 1.0.3.Modified it a bit to run in parallel. I guess I'll leave it on for couple hours and see if it gets anywhere.
current output:
1363637914 2013-03-18 22:18:34.118051 +0200 EET Stats: 0/53659699 (0%) good/tries, 223559.91320127275 ops/secThe colors aren't that beautiful but it's much less stressful for my eyes, and the highlight colors were spot on as well.
Thanks to emidln for informing that it's Solarized Dark, I've used the default Solarized but I've skipped the Dark one because of somewhat ugly colors.
So.. thank you.
There's really no reason at all to obfuscate text based information in such way unless you want to display ads or track the user. It even shows the actual article behind the loading screen but you can't read the article itself since the loading never finishes. That's just bad design.
It's not the first time I've had to open lynx in order to read an article that's behind some javascript nonsense. (note: the text data is fine, it's actually only broken on modern browsers which actually handle js)
Not sure what's the best way to generate users on WP but I do hope you get enough users and continue to support the platform.
Probably one of the most aesthetic apps on WP7, I for one will be using this from now on.
Just thought I'd point out to people that this rewrite was done "last year", which was before Go1 was released march this year. The API was in constant change and it all projects needed constant updating to keep up with weekly releases. (or stick with the r60 with totally different and soon-to-be deprecated API)
API is frozen now and life is good.
For me it's these two lines you mentioned:
1) You should never have to look for documentation
2) Files are not the best representation of code, just a convenient serialization.
First one is easily doable and there are a lot of plugins that help you with that.
The second is what makes this project interesting and almost made me write my own editor the moment I first saw Light Table.
Files are indeed good way to serialize stuff, but handling each separate section of code as independent (and at the same time, dependent on other sections of code) could actually be a better way. At least it's something I'd like to try.
That's also something that's doable for most languages there are.
Only thing needed are the rules that tell what parts are separate, and additional logic that links those parts to the parts that are called from that one to connect the whole thing as one big entity.
Go 1 should solve most of the big problems, currently libraries need to keep up with weekly releases and packages are still being moved around.
(No seriously, he described Go)