Full Width [alt+shift+f] Shortcuts [alt+shift+k]
Sign Up [alt+shift+s] Log In [alt+shift+l]
55
One of the ways I like to do development is to build something, click around a ton, make tweaks, click around more, more tweaks, more clicks, etc., until I finally consider it done. The clicking around a ton is the important part. If it’s a page transition, that means going back and forth a ton. Click, back button. Click, right-click context menu, “Back”. Click, in-app navigation to go back (if there is one). Click, keyboard shortcut to go back. Over and over and over. You get the idea. It’s kind of a QA tactic in a sense, just click around and try to break stuff. But I like to think of it as being more akin to woodworking. You have a plank of wood and you run it through the belt sander to get all the big, coarse stuff smoothed down. Then you pull out the hand sander, sand a spot, run your hand over it, feel for splinters, sand it some more, over and over until you’re satisfied with the result. With software, the fact is that sometimes there are just too many variables to know and test...
6 months ago

Improve your reading experience

Logged in users get linked directly to articles resulting in a better reading experience. Please login for free, it takes less than 1 minute.

More from Jim Nielsen’s Blog

Building WebSites With LLMS

And by LLMS I mean: (L)ots of (L)ittle ht(M)l page(S). I recently shipped some updates to my blog. Through the design/development process, I had some insights which made me question my knee-jerk reaction to building pieces of a page as JS-powered interactions on top of the existing document. With cross-document view transitions getting broader and broader support, I’m realizing that building in-page, progressively-enhanced interactions is more work than simply building two HTML pages and linking them. I’m calling this approach “lots of little HTML pages” in my head. As I find myself trying to build progressively-enhanced features with JavaScript — like a fly-out navigation menu, or an on-page search, or filtering content — I stop and ask myself: “Can I build this as a separate HTML page triggered by a link, rather than JavaScript-injected content built from a button?” I kinda love the results. I build separate, small HTML pages for each “interaction” I want, then I let CSS transitions take over and I get something that feels better than its JS counterpart for way less work. Allow me two quick examples. Example 1: Filtering Working on my homepage, I found myself wanting a list of posts filtered by some kind of criteria, like: The most recent posts The ones being trafficked the most The ones that’ve had lots of Hacker News traffic in the past My first impulse was to have a list of posts you can filter with JavaScript. But the more I built it, the more complicated it got. Each “list” of posts needed a slightly different set of data. And each one had a different sort order. What I thought was going to be “stick a bunch of <li>s in the DOM, and show hide some based on the current filter” turned into lots of data-x attributes, per-list sorting logic, etc. I realized quickly this wasn’t a trivial, progressively-enhanced feature. I didn’t want to write a bunch of client-side JavaScript for what would take me seconds to write on “the server” (my static site generator). Then I thought: Why don’t I just do this with my static site generator? Each filter can be its own, separate HTML page, and with CSS view transitions I’ll get a nice transition effect for free! Minutes later I had it all working — mostly, I had to learn a few small things about aspect ratio in transitions — plus I had fancy transitions between “tabs” for free! This really feels like a game-changer for simple sites. If you can keep your site simple, it’s easier to build traditional, JavaScript-powered on-page interactions as small, linked HTML pages. Example 2: Navigation This got me thinking: maybe I should do the same thing for my navigation? Usually I think “Ok, so I’ll have a hamburger icon with a bunch of navigational elements in it, and when it’s clicked you gotta reveal it, etc." And I thought, “What if it’s just a new HTML page?”[1] Because I’m using a static site generator, it’s really easy to create a new HTML page. A few minutes later and I had it. No client-side JS required. You navigate to the “Menu” and you get a page of options, with an “x” to simulate closing the menu and going back to where you were. I liked it so much for my navigation, I did the same thing with search. Clicking the icon doesn’t use JavaScript to inject new markup and animate things on screen. Nope. It’s just a link to a new page with CSS supporting a cross-document view transition. Granted, there are some trade-offs to this approach. But on the whole, I really like it. It was so easy to build and I know it’s going to be incredibly easy to maintain! I think this is a good example of leveraging the grain of the web. It’s really easy to build a simple website when you can shift your perspective to viewing on-page interactivity as simple HTML page navigations powered by cross document CSS transitions (rather than doing all of that as client-side JS). Jason Bradberry has a neat article that’s tangential to this idea over at Piccalil. It’s more from the design standpoint, but functionally it could work pretty much the same as this: your “menu” or “navigation” is its own page. ⏎ Email · Mastodon · Bluesky

