Visual Studio Code is a different thing... and claims to be open source, but by intent and approach really is closer to source available.
1,032 karma · joined July 16, 2013
Visual Studio Code is a different thing... and claims to be open source, but by intent and approach really is closer to source available.
While I wouldn't say more people shouldn't do this more of the time, there is also a lot of social capital you have as a staff level person that makes it "easy" to do this. (and is part of why it's important to)
In addition, the source you linked explicitly points out that the id standards were just one part of a bill that "would repeal the provisions regarding identification documents in IRTPA, replace them with a version that would set the federal standards directly rather than in negotiation with the states, and would make various changes to US immigration law regarding asylum, border security and deportation."
Immigration politics
Really? My thinking is more that human devs are way too likely to sink time into powerful but complex tools that may end up being a yak shave with minimal/no benefit in the end. "too lazy to use" doesn't seem like a common problem from what I've seen.
Not that the speed of an agent being able to experiment with this kind of thing isn't a benefit... but not how I would have thought to pose it.
Your definition of class also seems to be very different from a traditional Marxist take -- hereditary systems were mostly seen as a symptom and not the problem itself, and were mostly orthogonal to any understanding of class.
I _hope_ there is hope, but I don't have much confidence that it lies in century old tropes of "rise up and throw off your chains."
Doesn't this make it prohibitively difficult to do local builds of open source projects? It's been a long time since I've done this, but my recollection was that the process to do this was essentially you would build someone else's (the project's) package/namespace up through signing, but sign it locally with your own dev keys. A glance at the docs they've shared makes it sound like the package name essentially gets bound to an identity and you then can't sign it with another key. Am a I misremembering and/or has something changed in this process? Am I missing something?