That’s a little different, right? Using port 0 would imply that clients have not hard coded what port they should connect to and also we don’t mind having duplicate processes occupying other ports which are no longer on active use
This is amazing. Thanks for sharing. Did you ever look into capturing the states of where all the windows are once you are done with resizing them? So as to restore them later back into position if they ever get out of alignment ?
Thinking of the usecase where every task or a project deserves a certain arrangement of windows and it would be good to summon them into existence as and when needed?
> A good use of LLMs imho is trying to get a start point for lookup docs, like
I like this and resonate with it a lot. Sometimes you don’t know what you don’t know or you you just a little about what you might not know. This helps at least give you a name for the thing which you can then verify from source.
> Sometimes you don’t know what you don’t know or you you just a little about what you might not know.
If you find yourself in this situation, that usually means you've skipped something on the way. Kinda like wanting to contribute to ffmpeg's core with no understanding of audio codecs and containers. Or wanting to code web applications with no knowledge of HTTP and the TCP stack, sysadmin, the DOM API, what cascading in CSS means,...
Learning is one thing and being able to comprehend a piece of code at a glance is another. I might know them but wouldn’t immediately remember all the past and future short form of flags ever written. What is even the point of that? If I am comfortable with the essence of what they do, does it really matter that much if I have that ingrained in my memory that -r does foo while -f does bar?
Interesting. I didn’t know they did. Though can’t help but thinking that this is all going be a lot less valuable if your ovservability platform is on those mainstream cloud providers.