2 hours ago 2 votes
AX, DX, UX

Matt Biilman, CEO of Netlify, published an interesting piece called “Introducing AX: Why Agent Experience Matters” where he argues the coming importance of a new “X” (experience) in software: the agent experience, meaning the experience your users’ AI agents will have as automated users of products/platforms. Too many companies are focusing on adding shallow AI features all over their products or building yet another AI agent. The real breakthrough will be thinking about how your customers’ favorite agents can help them derive more value from your product. This requires thinking deeply about agents as a persona your team is building and developing for. In this future, software that can’t be used by an automated agent will feel less powerful and more burdensome to deal with, whereas software that AI agents can use on your behalf will become incredibly capable and efficient. So you have to start thinking about these new “users” of your product: Is it simple for an Agent to get access to operating a platform on behalf of a user? Are there clean, well described APIs that agents can operate? Are there machine-ready documentation and context for LLMs and agents to properly use the available platform and SDKs? Addressing the distinct needs of agents through better AX, will improve their usefulness for the benefit of the human user. In summary: We need to start focusing on AX or “agent experience” — the holistic experience AI agents will have as the user of a product or platform. The idea is: teams focus more time and attention on “AX” (agent experience) so that human end-users can bring their favorite agents to our platforms/products and increase productivity. But I’m afraid the reality will be that the limited time and resources teams spend today building stuff for humans will instead get spent building stuff for robots, and as a byproduct everything human-centric about software will become increasingly subpar as we rationalize to ourselves, “Software doesn’t need to be good for human because humans don’t use software anymore. Their robots do!” In that world, anybody complaining about bad UX will be told to shift to using the AX because “that’s where we spent all our time and effort to make your experience great”. Prior Art: DX DX in theory: make the DX for people who are building UX really great and they’ll be able to deliver more value faster. DX in practice: DX requires trade-offs, and a spotlight on DX concerns means UX concerns take a back seat. Ultimately, some DX concerns end up trumping UX concerns because “we’ll ship more value faster”, but the result is an overall degradation of UX because DX was prioritized first. Ultimately, time and resources are constraining factors and trade-offs have to be made somewhere, so they’re made for and in behalf of the people who make the software because they’re the ones who feel the pain directly. User pain is only indirect. Future Art: AX AX in theory: build great stuff for agents (AX) so people can use stuff more efficiently by bringing their own tools. AX in practice: time and resources being finite, AX trumps UX with the rationale being: “It’s ok if the human bit (UX) is a bit sloppy and obtuse because we’ll make the robot bit (AX) so good people won’t ever care about how poor the UX is because they’ll never use it!” But I think we know how that plays out. A few companies may do that well, but most software will become even more confusing and obtuse to humans because most thought and care is poured into the robot experience of the product. The thinking will be: “No need to pour extra care and thought into the inefficient experience some humans might have. Better to make the agent experience really great, so humans won’t want to interface with our thing manually.” In other words: we don’t have the time or resources to worry about the manual human experience because we’ve got all these robots to worry about! It appears there’s no need to fear AI becoming sentient and replacing us humans. We’ll phase ourselves out long before the robots ever become self-aware. All that said, I’m not against the idea of “AX” but I do think the North Star of any “X” should remain centered on the (human) end-user. UX over AX over DX. Email · Mastodon · Bluesky

2 days ago 4 votes
Can You Get Better Doing a Bad Job?

