Over a few days I wrote a bunch of #C++, #Rust, #Haskell, and #Python. Something I don’t get is that while I might say that Python has the most extensive ecosystem, it seems to have the worst tooling in terms of package management and LSP features (clangd, rust-analyzer, hls, and pylsp). How does that happen? Why don’t the economics that plow programmer hours into Python libraries raise the level of its tooling?
Anyone having these arguments hasn't even watched a "Rust in 100 seconds" or #ELI5 post of #Rust. All these are advertised and well-known functionalities they are flat out denying with worse arguments than flat-earthers.
@clacke I also saw people talking about the main #Rust group threatening trademark complaints against gcc-rust. I did not follow any links to learn more.
And here's why the AV detects it. They don't have many samples written in #Nim, and most that they have are malware / trojans. But attackers are using more than just #Nim-lang. They're also using #GoLang, #DLang, and #Rust. This suggests that antivirus vendors need to get smarter.
@natecull#ocaml, #rust and #Haskell all have specific packages in #Fedora and #Debian to deal with #endianness so it seems to matter. Also add that according to utfcheck Debian package description UTF-16 can be encoded in big or little-endian
More #rust musings: I'm given to understand that the hardest thing to wrap one's head around is ownership. Having needed to deal with manual memory management in C/C++ in the 90s, this just seems like the compiler doing automatic sanity checking on my code. I can see why it would be hard for someone who's always just relied on a garbage collection before though.
#Rust seems to have grown an individualist community, with all its tiny packages hosted in a non-curated repo, with its rejection of copyleft, and with its disregard of #FreeSoftware “community standards” developed by distro folks over the years.
I feel that introducing Rust right into once collectively-developed code bases at the core of GNU/Linux will have unpredictable and detrimental effects.
Correction: #Pijul ... it is a #dvcs / #scm system written in #Rust, and an evolution of some of the ideas behind #Haskell's #Darcs, including fleshing out the theoretical basis and solving a couple of major bugs.
@geniusmusing I do have #Rust, #Cargo, and #Pijol installed on the main laptop and on the Win10 laptop, so learning to use Rust is something on my mind.
* #M / #MUMPS unified database & language * Forked from #GT.M by long-time members of the GT.M dev team * Compatibility / interop with #C, #Go, #Rust, #Perl, ...
If you’re interested in !TclTk, then you may find #jsish interesting, because its internals are designed based on some of Tcl’s internals, and because it integrates the #Fossil #DVCS and can be updated using standard Fossil commands.