This seems like a shortcut to type less at the cost of very leaky encapsulation, which I don't think is a good trade. You may or may not want to expose all of jnettool.tools.elements.NetworkElement as a new interface, but choosing inheritance will always force you to expose everything from the inherited class. Furthermore, if you're extending classes that were not explicitly designed to be extended, this is fragile as there is no contract between your subclass and the base class and an implementation change in the base class may break you in unexpected ways.
What I also don't understand is how you're supposed to instantiate the new NetworkElement from an existing jnettool.tools.elements.NetworkElement. With delegation it's easy (just construct a wrapper with the object to be wrapped), but if the library is giving you instances of jnettool.tools.elements.NetworkElement, how do you get instances of your own subclass instead?
Decompiling object code produces an approximation of the original source code. Merely making this rough copy would usually violate the copyright holder's exclusive rights, even if the person who decompiled the code only used it as a preliminary step in making another work.
The only reason anyone believes this is fair use is because the copyright holders have chosen not to enforce it.
If I took images from the game and converted them to WebPs then distributed them, that is still copyright infringement, even though those are not the images Nintendo created. Likewise, if you do the same with machine code to reconstructed code, that's the same in principle.
I don't think that's a real legal defense. Code is just as subject to copyright as game assets (why wouldn't it be? it's just another kind of game asset), and the whole extracting assets thing making decompilations free from copyright infringement that gets bandied about is complete armchair lawyering. It's only by Nintendo's good graces these are still allowed to be hosted on GitHub.
I feel like all bets are off if you're modifying your phone away from what the manufacturer explicitly supports. Not saying you shouldn't, but this says nothing about the brokenness of the stock software.
This is an absurd argument that you are just making for the sake of argument and you know it. There's a difference between someone getting things wrong and a LLM shamelessly making something up out of the whole cloth.
The social solution is to abolish timezones (mine is of course objectively the right one, other people must deal with breakfast at 9pm wherever they are).
You might not, but the standard library sure does. And that's the exactly the problem! How can functions in the standard library know if the time is local or UTC without any indication on the value itself? (spoiler: they can't!)
Kind of ironic the raison d'être of Go is a memory safe language for concurrent programming but you can easily footgun yourself into doing something memory unsafe using concurrency...
That's not how authority works. Whatever you would choose to implement, you will need to have enough buy in from those middle managers and fiefdoms otherwise you will end up with heel-dragging or, worse, malicious compliance. If you've been in any kind of organization that's tried to impose completely top-down edicts, you should have seen the kind of destruction of morale it leaves in its wake.
Why shouldn't we want to pay people working at non-profits the same for their labor than they would get at for-profits? If they are doing just as or even more important work, why do we want to bend over backwards to justify them getting paid less for it?
As someone technically savvy, I don't trust myself to manage my own private keys sufficiently for a service that's the point of contact for all my friends and family. I think it's a much taller order for someone without the technical knowhow – remember that Signal's audience includes very non-technical people who don't have time to learn the technical ins and outs but absolutely require its utility, like journalists and dissidents.
- That's $338k/head on average. At face value for a nonprofit, I'd like these costs broke down as this seems excessive. There is far cheaper IT labor available outside SV.
You get what you pay for, though. $338k/year seems like a reasonable salary for people working on something as privacy critical as Signal – just because you're working for a nonprofit doesn't mean you have to work for less competitive wages.
I think it's pretty rare you would ever use std::list and rarer still std::forward_list – the on-paper complexities might be okay but the memory locality is so bad you should almost always be using std::vector or std::deque.
Personally, I feel like I'm not any more uncomfortable with it anymore than I am with cremation – both would be pretty gnarly if they happened to you if you were alive!