3 ms·
Hey folks! This is part of our whitepaper series. This means that the audience is CTOs of larger organizations, and so the tone and content are geared for that,
by steveklabnik 8y ago
Hey folks! This is part of our whitepaper series. This means that the audience is CTOs of larger organizations, and so the tone and content are geared for that, more than HN. Please keep that in mind!
- breatheoften 8y agoAre CTO's of largish organizations still not part of the hacker news audience ...? That seems a bit of a damning statement to be about the population of CTO's ...
- tejasmanohar 8y agoI'm sure some are on HN, but it's definitely not "the place" for them, and many have probably never heard of it
- shaklee3 8y agoI would be shocked if any CTOs of large organizations browse HN. Large orgs put people in those positions that are more about theory and future thinking over current knowledge.
- manigandham 8y agoIt's expected that high-level executives of large organizations deal with planning and strategy rather than low-level technical details. They're not following language features or implementations. However in that case, this whitepaper (and many others) are damning in how little they actually state and why so many technical decisions go wrong.
- phillipcarter 8y agoGood overall whitepaper and I like to see efforts like these. One are I felt was missing is some data here: "It keeps resource usage low without the possibility of compromising memory safety. " How did the resource usage compare with the Go and node rewrites? What metrics were used under which workload? Benchmarks are never perfect but I think a CTO-level person would like to see a table of results like that.
- deleted 8y ago[deleted]