My subject is Clarice Lispector’s Near to the Wild Heart (1943), her first novel, and the only book of hers I have read.  I read Alison Entrekin’s English translation because 1) I did not have a Portuguese text handy and 2) I figured it would be too hard for me, which I think is right.  I had enough trouble with the book in English. When she spoke, she invented crazy, crazy!  (162) For 90 pages, Lispector alternates scenes of Joana’s childhood and the beginnings of her marriage.  Then we get a hundred pages of the marriage falling apart.  The husband has, for example, a pregnant girlfriend, although that is more of a symptom of the collapse.  The real cause is that Joana is psychologically, hmm hmm hmm, unusual. How many times had she tipped the waiter more than necessary just because she’d remembered that he was going to die and didn’t know it. (101) That is maybe the strangest clear thought she expresses.  Joana’s stream of thoughts are generally much more abstract.  Entirely abstract.  Here is the ending of one abstract paragraph moving into the beginning of another. Eternity was not an infinitely great quantity that was worn down, but eternity was succession. Then Joana suddenly understood that the utmost beauty was to be found in succession, that movement explained form – it was so high and pure to cry: movement explains form! – and pain was also to be found in succession because the body was slower than the movement of uninterrupted continuity. (36) Joana’s thinking, outside of the childhood scenes, if often unconnected, or just barely connected, to a scene, or anything material at all.  A lot of this: How was a triangle born? as an idea first? or did it come after the shape had been executed? would a triangle be born fatally? things were rich…  Where does music go when it’s not playing? (164, ellipses mine) I would describe passages like this as philosophical if I understood how Joana moves from one thought to another, which I generally did not.  Sometimes I felt a move toward Surrealism, although without the playfulness or materiality I enjoy in Surrealism. The man was a child an amoeba flowers whiteness warmth like sleep for now is time for now is life even if it is later… (165, ellipses in original) This is Joana falling asleep, so here I did know what Lispector was depicting.  I could, in this section, draw a connection between my own perceptions of what I call “reality” and Lispector’s representation of an aspect of reality, the process and psychology of falling asleep.  But mostly I found that hard to do. Another possibility is that Joana is meant to be a pathological case study, repellent to understanding.  Or that she is meant to be entirely normal, a version of the way Lispector sees the world, however nuts she looks to me, the kind of mismatch I often bounce off when reading D. H. Lawrence, where I think I am reading about someone who is psychologically unusual and begin to think, oh no, he thinks everyone is like this. Yet another idea is that the novel is full of nonsense and anti-rationality, again like Surrealism, something I usually enjoy a lot.  I could have used more, I don’t know, jokes, I guess.  Surrealism is fun.  And material, too, not abstract.  Paris Peasant is about walking around in the mall. Benjamin Moser, in the introduction, suggests that Lispector’s “project was less artistic than spiritual… not an intellectual or artistic endeavor” (xi), a good clue about my difficulties with Near to the Wild Heart.  Beyond a couple of the childhood scenes I never found a hook into the art of Lispector’s novel.  It is the biggest mismatch of a book with my taste that I have bumped against in quite a while. Tony Malone liked the novel more than I did but his response, section by section, looks similar to mine: “the internal monologues were a little too abstract at times,” were they ever. Someday I will try another Lispector novel, perhaps one from the 1960s, and see how that goes.  Perhaps I will try one in Portuguese.

