mononcqc

35 ms·

1. 301.▲
   by mononcqc 16y ago

   Hello, I'm the author of Learn You Some Erlang. Let me know if you have any comments or questions :)
2. 302.▲
   by mononcqc 16y ago

   Thanks. Makes sense.
3. 303.▲
   by mononcqc 16y ago

   This part was interesting to me: VP8 is simply way too similar to H.264: a pithy, if slightly inaccurate, description of VP8 would be “H.264 Baseline Profile with a better entropy coder. Then later, about the encoder: there were comments
4. 304.▲
   by mononcqc 17y ago

   Reading the article, the author especially warns about doing this with anyone and instead suggests trying this technique with long term customers who you trust (and trust you back), find the project to be important for their enterprise (not
5. 305.▲
   by mononcqc 17y ago

   Well, Erlang has its own database that can store Erlang terms (see mnesia). As you can save some there for the impedance mismatch. Nitrogen itself deals with reducing the differences between your backend code and the frontend. See the demos
6. 306.▲
   by mononcqc 17y ago

   The advantages of Erlang are not limited to distribution, but also excellent concurrency. By this, I don't necessarily mean high throughput and amount of queries served per second, but a general resilience over high loads. Because every tas
7. 307.▲
   by mononcqc 17y ago

   The title is only true if you sit downstream :(
8. 308.▲
   by mononcqc 17y ago

   I found myself having no problem reading it, knowing bits of set theory I had taught myself beforehand, but I have to admit I would have been confused otherwise. Given the authors have the book open-sourced and that this looks like it's sti
9. 309.▲
   by mononcqc 17y ago

   Ah, my bad - hadn't seen that one and it (obviously) didn't get picked up as the same link.
10. 310.▲
    A free graph theory book by David Joyner, Minh Van Nguyen, and Nathann Cohen(code.google.com)

    42 points by mononcqc 17y ago|11 comments
11. 311.▲
    by mononcqc 17y ago

    Thanks for submitting the article. This is very useful. I've considered eventually offering a version of Learn You Some Erlang ( http://learnyousomeerlang.com ) as an ebook. Obviously, being able to use straight HTML would make things infin
12. 312.▲
    by mononcqc 17y ago

    I know that. What I don't get is why they chose that over JSONP, which solves the exact same problem by using <script> tags and a callback function. Their solution seems to work well, anyway.
13. 313.▲
    by mononcqc 17y ago

    I hope not, because it's hard to blame only Erlang. First of all, they rolled their own epoll-based server for the whole chat system. Then, instead of using a 'sane' comet/long-poll implementation based on JSONP (to avoid limitations of sam
14. 314.▲
    by mononcqc 17y ago

    Having evaluated some XMPP solutions (over BOSH), one of the problems I have had with it was about the openness of the protocol. You need to tweak the server a whole lot if you want to close down what your users can do and from where they c
15. 315.▲
    by mononcqc 17y ago

    One of the thing proper to Erlang's hot code loading is that it uses a vm-centralized code server that handles and garbage collects the different versions of code. This server can in turn notify subscribers about code changes; the OTP frame
16. 316.▲
    by mononcqc 17y ago

    You bury the ashes
17. 317.▲
    by mononcqc 17y ago

    And here I was wondering why random people started following me on twitter. Thanks for the reference!
18. 318.▲
    by mononcqc 17y ago

    That's okay, though. Concurrency =/= parallelism. The most important part is being able to build independent blocks that can interact. Having them run at the same time is just a nicety on top of it, but it's in no way essential. Erlang work
19. 319.▲
    by mononcqc 17y ago

    I've never got the "And turd tokens" thing after using the language for a few days. It pretty much all makes sense to me. I've already posted http://news.ycombinator.com/item?id=837217 to express my opinion on that though, if you want to
20. 320.▲
    by mononcqc 17y ago

    The Gambit Scheme lib you're talking about might just be termite ( http://code.google.com/p/termite/ ). It sounds like an interesting lib, although it doesn't do everything Erlang does.
21. 321.▲
    by mononcqc 17y ago

    The Nine nines of reliability often quoted is for the availability of a complete distributed system, including maintenance downtime. A typical single Ericsson AXD 301 switch had a target of 5 nines of reliability without network redundancy,
22. 322.▲
    by mononcqc 17y ago

    If you want to write lisp macros in Erlang, Robert Virding's Lisp Flavored Erlang might be what you look for: it's a lisp syntax on top of the Erlang VM (so it should be compatible with everything else) and it's supposed to support more pow
23. 323.▲
    by mononcqc 17y ago

    The end result is relatively similar. Erlang has an underlying representation that uses something akin to prefix notation, albeit more verbose and a lot uglier than what you'd get from lisp. Here's a blog post with an Erlang Abstract Syntax
24. 324.▲
    by mononcqc 17y ago

    This makes me realize I would listen to a podcast of them debating and discussing stuff. And I never listen to any podcast. They're both pretty nice guys, always civil in their opinions (a bit less for Joe Armstrong when he talks about OOP)
25. 325.▲
    by mononcqc 17y ago

    Presence probably takes more juice than the billion messages, and a good chunk of these servers can probably be there as fallbacks in case of failures. Just a supposition. They do use C++ for the chat system, it's mainly the channels/presen
26. 326.▲
    by mononcqc 17y ago

    Check out Lisp Flavored Erlang for a lisp developed on the Erlang VM. http://github.com/rvirding/lfe
27. 327.▲
    by mononcqc 17y ago

    Release R13B02-1 is out. It contains the patch for reltools, given it was pretty dangerous for those who used it unpatched.
28. 328.▲
    by mononcqc 17y ago

    I'm pretty much addicted to Dialyzer, so the possibility to refer to types defined in another module (using the syntax Module:Type()) is pretty awesome. I didn't have time to see if they made anything faster, but the release notes seem to m
29. 329.▲
    by mononcqc 17y ago

    I've always found the rules quite simple, once you think of everything as expressions (and not lines): "." ends an expression in the shell. In modules, "." ends forms. Forms are module attributes and function declarations. Forms are technic
30. 330.▲
    by mononcqc 17y ago

    Yeah, it's where I got the difference too. I decided to add it to LYSE after that.