The game engines for C&C and Red Alert are full of Dune II references; as just one example, the factions (GDI/Nod or Allies/Soviets) are still called "houses" in the internal configuration files of C&C/RA.
C&C is pretty much what you get when you want to produce a sequel to Dune II but can't (or don't want to) license the Dune I.P. again so everything has to be re-skinned...
There's also the 'reticulate' package for R, which allows you to import Python libraries and exchange objects between the two languages. It includes a proper Python engine for knitr (with matplotlib support), letting you use both R and Python code blocks in the same R Markdown document.
excellent! I'm tired of search engines that optimize for natural language queries because the inevitable trade-off is that they become useless at keyword/exact queries.
The 8088 has a four-byte instruction queue, and at times when the data bus would otherwise be idle the bus interface unit will prefetch the next instruction byte. So fetch and decode/execute are already overlapped.
What really slows down the 8088 is that each 8-bit transfer on the data bus requires four clock cycles. That means simply fetching the two-byte instruction requires eight clocks! Instruction fetch is so slow on the 8088 that it's virtually impossible to achieve the published instruction timing.
> it's missing many many culturally specific things like accents and other diacritics
fun fact: some of the symbols included in ASCII were intended to be used as (non-spacing) diacritical marks, specifically the tilde/caret/backquote characters...
[too lazy to dig up a proper source at the moment but the Wikipedia ASCII article covers some of this]
When implementing the decoding in silicon, each bit you want to compare requires one or more transistors; but no transistors are required for the "don't care" bits.
What are your thoughts on handling the authenticated portions of the API? For example, retrieving the list of subreddits a user is currently subscribed to? Or posting a comment / checking the user's inbox?
Are there any alternative (open source) implementations of the _server_ side of the Reddit API? Then you could just point Teddit, Aurora, etc. at the alternative server. The only required work would be implementing the database backend which seems... feasible.
This is fascinating, I really did not think it was possible to implement even a tiny subset of C in just 512 bytes of x86 code. Using atoi() as a generic hash function is a brilliantly awful hack!
I miss the days when NZ was truly innovative. RealMe was very promising when first introduced.
Of course it was never going to be adopted en masse by the private sector since part of the "get approval to use RealMe on your website" was "get Parliament to pass an Order in Council adding you to the authorized users schedule".
His geometry-centric approach to linear algebra was exactly what I needed to finally grok the subject. Topics like matrix multiplication and discriminants went from "why are they defined like this? it makes no sense?" to "of course that's how you multiply matrices because it's the only logical answer".
It's only later that I discovered Wildberger has some ~strange~ very interesting ideas regarding imaginary numbers, but these ideas don't detract one bit from his presentation of linear algebra. Highly recommended viewing for anyone who is keen on neural networks and machine learning but struggles with understanding the underlying mathematics.
If you have a "stock" IBM PC, just the standard dual 360K floppy drives without a hard drive, it's actually possible to run this demo!
Use DOS 3.30 and FORMAT /S a blank floppy, copy APPEND.EXE to the floppy, and copy as many of the AREA5150 demo files as will fit. Then copy the remaining files to a second floppy. Put first floppy in A: and boot off it, put second floppy in B:, and then run APPEND B: followed by AREA5150. Behold, it works!
You absolutely do need the full 640K of RAM though, refuses to run with only 512K.
Yep, there was a (brief) period of time -- before MS-DOS became wildly popular -- when Microsoft was pitching Xenix as the future operating system for the PC.
(Also worth noting is that MS-DOS 2.0 was a nearly complete rewrite of the 1.x codebase...)
CP/M was (mostly) written in the PL/M language and ran on the 8-bit 8080/Z80 processors. 86-DOS was written in pure assembly language and ran on the 16-bit 8086 processor. Tim Paterson, its author, wrote an 8086 assembler and an 8080-to-8086 source code translator that ran on a CP/M machine. He used these tools to bootstrap 86-DOS.
86-DOS was intentionally designed to mimic the CP/M APIs to make it easy to port CP/M applications to 86-DOS through mechanical translation of the source code.
(And, surprise surprise, much of the business software that was available for IBM PC-DOS in the first couple of years were direct ports of existing CP/M applications: SuperCalc, WordStar, dBase II, etc.)
There's a good chance that all of the components in the car have similar/identical command sets for test/debug operations, even if the individual components have been produced by different OEMs.
Did any terminal ever implement the ANSI escape codes for block mode (i.e. form) fields?
The block mode terminals on IBM mainframes (e.g. the 3270) have all the functionality of a basic HTML form if you squint hard enough: the screen is divided into form fields and labels, the user can fill out the fields (and tab the cursor between them) while the terminal is offline/not communicating with the server, and then when the user presses one of the special 'submit' keys the terminal sends all of the data from the form fields to the server and awaits instructions on what to do next.
The 3270 even had hidden fields, so the server could stuff a bit of state information (like a session ID) into the form, which the terminal would dutifully echo back to the server when submitting the form....
It's a very different style of interaction as compared to the conventional Unix/PC character-by-character terminals, and leads to some pretty weird user interface conventions:
https://www.youtube.com/watch?v=9qwFSJZSjeA
Originally HTML just had the <isindex> element, which was very similar to Gopher's primitive "search" functionality. Adding the <form> element with named input fields was a pretty obvious next step, and the fact that HTTP/HTML evolved to support it while Gopher did not says quite a bit about the culture behind these two protocols.
C&C is pretty much what you get when you want to produce a sequel to Dune II but can't (or don't want to) license the Dune I.P. again so everything has to be re-skinned...