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...
> 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...
What REALLY set C&C apart was its presentation, which was like nothing else* when it came out. It made a serious and earnest attempt like you were actually using your computer as an interface to command an army*, from the "in-universe" installer to the present day setting where "you" choose a side after NOD and GDI hijack your TV, to the non-western battlefields, to the way Kane and General Shepphard addressed "you" personally in the live-action kinematics. The CD music was awesome too.
* Dune II also was known for its great graphics and having strict system requirements
* This continued in later games, but they were much more self-aware.
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.
Interesting, if I remember correctly, 8080 also required 4 clock cycles to fetch and execute a single-byte instruction. Did 8088 inherit some schematics from 8080? And 6502 uses 1 clock cycle for one memory access.
> 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.
Since the decoder is implemented in a PLA-style matrix, you don't save any space by omitting transistors. So that's not a motivation.
Random thing: chip transistor counts usually count "transistor sites" rather than physical transistors, so the omitted transistors still show up in the transistor counts.
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?
My thoughts are: the read-only unathenticated API should cover 80% of the API usage for apps. If there is adoption I will think about the authenticated portions.
There are two things going on here: the shell script is replaced with a more verbose Guile script (this part isn't actually necessary); and the Guile script uses G-expressions to include deployment information.
G-expressions are not meant to replace shell scripts.
You could just as well use G-expressions with a shell script; the stringly typed shell script just doesn't feel nice when working with Scheme.
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!
Hashes are perhaps the holy-grail of computer-science. With a good hash, we can just side-step all the hard problems by trading them for an even harder problem (hash collisions), and then we just ignore that harder problem. Brilliant. (sticks fingers in ears)
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...