41–50 of 55 posts
I find how offended some of the people commenting are really compelling. What is the rationale behind this? Like why do it, then why again? I'm still open to the possibility this could be brilliant.
Indeed. Thank you, friend! I'll keep you updated.
Lack of versioning support makes this absolutely unusable for anything but sandboxing. And since the imports are scattered all over the code, it's hard for security scanning tools to check for vulnerabilities and to update libraries regularly. Pip isn't perfect but at least piprot helps me keep libs up to date. This tool was clearly designed in a vacuum.
Friend, there is a versioning mechanism. I'll share details in our Discord group. Please, subscribe to our email list to participate in our alpha.
This tool is clearly not ready for any use outside of a sandbox or toy.
Earlier quoted context omitted.
"Lego blocks" "tech toys" "tinkering" "cool kids" "next big-thing" -- perhaps they are your hopes for this project, but these are all vague, filler words that don't tell me what this thing actually does. If I take a look at it what do I see? It's not until I get to the twitter account that I see that it looks like you're trying to create not just a different python package manager, but a new ecosystem that's not back…
https://twitter.com/functorflow/status/1157396077043167232
Absolutely terrible. I can see why data science types who use / produce a lot of (typically throwaway) Python code might be enamored with this, but as far as the Python language goes, functorflow will be another nail in its coffin if it ever gains mass-acceptance. It will turn the already messy and inconsistent ecosystem into shambles that no sane person will want to build anything robust on top of. With the mass mig…
Brother, those "data science types" are also people. Be respectful of other people.
The source for the primary package is not published, afaik. The primary entrypoint function is implemented in cython, resisting casual analysis. The stated purpose is to pull (unversioned!) code from the internet and run it, but no mechanism to trust or verify that code is even mentioned. The advisability of the idea aside, the presentation here feels exceedingly and unnecessarily risky
Friend, (1) there is a versioning mechanism already in place (2) Cython is used to optimize the speed (3) FunctorFlow only works on Repl.it. We are in alpha. It does not work on your machine. Just go and install it. See if it works. It doesn't!
Earlier quoted context omitted.
> I can see why data science types who use / produce a lot of (typically throwaway) Python code might be enamored with this I think that's honestly its killer app. I don't do data science, but I often use jupyter to write short prototypes, and make plots and such. I've been looking for something that lets me: 1. Set up a jupyter notebook. 2. Run some tests or experiments, pulling in libraries as needed. 3. Ignore it…
Hmmm, that feels more like a jupyter extension than a standalone module. The extension could intercept imports automatically without the need for a prefix. Might require a custom kernel that does some magical per notebook lib mapping. Maybe it installs libs in version specific central folders and then does some symlinks to build a notebook specific lib folder based on the date specified. Feels more seamless but also…
Earlier quoted context omitted.
Friend, (1) there is a versioning mechanism already in place (2) Cython is used to optimize the speed (3) FunctorFlow only works on Repl.it. We are in alpha. It does not work on your machine. Just go and install it. See if it works. It doesn't!
Lemme repeat once again: FunctorFlow only works on Repl.it, not on your machine! Currently making tutorials and assignments for Repl.it community
Earlier quoted context omitted.
Hmmm, that feels more like a jupyter extension than a standalone module. The extension could intercept imports automatically without the need for a prefix. Might require a custom kernel that does some magical per notebook lib mapping. Maybe it installs libs in version specific central folders and then does some symlinks to build a notebook specific lib folder based on the date specified. Feels more seamless but also…
I'd actually implement it as a transparent venv and use pinned versions in a requirements.txt – with hashes, of course.
Only issue is that it'd be really space inefficient, my DS venvs clock in at 400+mb each so having one per sheet will probably quickly become unusable. Which is why I thought of some sort of smart system wide caching akin to maven/ivy. But I'd forgotten how complicated python dependencies (binaries, c code, etc.) were and how little api support pip had.
Earlier quoted context omitted.
Lemme repeat once again: FunctorFlow only works on Repl.it, not on your machine! Currently making tutorials and assignments for Repl.it community
Ah - you might want to clarify that point then, the marketing copy on your site implies that is (will be) usable in any python environment.