Original title: RDAP to Replace WHOIS for gTLD Registration Data
The Registration Data Access Protocol (RDAP) will replace the WHOIS service for gTLD registration information by January 28, 2025. RDAP, developed by the Internet Engineering Task Force, offers advantages like internationalization support, secure data access, and differentiated access to registration data. ICANN-accredited registrars and gTLDs have offered RDAP since 2019. Users are encouraged to use ICANN's RDAP-based Lookup service or the open-source command-line client. To request access to nonpublic gTLD registration data, users should use the Registration Data Request Service (RDRS) or contact the sponsoring registrar directly. The RDRS is intended for legitimate interests such as law enforcement and cybersecurity professionals.
Original title: Welcome to Docs! The open source document editor where your notes can become knowledge through live collaboration
Docs is a collaborative text editor developed by the French and German governments, designed to address challenges in knowledge building and sharing. It offers features like simple collaborative editing, offline functionality, clean formatting, productivity tools (markdown support, block types, slash commands, keyboard shortcuts), AI actions (generate, sum up, correct, translate), real-time collaboration, granular access control, professional document exports, and built-in wiki functionality. The project is built on Django Rest Framework, Next.js, BlockNote.js, HocusPocus, and Yjs. It aims to be an easy-to-install, scalable, and secure alternative to platforms like Notion, Outline, or Confluence. Users can test Docs via a provided login and are encouraged to contribute through various channels. The project is released under the MIT License, with a directory structure that includes bin, crowdin, docker, docs, env.d/development, gitlint, playground, and src directories. The project is part of a suite of tools for public agents called "La suite numérique".
Original title: I fell down a rabbit hole and ended up with the world's tiniest Git patch
The author investigated the bundle-uri
feature in Git, designed to speed up clones by using pre-calculated seed files. The feature allows cloning from a local file or a CDN, potentially saving time by reducing server load. Initial tests revealed that using a CDN-hosted bundle file did not improve clone times, and in fact, it took longer than a fresh clone. The author discovered that Git only copies local branch references from the bundle, causing unnecessary object downloads. By modifying the code to include all references, clone times improved significantly, resulting in a small patch to the Git codebase. The author suggests that this feature could benefit Git forges by reducing server load and could be useful for internal Git servers or automated setups. The server can advertise bundle URLs, and Git clients will automatically download bundle files if the server provides them. The author hopes for a fix to prevent unnecessary data downloads.
Original title: The Amiga 600: The Worst Amiga, But Also the Best?
The Amiga 600, released in 1992, was a cost-reduced version of the Amiga line, but it was poorly timed and ultimately unsuccessful. It was essentially a repackaged 1985 Amiga 1000, lacking the processing power and graphics capabilities of contemporary PCs. The machine's $500 price tag didn't include essential components like a monitor and hard drive, pushing the total cost close to $1,000, making it less competitive than PCs. The Amiga 600's dated technology, including its Motorola 68000 CPU and graphics, couldn't compete with the advancements in PC technology, particularly VGA graphics and the emergence of 3D games. Commodore's failure to understand its market and its inability to produce the more advanced Amiga 1200 in sufficient quantities further contributed to the 600's failure. Despite its shortcomings, the Amiga 600 is now appreciated by retro enthusiasts for its compact size and compatibility with modern peripherals. However, the machine's surface-mount capacitors are prone to failure, requiring replacement for reliable operation. The Amiga 600's design choices, such as the lack of a full keyboard and limited expansion options, presented challenges for users. The article suggests that a faster CPU or the AGA chipset could have improved the Amiga 600's competitiveness. The author, a computer security professional, reflects on the Amiga 600's legacy as a symbol of Commodore's missteps, while acknowledging its appeal in the retro computing community.
Original title: Tcl Tutorial
The tutorial provides a comprehensive introduction to Tcl, covering fundamental concepts and advanced topics. It begins with the basics of running Tcl and simple text output, then moves on to assigning values to variables and exploring evaluation and substitutions using different grouping methods. The tutorial delves into mathematical operations, numeric and textual comparisons, and various looping constructs like while and for loops. It explains how to add new commands using proc, including variations in arguments and return values, and discusses variable scope with global and upvar. Data structures, such as lists and associative arrays, are introduced, along with commands for adding, deleting, searching, sorting, and extracting elements. The tutorial also covers pattern matching, string manipulation, and regular expressions, including more complex examples and quoting. Furthermore, it explores dictionaries, file access, and invoking subprocesses, as well as obtaining information about commands, variables, and procedures using info. Modularization techniques, such as source, packages, and namespaces, are explained, along with command construction using eval, format, and list. Substitution without evaluation, changing the working directory, and debugging techniques are also covered. The tutorial concludes with command-line arguments, environment strings, channel I/O, time and date functions, and child interpreters.
Original title: Remembering Pivotal Tracker
The article discusses the legacy of Pivotal Tracker, a project management tool known for prioritizing developer productivity and streamlined workflows. It highlights the tool's focus on simplicity, avoiding features that hinder productivity, and automating processes. Project trackers, as opposed to bug trackers or general project management tools, are designed to be intuitive for developers and project managers, offering shared views and minimal customization. The article emphasizes the importance of cycles, lanes, and a responsive UI for efficient project management. Cycles are automatically updated, and lanes preserve story priority, reducing mental overhead. The UI is designed to be fast and provide a clear overview of project status. The article also mentions the tool's rejection of Gantt charts and arbitrary deadlines. The community initiative aims to remember Pivotal Tracker and showcase projects carrying its legacy forward.
Original title: The Day Microsoft Went Public
Microsoft's initial public offering (IPO) on March 13, 1986, valued the company at $777 million, with shares priced at $21.00. The IPO raised $61 million and propelled Bill Gates to billionaire status. Microsoft delayed going public for 11 years to maintain control, but the need to manage a growing number of shareholders forced the decision. The company's profitability stemmed from its dominance in operating systems like MS-DOS and Windows, and applications like Excel and Word, which were licensed on nearly every PC sold. Microsoft's success led to a monopoly in operating systems and office suites by the early 1990s, but also to legal challenges. The IPO's legacy includes inspiring tech entrepreneurs and contributing to the dotcom bubble. Microsoft's minimal use of venture capital is highlighted as a key factor in its success. The article also notes that while Microsoft is still a major player, other tech companies like Apple, Amazon, and Alphabet are now larger.
Original title: Teach, Don't Tell
The article emphasizes that effective technical documentation should function as a teaching tool, guiding users from novice to expert. It critiques common documentation pitfalls like relying solely on source code, tests, or literate programming outputs, arguing these are insufficient for initial learning. The author advocates for a structured approach, dividing documentation into four key components: "First Contact" to introduce the project, the "Black Triangle" for a quick start, the "Hairball" for in-depth learning, and "The Reference" for expert users. The "Hairball" should be organized and comprehensive, while "The Reference" should include API documentation and a changelog. The author stresses the importance of anticipating user needs and providing clear, organized information, and discourages the use of wikis for documentation due to their lack of a coherent voice and potential for disorganization. The author suggests that documentation should be written by hand, not auto-generated, to maintain a consistent voice and provide better context for users.
Original title: 25 years ago, the dotcom bubble reached its peak
The dotcom bubble reached its peak on March 10, 2000, with the NASDAQ doubling in value in a year, fueled by investor fear of missing out and Y2K spending. Despite the emergence of successful companies like Amazon and Google, many dotcoms lacked solid business plans and profitability, leading to failures and acquisitions. The Super Bowl XXXIV commercials exemplified the excess. The market crashed after the peak, with tech stocks tumbling and taking years to recover. Established tech companies also suffered, with sales drying up and some becoming acquisition targets. The recovery was slow, with the NASDAQ not surpassing 5,000 again until 2015, and Google's IPO marking a turning point. The author, a computer security professional, reflects on the era's impact on the tech industry and the long-term consequences of the bubble's burst.
Original title: PicoLisp Documentation
The PicoLisp documentation serves as a comprehensive guide to the PicoLisp programming language, offering resources for users of all skill levels. It provides tutorials, examples, and references to help users learn the language, including a guided tour, a blog, and a reference manual. The documentation covers various aspects of PicoLisp, such as web development, database systems, embedded programming, and server-side applications. It also includes articles and essays on topics like metaprogramming, recursion, and the language's unique features. Furthermore, the documentation offers information on efficient editing tools, different PicoLisp versions, and additional resources like online books and source code. The documentation also highlights various libraries and repositories for web development, content management, and other applications. Users are encouraged to explore the resources, experiment with the code, and contribute to the community.
Original title: That time I recreated Photoshop in C++ and Windows API!
The author reflects on a past project where they recreated Photoshop using C++ and the Windows API. The project, named Fedit, was developed in 2006 after completing a C++/Windows API course. The goal was to create an image editor similar to Photoshop, incorporating features like free-floating windows, a color picker, layer management, history, and image filters. Fedit adhered to five rules: no installers, archives, registry keys, additional runtimes, and a single executable file. The user interface was designed to mimic Photoshop's workflow, with the tool settings pane being particularly challenging. Despite the effort, the author did not promote Fedit but later secured a C++ job based on the project's impression. The source code for Fedit and the earlier project Fiew is available on GitHub, and the thesis documentation is also accessible.
Original title: From Languages to Language Sets
The author categorizes programming languages into four levels based on typing and memory management, with level 4 being interpreted and dynamically typed, and level 1 being compiled with manual memory management. The author suggests that most business logic programming benefits from a language in the middle of the hierarchy. They propose a language set based on Rust, including a level 2/3 hybrid (RustGC) and a level 4 language (RustScript), all sharing similar syntax. RustScript is designed for prototyping, RustGC for general use with async support and a garbage collector, and Rust for maximum performance. The languages are designed for seamless interoperability, allowing easy calls between them and access to the Rust ecosystem. Examples of UI components in RustScript and async code in RustGC are provided to illustrate the concept.
Original title: My MathAcademy Review
The author shares their experience with MathAcademy, a platform for learning mathematics. They describe a personal journey marked by a shift from disinterest in math due to negative experiences with teachers to a renewed interest sparked by observing others' progress on the platform. The author highlights the platform's structured approach, clear roadmap, and supportive community as key pros. They emphasize the gamification features, such as XP, daily goals, and leaderboards, as motivators. The author also acknowledges the platform's cost as a significant con, especially for those in less developed countries. They mention the time required to complete quizzes, often needing multiple attempts. The author concludes by reflecting on the serendipitous nature of rediscovering passions and the importance of pursuing them regardless of perceived limitations.
Original title: Local-First & Ejectable
The article introduces the concept of "ejectable" apps, which combine the benefits of cloud-based applications with the data ownership of traditional desktop software. Ejectable apps allow users to switch between cloud and self-hosted versions, ensuring continued access to data and functionality even if the cloud service shuts down. This is achieved by saving a workspace as a .zip file, providing a server executable for self-hosting, and making the process reversible. The goal is to offer the convenience of cloud apps while being as future-proof as traditional software. The article highlights the importance of local-first design and the potential of ejectable apps to ensure data accessibility and longevity. The author mentions their own app, Thymer, as an example of an ejectable app. The concept is presented as a solution to the problem of cloud app shutdowns and the loss of functionality that comes with them. The article emphasizes the importance of making apps local-first and ejectable to provide the best of both worlds.
Original title: Founding Applied AI Engineer at Kastle
Kastle, an AI platform backed by $2.3M from Y Combinator and others, is hiring a Founding Applied AI Engineer. The role involves integrating advanced AI technologies into their platform, specifically focusing on fine-tuning large language models (LLMs) and designing AI workflows for highly regulated enterprises. Responsibilities include fine-tuning and deploying LLMs, designing prompts, training domain-specific AI models, and ensuring solutions meet regulatory standards like FDCPA, RESPA, and TILA. The engineer will also build data pipelines, optimize AI performance, and enhance borrower experience. The ideal candidate should have 3+ years of experience in applied AI or ML engineering, proficiency in Python, TensorFlow/PyTorch, and experience with LLMs. A strong product mindset and understanding of mortgage regulations are also required. The role offers the opportunity to work on cutting-edge AI technologies, collaborate with a top-tier team, and receive competitive compensation with early-stage equity.