InarticulateQuilterPixWHEN RIVALRIES WERE REAL
2015
Square in a Square/Applique
70” x 70”
#Quilt #InarticulateQuilter #Big8 #NCAA #KansasUniversity
2015
Square in a Square/Applique
70” x 70”
#Quilt #InarticulateQuilter #Big8 #NCAA #KansasUniversity
Packet-lost soulHello #hackers #tinkerers #explorers #minimalist #oldschoolers etc there are now #usenet talks about a new newsgroup for the #rust #rustlang programming language, you can participate in the #big-8 #big8 decision making in the #newsgroup news.groups.proposals the thread is under comp.lang.rust the big-8 approved an official #go lang newsgroup last year or so, among all the old newsgroups cleaning and spam blocking this is another sympton of the revamping of usenet 2.0 https://news.novabbs.org/usenet/article-flat.php?id=393&group=news.groups.proposals#393
Mima-samaI have to say, I am not a big fan of how this #USENET RFD was conducted. As I'm writing this I have not seen any proof of the #Go language or #Golang projects being discussed in a newsgroup. It's either "I'm gonna read this newsgroup" or "I'm gonna post!" in the messages supporting this proponent in that RFD. I especially hate those who are writing the latter because I have not seen them post a Go article during the RFD. It's your chance to show that Golang deserves its own newsgroup, why do you have to screw it?!!! :parsee_angy:
ahk in news.groups was right; in order for the creation of the newsgroup to be considered you should show that the topic is actually being talked about regularly on Usenet to warrant its own newsgroup. Others might even want you to show how the current existing newsgroups the topic is being discussed on is insufficient or causing conflicts with those newsgroups. But proof of the topic being regularly discussed in the first place is the BARE MINIMUM.
I have not seen a single article about Golang in comp.lang.misc where the RFD was distributed. Nothing before the RFD was distributed, nothing during the RFD, and it will probably be nothing in both comp.lang.misc and the new comp.lang.go after the RFD is passed because the proponent couldn't be assed to actually talk about Go in Usenet without a dedicated newsgroup.
comp.lang.go turns out to be a failure? Too bad! Perhaps c.l.m is truly where it belongs for now.
If #Big8 creates this comp.lang.go newsgroup, it's going to be yet another spit on decades of Usenet culture. But hey, I guess we have to appeal to the cool kids now how grew up on #Reddit and not on #netnews.
RE: https://hispagatos.space/users/rek2/statuses/111103760273306805
ahk in news.groups was right; in order for the creation of the newsgroup to be considered you should show that the topic is actually being talked about regularly on Usenet to warrant its own newsgroup. Others might even want you to show how the current existing newsgroups the topic is being discussed on is insufficient or causing conflicts with those newsgroups. But proof of the topic being regularly discussed in the first place is the BARE MINIMUM.
I have not seen a single article about Golang in comp.lang.misc where the RFD was distributed. Nothing before the RFD was distributed, nothing during the RFD, and it will probably be nothing in both comp.lang.misc and the new comp.lang.go after the RFD is passed because the proponent couldn't be assed to actually talk about Go in Usenet without a dedicated newsgroup.
comp.lang.go turns out to be a failure? Too bad! Perhaps c.l.m is truly where it belongs for now.
If #Big8 creates this comp.lang.go newsgroup, it's going to be yet another spit on decades of Usenet culture. But hey, I guess we have to appeal to the cool kids now how grew up on #Reddit and not on #netnews.
RE: https://hispagatos.space/users/rek2/statuses/111103760273306805
Got Root :hispagatos: # :idle: (@[email protected])
#usenet the new #comp.lang.go #newsgroup for the #go or #golang language was submitted to the big-8 a couple of days a go for a last review and voting, this here is the original first proposal https://www.big-8.org/wiki/Nan:2023-07-04-rfd-comp.lang.go, but now we have moved forward, after these we are aiming to add #comp.lang.rust I code on both of them, and like them both for different aspects. So I am glad we're working on this the #comp.lang.c is a vibrant and super active community, so will be happy to have the other two.