I’m always a bit irritated by that definite statement that companies don’t care.
The company I work for is small, ~30 people, and my boss/employer as a person cares about me. A lot as a worker/employee, maybe less so but also as a person/individual.
Yes, the company as a theoretical construct does not care for or about me. It’s a construct. But that ignores the people in it, and the variance between companies (even if it’s only a minority where leadership personally cares).
This is why older people think slower and lose memories or cognitive functions as side effects. They are depriorizized and moved from ram to pagefiles/swap disk.
If you’re unfamiliar, the OS will move process memory onto disk when RAM runs out.
None. I don’t think clones could satisfy my wishes. And I wouldn’t want to burden them with a life.
Regarding visual client: I’ve been using TortoiseGit since early on and no other client I’ve tried came close.
I use the log view and have an overview, and an entry point to all common operations I need. Other tools often fail on good overview, blaming through earlier revisions, filterable views of commits or files, or interactive rebase.
I’ve never found pressing modifier keys to be an issue. I’ll be mindful of my use today.
I guess the hold to repeat input (of letters) is not used much, so not a significant or noticeable loss when replaced. I’d certainly see false positives and having to type slower as deal breakers.
Note: Not stable/suggested yet.
F-Droid emphasizes that it wants to ensure that the experience with it is as stable as possible, so version 1.19 isn’t marked as the suggested version yet
Why would you title it a “trick”? Inappropriate term.
now supports the unattended updates API introduced in Android 12
Hardly a trick if you use a standard API.
If you’re looking for collaboration or audience I’d stay with github. It’s too prevalent to skip for alternative niche with account signup and that elsewhere as a barrier.
If that’s no concern to you it’s viable.
Do you mean !anime@ani.social?
Linking works fine. Whether it is defederated depends on your Lemmy instance.
(According to the sidebar user stats this community doesn’t have much less activity than that one either way. So dunno about “all action”!?)
One
it’s not yet the suggested version. Meaning that brave users need to install this manually for now
not production-/stable-live yet
You copied that function without understanding why it does what it does, and as a result your code IS GARBAGE.
AGAIN.
[…]
Debate continued for some time, in a cooler tone, with Torvalds offering suggestions on what he felt would be a better approach to the issues Rostedt hoped to address.
Harsh tone (in only two instances?), but he still invested in offering suggestions 🤷
I expected more behind the verb “flaming”.
Alternatives
Lemmy save, and browser bookmarks
The Ice Guy and His Cool Female Colleague
The eye movement animation in it is unique and an exceptional stylistic, visual choice.
Overall charming, heartwarming, good.
“Like any secret, SAS tokens need to be created and handled appropriately,” said the MSRC team. “As always, we highly encourage customers to follow our best practices when using SAS tokens to minimise the risk of unintended access or abuse.
lol - follow our best practices - ironic. Of course documented best practices don’t mean everyone follows them, even internally, but that statement still makes for humorous irony. Ambiguous, almost implies, “follow how we did it here” in my reading.
Among other things, their access levels can be easily and readily customised by the user, as can the expiry time, which could in theory allow a token to be created that never expired (the compromised one was in fact valid through to 2051, 28 years from now).
[…] it’s not easy to revoke the token either […]
Reading this, the drive to managed cloud and centralization feels like an effort to replace memory management issues as the top vulnerability cause. We - as an industry - are more aware of those as ever, and have interesting efforts like Rust adoption. And at the same time, hierarchical access tokens you can’t easily revoke, with arbitrary configured lifetimes and access, that are hard to monitor, track, and trace (from reading this article) are introduced as an entirely new set of risk and attack surface.
Of course - cutting scope is a good call to keep it manageable and fun, and not end up with creep and what you wanted to evade in the first place. :)
Index categories are blog, docs, magazines. Have you considered indexing source code websites?
I thought I would remember a second one, but I can’t recall right now.
Subpaths on GitHub and GitLab would be a similar fashion but would require more specific filters - unless they are projects hosted on dedicated instances.
Project issue tickets may also be very relevant to developer searches!?
The title question is very broad, varied, and difficult. It depends.
For anything that is not a small script or small, obvious and obviously scoped takes, you can’t assess at first glance.
So for a project/task/extension like you wrote it’s a matter of:
Is there docs or guide specifically for what I want to do/add? If yes, the expectation is it is viable and reasonably doable with low risk.
If there is no guide the assessment is already an exploration and analysis. How is the project structured, is there docs for it or my concerns, where do I expect it as to go and what does it have to touch, what’s the risks of issues and unknown difficulties and efforts. The next step would already be prototyping, and then implementing. Both of which can be started with a “let’s see” and timebox approach where you remain mindful of when known or invested effort or risk increases and you can stop or rethink.