Rick Rubin has an interview with Woody Harrelson on his podcast Tetragrammaton. Right at the beginning Woody talks about his experience acting and how he’s had roles that did’t turn out very well. He says sometimes he comes away from those experiences feeling dirty, like “I never connected to that, it never resonated, and now I feel like I sold myself...Why did I do that?!” Then Rick asks him: even in those cases, do you feel like you got better at your craft because you did your job? Woody’s response: I think when you do your job badly you never really get better at your craft. Seems relevant to making websites. I’ve built websites on technology stacks I knew didn’t feel fit for their context and Woody’s experience rings true. You just don’t feel right, like a little voice that says, “You knew that wasn’t going to turn out very good. Why did you do that??” I don’t know if I’d go so far as to say I didn’t get better because of it. Experience is a hard teacher. Perhaps, from a technical standpoint, my skillset didn’t get any better. But from an experiential standpoint, my judgement got better. I learned to avoid (or try to re-structure) work that’s being carried out in a way that doesn’t align with its own purpose and essence. Granted, that kind of alignment is difficult. If it makes you feel any better, even Woody admits this is not an easy thing to do: I would think after all this time, surely I’m not going to be doing stuff I’m not proud of. Or be a part of something I’m not proud of. But damn...it still happens. Email · Mastodon · Bluesky

4 days ago 4 votes
Limitations vs. Capabilities

Andy Jiang over on the Deno blog writes “If you're not using npm specifiers, you're doing it wrong”: During the early days of Deno, we recommended importing npm packages via HTTP with transpile services such as esm.sh and unpkg.com. However, there are limitations to importing npm packages this way, such as lack of install hooks, duplicate dependency resolution issues, loading data files, etc. I know, I know, here I go harping on http imports again, but this article reinforces to me that one man’s “limitations” are another man’s “features”. For me, the limitations (i.e. constraints) of HTTP imports in Deno were a feature. I loved it precisely because it encouraged me to do something different than what node/npm encouraged. It encouraged me to 1) do less, and 2) be more web-like. Trying to do more with less is a great way to foster creativity. Plus, doing less means you have less to worry about. Take, for example, install hooks (since they’re mentioned in the article). Install hooks are a security vector. Use them and you’re trading ease for additional security concerns. Don’t use them and you have zero additional security concerns. (In the vein of being webby: browsers don’t offer install hooks on <script> tags.) I get it, though. It’s hard to advocate for restraint and simplicity in the face of gaining adoption within the web-industrial-complex. Giving people what they want — what they’re used to — is easier than teaching them to change their ways. Note to self: when you choose to use tools with practices, patterns, and recommendations designed for industrial-level use, you’re gonna get industrial-level side effects, industrial-level problems, and industrial-level complexity as a byproduct. As much as its grown, the web still has grassroots in being a programming platform accessible by regular people because making a website was meant to be for everyone. I would love a JavaScript runtime aligned with that ethos. Maybe with initiatives like project Fugu that runtime will actually be the browser. Email · Mastodon · Bluesky

6 days ago 9 votes
Sanding UI, pt. II

Let’s say you make a UI to gather some user feedback. Nothing complicated. Just a thumbs up/down widget. It starts out neutral, but when the user clicks up or down, you highlight what they clicked an de-emphasize/disable the other (so it requires an explicit toggle to change your mind). So you implement it. Ship it. Cool. Works right? Well, per my previous article about “sanding” a user interface UI by clicking around a lot, did you click on it a lot? If you do, you’ll find that doing so selects the thumbs up/down icon as if it were text: So now you have this weird text selection that’s a bit of an eye sore. It’s not relevant to text selection because it’s not text. It’s an SVG. So the selection UI that appears is misleading and distracting. One possible fix: leverage the user-select: none property in CSS which makes it not selectable. When the user clicks multiple times to toggle, no text selection UI will appear. Cool. Great! Another reason to click around a lot. You can ensure any rough edges are smoothed out, and any “UI splinters” are ones you get (and fix) in place of your users. Email · Mastodon · Bluesky

a week ago 13 votes

More in literature

'To Think, to Read, to Meditate, to React'

