Live data from Hacker News

Fastai: A Layered API for Deep Learning

arxiv.org

21–30 of 43 posts

Re: Fastai: A Layered API for Deep Learning

#21
I think this is cool... but... personally, I feel that PyTorch’s API is more or less where I want a deep learning API to be.

TensorFlow is too low level. Fastai abstracts too much away and feels way too magical - once things start going wrong, or if you need to do something totally outside the bounds of the library, good luck.

Guess I’m mostly just a bit tired of frameworks for what feels like frameworks sake.

Re: Fastai: A Layered API for Deep Learning

#22

I think this is cool... but... personally, I feel that PyTorch’s API is more or less where I want a deep learning API to be. TensorFlow is too low level. Fastai abstracts too much away and feels way too magical - once things start going wrong, or if you need to do something totally outside the bounds of the library, good luck. Guess I’m mostly just a bit tired of frameworks for what feels like frameworks sake.

For most cases, objects in the fastai framework inherit pytorch objects and are often rather thin. This means that you can usually roll your objects if the fastai ones aren't sufficient. This really help alleviate the feeling that you're "on rails" of the library.

That being said, a current project I'm working on didn't really fit the fastai pipeline and I needed to drop into pytorch. It's a total shame since there are so many little niceties that make things easier.

Re: Fastai: A Layered API for Deep Learning

#23

I think this is cool... but... personally, I feel that PyTorch’s API is more or less where I want a deep learning API to be. TensorFlow is too low level. Fastai abstracts too much away and feels way too magical - once things start going wrong, or if you need to do something totally outside the bounds of the library, good luck. Guess I’m mostly just a bit tired of frameworks for what feels like frameworks sake.

For most cases, objects in the fastai framework inherit pytorch objects and are often rather thin. This means that you can usually roll your objects if the fastai ones aren't sufficient. This really help alleviate the feeling that you're "on rails" of the library. That being said, a current project I'm working on didn't really fit the fastai pipeline and I needed to drop into pytorch. It's a total shame since there a…

Can you go into more details on why pytorch was a better fit for your particular use-case?

My coworker recently completed a bootcamp using pytorch, and I am working through the fastai course, so it has been interesting to compare experiences.

Re: Fastai: A Layered API for Deep Learning

#24

The lectures have a ton of gems in them, but I have a hard time following the lectures as a beginner/intermediate practitioner, as around 1-5 percent is relevant for me. I don't particularly like the fastai library as it feels like an obstacle between me and the underlying pytorch library. After trying to use fastai for some time, I started looking directly at pytorch and found that all the abstractions and features…

The second part of the course ( https://course.fast.ai/part2 ) - builds stuff bottom-up, starting from matrix multiplication all the way up to ResNets. This is a great resource even if you want only use Pytorch.

Great tip. Thanks:)

Re: Fastai: A Layered API for Deep Learning

#26

I think this is cool... but... personally, I feel that PyTorch’s API is more or less where I want a deep learning API to be. TensorFlow is too low level. Fastai abstracts too much away and feels way too magical - once things start going wrong, or if you need to do something totally outside the bounds of the library, good luck. Guess I’m mostly just a bit tired of frameworks for what feels like frameworks sake.

I feel the same way about Fastai v1. Hard to use bits and pieces of it without rewriting everything. Apparently they heard this and addressed it with fastai V2 though so you can just pull in the critical bits you need.

Re: Fastai: A Layered API for Deep Learning

#27
Nice to see our paper on HN! FYI the paper covers v2, which is a from-scratch rewrite that introduces a new layered API.

There are quite a few comments here pointing out (quite correctly!) that v1 was not at all easy to hack on. We've spent the last couple of years fixing that. Have a look at the paper to see what mean - especially the "mid-layer API".

Re: Fastai: A Layered API for Deep Learning

#28
post #27

Nice to see our paper on HN! FYI the paper covers v2, which is a from-scratch rewrite that introduces a new layered API. There are quite a few comments here pointing out (quite correctly!) that v1 was not at all easy to hack on. We've spent the last couple of years fixing that. Have a look at the paper to see what mean - especially the "mid-layer API".

Oh btw if you don't have time to read the paper, I've summarized some key bits here: https://mobile.twitter.com/jeremyphoward/status/122797513809...

Re: Fastai: A Layered API for Deep Learning

#29
Personally, I really enjoy the design and level of abstraction that Pytorch provides. FastAI has always felt too abstracted and trying to go outside the bounds of it gets really hard and complex, really fast. I glanced through the paper and while it certainly looks interesting and to be an improvement, I am not very convinced that doing custom things will be easy, like it is with Pytorch. My experience has been that it is easy, if you already understand all the pieces of the entire library, which is not an easy task at all.

That being said, I admire the passion and effort that goes into FastAI and I think it does a great job at providing an entry point into the world of ML/deep learning that is far more accessible to people. I'll probably still read through the library because I always pick up interesting ideas and learn new things when reading other peoples code, especially when a lot of thought has been put into structuring a library.

Re: Fastai: A Layered API for Deep Learning

#30
post #16

Bleeding edge is great for fun and personal development, Jeremy (with the fast.ai team as a whole) is wonderful and all that, but you need to have your own suitable case study to make the most of such techniques and implementation... nlp for the time being, it was image processing when they were just starting and I followed their courses. In 2020 or year V, VI or VII of this new machine learning explosion, generalist…

My impression from 3 years of working under the job title of "data scientist" is that generalists have a huge advantage compared to specialists. Data scientists these days have to have some idea of how each step in the data science workflow works, including non-technical aspects like business, office and institutional politics, and domain knowledge.
Post reply on HN