31–40 of 55 posts
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
Earlier quoted context omitted.
What? Python is arguably the go-to language in data (and other) science. With a massive ecosystem of mature, powerful libraries like numpy and scipy, you immediately and freely have access to a range of features, managed almost trivially with pip/virtualenv/conda. I don't think any other language has a larger number of performant ML libraries like tensorflow and pytorch, and more importantly, if you want source from…
"I mean, data science is really the thing that people should be using Python for." Did you read my comment?
Hi HN! Meet FunctorFlow ^_^ Think of it like lego blocks for your next tech-toys and hopefully (in the future) for your next big-thing ^_^. If you love tinkering with new toys then give it a try with Repl.it: https://dev.to/t/functorflow . If you want to meet cool kids like you then join our club at Discord by subscribing to our email-list. ...and follow updates at https://twitter.com/functorflow Together, we will re…
"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…
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
Even if it was about modules, if anything FunctorFlow makes it worse because you now have X+1 things creating modules (FunctorFlow has to live somewhere after all so it doesn't remove the previous system).
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.
I'll keep you updated.
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…
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 for a few years.
4. Come back and run the same notebook without everything breaking.
If this could patch into Python's native import mechanism and let me specify the repo version as todays date, it'd be great.
import functorflow
functorflow.repo("2019-08-04")
from ff.package_name.whatever import foo
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…
> 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…
A better suited name which encodes the core feature, "installationless helper routines", could really help this library to become actually recognized for what it can provide.
Here's another comment about the API: I would prefer a syntax like
f.name_of_function(args)
f("name-of-function", args)
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
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!
FunctorFlow only works on Repl.it, not on your machine!
Currently making tutorials and assignments for Repl.it community