322 karma · joined June 13, 2012
Regarding "copyright abuse", it depends on multiple factors IMHO, but that was not the point of my comment at all.
That problems happen if you try to use the 100EUR one and obove.
Regarding your first question: I have tried virtualized and bare metal macOS (hackintosh) and I would recommend not virtualizing it if it's gonna be your primary workstation. Currently my main workstation is a hackintosh after trying first using it in a VM.
Virtualizing works, but under a VM there are several minor annoyances here and there that might drive you crazy (most of them are UI related, some app crashes, etc.). It would be perfect for example for a xcode build server. thought. YMMV!
[1] https://owncloud.com/client/ [2] https://owncloud.org/hosting-partners/
I agree that engineers might also have something to say, but we don´t actually have a clue if some of them actually expressed they concerns for this change, unless you have some insight from inside the company that you may not be able to share.
Even if some of them left as you suggest, I´m pretty sure Google wouldn´t have any problem to find some other engineers that would happily implement anything without questions.
Nevertheless, I agree that concerns should be raised by everyone in the org, but the only ones that might lead to an actual change is stock holders/board of directors.
Thanks for the link as well! I would love to see that experimented somewhere and see if it works.
Well, what he exactly says is that URLs should not include versioning, because URLs are the interfaces names and REST estates that interface names should not be versioned, as that implies a breaking change in the API. It's just the wrong place for versioning in the REST way.
But he is not against versioning, as you say, you can use the Accept header. You could also use a custom header if you might, but the canonical way would be the Accept header.
Thanks!
[0]: https://blogs.oracle.com/java-platform-group/java-se-support...