Currently deciding which #Linux distro to install besides #Windows on my laptop. I want to switch back to Linux for #programming (had to switch to Windows for work). I have used #Ubuntu and #LinuxMint in the past. Any suggestions?
;; Getting rid of explicit indexing was just step one.
-- After a few days/months/years, I now realize that it is more important and less buggy if I think only of the function to call (and whether I want to end up with a new (maybe pruned) collection, a single thing, or "both" (that's how I think of scans))
I remember having a discussion about argument parsing in #Python a while ago where someone recommended a small library that was kind of like argparse except that instead of returning an argparse.Namespace, it returns a fully typed object (which you define), a dataclass or something similar. Anyone know what I'm talking about? I wanted to try that library but I forgot what it is and I can't find the discussion.
When I decided to try to build up some development momentum by restarting the Ray Tracing Challenge but with Dart/Flutter it was a toss up between that idea and deep diving into some retro coding on an Apple II. I briefly thought, "Why not do both?" Har har har. Well, it turns out someone did just that. A ray tracer in BASIC on a ZX Spectrum. #RetroComputing#RetroGaming#programming#ZXSpectrum#BASICgabrielgambetta.com/zx-raytrac…
The good news is Android Studio has come a long way since I first tried it when Android first launched. It’s matured, but still has a lot of obtueseness. At least it’s usable now.
I wish CompSci people would stop designing tools and programming language syntax.
Well. You know how I complain how slow XCode is? Android Studio is just as slow. It has something that goes through “Gradle project sync” on launch every time and takes as long as XCode’s “Preparing device”. I’m liking Python and its ilk more and more… Get more done.
Want a simple form of #MCMC analysis in #R well, I got you covered.
My #R#Package TidyDensity has a function called tidy_mcmc_sampling() that is pretty straight forward. It takes a raw vector and performs the calculation you give it over a default of 2k samples.
Is there anyone who knows about the internals of the #NeXTStep 3.3 finder/wm? It does some mount magic with CDROMs on inject/eject - but I cant find it documented or if there's API's to hook into that process.
The newest project is finally ready for its public debut! Inspired by a tool on #Kali for XFCE desktops, Nix-Incognito was developed to provide a similar mechanism for masking a user's GNOME desktop to better blend in with surrounding #windows PC's during #redteam engagements!
Although it's meant for use on #NixOS systems, it can easily be compiled and ran on any device running #GNOME. Support for other DE's is in the works! 🙌 🤘 😎 #rustlang#cli#programming
I think in PowerShell and can manage in Python. I want to learn Rust to the degree I can write in it directly, rather than prototyping in PowerShell and then converting.
A lot of what I do is data manipulation and analysis. (Take several CSV files as input, and output new CSV files that answer business questions based on the inputs.) I'm seriously impressed with Rust's performance here.
If you've made this transition, advice on where to begin?
Exciting news for R users! TidyDensity's latest update introduces util_chisquare_param_estimate(), leveraging MLE to estimate Chi-square distribution parameters like dof and ncp.
Generate a dataset with rchisq() and use util_chisquare_param_estimate() to analyze it, even without knowing the underlying distribution. Visualize results with tidy_combined_autoplot().
In #Rust, how can I leverage the type system to enforce that one object originates from another? Even requiring the lifetime be exact ('a: 'b and 'b: 'a) wouldn't work.
Basically, I have struct Bytes<'a>(&'a [u8]); and want to prevent someone from creating an arbitrary value that can be swapped in for the correct one. Yet at the same time it is essential that arbitrary values can be created.
Basically I'm trying to enforce my own version of provenance…
I believe I've done it. After a few attempts, I was able to enforce provenance while minimally affecting the API.
Implementing a trait now has a trivial amount of overhead, while end users will see no difference whatsoever from what I wanted.
To those wondering, I ended up using the closure hack along with forcing invariance. GhostCell, while neat, only appears to work within a single function.
Should I write something up about this? It's an interesting problem.