737 karma · joined July 19, 2018
The other gain here is with duck-typing as being less explicit allows you to write more generic code which will often do what you want as long as the shape fits without `void*` which gives up on type safety.
The majority of uses of it in unrolling duck-typing cases will most likely be replaced by [1] which allows the same but with `switch` instead. Thus `inline for` will be left for loop unrolling and possibly in use with `inline switch` where it matters.
Currently there's a large number of resources that refer to the program as GIMP which are unlikely to be updated if the name changed and thus making years worth of guides, tutorials, and so on harder to find unless you know to search for (which if you do... the name change is meaningless as you'll still see GIMP). Harassing GIMP over the name is hardly a way to get things moving forwards and only sparks a negative environment. Should you find the name to make the software unusable then it would be better to focus your attention on the fork which changes the name rather than continuing to contribute a negative to the positive news of GIMP turning 25.
Compare something like flow [1], reason [2], or prepack[3] as it's tools which serves you rather than the company behind it with access to the source which is the same as the case for weboob if you want to compare against facebook. I don't see an issue with using them though as they don't collect data on you.
[1]: https://github.com/facebook/flow
[2]: https://github.com/facebook/reason
Now I can agree that having decent documentation or even literate programming [1][2] contribute in large to understanding but it's never a replacement for clean and maintainable code. It's the same as architecture where if you're sloppy with the designing a bridge it can (and often will) come crashing down resulting in high expenses and lives lost over something that could have been prevented had others been able to understand the design and question the practices. The same applies to code.
[1]: https://cs61.seas.harvard.edu/site/pdf/p384-bentley.pdf [2]: https://jhidding.github.io/adhesion-code/
Judge the code for technical merit and not the assumed character of the author. Denying work based on social correctness only curbs engineering and scientific progress in the long run over bikeshedding matters.
Hard tabs are not accepted by stage1 because:
- It doesn't need to. All of the self-hosted compiler source is formatted with zig fmt and so there are no hard tabs. The complexity of dealing with hard tabs need not be present in stage1.
- zig fmt is not fully stable yet; use of zig fmt is not yet ubiquitous. If stage1 accepted hard tabs, then in practice, there would be accidental mixing of tabs and spaces.
[1]: https://github.com/ziglang/zig/wiki/FAQ#why-does-zig-force-m... [2]: https://github.com/ziglang/zig/issues/544g
Trust until broken and gratitude for upholding good values is the path to a better community along with giving a chance to do better. Quick punishment only leaves a sour taste for everyone.
Also, a good rule is to wait 5-10 minutes or more and see if what you've written aligns with what and how you want to say it or at least expanding on your point a bit further to avoid being misinterpreted.
> If someone were to open an issue "Please change master to main," and they were genuine about the request, I'd be like ... ok. And that would be the end of it. It's a s/master/main/g. Sure, whatever.
Not at all, it's just a question of who will pay to update all code and documentation to follow the new naming standards. That's not only the documentation of the project in question but also resolving issues when refering to external sources which also use master/slave terminology such as the MBus and related tooling.
> Why not let them?
Will they pay someone to make the changes or do they expect smaller places to shell out money to fix a non issue to avoid being associated with something they've never had any relation to? No? No change unless they either do the work themselves or pay for the cost of changing it.
> From my point of view, this is a big ball of "whatever, who cares, just do it." But my mind is open: can you convince me that it's important to resist this trend? Without invoking slippery-slope arguments?
There isn't really much of an argument for implementing it other than being pushed into exile by others if you don't. Resisting it would mostly come down to the cost of yet another cosmetic change that does nothing other than cost hours of work with no real reason than some being "offended" by well established terms.
In the end, this is a change where I just don't see the merit of. In the end it seems to be the practice of banning being easier than understanding what it's actually used for and comming up with a solid argument for change. It's not the burden of those sitting on `master` branches to explain why not but rather those suggesting this change to provide at least something which hints to the change being worth the effort.
Reuse saves work when your problem maps perfectly to existing tools while what may seem like a minor difference will propagate down your program to end in countless issues from a codebase you don't know.
Well I live in Europe as I'm Swedish; in the UK it's common to say "bless you" while in Sweden we usually say "prosit" (the two I've spent a significant portion of my life in). The former would even be from those not following Christian traditions but rather as stated before. This seems to reflect the trend in quite a few others in Europe such as Spain, Ireland, Wales (UK), etc.
Again, most of it isn't an attempt at "converting" or even some other hidden motive. It may be different in other parts of the world but from the places I've lived in Europe it's been as I've stated.
As for culture, sure, every single one is at some point guilty of crimes against humanity such as in my country [1], [2], etc and we must be able to look past those things as otherwise it's impossible to change for the better.
We will be different, have different beliefs, different sexuality, different colours of skin, and different languages to convey our thoughts. If we continue to see even an act of kindness as hostile then I don't have much hope people will ever get over differences. It shouldn't be different if they're Christian, Sunni, or any else and extend their greeting in their way to you along with their own way of wishing you well. What matters most is the intention rather than if they're from the same faith as you.
[1]: https://en.wikipedia.org/wiki/Compulsory_sterilisation_in_Sw... [2]: https://en.wikipedia.org/wiki/Midsummer_crisis
What stallman pointed out was the inaccurate definition of a specific term and possibly wanting a fair and accurate description of the events of someone he knew. He's previously taken issue with inconsistency which could place and 17 year old in prison on their 18th birthday if they're already in a relationship with someone even born just a few days apart depending on which country they're in. He also stressed that placing Minsky at the same level as Epstien is wrong unless there's evidence Minsky was completely in on the deal (which there seems to be none as far as I'm aware).
The many other things seem to be lacking in evidence. The earlier point of women unwilling to report men in high positions just means a lack of evidence thus no justice can be had. It's the same as not reporting a robbery. Nobody can do anything if nobody knows it ever happened (outside of those involved).
I do agree that there should be some work within helping victims report without feeling as vulnrable to the point of keeping it to themselves but I don't think media outlash is the right tool for this. Nor do I think trying to socially hang those that comment on the topic is the right thing to do. All it does is prevent the much needed discussion around what the terms actually mean and if we can be more accurate in their definitiion to provide a better framework for dealing with such cases.
I'm not religious at all and I still say "bless you" since it's from the culture I grew up with of wishing others well. If anyone finds that offensive then they certainly have more issues than I do.
So am I and I often come off as awkward with a list of misinterpretations to the point of having a "do not interact with this person as they won't understand" list to avoid it.
His behaviour is typical of someone with an foot on the spectrum and I don't see too much oddity in his behaviour. He's obsessed with meaning of words, comes off the wrong way, seemingly no social manners by most standards yet it's incredibly consistent which hints to different interpretations of social interaction.
His behaviour isn't "problematic" in this case, rather, it's correct in a desire for exactness.
That said, I find it difficult to follow what is happening when using several variables as you're then likely doing something wrong in the complexity of the function. A function should say much with very little and control flow should be clear instantly. The only thing outside of this would be a procedure which do-notation allows one to express.
Imperative programming is already within Haskell with do-notation an it's composition is that of imperative. Mixing functional with something else makes it much harder to make use of combinators and other forms which ends in more messy code (in my experience). If one could go pure functional without do-notation emulating the "C monoid" it would be rather nice.