4 ms·
Seems to be a summary/rehash of https://www.usenix.org/publications/loginonline/freebsd-firecracker https://www.usenix.org/publications/loginonline/freebsd-fire
by wink 3y ago
Seems to be a summary/rehash of https://www.usenix.org/publications/loginonline/freebsd-firecracker https://www.usenix.org/publications/loginonline/freebsd-fire... - which I guess came first, and is a better article.
- lproven 3y agoI wrote the article. Yes, it's a summary of that, overall, and I linked to that post in my article. That blog post is by the developer who did the work. Of course it came first: it is the source material! Did you not even notice that I linked to it and recommended reading it?!
- wink 3y agoYes, and sorry if that sounded too confrontational. I didn't take a lot of new things from this and I know many people here read the comments first, and in this case I prefer the source material.
- lproven 3y agoFair enough. It is a hard line to walk as a journo. I have discovered, the hard way, that: * _many_ people can't skim * but they don't know that they can't * so they misunderstand and blame the writer * no matter if you provide links to explain everything, many won't follow any of 'em * but you _must_ provide citations for every fact or claim What I try to do is boil down long stuff to shorter punchier summaries, and explain harder tech stuff so non-experts can follow it. If the reasons for something, or what it means, or why it matters, are not very obvious, I try to explain the whys and wherefores. But when it's simple, some will complain there's not enough. If it's not simple, some will complain it's too hard. No matter how well referenced, some will argue. Even if it's my direct personal experience, some will tell me I am wrong.