I’m the administrator of kbin.life, a general purpose/tech orientated kbin instance.
Yes, especially when you’re running linux, and the project you started on windows that uses serial ports suddenly doesn’t work any more and you wonder why.
Hint: The events for serial data received didn’t fire under mono, for reasons.
I use perl for that stuff (mostly automation) that’s a bit too complex for bash, but doesn’t need a proper project. Modern people would use python for this kind of thing. But, I’m too old to change!
And someone would pick up the phone 30seconds from the end, and there was no resume!
OK, but there’s need to be some automatic beeping over my \ comments.
try
{
doStuff();
}
catch { }
Bug fixed.
Until they redirect twitter.com to x.com and not the other way, and actually change twitter on the site, it’s still twitter but with a new logo.
I suspect eventually he’ll do that though.
I never quite understood the point of twitter though, so never had an account. I dare say there’s less chance I’ll get one now.
Yeah, this is a known interoperability thing between kbin and lemmy. So, I’m afraid I can’t give you this week’s lottery numbers ahead of time.
Nah, it was TCP. But there was a pixel out and didn’t pass checksum. This is the retransmission.
No. Both UDP and TCP can be intercepted the same. The difference is that UDP sends a packet to an address. But doesn’t have any in built system to check that it arrived, that it arrived intact or to resend if it didn’t. There’s also no built in way to protect against spoofing or out of order packet delivery. But generally implementations will handle the ones that are important of those themselves.
TCP establishes a circuit, packets are sent, verified and resent if required until the original data, in the correct order is delivered to the application. Also there is some protection against spoofing with sequence numbering. The downside is that time sensitive data might be delayed because of the retransmission and re-assembling. Which is why time sensitive streams like VoIP are usually sent over UDP.
A lot of the things I’m using are generally hangovers from those low bandwidth days. I’ve opened a file and I know what I want is a way down? Not a problem 10-Page down to move 10 pages down the file without sending all that to the terminal.
What to cut the next 5 lines into the buffer? 5dd. Move to the line you want to paste to. Want to remove the next 5 characters? 5x. Often on a slow link moving your cursor along had a delay. But if you knew how far you needed to go you could do 30+arrow right to get the cursor to move directly there.
I think most are obsolete now, but I’m still used to using them out of habit mostly.
Well it is. But back on unix proper it was just called vi, not vim (aliased to vi)
Don’t discount the possibility that some people that use vim, are old enough to remember using vi, over a modem connection. When you know the keyboard shortcuts it can be a lot quicker too even now.
Same as every other technological innovation though. Productivity goes up. Revenue goes up. Pay goes… No wait, I must have got something wrong here.
To be fair, documentation is very often a much longer route to understanding your specific use case. At the same time, SO is responsible for far too much cargo cult programming and I fear ChatGPT will be the same for this.
How ironic, killed by the very thing that created it.
Hah. I remember working with accounting software in the early 90s. Legacy stuff even then. Programs and data needed to fit in 64k.
Need to make a simple customisation? Well now you need to split one program into two. Have fun.
There needs to be a space blocked by a pillar with “409”
Meanwhile, in the background the compiler optimizes them all to the same result anyway. :P
Back in the early 2000’s I had the windows error sound play Neo saying “Oh shit!” from the Matrix. After a while, it just got annoying though.
Hold the power button for 10 seconds!