luriel

30 ms·

241.
by luriel 14y ago
Plan 9's libthread ( http://man.cat-v.org/plan_9/2/thread ) provides similar CSP-style concurrency to Go. Yet, the authors, after using it for many years, and after having used and built systems where it was part of the language (eg., Inf
242.
by luriel 14y ago
> Today we are very much blessed with quite a few large libraries And with magnitude orders more RAM. And just because there are large libraries doesn't mean they are either necessary or desirable. > not just X but Qt on top of that
243.
by luriel 14y ago
Java and Flash are notoriously problematic (not to mention insecure) on 32-bits too.
244.
by luriel 14y ago
Yes, his code style is bizarre at best, both for C and Go. This is particularly jarring in Go when gofmt exists and is used almost universally (I think this is the first time I see non-gofmt'd code in quite a while).
245.
by luriel 14y ago
I disagree that panic/recover is worse than exceptions, I find it a more pleasant and lightweight mechanism, but the big difference is that panic/recover are not used like exceptions at all in Go, they are basically used only for programm
246.
by luriel 14y ago
There is also sam -d ;) http://man.cat-v.org/plan_9/1/sam (It hides the GUI and gives it a more ed-like interface that you can easily script, but this is kind of a hack for Plan 9-nuts ;)
247.
by luriel 14y ago
Except that PCREs (or most of their implementations which are used in all those languages, re2 and Go's standard regexp package are exceptions) have some fundamental issues: http://swtch.com/~rsc/regexp/regexp1.html
248.
by luriel 14y ago
Acme mouse chording is really cool, doing something similar with keyboard-oriented editors is much more tedious and often outright painful ( http://acme.cat-v.org/mouse ). I suspect ken spends most of his time thinking rather than typing,
249.
by luriel 14y ago
This is not really an issue with the language but with the implemetnation and most languages/libraries/OS-es are not suited for "hard real-time" either. How many people are writing "hard real-time" code? I suspect not many, and yes, for the
250.
by luriel 14y ago
I'm not sure how to take that review given that his two main complaints seem to be: 1) That Go has i++ and not ++i. Don't even know what to say to someone who thinks this a major issue, really. 2) That the declaration syntax is 'unattractiv
251.
by luriel 14y ago
In Go you can also just disable the GC if you really want to, but obviously then you have to be more careful.
252.
by luriel 14y ago
> It's a royal pain writing go that talks to C code, compared to say, lua or python This is plain wrong, you can pretty much call C code directly, while in Python and the like you really have to write a wrapper. Of course in Go you wi
253.
by luriel 14y ago
The C and C++ code Google runs on their servers is always statically linked, and I would call that Serious Work. In the end, static linking is almost invariably superior to dynamic linking: simpler toolchain, simpler runtime, better reliabi
254.
by luriel 14y ago
The GC in Go 1 is a bit smarter than it used to be, and it is going to be even smarter in Go 1.1, this things take time, and the current GC works quite well for most people. Also Go gives you control over memory layout, which allows you to
255.
by luriel 14y ago
> For those problems, after a while, the bare metal support was removed from the language completely... Not really true, you have direct control over the memory layout of your data structures, and if you want to do really tricky stuff t
256.
by luriel 14y ago
> The point you mention is only valid when using entirely static memory Exactly, and you can also do that in Go to avoid the GC.
257.
by luriel 14y ago
Your C code looks very unidiomatic to me, but I guess that is relatively a matter of taste (still I don't understand why would somebody use C if they don't like to write code in the 'classic' C style as seen in the original Unix and Plan 9
258.
by luriel 14y ago
Go is relatively beginner friendly, is simpler and smaller than most languages around (even for example Python). Go code is concise but without dark magic (is easy to see what code does by just looking at it). And you can even read the whol
259.
by luriel 14y ago
Goroutines are great, but I'm not convinced they are the greatest advantage over C. Go cleans up and fixes pretty much every issue C had, and improves it in many non-obvious areas, from the syntax to the type system. And when porting an exi
260.
by luriel 14y ago
> Looking at other systems such as Haiku shows that porting Go is encouraged, the only issues have to deal with assumptions in the build (in this case, I think /bin/env/bash is included everywhere, there's no global variable to change t
261.
by luriel 14y ago
OpenBSD and Plan 9 pretty much work already, even if the ports might not be as polished as FreeBSD. Also there is gccgo, which AFAIK also works on Solaris and probably elsewhere.
262.
by luriel 14y ago
A somewhat related video that often gets posted, but is worth posting again: Why you should never talk to the police (even if you have nothing to hide!): http://www.youtube.com/watch?v=6wXkI4t7nuc It includes some stories that illustrate
263.
by luriel 14y ago
I don't think the Go developers "think in oop", and they certainly don't love Java.
264.
by luriel 14y ago
> One thing to remember about the little guy is, he doesn't have any money, so he's not worth going after. But part of the point of being a little guy is that you have a chance to not always be a little guy, but with the patent cartel/
265.
by luriel 14y ago
Note that Go has no 'classes', and doesn't follow what many people consider mainstream OO principles (eg., inheritance), and many people would say this is one of the things that make it so great, specially in large projects (working out a g
266.
by luriel 14y ago
> The problem with this is that may of the victims of these crimes are too stupid (EDIT: under-educated / let down by the schooling system) to vote for the right person (or at all) during elections. They are not necessarily stupid, see
267.
by luriel 14y ago
> The code relies heavily on preprocessor macros and some weird gcc-only syntax that made my head hurt. The preprocessor is generally recognized as one of C's biggest flaws, is not for nothing that Ken Thompson, the first C programmer
268.
by luriel 14y ago
If you want to learn C, K&R is the right way to do it. C: A Reference Manual is excellent and is probably the only other C book you need, but only if you are already a C programmer, and only for what the title implies: reference.
269.
by luriel 14y ago
I don't think the concern is training, but the complexity caused by how various features interact, and how hard they make to reason about code. Go is designed so it is very easy to read and reason about what code does.
270.
by luriel 14y ago
YouTube is starting to use Go quite a lot. They even released this: http://code.google.com/p/vitess/

More ›