Show HN: FunctorFlow – An attempt to re-imagine Python libraries
1–10 of 55 posts
Re: Show HN: FunctorFlow – An attempt to re-imagine Python libraries
#2Re: Show HN: FunctorFlow – An attempt to re-imagine Python libraries
#3Looks convenient for notebook/repl style use (assuming the the editing environment still supports autocomplete/correct and other niceties). I might just be stodgy and change averse, but I'd be a bit less willing to try things like this in production.
Landing page or FAQ could possibly benefit from an explanation along these lines.
Re: Show HN: FunctorFlow – An attempt to re-imagine Python libraries
#4How would one use this with existing Python packages? Or is this a parallel universe to PIP where libraries need to be written explicitly with FF?
The website doesn’t mention how FF packages are versioned or how version restrictions between dependencies are resolved.
I see this as quickly becoming full of “left-pad” sized packages, can you analyze a full project to fetch everything ahead of time?
Re: Show HN: FunctorFlow – An attempt to re-imagine Python libraries
#5What's the target audience? Looks convenient for notebook/repl style use (assuming the the editing environment still supports autocomplete/correct and other niceties). I might just be stodgy and change averse, but I'd be a bit less willing to try things like this in production. Landing page or FAQ could possibly benefit from an explanation along these lines.
Yes, do not try this in production yet.
Currently, this library works only on Repl.it for the exact reason.
This is why you see the headline with "an attempt". :)
Re: Show HN: FunctorFlow – An attempt to re-imagine Python libraries
#6Re: Show HN: FunctorFlow – An attempt to re-imagine Python libraries
#7Where are the docs? The “docs” link just forwards to a Twitter account. How would one use this with existing Python packages? Or is this a parallel universe to PIP where libraries need to be written explicitly with FF? The website doesn’t mention how FF packages are versioned or how version restrictions between dependencies are resolved. I see this as quickly becoming full of “left-pad” sized packages, can you analyz…
Thanks for understanding. ;)