TCP is the way that you send information, HTTP is what it means.

The difference, in your case, is the port. You can’t CAN have TCP and UDP on the same port, but you can’t have the same protocol on the same port.

edit: I didn’t knew you could have different transfer protocols on the same port, ty!

Oh, I already hated windows, that was just the last straw

The pandemic and programming.

I was watching some tutorials and saw how easily people used the terminal, and how clunky cmd felt.

Next day I had ubuntu running.

While it’s true that’s a progess bar is guessing (since it doesn’t know what would take more time in your computer). It should still finish when at 100%

You can just alias to do this in the programs you do use

Sure, the first time you won’t have this enabled, but after that it just works.

Even if they do have the same in-memory representation, you may want to assert types as different just by name.

AccountID: u64

TransactionID: u64

have the same in-memory representation, but are not interchangeable.

the vim-visual-multi plugin tries to do this. It takes some time to get the hang of it, but, even if using only the simplest features, it’s way better than not having the option.

Eu não sou seu parça, camarada

“src/utils/typing: added tests for isArray”

we have 90% coverage minimum

The point, I think, is not about fetching the page, but how to navigate it.

I adore using man pages with vim and i would rather have that than a web browser

I don’t know how luxon works, but isWeekend could be a property instead of a function

Im pretty sure tsoding has some videos with it

yeah I just thought it was kinda funny

the house was stuck

I’ll take this as a complement mano

https://doc.rust-lang.org/cargo/reference/manifest.html

it’s the sixth from the bottom in the table of contents

You can setup a cargo configuration file, in it you put a manifest and define some profiles, and in them define what features you want compiled

Yeah!

it’s basically a noop, I use it as a placeholder when I’m writing a script, since bash doesn’t accept code blocks with no commands

or :>>file then you don’t need to interrupt

I would agree if OP was trying to get a job as a developer, however I don’t think they are.

It’s more like you used a beaker for something and shook it to mix water and salt, it’s not the recommended way, but it’s fine.