Posts

Famicom Programming Even Giko Cat Can Understand

  Famicom Programming Even Giko Cat Can Understand is a Japanese-language tutorial that invites the reader to appreciate the Family Computer not merely as a finished consumer product, but as a small computer in which the CPU, PPU, memory, interrupts, and input devices operate in close coordination. Beginning with the installation of NESASM, the course proceeds through palettes, sprites, controller input, zero-page memory, DMA, VBlank, background scrolling, sound, the stack, raster scrolling, indirect addressing, and memory mappers. The reader therefore comes to understand a game not simply as a completed arrangement of images and sounds, but as a process of allocating time instruction by instruction, placing state within limited memory, and rewriting the screen in synchronization with the scanlines. The distinctive appeal of the site lies in its rejection of the polished abstractions associated with modern frameworks. Through examples that the author openly describes as rough and ...
Post a Comment
Read more

# Browser-Based Robotics Simulation and Online Physics for G1

## Executive summary If your goal is to get a **Unitree G1** running *in a browser*, the strongest practical options split into three tiers. **For highest fidelity and direct use of G1’s existing MJCF assets, MuJoCo’s official JavaScript/WebAssembly bindings are the best fit**: MuJoCo natively loads **MJCF and URDF**, its web bindings are now official, and the bindings expose a workable file-system model for loading XML assets in-browser. Unitree’s own G1 description package explicitly ships **URDF and MJCF** variants, so the asset path is already aligned. The trade-off is that the web bindings are still marked **work in progress**, and you still need to build a small upload/asset-loading wrapper yourself. citeturn14view1turn15view1turn19view0 If you want the **fastest path to “a standing G1 in the browser”**, **Three.js + URDFLoader** is the easiest route. It is effectively a browser-native robot viewer with joint control, drag-and-drop examples, package-path handling, and custom...
Post a Comment
Read more

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