jnoller

64 ms·

1. 631.▲
   Words Apple Won’t Hear (Right Now) – Code For Android First(kenyarmosh.com)

   4 points by jnoller 16y ago|0 comments
2. 632.▲
   Python's Innards: Naming(tech.blog.aknin.name)

   8 points by jnoller 16y ago|0 comments
3. 633.▲
   In Cloud Market, Arming David May Be the Way to Take Down Goliath(gigaom.com)

   3 points by jnoller 16y ago|0 comments
4. 634.▲
   The Cloud’s Little Secret: Vendor Lock-In(nasuni.com)

   19 points by jnoller 16y ago|5 comments
5. 635.▲
   by jnoller 16y ago

   Yes, it was a clever hack in the beginning - which is what counted. Given that Python's implementation (CPython, with a GIL) was started in December of 1989 ( http://python-history.blogspot.com/2009/01/brief-timeline-of... ) I'd say that it
6. 636.▲
   by jnoller 16y ago

   Ironic, because I'm only 30. It's not outdated at all - take for example, the GIL - sure, get rid of it, and put in granular locking. You've now actively harmed the lives of every C extension author and maintainer out there, and slowed down
7. 637.▲
   by jnoller 16y ago

   Python has never; and probably never will claim to be the fastest language in the stable. The tradeoff made is processor time, versus developer time - one is cheap, one is not. Should, and can Python be faster without sacrificing the speed
8. 638.▲
   Nasuni (cloud storage appliance) adds Rackspace support(nasuni.com)

   1 points by jnoller 16y ago|0 comments
9. 639.▲
   Mailing list debates considered harmful(tech.blog.aknin.name)

   21 points by jnoller 16y ago|18 comments
10. 640.▲
    by jnoller 16y ago

    Fair enough; but I'd rather see things fixed then see the constant drum beat of "this is broken and a piss-poor design decision". If it's broken, fix it. There's no excuse to not fix bugs, even in the name of backwards compatibility.
11. 641.▲
    by jnoller 16y ago

    Agreed, this has come up more and more frequently and I'm beginning to see the light of allowing string methods on bytes more and more.
12. 642.▲
    by jnoller 16y ago

    Not worth the bytes on the wire; the short version: the app store approval process is schizophrenic and fascist. Everyone already knows this.
13. 643.▲
    by jnoller 16y ago

    To us (Nasuni - I am an employee) losing objects in the cloud is unacceptable, therefore, the blog post reenforces that. The Nasuni Filer (our product) is a local-to-the-site, cloud-backed filesystem - and losing objects in a filesystem i
14. 644.▲
    by jnoller 16y ago

    Standard library changes in Python 3 which make supporting WSGI and stacks like it (and protocols in general) more difficult or painful are bugs. Since the stdlib isn't set in stone, those bugs should be fixed by the interested parties. No
15. 645.▲
    by jnoller 16y ago

    You are right; much of the python community dislikes the GPL (myself included) but I don't know of widespread "how the hell do we get around it" disease. Most of us just see GPLed code, shrug, and move on. You seem to be making it out like
16. 646.▲
    by jnoller 16y ago

    I'll believe it when I see it - it will be very interesting to see if other VC firms in the area (Sigma, Greylock, Matrix, Polaris, North Bridge, etc) get involved in this at all. As it is, I've not seen very many business-or-startup friend
17. 647.▲
    by jnoller 16y ago

    _multiprocessing is C code which is a compiled library which is references in Lib/multiprocessing - essentially, the C code is compiled, but only exposed to/through the python module which is multiprocessing proper.
18. 648.▲
    by jnoller 16y ago

    Yup, looks like it was deleted. I totally understand it when people don't have the time to submit patches :). I have almost no time lately, and way too many projects I want to be part of so I'm the last person to ask people to spend time th
19. 649.▲
    by jnoller 16y ago

    yup, close enough, though here's trunk: http://svn.python.org/view/python/trunk/Lib/multiprocessing/
20. 650.▲
    by jnoller 16y ago

    I said this in a reply to another comment, but it's worth repeating. Yes, brandon is right, there is a difference, albeit an intentional one. I agree with him that having an option to force this behavior to match across platforms is desirab
21. 651.▲
    by jnoller 16y ago

    The python-multiprocessing source on google code is not canonical fwiw, you're better viewing the python.org svn version.
22. 652.▲
    by jnoller 16y ago

    Hi, I am that jnoller. And no, I wasn't trying to be rude. Yes, I want it too, I agree with Brandon, however I do not have the time to do so. He asked for a feature; I told him I agree, but that I don't personally have the time for a patch.
23. 653.▲
    Building A Gateway to Cloud Storage for The SMB(wwpi.com)

    0 points by jnoller 16y ago|0 comments
24. 654.▲
    by jnoller 17y ago

    Nasuni (Natick, MA) is hiring! http://www.nasuni.com/sub/jobs/ Inside Sales Representative (Account Manager) Web Marketing Specialist Community/Social media manager QA Test Engineer Most of these would be onsite - I'm pretty sure the Comm
25. 655.▲
    by jnoller 17y ago

    Yes, and Brett and I have discussed grossly improving the dev.python.org site. It's on the plan, but somewhat orthogonal to what I'm asking for from the community. Personally, I'm quite aware of how to contribute :)
26. 656.▲
    by jnoller 17y ago

    But is it possible that making the bugs we have more apparent would scare people off from using it? "Oh no! A programming language with bugs!"
27. 657.▲
    by jnoller 17y ago

    We do have an "easy" list in the bugtracker, but it can be annoying to find.
28. 658.▲
    by jnoller 17y ago

    I actually completely agree with you, and your final point is what I want to drive towards.
29. 659.▲
    by jnoller 17y ago

    Thanks
30. 660.▲
    by jnoller 17y ago

    Thanks for sharing this. I'm definitely interesting in HN feedback as well.