Top all-time · #12337
Manuel Simoni
Personal blog · pwpwp.blogspot.comprogrammingphilosophysystems
Manuel Simoni writes plans within plans within plans, a personal blog at pwpwp.blogspot.com about programming, philosophy and systems. Since 2009, 6 different Hacker News readers have linked it 13 times, most often “What I Don't Get About Google Wave”. The last post was in 2012, but the archive is still widely read.
Too few sampled comments (5) to say how often HN recommends it.?
Why HN links it
HN readers link Manuel Simoni's blog for rough notes on a Paul Graham talk, a critique of Google Wave, and a method for storing JSON as Protocol Buffers.
Summarised by Claude from a sample of 5 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Manuel Simoni's blog about the internet
Most-linked posts?
- What I Don't Get About Google Wave2 people · 2 mentions · first linked 2009-08-06
What Hacker News says?
I took some rough notes here: http://pwpwp.blogspot.com/2010/08/paul-graham-on-trends-for-...
Comment linking /2010/08/paul-graham-on-trends-for-future.html
on “Paul Graham on trends for the future”Submitted Python Community in Anguish, Pain, Despair Over Web Server as a story · 45 points
HN discussionFirst, you should take the whole post with more than a grain of salt. ;) Re JavaScript, I'm referring to the lowlevel nature of many of its constructs: - its impoverished way to pass parameters (i.e. there are no keyword parameters; you don't get an error if you pass too many or too few arguments) - its impoverished exception handling (i.e. you can't catch exceptions of a specified type) - its impoverished standard…
Comment linking /2009/08/awesome-helma-and-lacking-javascript.html
on “Letter to a Young PL Enthusiast”Submitted Steps Towards an Acceptable Lisp as a story · 19 points
HN discussionWhat happens when you take the one dumbest data format in existence, extend it (I won't even go into that), stuff it into a centralized server, and let people manipulate it concurrently, using a TECO-ish differential editing protocol? Answer: Google Wave. http://pwpwp.blogspot.com/2009/08/what-i-dont-get-about-wave...
Comment linking /2009/08/what-i-dont-get-about-wave-part-1.html
on “What Works: The Web Way vs. The Wave Way”Submitted Our conceptual dark age of man-machine interaction as a story · 13 points
HN discussionIf your data layout is fairly static, PBs are good. What I did for an app was encode a kind of JSON in PBs: http://pwpwp.blogspot.com/2009/08/storing-json-as-protocol-b...
Comment linking /2009/08/storing-json-as-protocol-buffers.html
on “Ask HN: Experience with Protocol Buffers”Submitted The Coming Post-Platform Era as a story · 8 points
HN discussionThat might be the most obnoxious design for a blog I've ever seen. I'm not quite sure what their point is. Google Wave is intended to be a reinvention of the user interface we use to communicate, and I think it introduces features that make a lot of sense: - Sending all user a thumbnail while the full image is still uploading - Instantaneous character-by-character update in chat - Better management of conversations…
Comment linking /2009/08/wave.html
on “What I Don't Get About Google Wave”Submitted Looking for the Super-Structure of Information Organization as a story · 6 points
HN discussionSubmitted Tinkerer's High Noon as a story · 2 points
HN discussionSubmitted Why I don't want lightweight threads in my programming language as a story · 2 points
HN discussionSubmitted What I Don't Get About Google Wave as a story · 2 points
HN discussion