20 years of Linux on the Desktop (part 3) Previously in "20 years of Linux on the Deskop": After contributing to the launch of Ubuntu as the "perfect Linux desktop", Ploum realises that Ubuntu is drifting away from both Debian and GNOME. But something else is about to shake the world… 20 years of Linux on the Desktop (part 1) 20 years of Linux on the Desktop (part 2) The new mobile paradigm While I was focused on Ubuntu as a desktop solution, another GNOME+Debian product had appeared and was shaking the small free software world: Maemo. It will come as a shock for the youngest but this was a time without smartphones (yes, we had electricity and, no, dinosaurs were already extinct, please keep playing Pokémon instead of interrupting me). Mobile phones were still quite new and doing exactly two things: calls and SMSes. In fact, they were sold as calling machines and the SMS frenzy, which was just a technical hack around the GSM protocol, took everybody by surprise, including operators. Were people really using awkward cramped keyboard to send themselves flood of small messages? Small pocket computers with tiny keyboard started to appear. There were using proprietary operating systems like WinCE or Symbian and browsing a mobile version of the web, called "WAP", that required specific WAP sites and that nobody used. The Blackberry was so proprietary that it had its own proprietary network. It was particularly popular amongst business people that wanted to look serious. Obama was famously addicted to his Blackberry to the point that the firm had to create a secure proprietary network only for him once he took office in the White House. But like others, Blackberries were very limited, with very limited software. Nothing like a laptop computer. N770, the precursor In 2005, Nokia very quietly launched the N770 as an experiment. Unlike its competitors, it has no keyboard but a wide screen that could be used with a stylus. Inside was running a Debian system with an interface based on GNOME: Maemo. The N770, browsing Wikipedia Instead of doing all the development in-house, Nokia was toying with free software. Most of the software work was done by small European companies created by free software hackers between 2004 and 2005. Those companies, often created specifically to work with Nokia, were only a handful of people each and had very narrow expertise. Fluendo was working on the media framework GStreamer. Immendio was working on the GTK user interface layer. Collabora was focusing on messaging software. Etc. Far from the hegemony of American giant monopolists, the N770 was a mostly European attempt at innovating through a collaborative network of smaller and creative actors, everything led by the giant Nokia. During FOSDEM 2005, GNOME developer Vincent Untz lent me a N770 prototype for two days. The first night was a dream come true: I was laying in bed, chatting on IRC and reading forums. Once the N770 was publicly released, I immediately bought my own. While standing in line in the bakery one Sunday morning, I discovered that there was an unprotected wifi. I used it to post a message on the Linuxfr website telling my fellow geeks that I was waiting for my croissants and could still chat with them thanks to free software. Those days, chatting while waiting in a queue has been normalised to the point you remark someone not doing it. But, in 2005, this was brand new. So new that it started a running meme about "Ploum’s baker" on Linuxfr. Twenty years later, some people that I meet for the first time still greet me with "say hello to your baker" when they learn who I am. For the record, the baker, an already-old woman at the time of the original post, retired a couple years later and the whole building was demolished to give place to a motorbike shop. This anecdote highlights a huge flaw of the N770: without wifi, it was a dead weight. When I showed it to people, they didn’t understand what it was, they asked why I would carry it if I could not make calls with it. Not being able to use the Internet without a wifi was a huge miss but, to be fair, 3G didn’t exist yet. Another flaw was that installing new software was far from being user-friendly. Being based on Debian, Maemo was offering a Synaptic-like interface where you had to select your software in a very long list of .deb packages, including the technical libraries. Also, it was slow and prone to crash but that could be solved. Having played with the N770 in my bed and having seen the reactions of people around me when I used it, I knew that the N770 could become a worldwide hit. It was literally the future. There were only two things that Nokia needed to solve: make it a phone and make it easy to install new software. Also, if it could crash less, that would be perfect. The Nokia (un)management guide to failure But development seemed to stall. It would take more than two years for Nokia to successively release two successors to the N770: the N800 and the N810. But, besides some better performance, none of the core issues were addressed. None of those were phones. None of those offered easy installation of software. None were widely released. In fact, it was so confidential that you could only buy them through the Nokia website of some specific countries. The items were not in traditional shops nor catalogues. When I asked my employer to get a N810, the purchasing department was unable to find a reference: it didn’t exist for them. Tired by multiple days of discussion with the purchasing administration, my boss gave me his own credit card, asked me to purchase it on the Nokia website and made a "diverse material expense" to be reimbursed. The thing was simply not available to businesses. It was like Nokia wanted Maemo to fail at all cost. While the N800 and N810 were released, a new device appeared on the market: the Apple iPhone. I said that the problem with the N770 is that you had to carry a phone with it. Steve Jobs had come to the same conclusion with the iPod. People had to carry an iPod and a phone. So he added the phone to the iPod. It should be highlighted that the success of the iPhone took everyone by surprise, including Steve Jobs himself. The original iPhone was envisioned as an iPod and nothing else. There was no app, no app store, no customisation (Steve Jobs was against it). It was nevertheless a hit because you could make calls, listen to music and Apple spent a fortune in marketing to advertise it worldwide. The marketing frenzy was crazy. Multiple people that knew I was "good with computers" asked me if I could unlock the iPhone they bought in the USA and which was not working in Europe (I could not). They spent a fortune on a device that was not working. Those having one were showing it to everyone. With the iPhone, you had music listening and a phone on one single device. In theory, you could also browse the web. Of course, there was no 3G so browsing the web was mostly done through wifi, like the N770. But, at the time, websites were done with wide screens in mind and Flash was all the rage. The iPhone was not supporting Flash and the screen was vertical, which made web browsing a lot worse than on the N770. And, unlike the N770, you could not install any application. The iPhone 1 was far from the revolution Apple want us to believe. It was just very good marketing. In retrospective, the N770 could have been a huge success had Nokia done some marketing at all. They did none. Another Linux on your mobile In 2008, Google launched its first phone which still had a physical keyboard. Instead of developing the software from scratch, Google used a Linux system initially developed as an embedded solution for cameras: Android. At the same time, Apple came to the realisation I had in 2005 that installing software was a key feature. The App Store was born. Phone, web browsing and custom applications, all on one device. Since 2005, people who had tried the N770 knew this was the answer. They simply did not expect it from Apple nor Google. When Android was first released, I thought it was what Maemo should have been. Because of the Linux kernel, I was thinking it would be a "free" operating system. I made a deep comparison with Maemo, diving into some part of the source code, and was surprised by some choices. Why Java? And why would Android avoid GStreamer in its multimedia stack? Technical explanations around that choice were not convincing. Years later, I would understand that this was not a technical choice: besides the Linux kernel itself, Google would explicitly avoid every GPL and LGPL licensed code. Android was only "free software" by accident. Gradually, the Android Open Source Project (AOSP) would be reduced to a mere skeleton while Android itself became more and more restricted and proprietary. In reaction to the iPhone and to Android, Nokia launched the N900 at the end of 2009. Eventually, the N900 was a phone. It even included an app store called, for unknown marketing reasons, "OVI store". The phone was good. The software was good, with the exception of the infamous OVI store (which was bad, had a bad name, a non-existent software offering and, worse of all, was conflicting with deb packages). The N900 would probably have taken the world by storm if released 3 years earlier. It would have been a success and a huge competitor to the iPhone if released 18 months before. Is it too late? The world seems to settle with an Apple/Google duopoly. A duopoly that could have been slightly shacked by the N900 if Nokia had done at least some marketing. It should be noted that the N900 had a physical keyboard. But, at that point, nobody really cared. When failing is not enough, dig deeper At least, there was the Maemo platform. Four years of work. Something could be done with that. That’s why, in 2010, Nokia decided to… launch Meego, a new Linux platform which replaced the Debian infrastructure by RPMs and the GNOME infrastructure by Qt. No, really. Even if it was theoretically, the continuation of Maemo (Maemo 6, codenamed Harmattan, was released as Meego 1), it felt like starting everything from scratch with a Fedora+KDE system. Instead of a strong leadership, Meego was a medley of Linux Foundation, Intel, AMD and Nokia. Design by committee with red tape everywhere. From the outside, it looked like Nokia outsourced its own management incompetence and administrative hubris. The N9 phone would be released in 2011 without keyboard but with Meego. History would repeat itself two years later when people working on Meego (without Nokia) would replace it with Tizen. Yet another committee. From being three years ahead of the competition in 2005 thanks to Free Software, Nokia managed to become two years too late in 2010 thanks to incredibly bad management and choosing to hide its products instead of advertising them. I’ve no inside knowledge of what Nokia was at this time but my experience in the industry allows me to perfectly imagine the hundreds of meetings that probably happened at that time. When business decisions look like very bad management from the outside, it is often because they are. In the whole Europe at the time, technical expertise was seen as the realm of those who were not gifted enough to become managers. As a young engineer, I thought that managers from higher levels were pretentious and incompetent idiots. After climbing the ladder and becoming a manager myself, years later, I got the confirmation that I was even underestimating the sheer stupidity of management. It is not that most managers were idiots, they were also proud of their incompetence and, as this story would demonstrate, they sometimes need to become deeply dishonest to succeed. It looks like Nokia never really trusted its own Maemo initiative because no manager really understood what it was. To add insult to injury the company bought Symbian OS in 2008, an operating system which was already historical and highly limited at that time. Nodoby could figure out why they spent cash on that and why Symbian was suddenly an internal competitor to Maemo (Symbian was running on way cheaper devices). The emotional roller coster In 2006, I was certain that free software would take over the world. It was just a matter of time. Debian and GNOME would soon be on most desktop thanks to Ubuntu and on most mobile devices thanks to Maemo. There was no way for Microsoft to compete against such power. My wildest dreams were coming true. Five years later, the outlooadministrative hubris. The N9 phone would be released in 2011 without keyboard but with Meego.k was way darker. Apple was taking the lead by being even more proprietary and closed than Microsoft. Google seemed like good guys but could we trust them? Even Ubuntu was drifting away from its own Debian and GNOME roots. The communities I loved so much were now fragmented. Where would I go next? (to be continued) Subscribe by email or by rss to get the next episodes of "20 years of Linux on the Desktop". I’m currently turning this story into a book. I’m looking for an agent or a publisher interested to work with me on this book and on an English translation of "Bikepunk", my new post-apocalyptic-cyclist typewritten novel which sold out in three weeks in France and Belgium. I’m Ploum, a writer and an engineer. I like to explore how technology impacts society. You can subscribe by email or by rss. I value privacy and never share your adress. I write science-fiction novels in French. For Bikepunk, my new post-apocalyptic-cyclist book, my publisher is looking for contacts in other countries to distribute it in languages other than French. If you can help, contact me!

