vseloved

10 ms·

1. 31.▲
   by vseloved 7y ago

   I would suggest you to read it before jumping to conclusions (as the new chapters will be published). Lisp will not be the main focus of the book, for those who don't plan to use it at work, it may be perceived just as pseudocode. As f
2. 32.▲
   by vseloved 7y ago

   Thanks for the comment. The style issue will be addressed in the next chapter that is entitled "Crash-Course into Lisp"
3. 33.▲
   by vseloved 8y ago

   it's a classic "worse is better": if doing good is hard, let's do the easy stuff. meh
4. 34.▲
   by vseloved 8y ago

   Thanks for your work on cl-async/blackbird: we also used it in our recent project (and you should have gotten a couple of related requests)! I don't think you should be discouraged though: your contribution is very valuable and su
5. 35.▲
   by vseloved 8y ago

   That's not unique to startup - I'd say it's even more relevant to regular "corporate" software development, no? What's unique to real startups (for my definition of "real": the ones that solve yet uns
6. 36.▲
   by vseloved 8y ago

   JVM's GC is surely better (actually, is there any other platform that has a better-developed GC infrastructure?) But the point, I guess, was not about the GC but about the usual size of Java applications
7. 37.▲
   by vseloved 8y ago

   you misunderstand the meaning of startups. Startups, at core, are not about rebuilding the same stuff by combining existing solutions but about building novel solutions to solve yet unsolved problems. The other things are really secondary t
8. 38.▲
   by vseloved 8y ago

   well, those 25 GB come bundled with the number of hyperthreads that we used (i.e. 8 for an AWS xlarge server), so we didn't bother to optimize for memory usage
9. 39.▲
   Minimal Perfect Hash-Tables in Common Lisp(lisp-univ-etc.blogspot.com)

   73 points by vseloved 9y ago|13 comments
10. 40.▲
    by vseloved 10y ago

    I presented a very similar implementation here: http://lisp-univ-etc.blogspot.com/2016/05/improving-lisp-ux-... Still, a lot of interesting questions remain, which are discussed here: http://lisp-univ-e
11. 41.▲
    by vseloved 10y ago

    +1
12. 42.▲
    5 Steps to Grasping Modern ML(lisp-univ-etc.blogspot.com)

    1 points by vseloved 10y ago|0 comments
13. 43.▲
    by vseloved 10y ago

    .. and, finally, you realise that Common Lisp is an acceptable Lisp (because when you learn it well enough you start to understand how to tune it to make it acceptable for you personally ;)
14. 44.▲
    by vseloved 11y ago

    First of all, this isn't so much about CS as about Computer Engineering. Next, as pointed out already, this selection is quite random and subjective
15. 45.▲
    by vseloved 11y ago

    But that's not the reason. Personally I find Lisp superior in most respects, but I don't think it's a good place and time to argue on Lisp vs Racket and similar topics.
16. 46.▲
    by vseloved 11y ago

    Yes, we're in the process of moving to docker-based deployments now. In fact, we already have ClozureCL running inside docker, but haven't yet done the same for SBCL. TBD soon :)
17. 47.▲
    by vseloved 11y ago

    that's much older than what we used recently, so it should be a different thing
18. 48.▲
    by vseloved 11y ago

    Can you also point to the particular version of SBCL that fixed for long-running compilation? We have recently upgraded to one of the latest version, but I think I've missed this change - I'm interested to check it in more detail.
19. 49.▲
    by vseloved 11y ago

    We played with sb-ext:bytes-consed-between-gcs, but couldn't find the right balance. That's why we were surprised with the result of the oversized heap experiment
20. 50.▲
    by vseloved 11y ago

    are there many platforms, besides JVM and .Net, that have good-quality concurrent GCs?
21. 51.▲
    by vseloved 11y ago

    There's a reference to upstart in the article. We have played with demonizing SBCL (there are a couple of projects out there), but then Grammarly as a whole moved to upstart-based deployments. They are really easy to manage: basically,
22. 52.▲
    by vseloved 11y ago

    Well, the HDF5 problem was actually not on the Lisp side ;) But, in general, do you really believe that there are no issues with libraries in other languages? I've had my share in Python or on the JVM, as well. The whole point in the a
23. 53.▲
    by vseloved 11y ago

    As for me, adaptability is one of the important traits of a senior engineer. Surely, you don't have to be an expert in every platform, but you also shouldn't go mad if you need to do some work outside of your comfort zone occasion
24. 54.▲
    by vseloved 11y ago

    I have pointed to the call-with-* style which is a general "best practice" for that (it's even mentioned in Google CL Style guide). However, expanding to low-level stuff also has it's benefits for a clearly delimited spa
25. 55.▲
    by vseloved 11y ago

    Yeah, but that's something you need to be prepared for. Such bugs happen in literally every platform (for instance, I had similar trouble with the JVM). So the question is not how to avoid them, but how to cope. Usually, there are 2
26. 56.▲
    by vseloved 12y ago

    Hi Kevin, thanks for great comments. I wanted to share a hack with you: Penn Treebank is included as part of OntoNotes which is free-of-charge :)
27. 57.▲
    by vseloved 12y ago

    Grammarly - http://www.grammarly.com/jobs
28. 58.▲
    by vseloved 12y ago

    Lots of 1st world problems here
29. 59.▲
    by vseloved 13y ago

    cause, in Lisp OO is done right ;)
30. 60.▲
    by vseloved 13y ago

    SF - Grammarly ( http://www.grammarly.com/jobs ) - Sr. Backend Engineer - Sr. NLP Developer - Lead DevOps Engineer - Director of Product Marketing - Product Marketing Manager - Public Relations Coordinator