[bsg75]

> I don’t see Go as something that is going to serve as a “better C”, so I’m waiting for something new.

Go probably would not be a good candidate for something like Redis, as performance and memory use could become worse. As pointed out elsewhere, Go has become a better replacement for scripting languages is some circumstances, more than it has been used to replace C.

> I’m not a big fan of new things in IT when they have the smell of being mostly fashion-driven, without actually bringing something new to the table.

Assuming this still refers to Go, I can't think of a new yet less "fashionable" language [1], which is in part why I like it.

[1] http://stevebate.silvrback.com/go-is-boring

[eloff]

I think the Go compiler, runtime, and GC would need to mature a lot before it could be used to create something competitive with Redis. But it is moving in that direction. A pauseless GC[1], a numa-aware scheduler with lower overheads[2], more efficient atomic operations[3], all these are/have been discussed by the Go team and are actual goals AFAIK.

I'm building a database in Go, keeping the data off-heap (which solves the GC problem for now.) The performance will lag C currently, but I do think it will eventually get close.

[1] https://groups.google.com/forum/#!topic/golang-dev/GvA0DaCI2... [2] https://docs.google.com/document/d/1TTj4T2JO42uD5ID9e89oa0sL... [3] https://github.com/golang/go/issues/8739