Posts

Postmortem of Kokoro

  Postmortem of Kokoro Reporter: “I” 1. Incident Summary This report is written from the perspective of “I,” the narrator who received Sensei’s testament. It organizes a sequence of serious events involving Sensei, K, Okusan, Ojosan, and myself. This case should be treated not as a single event, but as a two-stage incident. The first incident concerns the conflict of interest that arose between Sensei and K over Ojosan. Although this conflict had emerged, it was never explicitly mediated. Instead, Sensei made a private prior commitment by asking Okusan for permission to marry Ojosan. Afterward, K died by suicide. However, no sufficient explanation or testament from K can be confirmed, and therefore K’s motive cannot be determined. The second incident concerns Sensei’s long-term burden of guilt after K’s death. Sensei continued to carry this guilt without sharing its core with his wife, gradually becoming socially and psychologically isolated. The death of the Meiji Emperor and the ...
Post a Comment
Read more

In Java, the term “container” may have evolved from the AWT and JavaBeans component model into the server-side execution environment terminology later used in Servlet, J2EE, and EJB.

 Hypothesis: In Java, the term “container” may have evolved from the AWT and JavaBeans component model into the server-side execution environment terminology later used in Servlet, J2EE, and EJB. In AWT, a Container was originally a GUI object that could hold and arrange Components. This was not merely a passive box, but an object that participated in layout, event handling, and interaction with platform-dependent GUI peers. JavaBeans then extended this idea from GUI component containment to a broader component architecture. In the JavaBeans specification, a Bean could be embedded not only inside another Java object, but also inside platform-specific containers such as Microsoft Word, Visual Basic, ClarisWorks, or Netscape Navigator. In this context, a container meant an external application or environment that hosted, integrated, and managed a component. This usage is important because it bridges the older GUI/component meaning of “container” and the later server-side meaning. Whe...
Post a Comment
Read more

Famous Animal Geoglyphs

Image
 Below is a large collection of well-known Nazca geoglyphs and related archaeological sites with Google Maps URLs. Some coordinates are approximate because Google Maps imagery, labeling, and visibility vary over time. Famous Animal Geoglyphs Hummingbird https://maps.google.com/?q=-14.692272,-75.149181 Monkey https://maps.google.com/?q=-14.707406,-75.138994 Spider https://maps.google.com/?q=-14.694342,-75.122700 Condor https://maps.google.com/?q=-14.697300,-75.132400 Parrot https://maps.google.com/?q=-14.689889,-75.108169 Dog https://maps.google.com/?q=-14.706900,-75.129600 Whale (Killer Whale) https://maps.google.com/?q=-14.703700,-75.118400 Heron https://maps.google.com/?q=-14.690800,-75.137500 Pelican https://maps.google.com/?q=-14.686500,-75.141000 Flamingo https://maps.google.com/?q=-14.688700,-75.145200 Lizard https://maps.google.com/?q=-14.696900,-75.130300 Cat (discovered in 2020) https://maps.google.com/?q=-14.739800,-75.130700 Human Figures Astronaut https://maps.google.co...
Post a Comment
Read more

wayback

Image
 https://web.archive.org/web/20121213195317/http://notch.tumblr.com/post/37823268132/i-love-you-dad
Post a Comment
Read more

Microsoft InfoViewer program

  Microsoft InfoViewer Program Microsoft InfoViewer was a documentation viewer and help system used by Microsoft in the mid-to-late 1990s, especially around the Visual Studio 97 and Visual C++ 5.0 era. It was designed to browse large developer documentation sets such as the MSDN Library, Visual C++ reference manuals, Platform SDK materials, and bundled sample code collections. InfoViewer can be understood as an intermediate help technology between earlier Windows Help systems and later HTML Help. Before InfoViewer, Microsoft commonly used WinHelp files, usually with the .hlp extension, and multimedia-oriented documentation systems such as Microsoft Multimedia Viewer. After InfoViewer, Microsoft moved toward HTML Help, whose compiled help files used the .chm extension. The InfoViewer system used proprietary container files, most notably .ivt , often interpreted as InfoViewer Title files. These files could contain HTML-like documents, images, stylesheets, sample source code, pr...
Post a Comment
Read more

Chronospatial Record Locator (CRL)

  A Proposal for Persistent Internet Spacetime Referencing Abstract This document proposes the concept of the Chronospatial Record Locator (CRL), a generalized identifier for persistent records existing within internet spacetime. Unlike conventional URLs, which describe only resource location, a CRL identifies: where a record existed when it existed and how it may be re-observed across temporal layers of the network The concept is intended as a humorous but structurally plausible RFC-style abstraction unifying: web archives geospatial records blockchain histories version control systems persistent identifiers and cultural memory systems under a single chronospatial framework. 1. Introduction The modern internet increasingly contains objects that are not merely resources, but temporally anchored observations. Examples include: Wayback Machine snapshots Git commits blockchain transactions DOI references geotagged photographs archived social...
Post a Comment
Read more

From what I found, the strongest candidate is a Docker image that runs UMLetino directly.

 There are a few examples. From what I found, the strongest candidate is a Docker image that runs UMLetino directly. Main candidate: manslaughter/umletino Docker Hub has an image called manslaughter/umletino . Its description is “Docker image umletino (web application umlet).” It has not been updated for more than eight years, but Docker Hub shows 10K+ pulls. The startup command is listed there as well. docker run --rm -p 8080 :80 manslaughter/umletino Then open this in your local browser: http://localhost:8080 GitHub repository The corresponding GitHub repository is manslaughter03/docker-umletino . The README describes it as “Deploy umletino behind nginx,” and it includes both the Docker Hub run method and a local build method. For a local build, the README gives this flow: git clone https://github.com/manslaughter03/docker-umletino cd docker-umletino ./build.sh ./run.sh To change the port, for example: ./run.sh 9000 Then open: http://localhost:9000 What the set...
Post a Comment
Read more