It's hard to move browsers permanently if you're not prepared. I moved to FF Quantom for a bit, but had to regularly open Chrome to get passwords etc. And the Chrome assholes removed the password export (or at least I…
Everyone that is fully against killing insects has likely never lived anywhere that has insects.
And thus, a new law was born.
You do realise that storing them (be it Google, LastPass, or any other hopefully trusty manager) is safer than carrying them around on you, right?
Have been using Ecosia and I have to do a `g` search pretty much daily. Though the use Bing underneath, so maybe it's worth giving DuckDuckGo a try
I've been using both VSCode and JetBrains IDEs with their VIM plugins. The VSCode one is kind of shitty, but overall both do the job well enough that as a not-super-proficient-vim-master-guru I don't really lack any…
> within couple of decades We already do.
And it doesn't really need to. Consider this: from functools import singledispatch from typing import Union @singledispatch def myfunc(arg:Union[int, str]): print("Called with something else") @myfunc.register def…
My bad - I meant this but didn't know how to format code so that is showed the stars def func(*args, **kwargs) I am in full support of actual kwargs with names, it's the wildcard ones that I don't like.
I fully agree that named kwargs is perfectly acceptable, but this is the version I think is horrible: def func(*args, **kwargs) is valid and completely ambiguous - you have no idea what it's doing unless you read the…
On one hand - I agree, overloading isn't great. On the other hand having a `def func(args, kwargs)` is a pain the ass for everyone involved (people & IDEs): you have no idea what the args or kwargs could be without…
Is this any different than the debugger visualisations that other editors/IDEs have? Genuinely curious, because if I'm understanding this correctly, it's just another front-end like what…
I mean sure that's better, but now Apple is tracking you instead and you got ripped off $340 for it
It's a PDF.
> I would suggest that this is change, not a norm in the last few decades. I am not so sure that we changed so rapidly. It would also make sense that this is not new, and it has just become more apparent in the last few…
It's all about learning more things, which in turn expands what you could possibly think - the human mind's ideas are limited to what it already knows or has experienced. Learning new things expands that, allowing you…
It's hard to move browsers permanently if you're not prepared. I moved to FF Quantom for a bit, but had to regularly open Chrome to get passwords etc. And the Chrome assholes removed the password export (or at least I…
Everyone that is fully against killing insects has likely never lived anywhere that has insects.
And thus, a new law was born.
You do realise that storing them (be it Google, LastPass, or any other hopefully trusty manager) is safer than carrying them around on you, right?
Have been using Ecosia and I have to do a `g` search pretty much daily. Though the use Bing underneath, so maybe it's worth giving DuckDuckGo a try
I've been using both VSCode and JetBrains IDEs with their VIM plugins. The VSCode one is kind of shitty, but overall both do the job well enough that as a not-super-proficient-vim-master-guru I don't really lack any…
> within couple of decades We already do.
And it doesn't really need to. Consider this: from functools import singledispatch from typing import Union @singledispatch def myfunc(arg:Union[int, str]): print("Called with something else") @myfunc.register def…
My bad - I meant this but didn't know how to format code so that is showed the stars def func(*args, **kwargs) I am in full support of actual kwargs with names, it's the wildcard ones that I don't like.
I fully agree that named kwargs is perfectly acceptable, but this is the version I think is horrible: def func(*args, **kwargs) is valid and completely ambiguous - you have no idea what it's doing unless you read the…
On one hand - I agree, overloading isn't great. On the other hand having a `def func(args, kwargs)` is a pain the ass for everyone involved (people & IDEs): you have no idea what the args or kwargs could be without…
Is this any different than the debugger visualisations that other editors/IDEs have? Genuinely curious, because if I'm understanding this correctly, it's just another front-end like what…
I mean sure that's better, but now Apple is tracking you instead and you got ripped off $340 for it
It's a PDF.
> I would suggest that this is change, not a norm in the last few decades. I am not so sure that we changed so rapidly. It would also make sense that this is not new, and it has just become more apparent in the last few…
It's all about learning more things, which in turn expands what you could possibly think - the human mind's ideas are limited to what it already knows or has experienced. Learning new things expands that, allowing you…