jnoller

80 ms·

691.
by jnoller 17y ago
It's all OK :) I'm glad (ecstatic actually) that you were excited about it enough to post about it!
692.
by jnoller 17y ago
For what it's worth - I'm Jesse :) Like I've said in previous replies - I'm just a (very happy) employee. On launch day I did post to HN (here: http://news.ycombinator.com/item?id=1112218 ). If you're interested in details, take a look at
693.
by jnoller 17y ago
Correct; I am an employee, my boss is one of the founders.
694.
by jnoller 17y ago
Why I'm feeling really complimented right now - I'm just a Nasuni employee. Last week at PyCon I did a lightning talk thanking the Python world for everything that helped us along. But; back to the product - you're spot on. It's a auto-scal
695.
by jnoller 17y ago
Which he mentions in the actual keynote
696.
by jnoller 17y ago
I'll definitely share this feedback with the team, thank you.
697.
by jnoller 17y ago
Currently; the Filer works with regular CIFS. NFS support it on the roadmap.
698.
by jnoller 17y ago
Disclaimer: I am an employee. While I linked to the press release; I felt that it was relevant to HN especially given that Amazon S3 just announced versioning for S3, this is a versioned, encrypted file system on top of S3, and other cloud
699.
by jnoller 17y ago
I agree - while this new feature from S3 makes sense for a segment of users, just like in normal S3 usage, the complexity is left for the client application to deal with. This is a non starter for most companies. Full Disclosure - I am an e
700.
Nasuni launches encrypted, multi-cloud, versioned virtual NAS(nasuni.com)
13 points by jnoller 17y ago|9 comments
701.
by jnoller 17y ago
Nasuni is hiring - Cloud Storage startup near Boston, MA (Natick). Python developer, Test/QA Engineer, Inside Sales Rep, Admin. Assistant. We're in stealth right now, please do contact us if at all interested! http://www.nasuni.com/sub/job
702.
by jnoller 17y ago
Just to add to: "" This reads like he believes the standard library is the only library, which (considering he uses C++ and Java) is a truly bizarre belief. If he doesn't like the standard HTTP library, it's trivial to either distribute a m
703.
by jnoller 17y ago
An improvement over the old implementation is better . "Fixed and Perfect" would be free-threading, where it would be twice as fast with threads. I'll take incremental, concrete improvements anytime.
704.
by jnoller 17y ago
There has always been discussion about adding features to 3k to increase adoption speed. Even when unladen goes into 3k, which is probably the middle-to-end of this year, it's another year before major OS vendors pick it up, etc. Nothing ha
705.
by jnoller 17y ago
As a Cpython developer; you and I both know 2.7 is slated to be the final "big" release of python 2.x. Anything past that point will be only bug fix/security fixes. Unladen would require a whole new 2.x release, which is not, and more than
706.
by jnoller 17y ago
That assumes any of us (BDFL included) are desperate to get it in production Right Now, which isn't true. However, backwards incompatibility is a tough pill to swallow and while Py3k is a cleaner, saner language it has still been a tough se
707.
by jnoller 17y ago
Also see Michael's post: http://www.voidspace.org.uk/python/weblog/arch_d7_2010_01_02... ( http://news.ycombinator.com/item?id=1036400 )
708.
by jnoller 17y ago
Incorrect; On linux and OS/X it uses fork. On windows it uses a best-effort clone.
709.
by jnoller 17y ago
Nah, it's all good - I've seen the trend too.
710.
by jnoller 17y ago
Actually, the intention was to add to the rationale which spurred me to help author the PEP. That's ok though, it's still a correct decision. ;)
711.
by jnoller 17y ago
Well, not to nit - it's 2 years, which, given an 18 month release cycle typically, is actually a tiny, tiny drop in the pond. Rather than saying "python's syntax is good enough" - we can simply couch it as "there is enough syntax" to last f
712.
by jnoller 17y ago
The moratorium is only on syntax and builtins, not the stdlib, nor the interpreter. I don't see how this can be a "perl 6 moment" when we have multiple, functioning versions, a plethora of alternative interpreters, etc. I would more willing
713.
by jnoller 17y ago
I'd believe that, except for at least two of the times I've seen a comment in this vein, they've cited specific words in the PEP. I guess they just skipped the relevant parts.
714.
by jnoller 17y ago
They don't - at least not exactly. Also, not the same codebase. See: http://mail.python.org/pipermail/stdlib-sig/2009-November/00...
715.
by jnoller 17y ago
Yes and no; I actually think a stronger focus on the standard lib and the interpreter is plenty of work to keep the hype running. It's been my personal bugbear to do a heck of a lot of cleanup in that space. For example, right now there's d
716.
by jnoller 17y ago
Well; that's not what I meant when I said it. I would love to see PEP 380 in, but I think that the possible benefits of this moratorium outweigh the usefulness of a new feature only a relatively small populace of users will use over the nex
717.
by jnoller 17y ago
It did not. PEP 380 will not see the light of day until the moratorium is lifted. This made me sad while I was writing it, but it is what it is.
718.
by jnoller 17y ago
__future__ additions are banned under this. See "cannot change" point 4
719.
by jnoller 17y ago
No - it does not apply to bugs or security issues
720.
by jnoller 17y ago
tail call elimination is a language feature. The GIL is an implementation detail of the Cpython interpreter. Jython, IronPython, and one day PyPy and Unladen-Swallow will not have a GIL. Ergo, it is an implementation detail.

More ›