Nullspace is a programming blog by Alex Clemmer covering Windows, OCaml, Python, Lisp on the Apple //e and search engines.
HN links it for posts on the Windows command line, building a search engine to compete with Google, and recovering deleted files with grep.
If you follow the citation trail:
0. Dan writes an article about marginal employment decisions, which cites
1. Alex Clemmer wrote (http://blog.nullspace.io/building-search-engines.html) about building a search engine to compete with Google, who cites
2. John Peebles, who wrote (https://peebs.org/2014/01/04/we-need-viable-search-engine-competition-now/) about the urgent need for a viable competitor to Google, saying:
> I wonder if we haven’t all been hypnotised by the complexity, much of which is marketing hype, and have missed the enormous opportunity that exists right in front of our noses. Does the next search engine have to be as big, involved in as many things, employ as many people, and fight on the same footing to be accomplish the goal of providing a counterpoint to Google?
This article was upvoted fairly well on on HN (https://news.ycombinator.com/item?id=7011472), though the top comments are all in agreement this is not a simple task. This zeitgeist, along with Dan's personal experience on the subject, is why he wrote the article using Google as the example.
(Author of the repo here).
This is just a draft. I wasn't expecting this to be published here in its initial state.
Actually my intention was just to create an exhaustive collection of references to useful resources for the OCaml programming language. The list is far from complete and needs more refinements both in terms of content, organization and design.
So all of your critics are fair (and actually useful). I'll continue to improve it, and I promise you'll be surprised the next time you visit the page! ;)
Btw, if you want to quickly understand how the ecosystem of the language works and actually start experimenting with it, here's an excellent guide for beginners:
- <http://blog.nullspace.io/beginners-guide-to-ocaml-beginners-guides.html>
Hope it helps, and if you have any suggestions I'd be glad to know about them.
The classic Windows shell has many flaws in its design, appears to have come from OS/2, and it's amazing that it works at all for how it has been used:
https://blog.nullspace.io/batch.html
Powershell is a new arrival, limited outside of Windows. I admit that I don't know it.
The POSIX shell also has severe problems with ambiguity, and it is not an LR-parsed language:
https://archive.fosdem.org/2018/schedule/event/code_parsing_posix_s_hell/
Use the right tool for the job, imperfect as they may be.
It is unfortunate that awk didn't grow and supplant the shell, as for many years the BWK "One True Awk" did use straightforward lex and yacc grammars.
A couple months ago, I decided to write a very short tutorial/introduction to the program `telnet`. I ended up deciding to use the <blink> tag to make a cursor that blinks similar to how it blinks in the terminal.
Hilariously, I discovered that <blink> is actually no longer implemented in Chrome.
The one legitimate use!
I ended up mocking it with JavaScript. EDIT: it's here if you want to see how the cursor turned out! http://blog.nullspace.io/day-208.html
In 2012, The Economist reported that mainframes accounted for about a quarter of IBM's revenue and about half of its profits. [0] [1]
IT budgets for large banks and financial firms usually dedicate something like 20% their budget to mainframes, but it usually accounts for about 80% of the firm's workload/processing.
[0]: http://www.economist.com/blogs/schumpeter/2012/09/ibms-mainframes
[1]: http://blog.nullspace.io/mainframes.html
The Bond compiler is written in Haskell: http://blog.nullspace.io/bond-oss.html
It is about time considering that Microsoft research has been one of the main funders of work on the Haskell compiler.