Often, I think of the late Adam Zagajewski urging young poets – and by extension, the rest of us -- to “read everything.” The suggestion is not dictatorial. The Pole even admits he is a “chaotic reader,” as most of us are. I’ve never been systematic about much of anything and inevitably there are embarrassing holes in my education. Call it the Autodidact Syndrome. When it comes to books, we never know in advance what will come in handy, which volume will help solve a problem we didn’t know we were asking. Here is Zagajewski the literary cheerleader:  “Read for yourselves, read for the sake of your inspiration, for the sweet turmoil in your lovely head. But also read against yourselves, read for questioning and impotence, for despair and erudition, read the dry, sardonic remarks of cynical philosophers like Cioran or even Carl Schmitt, read newspapers, read those who despise, dismiss, or simply ignore poetry and try to understand why they do it. Read your enemies and your friends, read those who reinforce your sense of what's evolving in poetry, and also read those whose darkness or malice or madness or greatness you can’t yet understand because only in this way will you grow, outlive yourself, and become what you are.”   Zagajewski’s enthusiasm is almost embarrassing but the juggernaut of aliteracy and the threat it poses to Western Civilization may already be irreversible. My friend Cynthia Haven published an interview with Zagajewski not long after his death in 2021 in which she reminds him of his “read everything” essay. He replies:      “What can I say? I’m in favor of reading and taking into consideration past writers. But you know, I don’t know ancient Greek, my Latin almost doesn’t exist; I’m not one of those lofty professors who know everything and terrorize others with their perfect erudition. What’s important is to think, to read, to meditate, to react, to be imaginative. Sometimes a reduced reading list, if given strong attention, can be better than a classical education when pursued somewhat mechanically. Of course I want the past writers to persist but first of all I want thinking and being moved by intelligent texts to persist.”   Good advice. Don’t be intimidated by the vastness of the reading list. Choose a volume someone once mentioned he enjoyed or that had a strong emotional or intellectual impact on him. Say, the Life of Johnson, Richard Wilbur’s poems, Gershom Scholem’s Sabbatai Sevi: The Mystical Messiah, a novel by P.G. Wodehouse or Unamuno’s Tragic Sense of Life. Read it and see where it carries you.

15 hours ago 1 votes
“Writing in the Dark” by Denise Levertov

Poems read aloud, beautifully The post “Writing in the Dark” by Denise Levertov appeared first on The American Scholar.

16 hours ago 1 votes
Insomnia and the Secret Life of Ideas: Kafka on the Relationship Between Sleeplessness and Creativity

Where we go when we go to sleep and why we go there is one of the great mysteries of the mind. Why the mind at times refuses to go there, despite the pleading and bargaining of its conscious owner, is a greater mystery still. We know that ever since REM evolved in the bird brain, the third of our lives we spend sleeping and dreaming has been a crucible of our capacity for learning, emotional regulation, and creativity. But the price we have paid for these crowning curios of consciousness has been savage self-consciousness, thought turned in on itself,… read article

yesterday 2 votes
A measure of forever

