I don't understand why the control panel UI wasn't modernized instead? Would that really be unfeasible? I think it still might have been less work than to maintain 2 coexistent "settings/control panel" apps and migrate from one to another. Sometimes you have to throw out the old code base and start from scratch. But if you do so shouldn't you rather distrubute the result when your finished and not in a half-baked compromise-like state?
FrameXX
joined 1 year ago
I don't understand why the control panel UI wasn't modernized instead? Would that really be unfeasible? I think it still might have been less work than to maintain 2 coexistent "settings/control panel" apps and migrate from one to another. Sometimes you have to throw out the old code base and start from scratch. But if you do so shouldn't you rather distrubute the result when your finished and not in a half-baked compromise-like state?
To anyone with a TV running Android I recommend SmartTubeNext: https://github.com/yuliskov/smarttube
AOSP source code
He is asking about Android studio not Android Open Source Project?
I agree. Most custom ROMs already have such option.
I am sorry. I went to a little rant, but I meant it rather funny even though I realize it feels aggressive 🤣. I am just enthusiastic about this topic even though I don't know that much.
Isn't this a problem with every package/library system? Is there really a solution to this that doesn't limit packages with how they handle their dependencies?
This may also be about trust. npm probably could limit a number of dependencies that a single package can have with an arbitrary limit, but they don't do that, because they trust the developers they won't misuse their options. Well...
Node packaging is fucked. Node packaging remains fucked.
I am sorry, but as a noobie user of npm I don't understand. It works pretty well for me if you use it normally for what it is supposed for.
view more: next ›
Change for the sake of change. At least it seems to be in a good direction.