@dansup@loops Does it page from one loop to the next using standard keyboard buttons (page up/down, space) and mouse/touch gestures? If so, that'd make me happy.
Please don't replace #GUI widgets with images. This is supposed to be a sliding on and off switch. An image replaces the check box. But if that image doesn't load, the result becomes #unusable
@Gargron Please avoid devolving into Microsoft Outlook, which won’t even let us copy a user’s email address anymore without opening yet another dialog screen that also refuses to let us copy the shown email address unless we specifically press the copy button. They created 3 actions and a wait time for what could have been as simple as ctrl-c.
@youronlyone Hello! Do you perchance speak native Pinoy? I'm looking for names of weekdays. Does Pinoy culture count time in weekdays like Israelites and Europeans do? If so, how do they name their weekdays? Are they named after deities, planets, a numbering system, or something else?
There are so many single-threaded GUI applications programmed in many a language that prevent interaction while some heavy data analysis is happening that I really don't care whether or not #python 's #GIL causes that for Python programs. Too many software developers out there who don't use asynchronous execution.
@feld That server may or may not be hosted by #cloudflare ... And we can't tell how much of the GOAWAY is signaled by them or by the destination server.
@feld I will take your word for that. But we experience GOAWAY signals after 1000 requests, and we are not the only one, according to StackOverflow.com. We didn't implement the server, so we can't vouch for how or why it does anything.
#NGINX and other #HTTP servers will throw a fit if a client sends 1000 requests, and literally tell the client to go away. In the #java programming language, the #HttpClient built into the #jdk throws an IOException, without any further specialization. The #Jetty client for HTTP/2 does throw a specific error and also indicates the lost frame ID, for easy resumes. I guess we could switch clients, or I could find a nice way to catch this error and resume communications. Any suggestions?
Today I was reminded that HTTP/2 servers can deny communication quite unceremoniously by sending back a #GOAWAY signal. What do you do to resume communication? Simply retry the request? Or also refresh the #HTTP client that makes the requests?
Hi, this is Andre. I'll be writing about software architecture and development, cyber security, UX/UI topics, politics, and queer experiences. I'm a classically trained musician and music composer, band director, and music instructor. I'm handfasted, have kids, and play and create (video) games. Sometimes I don't recognize social cues.