A while back, I wrote a post titled “What is a Platform?”. I defined what a platform is and why tech companies are so determined to become labeled as one. My definition of a platform is a tool that allows users to define and build their own things, which can be used by other users. Tech companies wish to own platforms, as they are the engines that propel the flywheel toward infinite growth. But as Bill Simmons puts it best, there’s always a good “zag” to every “zig”. I want to challenge my own assumptions that platforms are inherently the best business model and explore how the opposite model, point solutions, can be just as healthy in product design. I want to compare two companies I admire: Notion (the platform) and Linear (the point solution). I also want to acknowledge my feelings about Kibu’s place in this battle and how forces like competitors, AI, and market needs influence us. Notion, the Platform Notion, known for its minimalism, speed, and extensibility, has been the techy alternative to Google Docs for almost a decade. Its approach of building ‘Lego for software’ is embedded in the company’s culture and felt inside its product. From the beginning, Notion’s mission was to allow anyone to create software. But, after realizing that everyday humans had neither the time nor care to develop, they switched to productivity. Create a Notion account today, and you will be greeted with a blank canvas, much like a Word doc. But the real magic is the first time you press the / key, which opens a world of blocks, allowing you to seamlessly create lists, tables, charts, mentions, and embeds that all cooperate in the ecosystem of your given folder. Notion called itself the Lego of software. With blocks, you can define your own things. With a collection of things, you can design templates, which can be consumed by many. Notion entered a rocky era when it strayed from this path. On Lenny’s podcast, CEO Ivan Zhao recounts Notion’s “lost years,” where he reflects on a failed feature. Notion introduced Sprints, a specific methodology for managing projects. From the start, Ivan and the team felt Sprints didn’t feel right. After a year, they could articulate that injecting a rigid, less adaptable solution didn’t align with Notion’s core philosophy of block-based design. Imagine opening a box of Legos and finding a perfectly curved, painted airplane inside! Where’s the fun and customization in that?? For Ivan and Notion, anything outside of block-based thing-builders is not a tool that belongs in Notion. While incredibly friendly and familiar, Notion is very much a platform. Linear, the Point Solution I’ve already written about what makes Linear so beautiful. Linear’s strength lies in its focus on building the best issue-tracking tool for the IC engineer: the 20-something developer who just wants to code without the bureaucracy. This unwavering focus on a specific persona is what makes them a point solution for modern software development teams. A point-solution mindset is embedded in how Linear decides on features. In an interview with Head of Product Nan Yu, he reflects on one decision (paraphrasing): We never liked the idea of letting management add custom fields to Linear because if you add 100+ custom fields, all your ICs would hate it. But we kept getting requests for it, and we’d ask, “Well, why do you want custom fields?” And 40% of customers said, “Well, I have Customer X, and their request is really important. I need everyone to know that Customer X needs this. I need to track it.” That sounded like a very useful and powerful thing for us to do. So let’s build a solution that solves that problem without making ICs’ lives harder. Instead of building custom fields, Linear created Customer Requests, which captures issues and tags direct customer quotes from various support channels- all without ICs needing to do anything. I’m impressed by the incredible discipline Linear exemplifies here. Clearly, the easy and “more scalable” solution would have been to introduce custom fields. But because they knew it would undermine their key persona, they kept poking at the real problem and addressed that instead. In spirit, Linear and Notion have polar opposite perspectives: Notion welcomes platform-like design with blocks, custom fields, and automations, while Linear rejects it- staying disciplined in building out-of-the-box solutions that fit the lowest common denominator of its addressable market. So, what’s right? Cold take: they’re both right, and the lesson is that two roads can lead to equally desirable destinations. I’m much more focused on the question: what’s right for Kibu? Kibu is already much closer to Linear as a point solution, and I believe it should stay there. Kibu already has an incredible niche in the Disability Provider market, and we’re building real point solutions tailored for Day Habilitation programs within these providers. Our competitors, namely Therap, take a horizontal approach to their solutions- seeing Disability Providers as just one vertical of many. This forces customers to do upfront and ongoing management of defining generic things within Therap. Some providers may see this as powerful and extensible- likely large organizations with dedicated IT resources. Kibu’s bet is that the vast majority of the market doesn’t have this luxury and would prefer out-of-the-box solutions where things are already in their language (service records, attendance, members). Kibu, as a point solution, makes more sense for the market. Our market is exceptionally non-technical, highly regulated, and rightfully sees software as a secondary asset to their true offerings: the physical facilities and human resources that provide the service. Taken together, my bet is that our market would rather be told what they need than inspired to build it themselves. The more specific we can get, the better. A press release that reads “Kibu launches ready-made solution for Day Habs in Georgia” will resonate more than “Kibu introduces custom fields, allowing any organization to build their own solutions.” Kibu, as a point solution, will open the floodgates for our product team to introduce omotenashi- anticipating our users’ needs before they ask. Notifications and help documentation can be more specific. LLM solutions can be prompt-engineered with niche instructions. Our codebase will be hardcoded with the nouns and verbs our market understands, forcing our tech team to truly understand the needs of our users, which is constrained by our inability to dogfood. There’s so much more to unpack with AI’s influence, scaling the “Day Habs in Georgia” solutions, and more. Nevertheless, I believe that point solutions are what our market needs, and our messaging and product decisions should be guided by that assumption.

