For users of any operating system, not just #Linux, what might keep you from trying/running an #immutable#Fedora desktop? If you are already running one, why did you choose it?
@hroncok this echos my feelings and also experience with trying it. As an end user it only adds friction so there's no benefit for me (I can't remember the last time I broke my install and would need to roll-back). @vwbusguy
@gaborcsardi yeah that was pretty much my thinking. Not sure whether any distros will think it worthy of back porting though as seems a bit meh 🤷♂️ @brodriguesco
@brodriguesco I’m no expert but isn’t this kind of “if you install a package you’re already trusting it anyway”?.Seems like this could obscure stuff but still kind of expected no? … will be interesting to see how it gets rated
Shiny and #RStats friends, I’m thinking about a Shiny 201 or 301 workshop. Imagine you took Intro to Shiny, and you’ve made a few apps. You’re ready to learn the next thing to level up. What do you wish you had learned next?
Everyone said get a Brother printer so I bought a 3-in-1 scanner and printer. There seems to be something wrong with it though. I plugged it into a Linux laptop, opened a document, pressed print, selected the printer, and it printed. Then I opened simple-scan, pressed scan, and it scanned.
This isn't how printers and scanners are supposed to work. Where do I install the drivers that don't work properly etc? This was no fun. I demand a refund.
Considering a Slack replacement for an open-source organisation. Here's the current contender list, in preference order, without much thought but based on personal experience. Got any other suggestions? :)
1 - IRC
2 - Mattermost
3 - RocketChat
4 - NextCloud Talk
105 - Signal
400 - Matrix
9000 - Discord
9998 - Skype
9999 - Slack
10000 - Zoom
10001 - WebEx
within the last year or so @Posit has taken a big tranche of venture capital. VC wants one thing: a massive return, 10x minimum. there are two ways to get that. first is to take a company public. I don't think that's likely here. second is a buy out by a major player like Oracle, Microsoft, Amazon, or another of that ilk. I guess this is what posit's sugar daddy is likely angling for. this isn't unprecedented in the #rstats world. who else remembers Revolution R?
@Cmastication
You have now sparked my interest though - Brighton Park Capital invested in 2021 which ties in with the link @awong234 shared. Who was the mystery 2022 investor? Feel like a poor mans sherlock holmes 🕵️ @davidbraze@Posit
Evening all, hope all is well. It's been weeks of dull grey clouds and it's real frustrating. Finding it a little hard to motivate myself to take the camera out with me at present. Hopefully that'll change soon.
Here's a back-lit male Stonechat, during a period where the sun existed 😂
If you see warnings/errors on GitHub Actions related to Matrix incompatibilities for your R package, see this issue for possible workarounds: https://github.com/r-lib/actions/issues/832
@brodriguesco looks like the latest has a dependency on R4.4.0 so the older one is still the one utilised by earlier R versions so being kept available. Same thing with Matrix. Things are a little tricky with the recommended packages. There were also a few wrinkles over the last couple of days so possible this/you got caught up in those as well (see Simon’s post at https://stat.ethz.ch/pipermail/r-devel/2024-April/083383.html).
Only came back to social media in the last few weeks and the weird pile on against #fosstodon was exactly the sort of thing I hate. Managed to block out the noise but today decided to start using patreon to support @kev / @mike and all of the other moderators that are keeping things going over here. Maybe one day I’ll have the time (and motivation) to start my own little instance but til then I’ll happily plod along with fosstodon 😀
Request for help from anyone with #rstats package development experience or knowledge of time data, especially if you've worked with .ical files before: checks failing in the {calendar} package preventing updated on CRAN and I'm not sure why 🤷 . Thanks to new contributors for reviving this package after ~5 years dev hiatus! Please spread the word @rOpenSci and anyone in this #foss for #DataScience (or at least dates) space! Details: https://github.com/ATFutures/calendar/issues/50
@robinlovelace Timezone issue? Away from computer but try setting a different timezone and rerunning the tests locally. That can often highlight logical errors when working with packages involving dates. Something like
TZ=NZ R CMD check
Or maybe TZ=AT which might match Vienna. Possibly sending you on wild goose chase but worth a try …
"You are not required to have a public position on everything. You are not an embassy".
I heard about this (possibly on a podcast), which resonates with me. Does anyone know where I heard it, or who should be credited with coming up with this?
Super easy thanks to the #QuartoPub shinylive extension! Also huge thanks to r-universe.dev for providing WASM binaries so I could install and demo this package even though it isn't on CRAN!
is "not-so-good" code. Anything that changes the state of random number generator (RNG) on package load prevents reproducible results. It's impossible to protect against this in some situations, e.g. when running things in #parallel where the result depends on whether the package is already loaded on parallel workers.
@henrikbengtsson Something R CMD check could check for (i.e seed changing on attach)? Away from pc but I’m now curious to search the GitHub CRAN mirror to get a sense of how widespread this is. @maelle
Motivated by the recent blog (https://duckdb.org/2024/04/02/duckplyr) I finally took {duckplyr} for a spin and 🤯. Staggeringly quick (though I only tried the example from the post). Definitely going to kick the tyres some more. {dplyr} on the front with #duckdb at the rear is the perfect example of the cool user experience you can create with #RStats (not forgetting to mention the years of experimenting / hard work from all involved). Big 😃 for me right now.
On a newly installed pc trying to remember the various incantations I need to do to get the various memory checkers working for #RStats packages ... decided now would be a good time to try rhub2 ... wow so so slick @gaborcsardi . Thank you 🙏 https://github.com/r-hub/rhub2
I wish more of the #reproducibility discussions in #rstats focussed on ensuring that analysis could be repeated with current/maintained R packages (and system libraries) rather than just taking a snapshot of your current environment. Fixing your environment is just accruing technical/analytical debt so "production" use cases aside (interpret "production" how you wish), I don't think it is as useful for research/science as some make out. There is of course more nuance to this but still ... 1/1