The Domain Name System (DNS) is a hierarchical and distributed name service that provides a naming system for computers, services, and other resources on the Internet or other Internet Protocol (IP) networks. It associates various information with domain names (identification strings) assigned to each of the associated entities. Most prominently, it translates readily memorized domain names to the numerical IP addresses needed for locating and identifying computer services and devices with the underlying network protocols.[1] The Domain Name System has been an essential component of the functionality of the Internet since 1985.
I occasionally receive emails asking me to look at the writer's new language/library/tool. Sometimes it's in an area I know well, like formal methods. Other...
I grew up in the world of BBSes, Usenet, and, to some extent, UUCP before that. This was fun – a world wide network all built up by volunteers sharing. Since we are all carrying supercomputers around now with massive idle storage and bandwidth, let's think about how we can recreate some of that fun, independent data sharing with modern web technologies, specifically Websockets and WebRTC. All you need is the computer that you already have with you.
The Unix philosophy, originated by Ken Thompson, is a set of cultural norms and philosophical approaches to minimalist, modular software development. It is based on the experience of leading developers of the Unix operating system. Early Unix developers were important in bringing the concepts of modularity and reusability into software engineering practice, spawning a "software tools" movement. Over time, the leading developers of Unix established a set of cultural norms for developing software; these norms became as important and influential as the technology of Unix itself, and have been termed the "Unix philosophy."
The 'Unix Way' Has a Right Way That's Almost a Lost Way
As I study tech sector innovations, I see signs that the old traditions are fading. I'm not one to sanctify tradition for tradition's sake, but I see merit in maintaining a traditional approach to computing tasks that encourages shrewdness. To illustrate what I mean, these are some ways we are straying from the Unix way, and my view on why we should return to the path.
In mathematical logic and logic programming, a Horn clause is a logical formula of a particular rule-like form that gives it useful properties for use in logic programming, formal specification, universal algebra and model theory. Horn clauses are named for the logician Alfred Horn, who first pointed out their significance in 1951.[1]
IPCM: Solving Dynamic IPFS Content with Blockchain Smart Contracts
Over the past few years, IPFS has become the default file network for offchain storage. When you combine immutable files with an immutable blockchain ledger, you get a powerful combination. While immutability is key to IPFS, it has also become one of its downsides. There are many crypto and blockchain
If you have been in the blockchain and crypto space, then there is a chance you've heard of IPFS and how it's used for offchain storage. In many ways, it's a perfect pairing: content on IPFS gets a hash that can be verified, it works as an address, and referencing
The 7 Most Influential Papers in Computer Science History
This post celebrates influential papers that shaped technology and communication. Their foundational concepts inspire continued innovation, highlighting the importance of understanding our roots fo…
The Lessons of Lucasfilm's Habitat | Journal For Virtual Worlds Research
Habitat is a "multi-player online virtual environment", created by Lucasfilm Games, a division of LucasArts Entertainment Company, in association with Quantum Computer Services, Inc. It was arguably one of the first attempts to create a very large scale commercial multi-user virtual environment in 1985. The system we developed could support a population of thousands of users in a single shared cyberspace. Habitat presented its users with a real-time animated view into an online simulated world in which users could communicate, play games, go on adventures, fall in love, get married, get divorced, start businesses, found religions, wage wars, protest against them, and experiment with self-government. Our experiences developing the Habitat system, and managing the virtual world that resulted, offer a number of interesting and important lessons for prospective cyberspace architects. The purpose of this paper is to discuss some of these lessons. We hoped that the next generation of builders of virtual worlds can benefit from our experiences and (especially) from our mistakes.