

That’s the ISO-8601 format, Japan uses “/” or alternatively yyyy年mm月dd日
That’s the ISO-8601 format, Japan uses “/” or alternatively yyyy年mm月dd日
That’s for images though, not text content.
Is that for scientific data/training sets, or are you mirroring ever Linux distro in existence?
It’s in the Elder Scrolls universe, so it’s probably a khajiit of the Alfiq variant.
I think it’s a thing mainly for hobby programmers and young students that don’t have a solid foundation/grasp of programming yet, which also likely makes up a big portion of programming meme communities.
Functional programming would have quite the problem if it wasn’t a thing.
Considering Russia’s interest in the islands, that might not be all that great of a choice.
It would be nice to have way for admins and mods to make notes on people. E.g. If you are giving someone a warning, you currently need to use an external tool to log the warning.
The hen can’t be alone with the fox or the grain, so it’s still the same.
The older generation in Norway also uses that format. I usually tell them that we aren’t under German occupation anymore, so they should use the sensible format.
I’m not anti bash or fish, I’ve written in both just this week, but if we’re talking about readability/syntax as this post is about, and you want an alternative to bash, I’d say python is a more natural alternative. Fish syntax is still fairly ugly compared to most programming languages in my opinion.
Different strokes for different folks I suppose.
For example, how could it know whether
cat $foo
should becat "$foo"
, or whether the script actually relies on word splitting? It’s possible that$foo
intentionally contains multiple paths.
Last time I used ShellCheck (yesterday funnily enough) I had written ports+=($(get_elixir_ports))
to split the input since get_elixir_ports
returns a string of space separated ports. It worked exactly as intended, but ShellCheck still recommended to make the splitting explicit rather than implicit.
The ShellCheck docs recommended
IFS=" " read -r -a elixir_ports <<< "(get_elixir_ports)"
ports+=("${elixir_ports[@]}")
If you’re going to write scripts that requires installing software, might as well use something like python though? Most Linux distros ship also ship with python installed
Writing Lua code that also interacts with C code that uses 0 indexing is an awful experience. Annoys me to this day even though haven’t used it for 2 years
How about 8 hours troubleshooting while trying to find the right documentation.
Plenty of projects have exe files available on the release page though, it’s just hard to find unless you’re familiar with github.
Can’t say I recommend
Windows/Microsoft’s biggest selling point is the backwards compatibility though. It has been the corner stone of their software development.
The flesh is weak, but deeds endure
Neither options will solve the problem though