I had to google to see what that meant. It appears that some moderator is a bit touchy regarding the Go programming language, because of all the comments I've made that's the only one that was modded as negative.
That's how science goes: a phenomenon is observe, an hypothesis is formulated, and then it is tested. As it isn't possible to test economic policies on countries, economy often deals with hypothetical models whose…
In addition, it's terrifying how a service that forces you to identify yourself tries to gather information not only on your social network but also on what search queries you run, who you talk to, what you talk about,…
Blaming the EPA for companies abusing a bug in the way tracking numbers were managed is like blaming the victim of a home invasion for putting up a defective lock.
Hacker News, through RSS feeds. Wikipedia is always fun to browse. I used to browse slashdot but once the shill epidemic kicked in, it started to become a complete waste of time.
You mean "Variable-Length array", also referred to as VLA, not "flexible array member".
Not true. While the "domain of keys" format is implemented through a list of tuples, the compressed row/column/diagonal storage data types, which are the formats used in popular matrix algebra/solver packages, are…
Quite true. In fact, comparing MessagePack to JSON can only be interpreted as comparing $own_project with $most_popular_project, with hopes of getting some attention.
What is there to be glad about? Considering Facebook's track record on privacy, censorship, and disabling accounts, and considering the number of alternatives out there, there is nothing to be glad about.
That isn't JSON's problem. It's your app's problem. Set your parser to recognize "Infinity" as a token and you are set.
looks like the real problem lies in some libraries being broken and poorly thought out. If your code chokes on invalid input then the problem lies in your code, not the input.
Sure, UI code tends not to be that processor-intensive, but it is a braindead idea to dump efficient state-methods with a bloated, inconvenient, and ill-conceived state-changing method which is both needlessly verbose,…
You repeat yourself yet again. How exactly can you claim with a straight face that a workspace doesn't need to be referred to in $GOPATH, and then proceed to claim that you only need to set $GOPATH to a directory which…
So, when faced with criticism mentioned in the blog post and referred to in a post, instead of thinking about it you mindlessly insult others and say absolutely nothing about what has been said. Who exactly is the troll…
These are not source modules I'm talking about. If it was only necessary to set $GOPATH to point to source modules then everything would be fine. The problem is that go requires that $GOPATH points to a project's source…
I'm not talking about gc. I'm talking about go. You know, the program which is extensively marketed as the only program which is required to build and run Go programs, and the standard and default way to deal with Go,…
Supporting declaring variables with new(), make and local variable assignment isn't mandated by the need to make the grammar regular. It's simply a braindead idea. Go might have significant improvements over C, but they…
That approach is nice and all if we are dealing with modules which we wish to reuse. If instead we would like to organize our source tree following a deep directory structure, we are forced to screw around with $GOPATH,…
You started your post by claiming it wasn't true, but you proceeded to say that yes, it is in fact true. As it is stated in the screencast, a programmer needs to add the workspace to $GOPATH to be able to build the…
He forgot to mention how programmers need to add each project directory to $GOPATH to be able to include files stored in project subdirectories. Talk about a braindead idea.
I had to google to see what that meant. It appears that some moderator is a bit touchy regarding the Go programming language, because of all the comments I've made that's the only one that was modded as negative.
That's how science goes: a phenomenon is observe, an hypothesis is formulated, and then it is tested. As it isn't possible to test economic policies on countries, economy often deals with hypothetical models whose…
In addition, it's terrifying how a service that forces you to identify yourself tries to gather information not only on your social network but also on what search queries you run, who you talk to, what you talk about,…
Blaming the EPA for companies abusing a bug in the way tracking numbers were managed is like blaming the victim of a home invasion for putting up a defective lock.
Hacker News, through RSS feeds. Wikipedia is always fun to browse. I used to browse slashdot but once the shill epidemic kicked in, it started to become a complete waste of time.
You mean "Variable-Length array", also referred to as VLA, not "flexible array member".
Not true. While the "domain of keys" format is implemented through a list of tuples, the compressed row/column/diagonal storage data types, which are the formats used in popular matrix algebra/solver packages, are…
Quite true. In fact, comparing MessagePack to JSON can only be interpreted as comparing $own_project with $most_popular_project, with hopes of getting some attention.
What is there to be glad about? Considering Facebook's track record on privacy, censorship, and disabling accounts, and considering the number of alternatives out there, there is nothing to be glad about.
That isn't JSON's problem. It's your app's problem. Set your parser to recognize "Infinity" as a token and you are set.
looks like the real problem lies in some libraries being broken and poorly thought out. If your code chokes on invalid input then the problem lies in your code, not the input.
Sure, UI code tends not to be that processor-intensive, but it is a braindead idea to dump efficient state-methods with a bloated, inconvenient, and ill-conceived state-changing method which is both needlessly verbose,…
You repeat yourself yet again. How exactly can you claim with a straight face that a workspace doesn't need to be referred to in $GOPATH, and then proceed to claim that you only need to set $GOPATH to a directory which…
So, when faced with criticism mentioned in the blog post and referred to in a post, instead of thinking about it you mindlessly insult others and say absolutely nothing about what has been said. Who exactly is the troll…
These are not source modules I'm talking about. If it was only necessary to set $GOPATH to point to source modules then everything would be fine. The problem is that go requires that $GOPATH points to a project's source…
I'm not talking about gc. I'm talking about go. You know, the program which is extensively marketed as the only program which is required to build and run Go programs, and the standard and default way to deal with Go,…
Supporting declaring variables with new(), make and local variable assignment isn't mandated by the need to make the grammar regular. It's simply a braindead idea. Go might have significant improvements over C, but they…
That approach is nice and all if we are dealing with modules which we wish to reuse. If instead we would like to organize our source tree following a deep directory structure, we are forced to screw around with $GOPATH,…
You started your post by claiming it wasn't true, but you proceeded to say that yes, it is in fact true. As it is stated in the screencast, a programmer needs to add the workspace to $GOPATH to be able to build the…
He forgot to mention how programmers need to add each project directory to $GOPATH to be able to include files stored in project subdirectories. Talk about a braindead idea.