I would be very surprised if that was actually the reason. human similar bots have been shown to be much worse than single purpose bots for decades now and tesla already uses tons of bots in its manufacturing.

you're welcome

But why

Order one from Canada? Not sure. And of the big tech companies that control phones, Apple is by far the best (at privacy at least, repairability is on the other end of the scale), I wouldn’t touch anything made by Google or Samsung with a ten foot pole. Maybe an old windows phone? Nokia?

On that note though, I have a friend who literally doesn’t own a smart phone. He has a flip phone (a new one too, no clue where he bought it) and he seems to get along in society just fine. Idk. Definitely not for everyone.

Also due to markdown being a very badly defined “spec”.

iMessage isn’t an app… you’re not paying attention to what they’re saying at all. iMessage has never been an app. It’s a protocol for Apple messages through their server hardware. Messages is the app, Messages can send emails, sms, mms, and iMessages.

how many songs by the same artist do you have in that playlist? Your comments here don't make sense. Repeating the same artist doesn't make something not random and definitely doesn't make it "the most 100 recently saved songs". In fact repeating the same artist makes it quite likely that it is random as randomness is frequently misinterpreted as non-random if you would have read the article I linked you would understand that.

Haha sorry, I wrote it all on my phone while traveling. and yeah, if you're running just shell commands it looks almost the exact same as a bash script, and then when you need actual scripting capabilities you get them.

I would not say “heavily based”. Literally only the closure/lambda syntax, which is cosmetic. Rust is mainly inspired by ML-family languages and C++.

All of Cargo is based on (and created by) the same person that created bundler for ruby. That list also misses out on a lot of things, like !, automatic returns, honestly most of the actual language 'design' rather than the internals (that seems to be a list of where the architects got their ideas for internal implementation as well, rather than just the readability of the language).

But Rust is very well suited to more complicated or long-lasting command-line tools, especially if performance is at all a concern. Clap alone is super nice, but there are a lot of awesome libraries for making rich CLI tools easily.

I disagree. Like I said, I wrote command line apps in all of these, performance was a factor. But a much larger factor is getting other devs on your team to contribute. And that was just absolutely impossible with Rust. The learning curve is just too high. For something that isn't a hobby project, but that you might need a team member to roll out a fix in just a few hours, Rust will not cut it.

Yes, you will have way more bugs in all the other programs, but honestly I had a shit ton of bugs in my rust cli as well, because, it turns out, rust works really well when it has control over everything, but man does it suffer when you have to interface with the real world.. And oh boy did that make it incredibly difficult to write. Like I said, I deployed CLIs in all three of these languages. Ruby was the easiest of them all. Not just in development, but also maintenance.

But like, what are they copying here?

Really surprised no one has mentioned Ruby. It's installed by default on almost every system out there (unlike python), it will have the same features on every platform (unlike python where you might get 2.7 or 3.x depending. It's simple and easy to read, and only slightly more verbose than bash. It's very well suited for scripting (please don't use it for application work). It also took a lot of its design from Perl, which a bunch of people are mentioning in this thread, and as a result has a ton of the features of perl, along with a ton of features from other languages. Rust is heavily based on Ruby's design, and i've used Rust to create cli programs and I wouldn't recommend it. It's good, but most cli programs don't need the difficulty of rust for the benefits that rust gives.

Anyway, python has a really really good cli library called Click, but that's about the only good thing about it. If you are looking to use this script on multiple systems then Ruby will be much easier to transfer between systems (it will just work). I've deployed complex python, rust, and ruby CLIs across an org and Ruby was the only easy one. Rust was second easiest, Python absolutely terrible.

If you're not deploying this to other platforms or sharing it across a team or something like that then a lot of the downsides and upsides here don't really matter. Just use the easiest language.

I haven't seen an issue for it. I need to create one.