The post Snowflake appeared first on The Perry Bible Fellowship.

“Maurine Smith died March 8, 1919, at the age of twenty-three years. Nearly her whole life had been one of intense physical suffering, and she knew few of the usual felicities.”  Yvor Winters is introducing us to a poet whose name you likely have never encountered.  Smith and Winters were members of the Poetry Club of the University of Chicago, along with Glenway Wescott, Elizabeth Madox Roberts and a few others. Five of Smith’s poems were published in Poetry two and a half years after her death. After another two years, Monroe Wheeler published a chapbook, The Keen Edge, containing eighteen of Smith’s poems. Winters provided the brief introduction:   “Unless one speaks of the dead from a very complete knowledge, one speaks with diffidence, and my acquaintance with Miss Smith was slight. . . . Thin, and a trifle bent, withdrawn  she surveys the autumn morning through a window. And then the lines from an unpublished poem:   “‘I dust my open book, But there is no dust on the pages.’   “A hand as fine as the lines, and that is all.”   Winters’ closing line might almost be a poem. After publication of the chapbook, Smith evaporated from literary history for sixty years. She has no Wikipedia page – one's confirmation of existence in the digital age. In 1987, poet and publisher R.L. Barth returned The Keener Edge to print, and he later gave me a copy. The poet-novelist Janet Lewis, Winters’ widow and also a member of the Poetry Club, published a critical article, “The Poems of Maurine Smith,” in the Winter 1990 issue of Chicago Review. Despite the growth in women’s studies and the revival of interest in many previously neglected female writers, Lewis’ piece remains the only substantial critical examination of Smith and her poetry I've been able to find. Lewis tells us she met Smith only once, in January 1919. I’m touched by Lewis using Smith’s first name after more than seventy years:     “I think of Maurine as having a mind well schooled in English verse. I can as easily relate her work to that of Christina Rossetti as to that of Adelaide Crapsey, who was almost her contemporary, and certainly an influence.”   Describing her sole meeting with Smith some 106 years ago, Lewis writes:   “I cannot remember if Maurine submitted any poems for discussion that evening. She was too ill to attend the next meeting, when Glenway Wescott read [Smith’s] “Ceremony.” He read it, as he read each of the poems which we dropped on the table, without giving the name of the writer. I remember, although not knowing whose poem it was, how deeply I was touched by it, the beauty of the control of both form and feeling. This is the poem. It may as well be introductory now, as it was then:   “The unpeopled conventional rose garden  Is where I shall take my heart  With this new pain.  Clipped hedge and winter-covered beds  Shall ease its hurt.  When it has grown quiet,  I shall mount the steps, slowly,  And put three sorrows in the terra-cotta urn  On that low gate-pillar,  And leave them there, to sleep,  Beneath the brooding stillness of a twisted pine.”   Lewis notes that the members of the Poetry Club were interested in free verse, the formless form then still something of a novelty: “It was not entirely respectable in 1918.” Another Smith poem reminds Lewis of Christina Rosetti’s “Haply I may remember, and haply may forget.” Here is “The Dead”:   “You, who were blind to beauty,  Unheedful of song, You have time now to remember In your quiet under the ground; And does the time seem long?   “Harken, in your silence; All things grow. Is not your heart importunate? You, too, must long again To feel the wind blow.”   As late as 1930, Winters was hoped to publish a more complete edition of Smith’s poems, with a biography supplied by her sister. He believed some forty poems were extant. In a letter to Glenway Wescott, Winters writes: “Maurine was one of our best poets, I am more and more certain.” See The Selected Letters of Yvor Winters (2000), edited by Barth and published by Ohio University Press/Swallow Press.