![](https://programming.dev/pictrs/image/c7e74aaf-fd1c-480f-a98e-da2a7a7e55e4.jpeg)
![](https://lemmy.ml/pictrs/image/c0ed0a36-2496-4b4d-ac77-7d2fd7f2b5b7.png)
Lisp variants like Clojure are being used for new projects (e.g. Logseq) but I’d be surprised to hear of anyone choosing COBOL for a greenfield project.
New account since lemmyrs.org went down, other @Deebster
s are available.
Lisp variants like Clojure are being used for new projects (e.g. Logseq) but I’d be surprised to hear of anyone choosing COBOL for a greenfield project.
CNLabelContactRelationYoungerCousinMothersSiblingsSonOrFathersSistersSon
The label for the contact’s mother’s sibling’s younger son or father’s sister’s younger son.
I thought it was just a male cousin, but it doesn’t include a cousin who’s your uncle’s son. Which culture needs this?
So you think it’s too unreasonable for you to cope with?
I think all of the communities would rather have something more than just a bare link. I’m not sure why you’re responding with such indignation, to be honest, it was a perfectly reasonable suggestion, politely made.
I went with Fedora on my VPS because I was also planning to use rootless Podman. Quadlets and running everything through systemd with SELinux enabled is working pretty well for me.
The author has no idea how to get his audience on-side! He starts with bragging about his 6400% profit margin on domain he resold, in a market where there’s no customer value for middlemen.
At least antique dealers will identify pieces as rare, clean/restore them and put them for sale in a more visible place. Whereas domain reselling is about as ethical as ticket touting.
That was given in the original question along with Pythonistas.
haha, ok thanks. So https://github.com/dtrx-py/dtrx
I’d initially assumed that it was a mnemonic but yes, listing and appending and extracting together is nonsensical, as tar notes: tar: You may not specify more than one '-Acdtrux', '--delete' or '--test-label' option
I didn’t know about -d
.
I can remember regex, but I need to check tar almost every time.
I see your point, but you likely also need to be compiling multiple versions for different architectures and OSes. If you offer an exe someone will turn up asking for a msi, etc, etc.
In theory, you can get this automated, but then you’re requiring a dev to learn and maintain these tools instead of working on their project.
I do edit and spell check my posts because I believe that when posting something (text, software, etc) it’s proper to make it easy to consume, without forcing dozens/hundreds/thousands of people to fix your errors. I would expect these things, but I don’t demand these things, and I think it’s inexcusably entitled for anyone to do so.
What I’m hearing is you’d rather that the developer used their time to produce binaries so you don’t need to spend your own time.
The problem with open source is that people expect a lot time and effort to go into things like bug fixes, documentation and support, when often the devs start out making something to scratch a personal itch. They then share it for the benefit of others, and it can be a slippery slope where you can end up with a second job, except you don’t get paid or even thanked.
Open source burnout is a big problem.
Longer means you’re more likely to be able to ride out a power cut, and gives you more options if you want/need to complete something more involved than saving and shutting down.
A general tip on buying UPSes: look for second hand ones - people often don’t realise you can just replace the battery in them (or can’t be bothered) so you can get fancier/larger ones very cheap.
That reminds me of Netflix’s Chaos Monkey (basically in office hours this tool will randomly kill stuff).
Interesting article, thanks, although I don’t know what the page is doing to make Firefox offer to kill it. Maybe it’s something to do with the 1455 comments.
If you look at the URL, it’s meant to be announcing 0.90.0 - I guess they noticed a problem just after it was posted and added a patch.
Edit: yup, they added #11786
IPs and access logs, plus email addresses aren’t public and are the kind of thing law enforcement wants.
Huh, there’s a lot of us calling software “beasts” in this thread.
Here’s the post they made on Reddit:
Hi everyone. I wanted to post a quick update on the plans that are progressing around the Bitwarden mobile app. For those of you that don’t know, our current mobile app is created using a technology called Xamarin, a framework provided by Microsoft that allows you to create a single app that works on both iOS and Android. I chose Xamarin in the early days of Bitwarden because it was a technology that I was proficient at (.NET and C#) and it afforded me the time to maintain a mobile app along with all the other apps I was building for Bitwarden. Xamarin is a real time saver, for sure and it has served us well over the past 8 years, but it comes with some downsides as well:
Because of some of these things, and because we have matured as an engineering organization here at Bitwarden, Xamarin doesn’t make sense for us to pursue any longer.
Early last year we began planning to retire our Xamarin-based mobile apps and made the decision to transition our mobile apps to fully native apps written in Swift (for iOS) and Kotlin (for Android). Over the past 6 months we have been actively developing these new native apps and at this time they are nearing completion. I wanted to share some sneak peeks of these new apps and rollout plans over the coming months with you all.
The upgrade to MAUI
In an effort to support passkeys sooner than later, we’ve had a parallel effort going on with adding passkey support in the existing Xamarin-based mobile app. This required us to “upgrade” the Xamarin app to the new MAUI framework. As anticipated, the upgrade has not been smooth, however, we are nearing the completion of that project and plan to release this temporary solution soon. Although this is largely a new app under the hood, overall, the new MAUI shouldn’t look or feel any different than the Xamarin app that we have today.
Demo video: https://www.youtube.com/watch?v=-rVQOESKbbA
Native app release
In a few months you will begin to see our completely revamped native mobile apps roll out. These new apps will look and feel different. They are completely new Bitwarden apps. Hopefully you will notice large improvements to the overall experience of using the mobile apps. The designs are different, using all native platform controls, but the layouts still follow similar user flows that we already have.
iOS
Android
Design iteration
Now that we have new native apps to build upon, following their initial release we also plan to begin introducing other UX improvements and redesign how you interact with certain flows throughout the app. This may include things like redesigning certain screens entirely, optimization of critical user flows, and introducing onboarding walkthroughs for new users. These types of updates are informed by usability research conducted by our product design team and tested with volunteers from the Bitwarden community.
In closing, we understand that our mobile app has lagged behind in recent years. Xamarin served us well, but it’s time to move on. When released, we hope you will all enjoy the new native apps we have been working hard at building. Your feedback is important to help make the experience of using Bitwarden great for everyone.