I won't talk about Google Colaboratory, but I usually use Google Colaboratory and have the disadvantage of "this is ...", so I will explain it.
There are two main disadvantages.
It's commonly known as the "12 hour / 90 minute rule".
The restriction of 12 hours of continuous use does not mean that such a heavy operation is performed, so there is no problem so much, but I felt that it was a disadvantage that it could not be executed regularly.
Personally, this was the biggest disadvantage.
For example, I was having trouble with automatic execution of browser operations, especially when scraping sites that use JavaScript. Of course, if you can specify the element, there is no problem, but when you download the canvas element, you must use the GUI.
I personally felt that it was a disadvantage that this could not be used.
After all, it's better to build the environment locally. Of course, it's frustrating if errors occur frequently in environment construction, so ... I think Google Colaboratory is a good entrance, but it's better to build a local environment as well as studying to get used to programming because there are more things you can do.
Also, Google Colaboratory has very good specifications, so it is suitable for handling large amounts of data. I can operate the browser, but I thought that the local environment was better.
Now that I'm used to programming to some extent, building an environment is not so difficult. After all, I don't know if you say docker or Anaconda without knowing anything. I don't like it when I suddenly show off the bright red error wording, and it's in English.
I think it's okay to build an environment after becoming resistant to such points.
Recommended Posts