And forums where readers still communicate with authors shaping the new chapters.
> This essay will focus on two particularly striking mid-nineteenth-century examples of the complex relationships that unite the writer, readers, and editor of a serial. The first one is a French novel. Les Mystères de Paris, by Eugène Sue, which was serialized over a year and a half in 1842-43 in the Paris daily Le Journal des Débats Politiques et Littéraires, which translates literally as the Journal of Political and Literary Debates; the second is Uncle Tom's Cabin, by Harriet Beecher Stowe, which first appeared in the antisîavery weekly, the National Era, between 1851 and 1852.
> My first point is that in the case of both works, apart from the fact that they aimed at social reform and were tremendously popular and violently criticized, their respective readers played a role in giving final form to each novel, particularly in terms of length. I will then examine the locus of the discussion that is being carried on between the readers and the writer. In Stowe's case, since she was writing far from Washington, where the National Era was based, the conversation between the reader and the writer was carried on in the columns of the Era itself. In Sue's case, the correspondence between reader and writer was mostly conducted via private letters, for reasons I will go into later. Sue kept more than three hvmdred of the letters he received while writing Les Mystères; those letters have now been edited and published. As can be imagined, they provide a rare and invaluable insight into the interaction between reader and writer during the publication of a serial.
I had this feeling exactly listening (great, as everything Aaron does) presentation about manipulation and transformation of trees in APL, https://www.youtube.com/watch?v=hzPd3umu78g
And 5 if not 9 out of that Fortune 10' NoSQL dbs were just tied with a duck tape ('Our frontend team needs something they could understand - Ah okay then') to the mainframe with a previous generation of NoSQL - like ADABAS, IMS or z/TPF - and a ton of COBOL code where all the work is done since forever.
OTOH, "As one step toward building high performance NVM systems, we explore the potential dependencies between system call performance and major hardware components (e.g., CPU, memory, storage) under typical user cases (e.g., software compilation, installation, web browser, office suite) in this paper. We find that there is a strong dependency between the system call performance and the CPU architecture. On the other hand, the type of persistent storage plays a less important role in affecting the performance."
It seems some highest-performant enterprise solutions consider the MS-DOS way as well.
"The Coherent Accelerator Processor Interface (CAPI) is a general term for the infrastructure that provides high throughput and low latency path to the flash storage connected to the IBM POWER 8+ System. CAPI accelerator card is attached coherently as a peer to the Power8+ processor. This removes the overhead and complexity of the IO subsystem and allows the accelerator to operate as part of an application. In this paper, we present the results of experiments on IBM FlashSystem900 (FS900) with CAPI accelerator card using the "CAPI-Flash IBM Data Engine for NoSQL Software" Library. This library provides the application, a direct access to the underlying flash storage through user space APIs, to manage and access the data in flash. This offloads kernel IO driver functionality to dedicated CAPI FPGA accelerator hardware. The results indicate that FS900 & CAPI, together with the metadata cache in RAM, delivers the highest IO/s and OP/s for read operations. This was higher than just using RAM, along with utilizing lesser CPU resources."
Universal kernel bypass for IO? Does it imply every userspace program should know how to communicate with every kind of IO device? No block layer? What about memory and caching?
"Itanium was in-order VLIW, hope people will build compiler to get perf. We came from opposite direction - we use dynamic scheduling. We are not VLIW, every node defines sub-graphs and dependent instructions. We designed the compiler first. We build hardware around the compiler, Intel approach the opposite."
https://www.anandtech.com/show/13255/hot-chips-2018-tachyum-...
> This find xargs mawk pipeline gets us down to a runtime of about 12 seconds, or about 270MB/sec, which is around 235 times faster than the Hadoop implementation.
> Now in Windows 10, User32/GDI is deprecated and obsolete for high-performance applications (and it’s really slow too after they axed GDI hardware acceleration in Vista), but there isn’t a single replacement, instead there’s like 5 of 6 - all incompatible with each other. While it’s true that it shouldn’t matter because OLE objects were rendered to their own separate hWnd, consider that the new UWP system doesn’t use hWnds, and frameworks like WPF have “air gap” issues with rendering their content overlaying another hWnd and often resort to hacks using window content blitting which drastically hurts performance (as you need to blit to/from RAM, instead of keeping it all in VRAM).
Classic, yes. Forums like XDA-Developers, EEVBlog, Head-Fi, or DIYAudio.com. You can pretty much just search for "<topic> forum" and find them. Many of the best forums in the modern Internet are Russian and Chinese by the way.