I just followed a few of the links Matthias posted today, and I must admit that I do not understand a word.
Karl pointed out that: > I don't think it's off-topic to once again point out that this way of phrasing it is very developer-centric. That's not a wrong way to look at it, but an end-user-centric way of looking at it is also valid. It seems to me that "developer" here refers to a very different kind of developer than me, which is probably because I mostly care about getting my mathematics done and (probably because of that) use only linux. I never had any severe build problems, although recently I have had some problems with TMPDIR. I therefore wonder whether the outcome of the dispute might affect me, and if so, how - other than socially, which would be probably the most important thing anyway. I am unable to answer the former question (i.e., would it affect me technically) by looking at the collection of links. As an example: the introduction of the `# needs something` comments did affect me, and I don't see the benefit yet, but it is only a very minor annoyance, so I certainly won't argue, assuming that at least somebody is convinced that it's a good thing. Best wishes, Martin On Thursday 11 January 2024 at 14:32:51 UTC+1 kcrisman wrote: > Many of these are disputed for the same underlying reasons. Appointing > a different editor for each PR is not likely to help. If you pick an > editor from Camp A, he or she will always rule in favor of Camp A; pick > an editor from Camp B... > > > The camps are roughly split across the question whether > Sage the distro should be deemphasized, and the development > process should be centered around sagelib, or not. > > As well, and it's not a coincidence, roughly the same partition > is on the basis of the developer platform used by the camp member. > It appears that the Linux users are primarily for deemphasizing > Sage the distro, and macOS user are primarily against. > > > As a general observation, this seems somewhat accurate. That said, as > Martin R points out, many (most?) people don't seem to be in a "Camp". > > > I suspect it's due to the latter used to Sage the distro as a "missing > macOS > package manager". > So they are happy adding more and more spkgs to Sage. > And Linux users rightly see adding to Sage spkgs, which > package software available on their systems in a regular way, > as a bloat, which moreover needs constant attention - > while sagelib suffers. > > I don't think that without solving this conflict the disputed PRs > dispute can be solved. > > I may go on discussing how the Sage macOS problems may be > mitigated, but not here and now. > > > > I don't think it's off-topic to once again point out that this way of > phrasing it is very developer-centric. That's not a wrong way to look at > it, but an end-user-centric way of looking at it is also valid. And these > are largely using Sage on Mac (without knowing about things like brew or > conda, nor really wanting to) or even Windows (where not even these options > exist, but people seem content to download whatever older version still is > available - and they do). Let's ignore the cloud solutions available for > now, since I still suspect that for "ordinary" solo uses this is not as > significant a factor (as opposed to collaborative ones). > > So somewhere on sage-devel (probably not this thread) it would be really > helpful for people *other* than the two or four primary "representatives" > of Camps A and B to explain the vision of Camps A and B regarding both > developers and end users. Because the developer time/bloat issue is real, > and the end user not being able to use Sage issue is real (on Windows, at > the very least, and it was nearly the case on Mac). > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/ca61d246-0d99-4912-8c15-518de90d254an%40googlegroups.com.