For me, fiction is a space of plainness and excess.             Amina Cain When TS Eliot read Dante for the first time, he noted a discrepancy between his enjoyment and his understanding, leading to the famous claim that "genuine poetry can communicate before it is understood". He warns potential readers against two extremes: believing one has to master the theology, structure and historical context of the Commedia to appreciate its poetry or that knowledge is irrelevant to further enjoyment, which is why he thinks many readers' enjoyment is limited to the local thrills of Inferno. The warning holds today as we remain uncertain about the role literature plays in our lives: is it a repository of instrumental knowledge, cod liver oil for the soul, or pure escapism? "All three" is the public answer, except the distinctions are never clear and never overtly discussed despite fueling an entire literary culture, manifesting in, for example, the Guardian's Where to start with series in which pellets of one are slipped inside morsels of another. (Dante started with a dark wood lacking a branch of Waterstone's.)  In the months before I read the sentence in Amina Cain's A Horse at Night, I had stopped enjoying novels. I picked up several hailed as modern-day masterpieces and, despite their mutually incompatible variety, there was no spark. I bought and borrowed more seeking to break the cycle. Nothing worked. It would be easy to deceive myself into a rhetorical enjoyment, such as one reads every day in reviews, and I have often done that myself only later to reflect and regret, but I couldn't deny something was missing. Be assured this isn't a prelude to announcing the death of the novel and a call toward the tethered blimp of non-fiction, as I maintain faith in the indefinable potential of formal adventure. So if my loss of enjoyment was not the dulling of age, I wondered if there was a common absence. A answer came in that sentence. Eliot defined his enjoyment. He called it "poetic emotion". The quotation marks are his own as the phrase refers to his earlier essay on Hamlet and its definition of the Objective Correlative in which "a set of objects, a situation, a chain of events" elicit a particular emotion. This suggests literature must stick to generic templates through which a skilled writer can provoke a response immanent to the work, and Eliot more or less confirms it by reckoning Hamlet an "artistic failure" because Shakespeare did not find an objective correlative for Hamlet's behaviour that he superimposed onto the "cruder material" of earlier plays: "Hamlet (the man) is dominated by an emotion which is inexpressible, because it is in excess of the facts as they appear." He dismisses the emotion as adolescent. However, if we go back to the essay on Dante, Eliot mitigates the mixture of autobiography, lyric poetry and allegory comprising the Vita Nuova because it is a recipe "not available to the modern mind", the one that assumes biographical detail is an exposé of a personality. Instead, in Dante's case it is a report of personal experiences that were important not because they happened to Dante but because they had "philosophical and impersonal value". We might ask in response: when did a change occur that makes such a recipe unavailable to us? Perhaps it was changing in Shakespeare's time and that is precisely what makes Hamlet an excessive play. For Dante, the inexpressible and excess of facts took the form of Beatrice, a childhood love who becomes a personification of the divine and leads to a religious commitment. For Hamlet (the man), the opposite is the case. What presents itself to him is not an undoubted human presence and its gift of beatitude but a ghost he may have hallucinated and yet whose demands press upon him. Can he trust the experience? If it is false, how can he trust himself? If it is genuine, how can he trust the world? If Eliot thinks Hamlet's angst is adolescent, it may be because such introversion is now firmly embedded in the modern mind (as embodied by a certain J. Alfred Prufrock) and so easily dismissed, whereas in Shakespeare's time it was only just emerging and out of joint with what was firmly embedded then and responsible for the plays Eliot judged as "assured" artistic successes.  Vita Nuova and Hamlet are anomalies in literary history (anomalies define literary history), and what they both exhibit and what they both emerge from is excess and deprivation. The combination plays out differently in each: for Dante, the excess of emotion caused by Beatrice's presence and the deprivation experienced when she withheld her greeting and then when she died is transfigured into a mystical apocalypse and a key to salvation. His new life will be one of praise. For Hamlet the excess of ambiguity and subsequent deprivation of trust leads to behaviour that nowadays might be considered signs of a breakdown. What they also have in common is a meeting of the personal and the other-worldly. William Franke says the Vita Nuova is modelled on the New Testament gospels in which the experience of the apparent son of God remains central to the life of the writer. Beatrice was Dante's path to God and lyric poetry was his witness, the only proper means of communicating the revelation, with the prose commentary grounding the divine in everyday experience. The phenomenon of transcendence that Beatrice was for Dante became possible "only by the instrumentality of the lyric, specifically by virtue of its powers to express registers of personal experience in which subjective response and feeling are constitutive parts or aspects of objective events, not secondary and less real". Franke compares this to Christ's beatitudes that "lend themselves...to liturgical recitation and serve as kernels inviting supplemental elaboration in the form of illustrative narratives or parables and edifying doctrinal discourses". Hamlet does not have this resource and the very different form the play takes from Dante's little book indicates stages in a long process in which lyric poetry and literary prose finally become divorced, as described by Robert Alter, cited by Franke. The progressive narrativization of verse specifically in the refashioning and transmutation of biblical poetry into epic narration...describes a natural evolution starting from poetry, as the original form of literary expression, and moving to prose as its extension and elaboration. The process follows the incremental secularisation of Western society and the decline of the effects of revelation. It may explain why certain phrases in Hamlet have become embedded in everyday life in the same way as lines of poetry have (and so the apocryphal story of someone complaining that the play is full of quotations), while passages of novels, the exemplary form of disenchantment, have not (and indeed why poetry and plays have become minor forms in literary culture). Of course, novels are often common reference points, but nobody has lines running through their heads or recites passages off the cuff. They neither lend themselves to recitation nor to the rituals of performance. By becoming wholly extension and elaboration, prose has freed itself from its roots in lyric poetry and in the process that which exceeds the everyday, divine or otherwise. The lyrical state is a state beyond forms and systems.                                        EM Cioran So it was when I read Amina Cain's sentence that I recognised the problem. Plainness and excess has become prosaic. Plainness has become unimpeachable by making the everyday consequential in itself, though this has constantly to be renewed with critical hype – Dirty Realism was all the rage when I got into reading – and yet the residue of lyric and its promise of something other than the everyday remains: revelation has become a ghost in popular features such the 'twist in the tale' and the resolution of a plot, while in more refined circles, the possibility of revelation is present in the value afforded to 'experimental' writing which seems to promise that "under the myopic scrutiny of a good close reading" as Catherine Liu puts it "an obdurate, clam-like text [would] give up its iridescent pearl of gorgeous meaning". Meanwhile, excess is converted into maximalist world-building breezeblocks telling stories spanning continents and centuries, packed with history, adventure, romance, horror and fantasy. Each, however, remains undisturbed by the excess of its own presence, the incomprehensible revelation that with one sentence, however plain, however excessive, something has been added to the world, in the world as a product of a culture, yet not completely of the world. The surprise of distance. This has an effect comparable to that which Beatrice had on Dante and the ghost had on Hamlet; comparable but distinct, as it goes unnoticed. You can see the return of the repressed in "lyrical humanism", the form Lee Rourke diagnosed as the default mode of 'literary fiction', poised uneasily between popular and elite culture. With 'poetic' prose, it seeks to enchant a world without transcendence, standing in for that transcendence, and while it is ultimately empty, drawing the contempt of popular authors, it comforts the reader as much as the cushions on their conservatory armchair. (Dirty Realism is lyrical humanism in black and white.) We overlook its origins because the reception of contemporary novels follows Eliot by using contemporary mutations of the objective correlative to contain the terms of evaluation.  The sparkless cycle was broken when in a desultory search I picked out Thomas Bernhard's 1967 novel Verstörung, unfortunately translated as Gargoyles (it means Disturbance or Derangement) and began to read it for the first time in 25 years. I had regarded it as an also-ran among his novels, perhaps because the first of its two chapters is a plain story. A doctor's son home from college is listening to his father describing his rounds in a handful of small Austrian towns. There was a schoolteacher in Salla who he found dying and then a child in Hüllberg who fell into a tub of boiling water. The visits wear him down and the death of his wife and his daughter's suicide attempt hang over him. Despite this, the son's presence gives him cheer and he speaks of the restorative effects of nature. They prepare for a walk along the local river but are immediately interrupted by an urgent call to attend an innkeeper's wife in Gradenberg who has been bludgeoned by a drunken miner. The son accompanies the father to the inn and then the hospital, where she dies.  Crime, sickness, psychological distress and death pervade the region with son and father like Dante and Virgil on a travelogue through Hell, only without Dante's contrapasso placing the suffering in God's design. Purgatory of sorts is suggested when they reach the father's friend Bloch, an estate agent. The father finds some equilibrium by discussing political and philosophical issues with him and borrowing the big books of European thought from his library: Pascal, Kant, Marx, Nietzsche. He says Bloch resists despair by "seeing his life as an easily understood mechanism" he can adjust as necessary to practical ends. The son, a student of mining, agrees: "It was worth making the maximum effort to shake off a tendency to despair". Next they visit a wealthy industrialist who also seeks to make the maximum effort, in his case by shutting himself up in a hunting lodge to write on a literary work on a "purely philosophical subject". Father and son enter the lodge and walk on wooden floorboards through dark and barely furnished rooms. The son wishes to scream and throw open the shutters, but makes the effort to check himself.  Throughout the first half then the tension between mind and body, between self and world, is held in place by the firebreak between the observer and observed. The son is part of the world, partly outside. The plain act of description maintains literary sanity, with its correlative in the story being the father's commentary on the cases in the sanctuary of the car as they drive towards the summit of the purgatorial mountain. It is here that they meet Prince Saurau on the outer wall of Hochgobernitz Castle perched high above the surrounding countryside, a paradise of sorts. It is also where the second chapter begins and is what led Italo Calvino to call Gargoyles one of the great novels of the 20th century.  The Prince greets the visitors and immediately begins talking about the three applicants for the job he had advertised that morning, commenting on their dress, their demeanour, their background, their family, the towns they come from and, leaping from one subject to another, doesn't stop talking for the next 140 pages. He is enraged by the "idiotic bureaucratic rabble" that runs the Austrian state who have "expropriated" everything. He repeats variations of "expropriated" several times, and then "empty" several times. "Everything is empty!". In his analysis he comes across as intensely sensitive, lucid perhaps, and in the repetitions on the edge of madness. As is familiar in Bernhard's novels, the conditions cannot be separated. If the Prince hasn't descended entirely it is because the repetitions of words and phrases coalesce to maintain him in an oscillation above his abyss, even if it is an oscillation in which anger, loneliness, alienation, distress and despair comprise its dynamo. The Prince's compulsive repetitions form a lyricism in the absence of meaning, a revelation of sorts. Gershom Scholem called it the nothingness of revelation: "a state in which revelation appears to be without meaning, in which it still asserts itself, in which it has validity but no significance. A state in which the wealth of meaning is lost and what is in the process of appearing...still does not disappear." It is a state we recognise in the process of reading Gargoyles. A more straightforward reader may interpret the condition as purely medical and the novel merely a case study, while admiring Bernhard's skill in capturing the symptoms. Lyricism has its place in these conditions, as Cioran observed: It is significant that the beginnings of all mental psychoses are marked by a lyrical phase during which all the usual barriers and limits disappear, giving way to an inner drunkenness of the most fertile, creative kind. This explains the poetic productivity characteristic of the first phases of psychoses. Consequently, madness could be seen as a sort of paroxysm of lyricism.  [Translated by Ilinca Zarifopol-Johnston] Except the condition enabling such a diagnosis is not an uncontaminated onlooker: rationalism could be seen as a paroxysm of psychic catalepsy, the checked scream in recognition of the eternal silence of infinite space beyond the shutters of science, unwilling to confront the utter mystery of conscious existence. Pascal's famous line is the appropriate epigram to Gargoyles. With this in mind, we may turn to German Idealism and the intellectual history of the deus absconditus to recognise that the Prince is in a "delirium of loss" whose theological ground is set out by Alina Feld in Melancholy and the Otherness of God. The unhappy consciousness is "torn between finitude and the infinite, between the fallen and the ideal, between the human self and transcendent God". And while this condition appears to be conclusive, the form it takes remains part of the possible paroxysm, with catalepsy its cure. The lack of satisfaction in rational codefication is why we turn to novels, to its excess of the world, to writing that has an openness to an apparent outside, made apparent by writing, however deceptive. What is revealed in reading Gargoyles, and by extension in all novels, is a relation to what does and at the same time does not exist. The Prince's disturbance of this novel in particular is a disturbance of the novel in its generic safety and its readers seeking knowledge, cod liver oil for the soul and escapism. It is the revelation of the novel as an other-worldly presence in our lives, a measure of forever, an enjoyment beyond our understanding.

yesterday 4 votes
Open Thread 371

...

yesterday 2 votes