Web Developer by day, and aspiring Swift developer at night.
I found this site which might help you in your search.
Food for thought (no pun intended), but unless you’re willing to build an app (could be a great app; I doubt you’re the only person who could use this), you might be over engineering this quite a bit. A spreadsheet could be made to do what you’re looking for, with much less effort.
Well for one, it encrypts all communications so that people can’t snoop on what you’re doing.
Ssh! 🫢 You’ll ruin the joke!
Hm. Might not be standup that’s the problem. Might be a company culture thing. But only you know that for sure. Good luck op! Disassociation can be a life saver.
The problem is that they both are contextual and can mean any position in a list/array. The starting index or starting offset is generally zero, but could be one, depending on the language used.
Amen. Now, where’s that Wine?
FWIW, I’m referring to the local DNS (domain name system) resolver; the mechanism that resolves local domain names into IP addresses so that computers can talk to each other over the LAN.
Here is a good primer on the configuration files and their possible locations: https://www.freedesktop.org/software/systemd/man/latest/resolved.conf.html
Edit: be careful because this is your domain name lookup you’re messing with. 😊
What I suggest is not the same as using git rebase. It’s pretty automatic and easily abortable.
In my experience, this amount of conflicts typically occurs because 1) most people mass commit a bunch of (mostly unrelated) changes at once, which leads to 2) inexperienced/impatient devs to clobber incoming merge conflicts without doing proper merges (mostly because they can’t make heads or tails of the diffs).
This is very easily mitigated if all developers would make small, related commits (with descriptive commit messages and not “committing changes”). This makes everybody’s life easier because 1) diffs are smaller and readable for conflicts, 2) the dev can see the progression of code through commit history, 3) broken code is more easily revertable (and traceable) if something goes wrong, and 4) it’s easier to cherry pick specific changes if the whole changes cannot be published all at once.
Also, git pull --rebase is your friend and not scary at all. It applies all incoming changes first, then applies your new commits last. 9 out of 10 times it avoids conflicts.
Lastly, use a GUI. There are plenty out there to suit your tastes, and I feel they are a safer and easier alternative than CLI. Some GUIs are very safe and even allow undo operations on most things.
I know this is a joke, but those errors/warnings/messages screenshot is not from git. That looks more like results from a compiler of some sort.
Sometimes it takes a little unintentional embarrassment to drive a point home. It’ll make them think twice next time.
What I mean by that is that as long as you’re not intentionally or maliciously trying to embarrass them, then you shouldn’t feel bad. You cannot always control how somebody receives information; nor should you. The best you can do is to be clear and polite in your communication. If someone’s feelings get hurt, that’s on them to reconcile, not you.
This is genuinely like parenting a child: they need to develop their critical thinking skills, and to gain their own confidence. So they must be left to make their own mistakes to learn from. Your job is to give show them the tools to use, give advice when necessary, and be there to catch them when they fall; because they will fall.
Doing this will help bolster their self-confidence and make them better mid-/senior-developers later in their career. Coddling them and constantly holding their hand will make them reliant on other people and prevent them from learning anything.
Edit: also remember KISS. 😊
It’s all good. If you’re using bash and readline to read the file, you can use sudo echo ${INPUT@Q} (assuming your variable is named $INPUT) to have bash escape things like the quotes and other characters that could get you into trouble.
sudo echo "# FYI quotes(") must be escaped with \ like \"
👆 that is not a comment. That is a command that says to echo the text “# FYI quotes(” and then to do ) must be escaped like \ \" which is invalid syntax.
I assume that startup script is reading the contents of the file and trying to echo them into another file? i.e., using the original file as a template, but is not escaping the input, hence the error — which you’re lucky that’s the problem you’re encountering and not something actually destructive like sudo echo "# foo" && rm -rf /*.
Banning members on their username. Locking down an entire community because of a small group of people spamming. Deleting posts because an account isn’t old enough?
Why not throw in the system to have to approve posts before they get published? Really make the community welcoming.
It was said in another comment above that this tool is easily abused by “overzealous mods”, but I believe the real problem are overzealous programmers.
Reddit failed for reasons, and I believe automod was one of them. But you’ll do you, and nothing I say can change that.
Though I’ll probably keep the feature to punish members by their usernames via regex or word blacklist.
This right here is the attitude that I have a problem with. I can think of one user who would get blacklisted right away because of their username alone. And that does not sit right with me.
I beg of you, please don’t. The worst thing to happen to Reddit was their Automod. Please reconsider.
Java/TypeScript
😒
Ladybird Browser Team Selects Swift as Preferred Language Andreas Kling announces Swift as Ladybird’s future language for better safety and ergonomics. Full transition awaits Swift 6.
ByBobby BorisovAugust 11, 2024 Ladybird Browser Team Selects Swift as Preferred Language Ladybird is a new name in the Linux ecosystem you might not be familiar with. So, let’s briefly explain what it’s all about.
It’s a web browser initiative, funded by $1 million, spearheaded by GitHub co-founder and former CEO Chris Wanstrath and tech visionary Andreas Kling. It seeks to challenge the status quo with a new browser written from scratch, completely independent of corporate interests. Our article on the subject has more on this. Now, back to the topic.
Over the past few months, Ladybird’s developers have been experimenting by rewriting different parts of the browser project in various languages. The outcome was clear: Swift emerged as the preferred choice among the team. According to Kling, the feedback favored Swift for its modern features and robust safety protocols.
Another significant advantage of Swift is its ongoing improvements in interoperability with C++. This development means Ladybird can adopt Swift gradually, without extensive rewrites, easing the transition and reducing potential integration issues.
Now, I’m sure you associate Swift with app development for Apple devices, where it’s been the go-to technology. But recently, that’s started to change.
What I mean is despite its strong associations with Apple, Swift has been making strides towards independence. It has been reorganized under a separate GitHub organization, distancing itself from Apple-specific projects.
This shift, coupled with better support for non-Apple platforms and diverse development environments, positions Swift as a more versatile and broadly applicable programming language.
Looking ahead, Ladybird plans to implement Swift once version 6 exits beta this fall. The upcoming release promises compatibility with the latest versions of Clang, essential for integrating Swift with Ladybird’s existing C++ code.
It’s worth noting that no browser engine has yet been developed using Swift, making this project particularly challenging. As things are still in the early planning stages, we shouldn’t expect to see any initial versions of the Ladybird browser this year.
A more realistic timeline suggests an early preview release could happen in 2025, though the developers have not yet committed to specific dates.
For more information, refer to Kling’s post on X.
Bobby Borisov Bobby Borisov
Bobby, an editor-in-chief at Linuxiac, is a Linux professional with over 20 years of experience. With a strong focus on Linux and open-source software, he has worked as a Senior Linux System Administrator, Software Developer, and DevOps Engineer for small and large multinational companies.
👆 This. In my experience, I’ve seen a lot of developers get upset about “their code” not being used, time wasted, or someone else changing the code after the fact. Who cares? Once you commit that code, it’s no longer your code. It’s the company’s code. Your paycheck will reflect the same amount of money regardless — and if it doesn’t, you may want to find a better employer. 😅