41–50 of 189 posts
"100% of our production system is now running Go as 95% of our application (C being the other bits)" So... 95% of their production system is running Go.
I guess it's playing word semantic. 100% of their MACHINES are running GO in SOME capacity, while other languages play some roles in other capacity.
Earlier quoted context omitted.
You cannot even see the front page without cookies. I suppose it's better than 1990s websites that would go into an endless loop but what about people who are just browsing?
It's probably necessary for click tracking. Macy's will pay either a CPC or a CPA for traffic coming into their website, and that includes traffic to their homepage.
"100% of our production system is now running Go as 95% of our application (C being the other bits)" So... 95% of their production system is running Go.
Earlier quoted context omitted.
In hindsight it doesn't seem so surprising. Go really isn't a good alternative to C++ for the kinds of things that really need the low-level control and direct memory access C++ provides. And if you don't really need those things you probably should have moved on to Java or Ruby/Python/etc already. And since a lot of Java shops are fantastically risk averse I'm not at all surprised that the same kind of people that w…
I write Go and I have been satisfied with the low-level control and direct memory access. The language has pointers and you can cast between ints and pointers, so you can do anything you can do in C. If you're writing realtime code, you can avoid triggering the garbage collector simply by not allocating memory on the heap. It is harder to get anything done this way, but writing realtime code in any language is diffic…
But there's a huge uphill battle ahead for Go here. For instance, I write C++ code because I'm doing music software and all the APIs and existing code libraries and samples are in C++. It's just so much easier in this environment to put up with C++'s warts than it would be to try to shoehorn Go in there. As John Carmack says, externalities can quickly overwhelm the advantages of any particular language.
But if you're implementing web services from scratch you don't have any of that baggage to carry around so it's much easier to choose Go.
Earlier quoted context omitted.
It's a shopping website. It's sorta hard to do cart management without cookies.
They are a good fallback, I think he is talking about using things such as Local storage, session storage, or global storage. Since the site is their mobile site I see no reason why they aren't using the new technology available to us since most mobile devices would be able to use it. DOM storage seems to be a better fit for shopping carts than cookies anyways.
Additionally, cookies can be marked as http only or even as secure, making it very hard to lose the token by virtue of a fire sheep like, or even just XSS attack.
For that reason, I personally would prefer a site using (session) cookies to one hacking it via DOM storage any day.
And finally, depending on the store you might want to persist the shopping cart between visits- likely across machines. Thus, the cart should be stored on the server and not in DOM storage.
We search with Google, run our phones with Google, run Google's browser, now they want us to write all our code in Google's language. Why Google? What's wrong with Java? Other than the fact that Oracle owns it, I miss Sun. Scott McNealy tried to make the technology world better. Scott, Gosling. Google...why should everything we do all day and night be about Google?
http://en.wikipedia.org/wiki/Go_(programming_language)
>> The syntax of Go is broadly similar to that of C
C, seriously? C??!? Why? Why would I want to go back to ... C?
>> Of features found in C++ or Java, Go does not include type inheritance, generic programming, assertions, method overloading, or pointer arithmetic.
And that is a good thing or a bad thing or what?
>> Go allows a programmer to write functions that can operate on inputs of arbitrary type, provided that the type implements the functions defined by a given interface.
Huh? Oh I can pass interface references, ok.
>> A Go interface is best described as a set of methods, each identified by a name and signature.
That sounds like Microsoft's crappy COM from the 1990's.
The code sample on that page shows there are no braces in the if evaluation statements. A wise man, Peter Van Der Linden formerly of Sun's Compiler Group and author of Deep C Secrets wrote about using more braces if needed as explicitness is always better. I agree with that.
At this point, I think I'd rather program in Groovy or even go to JavaScript if I had to, than use Go.
Oh...the language name sux.
Tip, buy Oracle and fix Java or by Java rights from them and fix it, then programming in a language owned by Google when you own so much of our lives now wouldn't be so bad.
PS How does Guido Van Rossom feel about Go?
It's really annoying to have to log in to read something on google+, or groups for that matter. I just won't do it.
Earlier quoted context omitted.
I write Go and I have been satisfied with the low-level control and direct memory access. The language has pointers and you can cast between ints and pointers, so you can do anything you can do in C. If you're writing realtime code, you can avoid triggering the garbage collector simply by not allocating memory on the heap. It is harder to get anything done this way, but writing realtime code in any language is diffic…
I actually haven't gotten this far with Go myself so I'm glad to hear that it's possible. But there's a huge uphill battle ahead for Go here. For instance, I write C++ code because I'm doing music software and all the APIs and existing code libraries and samples are in C++. It's just so much easier in this environment to put up with C++'s warts than it would be to try to shoehorn Go in there. As John Carmack says, ex…