drsintoma

Crockford's videos can not be recommended enough. Specially the first ones about the origins of everything I found really enlightening.

In a past life as sysadmin, I found very useful to encode a letter with number, so that serves with similar specs share the same letter.

a1, a2, ... aN for serves 2 cores 8GB ram

b1, b2, ... bN for serves 4 cores 8GB ram

c1, c2, ... bN for serves 4 cores 16GB ram

...

I have just now reliazed there is a search box at the bottom.

> they're expected to spend the first 6 months learning Go on the job.

Of course like in everything you have different levels of expertise. But I can tell you first hand that most developers can be productive in Go within 2 weeks if not less.

It is really worth having a .do domain? given that they are fairly expensive and seems like google will treat them as specific from Dominican Republic and not generic[1]?

[1]https://support.google.com/webmasters/answer/1347922?hl=en

Really nice guidelines, as someone always fearful of looking spammish almost made me want to submit my stuff, but it still needs some work.

A meta-search engine for English speaking jobs in Germany. Backed by Go, elastic search and python scripts.

https://englishjobs.de

Seems like an alternative to jquery-pjax but I don't see real upside of adding json to the equation.

Go produces fat binaries, probably not what you expect from this tiny tools. I even believe some linux distributions forbid packages that don't use shared libraries.

The real difference IMHO is the very low cognitive load that Go requires. It's a very minimal language very easy to reason about. This translates into 2 things:

1. Most programers (above and below average) can just pick-up Go and be productive without much hand-holding.

2. Most programers can, without much experience, pick anyone's Go code and understand what it's doing.

Working in a company where we introduced Go for backend services without anyone knowing much about it, I know first hand those 2 are true for Go. But I'm not so sure about how OCaml, F#, Haskell or Scala would do with some of my colleagues in that sense.

just yesterday I was searching for publicly available administrative geodata of European countries. it's not an easy task due to language barriers and fragmentation. Does anyone know where to download the source data of this project?

Anyone using NetBSD these days could share what's your use case? Is it just about exotic or legacy systems or are there any upsides compared to other BSDs?

> 502 Bad Gateway

I believe your go process crashed. Consider using something like runit or supervisord.

> In reality of course, most of us don't have that problem, never had and never will

Maybe you never had any problems, but I don't believe "most of us" can say the same. At least me, I'd encountered problems derived from join-abuse in almost every job I've had.

Ok, I just tried it. It still does.

Has anyone tried the new scheduler?

Does this still block forever?

package main

import "time"

func main() { go func(){ for {} }() time.Sleep(time.Millisecond) }

Probably I wouldn't have. I now they have to monetize the product, and for a software with simplicity as the strongest selling point, doing it through consulting/support I guess would be a conflict of interests. But when I saw the prices I was a bit shocked, and made me doubt about the company's strategy in the long term.

the thing that keeps me away from ansible is the pricing model. I find 100$/year/server way too much. and nobody can ensure me that the OSS version is all I'll always need.

nice. I've been waiting to see some full-text search engine in Go for a while to compete with the omnipresent Lucene. Things like Go's low memory footprint could give it an important advantage in this area. This looks like a first step in that direction.

I'd consider it as much of an error as a 404 in this context.

1) Link works: 200

2) Take down notice arrives

Now:

3) Link not found: 404

Then:

3) Link not available: 451

> but I think you would at least agree with me that node's popularity and growth has been unmatched.

Of course I agree. But node is an unique case, since javascript is not exactly new, and had a trillion people using it when node appeared. You can not expect that to happen again any time soon, unless all main browsers start supporting client-side PHP or something crazy like that.

Go is not 'there' yet, sure, and maybe it'll never be. But its growth can not be judged by node's standards, no really new language could compete then.

For a new language is growing quite good: http://www.google.com/trends/explore?q=golang#q=golang&cmpt=...

Of course this doesn't mean you have to use it, but IMHO it can not be regarded as a failure in anyway.

> Go really isn't that young either. It's been what at least 4 years now? There's no excuse. It's not like the language is 6 months old.

1.5 if you count from the first stable release. Which IMHO is what matters, before was just a experiment with a lot of uncertainties. It took ruby 9 years to arrive from 1.0 to Rails. They were other times, sure, but still.

I still consider it very young, or at least I don't know of any other younger language with a better ecosystem.

> Revel seems to be somewhere in between rails and express in terms of opinions which is fine but if it's going to make me less productive then I'm simply not going to use it.

Well, everyone has their preferences, certainly in Go there are not many choices so is not for everyone. But I'd keep an eye on it. Things can change very quickly.

Very interesting! It might be exactly what I was missing. I ended up using simplejson[0] but it still felt like a workaround. I'll give yours a try next time. Thanks!

[0]https://github.com/bitly/go-simplejson

may I ask, what exactly did you have to re-invent? It's true that Go is very young and so are the libreries, and that only recently has started to be seen as web language. But my experience is that the most common problems for web are solved with things like Revel. Is true that is a bit feature basic and there are not that many other options, but I wouldn't consider it insufficient.

> Typing in Go can still be annoying for some situations. If you're dealing with external content (creating an API with mutable content that you still need to read) it can be annoying at best (e.g. reminds me of writing C). Types in Go are a nice implementation though.

Indeed, that's probably the biggest flaw I've found working with GO's type system. Trying to work with unknown n-level JSON is real pain.

> Before you choose another language for your project, ask yourself if it's not going to cost more to write everything you'll need, or if using pre-existing, time-tested code might do the trick for cheaper.

I believe 99.9% of the people will find any libraries they need in pretty much any mainstream language. There is a point where quantity stops being a factor.

> What you did was quite offensive, for Muslims and non-Muslims.

Let me assure you that I don't know one single person in my circle that would consider that offensive.

| Swedish media chose not to report on Sweden's actions

Can you confirm if this part is true?

and yet, -sometimes- it's true

Let's not rule out the possibility that Zuckerberg saw Page's statement and sort of copy-pasted it.