3 ms·
Performance, I also feel more in control, it's hard to describe the feeling, it's just as though Go is providing an abstracted interface to the hardware, where
by shanelja 14y ago
Performance, I also feel more in control, it's hard to describe the feeling, it's just as though Go is providing an abstracted interface to the hardware, where as C++ provides raw, unfiltered but potentially dangerous access.
Perhaps it's just my personal experience though.
- vanderZwan 14y agoThat kind of fits Rob Pike's explanation for why Go isn't more popular with C++ programmers (although he gave it a negative spin). In a neutral way, it's like: if you spent all that effort mastering this language to get such fine-grained control, why would you give that up again? And really, I understand: why would you give that up? Especially if you know how to use C++ in a fairly painless way.
- shanelja 14y agoDo you have a link to that? I would be interested to read it. I also couldn't agree more, but normally, people retort with the Hammer and Screwdriver argument.
- mseepgood 14y agohttp://commandcenter.blogspot.de/2012/06/less-is-exponentially-more.html http://commandcenter.blogspot.de/2012/06/less-is-exponential...
- eru 14y ago> where as C++ provides raw, unfiltered but potentially dangerous access. Wouldn't that be assembly? Last time I heard Stroustrup, he was all raving about abstractions, not raw unfiltered access.
- pjmlp 14y ago> Performance, I also feel more in control, it's hard to describe the feeling, it's just as though Go is providing an abstracted interface to the hardware, where as C++ provides raw, unfiltered but potentially dangerous access. Funny I though C++ did exactly the same thing. Where are the L1, L2 and L3 caches references, multiple opcode execution pipelines, processor instructions ?