Typing when you need it gives you more freedom over a toggle. You can choose to type some parts of the code while leaving other parts untyped.
For example, if I’m writing a quick and simple Python script I may forgo typing, but when iterating on it I’d go back and add the types I need.
Python 3.x will never have static typing because that would break backwards compatibility.
However, typing hints have been Integrated into Python for a while, and you are heavily recommended to use them, so your IDE can enforce typing.
Better to have you here mate.
It’s so disappointing. India has a massive tech service industry and could’ve been a force for good, but the government loves their censorship and authoritarianism too much.
I use one of its forks called Insomnium which was forked right before compulsory login was added.
I would hold off on switching to AllDebrid for a bit, because they are also based in France and may be hit with a similar order.
Reading your comment and #32459, I realize that VSCode source control did have some major issues back then.
It looks like they have improved though, as the latest VSCode I use doesn’t auto-initialize repositories anymore.
It’s not that. It means discard all changes made after the last change committed to this local repository.
He wouldn’t have seen the “Discard Changes” button at all if source control wasn’t already setup (and detected by VSCode).
No sane program will delete files when you initialize source control either.
As I found later, VSCode did have weird behaviors with source control back then. My experience is more with the latest versions.
“Changes” encompass more than you think. Creating / Deleting files are also changes, not just edits to a file.
It can also be all of them at the same time, which is why VSCode uses “Changes” instead of “Files”.
What, your printer doesn’t have a full keyboard under its battery? You’ve gotta get with the times my man.
I’m curious, what if you move her bowl to the place where she drops it?
It’s a really awesome app! Thanks @[email protected] !
The core-js
story always makes me sad. Sure, he’s developing an open source project and no one HAS to pay him. But the meager amount of donations and the tons of hate he receives isn’t justifiable.
The problem I see here is that AI may write code that does compile, but has a bunch of logical errors, edge cases or bad architecture. From personal experience, even though AI can write small amounts of good code, it’s bad at understanding big and complex solutions.
At that point, fixing the AI codebase might take longer than just starting with a competent Rust dev.
It’s especially bad when it’s stuck like that for hours, and you have to make a gamble with a force restart.
Hello inject me with beans please
not again
God, they are literally baiting starving people using food and then hunting them.
Oof that’s quite a long-standing bug. Thanks for letting me know, I’ll follow it on GitHub.