It was hard to tell how he is doing and whether any of these treatments are working, but I sincerely hope for a good outcome for him. He has always seen like a genuinely good person. Cancer sucks.
I am nearing the end, depending on the refinements. The first two weeks I was regretting it, but adjusted quickly. Honestly for me the issue was more that I did not like the way my teeth feel with the trays out (and the rough field of the aligners on the teeth). The eating was not that big of a deal. I have a travel toothbrush and case I keep with me. It has been pretty easy.
Still looking forward to getting the stuff off my teeth.
Probably referring to me? I live 2 hours from the closest airport. There are no trains near me. Barely any buses. And I am not counting trains within a city just taking a train to travel between cities.
I do not live that far from an Amtrak station but there is only one train a day, it takes forever, and does not go anywhere that I am typically traveling.
My daughter recently moved to Vancouver. I was in Seattle for a work trip so decided to take Amtrak to visit her for the weekend. This was my first real train travel. Overall, it was pretty good and probably is what I will do in the future in the same situation.
The train moved at a frustratingly slow speed (< 10 mph) for probably 30% of the trip, but aside from that I liked the more relaxed atmosphere of the travel and it was overall more comfortable.
The train itself was a bit bumpier than I expected and the wifi was not very good. Those things and the slow speed would mean I could not imagine taking a much longer trip than this one. With the extra time and hassle of dealing with an airport, this one balanced out as probably only being slightly slower travel but it was less expensive and more relaxed. If it were Seattle to San Francisco, as an example, the slowness would be too much for me. The comfort and amenities like wifi and food would have to be a lot better than they are.
This is shocking and confusing. In the US if you watch HGTV and Mike Holmes, who works in Canada, all they do is talk about how great spray foam is and that is the gold standard. To the point I have had major FOMO for years because I do not have it.
Reading this article and the comments here ... I do not want to think, other than being glad it was too expensive to consider.
The market GitHub created was Social Coding and the idea that there were network effects to be gained by having all OSS in one place. This is the same thing that makes it difficult today for OSS projects to move off GitHub. If anything, GitHub deemphasized the "D" in DVCS.
My point, since you replied to my post, was simply that prior to GitHub, none of the other sites for OSS were trying to achieve the same goal. The goal was to establish a specific OSS community for a set of projects. SourceForge was a bit of an outlier in that a lot of projects used their distribution network, if they were not part of a foundation like Apache or Eclipse that had extensive mirrors setup.
SourceForge was never the main development and collaboration site for any of the major efforts happening around OSS.
Something this misses is that the mentality of OSS was just different before GitHub.
The thought from the original growth of OSS was that it would be more about the community than the code. So OSS would be a series of communities that would each have their own "identity" for their community. There were big OSS foundations like Apache and Eclipse. Sun had several like java.net, OpenOffice.org and netbeans.org. Gnome had their own place etc.
Like Sun, other enterprises like HP, Oracle and IBM were setting up their own communities for their projects and to collaborate with partners.
And then as the post touches on there were sites like SourceForge, Tigris.org, Google Code and Microsoft had something too (CodePlex?). These sites were places projects might spin up if they did not belong at one of the other foundations and wanted a place to host their code for free. Of these SourceForge was often used for distribution of binaries due to its vast mirror network and often that was all that was hosted there and the project was elsewhere.
Anyway, until GitHub sprang up and started to consolidate all the OSS in one place, I do not think anyone else was even really trying to do this. Obviously the rise of git played a big role in this. This change fueled the growth of OSS but it did kind of come at the cost of losing out on some of the community aspects that existed before in the mailing lists and forums of these other places. Now collaboration all happens in PR's and Issue and is often just between a small handful of people.
This is also my issue with pi-hole, I still use it but I lost the password. Every now and then I take a crack at getting back in so I can update it. I have been thinking of switching to NextDNS so I could have blocking everywhere.
Other than this problem, Pi-Hole has always been great
I wonder if the system on a chip design of Apple Silicon would work for servers. Would it just be a special packaging that crammed several Mac mini boards into a rack mounted chassis? If so, then they would just be repeating what others are already doing.
The RAM being part of the chip seems like a limiter to scaling up to a server model with a lot of cores and RAM in a single blade.
Not saying this is not all doable just that it probably requires design and investment they otherwise do not have any desire to do.
Well said, this is what I was getting at as well. I think the barrier to contribution was too high in the old days, and that is where GitHub brought improvements, but it came with the loss of community. Everything becomes about PR's and Issues and Discussion was just lost. In the Apache community, the expectation used to be that everything had to happen on the mailing list. Even if someone created an issue, there was an expectation it had to come out of a mailing list thread.
I am not saying this was perfect or even better. Just that the side effects were different. Probably a lot of people did not bother contributing because the barrier was too high, but overall I think it created healthier community dynamics and it was not uncommon to see people begin as users asking questions, and evolve into users answering questions and eventually contributing to the development.
Following up on my previous comment, I managed to never become fully burned out, but it required changes to myself, not the project. I had to become less emotionally invested in the project, realize I could not solve everything and step back a bit and do some other things. I guess it would be great if the project were reinforcing these ideas to its contributors to prevent burnout, but that also does not seem realistic. And "the project" is made up of others going through the same problems.
The large OSS project I contributed to thankfully had other contributors that were good role models for these behaviors and it helped seeing them disengage to do other things for a while.
It is a fair point, but I think your last sentence hits on the problem. People that contribute regularly to OSS projects are nearly always emotionally invested. It brings a lot of pleasure initially which I think also contributes to the eventual burnout.
This is a good description of what life is like working on almost any significant open source project. The only thing not included was the comments from overly entitled users that saps whatever morale and energy you have left. Probably best he did not include that though as that is what all discussion would be about.
I am not sure what to do about the burnout problem. The way he described it is very on point though. Since everyone working on the project is overloaded there is a great feeling of things only get done if you do them.
Most of my open source work was in the pre-GitHub days when we used mailing lists, not pull requests, to build community. I do think there was something better about that for the project itself as it encouraged a lot more discussion and community building. PR's and Issues become silos and are not great for general discussion. I think they also encourage drive-by contributions which honestly are intoxicating initially but once you see people are not coming back become defeating.