As I understand it, the Drive API is public and well-documented ( https://developers.google.com/drive/ ).
As I understand it, the Drive API is public and well-documented ( https://developers.google.com/drive/ ). What's to stop, well, anyone from just implementing this and throwing it up on GitHub? "Why did you do it?" "I guess I just got tired of waiting for someone else to do it for me."
Posted by fixermark on Apr 24, 2015, 6:45 PM
Tags
Related issues
- That isn't really relevant for the tool starting the container.
- Why is there no link to the source?
- Something I wonder about in this domain is if this is the fault of the language.
- Namespace pollution is an annoying problem in Rust.
- Currently, no language ports of Timefold Solver are planned.
- I agree with you, almost all .NET code I write is within the .NET framework, yet when I look at C# repos, it's disheartening to see so ma...
Raise real-world problems, find people facing the same issue, and discuss solutions.7,000 issues0 comments
hackernews (Software)
That isn't really relevant for the tool starting the container.
Why is there no link to the source?
Something I wonder about in this domain is if this is the fault of the language.
Namespace pollution is an annoying problem in Rust.
Currently, no language ports of Timefold Solver are planned.
I agree with you, almost all .NET code I write is within the .NET framework, yet when I look at C# repos, it's disheartening to see so ma...
Why is there no simple workaround for this?
I have been using https://github.com/jacktasia/dumb-jump to quickly jump to definitions.
As I understand it, the Drive API is public and well-documented ( https://developers.google.com/drive/ ).
As I understand it, the Drive API is public and well-documented ( https://developers.google.com/drive/ ). What's to stop, well, anyone from just implementing this and throwing it up on GitHub? "Why did you do it?" "I guess I just got tired of waiting for someone else to do it for me."
Comments (0)
No comments yet. Start the discussion.