yes deleting files wouldn't violate GPL-3.0 to the best of my knowledge as those files would still be under the GPL license,
it's just that you wouldn't be using them
if anyone wanted to use a file licensed under any of GPL licenses the user would be required to license any modified or redistibuted files under the same license ("or later") as to not violate the copyleft terms
Just a minor clarification/correction: the "or later" part also depends on the license per se. There is a GPL-3.0-only and a GPL-3.0-or-later. Usually you'll find something like "or at your option any later version." if that is the case, but by default you should expect the GPL-3.0-only to apply.
I was expecting something more profound. Isn't this just the concept of using variables to keep code readable? Not a new concept and likely one most devs learn early on.
Can someone give an example of a time when software patents are good for everyone? Because I can only think of software patents that have prevented the widespread adoption of ideas, and not the opposite.
Copy designs you like, and keep a couple of CSS files +/- web components that you can carry along with you from project to project. Tweak then as you go.
Like everything else, getting good at making designs that you like will take time and effort, so if you want you get good at it, do it! I find it fun, and my designs aren't to everyone's taste (I too like black tshirts), but whatever.
Plus, getting good at making designs that i like has made me better at making designs clients/projects will like, so, win/win.
Love GraphQL, but oh man is it being over used at my company. Management sees success with one of our large apis, now all the little niche ones have to be migrated and everyone consuming them must migrate as well.
I like it, but the small 2 endpoint APIs that haven't changed in years, have small 5 field models and no related entities, has like 1 or 2 teams that consume them DO NOT need it.
Sounds like a bunch of people here don't understand the graphql use case or implementation. I've used it projects and works no worse than other solutions, and met the requirement of not having to update tons of code when queries are refactored. It's not right for everything, but the same is true for anything.
Not sure I buy this. If you have a config header file and make backwards incompatible changes to it how is that different to having backwards incompatible changes to any other config system?
I think what the author meant to say is "don't make breaking changes to your config system". Maybe it's common to ignore that when using source code as config; I don't know.
It's a bad idea anyway because compile-time options should generally only be for configuring the presence of optional third party dependencies, which you can do automatically. Anything else should be a runtime option.
Programming
Hot
This magazine is not receiving updates (last activity 1 day(s) ago). Subscribe to start receiving updates.