pwpwp

30 ms·

1. 271.▲
   by pwpwp 16y ago

   gwt
2. 272.▲
   Why Content Is a Public Good(antipope.org)

   11 points by pwpwp 16y ago|5 comments
3. 273.▲
   by pwpwp 17y ago

   If 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...
4. 274.▲
   Swimming Upstream: 'Salmon,' Google's Open Source Social Web Aggregator(mediapost.com)

   2 points by pwpwp 17y ago|0 comments
5. 275.▲
   by pwpwp 17y ago

   I won't worry about BB. They seem to be the only company able to create a smartphone that works (i.e. doesn't crash etc.) at the moment.
6. 276.▲
   Draft: The Salmon Protocol(salmon-protocol.googlecode.com)

   15 points by pwpwp 17y ago|4 comments
7. 277.▲
   by pwpwp 17y ago

   See for example http://arstechnica.com/apple/reviews/2003/04/finder.ars While OS X may be prettier than earlier MacOSes, conceptually, it's much closer to Windows than to the MacOS spirit.
8. 278.▲
   by pwpwp 17y ago

   GAE: if you can reduce your problem to searching in a b-tree, you're in heaven. GWT: code for the browser like it's 1984.
9. 279.▲
   by pwpwp 17y ago

   Since when is humor inane?
10. 280.▲
    by pwpwp 17y ago

    Besides using JS on the server with Helma for some time, I even wrote a Lisp->JS compiler (CyberLisp) in JS. This project finally showed me that I don't want to use JS anymore. I agree with your point about prototyping, but I don't see
11. 281.▲
    by pwpwp 17y ago

    Prototypes vs classes is a matter of taste, and I don't think "power of expression" can be measured.
12. 282.▲
    by pwpwp 17y ago

    JavaScript is "assembler with closures and broken hashtables", and I don't get why anyone would want to use it on the server, compared to richer languages.
13. 283.▲
    Go Interfaces, by one of the Go authors(airs.com)

    4 points by pwpwp 17y ago|0 comments
14. 284.▲
    by pwpwp 17y ago

    For some values of true. While PicoLisp is certainly interesting, the bulk of Lisp and Scheme (and Dylan) implementations since the early 1980's have gone into a different direction. For me, true Lisps are languages like T, EuLisp, Dylan, G
15. 285.▲
    by pwpwp 17y ago

    del.icio.us
16. 286.▲
    by pwpwp 17y ago

    http://nakedobjects.org/ http://code.google.com/p/piccolo2d/
17. 287.▲
    by pwpwp 17y ago

    The takeaway for me was: 1) use a HMAC instead of using message digests directly 2) don't throw away structure in the strings you sign.
18. 288.▲
    Networking Named Content (PARC's take on next-gen internetworking)(cl.cam.ac.uk)

    4 points by pwpwp 17y ago|0 comments
19. 289.▲
    by pwpwp 17y ago

    Meta: I think it would be very helpful if "rate my startup" posts would include a short description of what the startup does in the title.
20. 290.▲
    Proceedings of the ICFP 2009(portal.acm.org)

    2 points by pwpwp 17y ago|0 comments
21. 291.▲
    Hierarchical Read-Copy-Update (lockless synchronization for 1000's of CPUs)(lwn.net)

    14 points by pwpwp 17y ago|0 comments
22. 292.▲
    by pwpwp 17y ago

    For my tastes, Clojure strays too far from proven ground. It's nice to experiment with stuff like persistent data structures and STM, but I don't think the next big Lisp, if there is one, will be based around that model. It's simply too far
23. 293.▲
    Steps Towards an Acceptable Lisp(pwpwp.blogspot.com)

    19 points by pwpwp 17y ago|12 comments
24. 294.▲
    by pwpwp 17y ago

    FWIW, I tried to write a satire by using only real quotes, and making nothing up (because I find the whole affair completely ridiculous by itself.) Judging by the comments left on the blog, I guess I failed.