26,735 karma · joined January 7, 2013
sir@cmpwn.com
Bazel is a nightmare. I wouldn't wish it on my worst enemy.
Focusing on the misuse of this tool by people is the most prudent worry to address.
Here's a sample from the file:
// For sprites, color 0 is transparency so don't draw anything.
if color == 0 {
continue;
}
This comment is probably not necessary: it would be equally clear if it were written as something like the following: if color == SPRITE_COLOR_TRANSPARENT {
continue;
}
A few lines up is another comment: // Is this specific pixel not on the screen? We already check that x_pos is not off
// the left side earlier, so only need to check that it's not off the right side.
if x_pos + p >= 160 {
continue;
}
If the code were written with a constant, then it would only need to clarify why we don't check the left side here (the only non-obvious thing about the code), so: // Note: bounds testing on the left side is handled earlier
if x_pos + p >= SCREEN_WIDTH {
continue;
}
One last example: // We want to iterate through 160 pixels to draw one scanline.
for col in 0..160u8 {
No comment, similar level of readability: for col in ppu.iterscanlines() {- Interopability between walled gardens like messenger apps
- Side-loading software on your devices
I'm also hoping that we see this specifically lead to the following:
- Installing your own operating system on any electronic device
- Third-party video games running on proprietary consoles without the vendor's approval
When companies like GitLab hire you, they lie about their principles and values. It's a polite lie that obfuscates their true goal, which is to generate profits for only a small fraction of the people to whom they are accountable, at the expense of the remainder.
This is cowardly, and morally wrong. I hope that those who were affected by this lie will find greener pastures at companies which live up to their stated goals and principles, who work in the service of what's right over what's profitable.
Opt-in or GTFO, Google. I'll be patching this out of the Alpine package for Go the day it ships.
I haven't seen such a poor discussion on HN in a long time.
There's still work to be done, but so long as work is moving forward and the Go team is communicative and pro-active about addressing the problem, then our concerns were satisfied, and I'm glad that we were able to address the issue.
The distinction between competitors and community contributions is false. Why should the publishers be entitled to exclusive monetization of the contributions of their community, and why should their community be denied the right to monetize a product they contributed to? The ability to share the wealth is why the open source movement works.
This approach stems from a position wherein the publishers view themselves as separate and privileged from their community, which is valid if you are the only entity investing in the software, but unjust if the community is an active participant in the software's development.
The mainstream view on OSS is often good for the original publisher, in that an organization which monetizes their software then has access to more resources with which to contribute back to the software -- particularly in the presence of a copyleft license to enforce this behavior. The original publisher is then able to benefit from a larger and more consistent workforce developing the project with them.
The orthodox view on open source is a useful and broadly understood shorthand for a certain enumeration of rights, the withholding of those rights disproportionately serves a certain group of interests at the expense of others, and disregarding these problems and using the terminology incorrectly in spite of them is willfully dishonest.
https://drewdevault.com/2022/03/01/Open-source-is-defined-by...
Happy to answer any more specific questions here on HN.