I've been toiling away for the past 2 years on a passion project. A native mobile app for the PWHL (Professional Women's Hockey League). It's privacy focused without ads and a bunch of features: https://pwhl.app
It uses flutter under the hood, with Kotlin and SwiftUI for native home screen widgets. A simple nodejs backend powers push notifications too.
I wonder how much of this is because (IME anyway) Tesla drivers are not very good. With all that tech it's easy to get distracted (there's literally a giant tablet looking thing for a console). It's also easy to think all the bells and whistles will do things for you so drivers are paying less attention because the car will beep and holler at them if things are going awry (except by that point it's too late).
This is how I made a better version of the nhl.com site [1] that has a better UI (you can see scores/schedules much more easily), is mobile first, has no ads, and responsiveness built in. I did the same for the AHL [2], and the PWHL [3].
I don't know. I am a woman who does not have those specific experiences. I happily buy stuff at Amazon, chat with relatives and friends on social media, and is active in some subreddits. I do know several harassment issues where I have received unsoliticed dick picks, been (verbally) sexually harassed, and received lots of creepy messages from strangers on the internet.
Sadly, it appears they have discontinued the free plan:
> But anyone who hasn’t created an account by December 31 [2021] at 11:59pm Eastern won’t be able to create an account via our open registration flow. Instead, they’ll need to choose a paid account, or get a Free account through another channel. Read on for details.
> Try to find the answer to "which units are going to be started on next boot?".
Isn't this just `ls /etc/systemd/{user,system,network}//*` (bah HN formatting is messing this up)
Also the other states:
> Speaking of which, why is systemctl daemon-reload even a thing?
Because configuration changes while things are running. Otherwise we wouldn't need apache2 reload, nginx reload, haproxy reload, etc. Also, according to the man page:
> After the units have been edited, systemd configuration is reloaded (in a way that is equivalent to daemon-reload).
As for systemctl edit, it allows you to add diffs to the unit file. For example, let's say I am using redis and I want to ensure it always restarts (for whatever reason). Rather than manually editing the unit file (which will have issues if an upstream change happens), I can simply use systemctl edit to add a diff for my change. This way I can still maintain compatibility with the upstream unit file instead of having to deal with potential conflicts. It's not so much babysitting the user as it is a potentially better experience.
To a Scala veteran, I'm sure that's easy to understand; to someone who's been learning the language (like me) it looks like gibberish.
I've also had to write code like this:
client.post(args).mapTo[Response].map(r => (r.success, r.serverException, r.unhandledException) match {
case (Some(response), None, None) => response
case (None, Some(serverEx), None) => throw serverEx
case (None, None, Some(unhandledEx)) => throw unhandledEx
})
simply because of the underlying api that other co-workers have built. When it takes you longer than 30 seconds to explain how a piece of code works to others, something is wrong.
All that being said, I do like the language; just not the compile times. It's also pretty close to ruby (with which I'm most familiar):
At least with Latitude, it doesn't force you to share your location 24/7. You can turn it off at will, so you can effectively only share it when you want your contacts to see where you are.
It uses flutter under the hood, with Kotlin and SwiftUI for native home screen widgets. A simple nodejs backend powers push notifications too.