C.f. The Aubrey and Maturin books as decisive counterpoint to this theory.
"Ah, the f'castle mizzen spizzen you say. Yes. Yes, of course." I nod sagely while my vision swims.
My nerves are shattered and I wasn't even watching. Out with the kids and furtively (frantically) refreshing the live score feed.
Poor old Borthwick really is going to get strung out to dry, isn't he?
Oh, totally (forking paths). You could see SCO had lost focus.
But must be infuriating for FRA supporters that they only dialed in for the final 10 minutes. Although, I expect that bonus point try will prove decisive for the tournament.
*somewhat.
But, really, the important thing is that PSDT would have never. 🐐
Forking paths and all that, but if DuPont hadn't thrown that ridiculous forward pass behind his own goal line, France, some unbelievably, would have been in with a shout for a draw.
France have imploded, clearly. But genuinely the best I've ever seen Scotland play.
Back in December, I presented at a "Fast Computing" workshop hosted by the Bank of Portugal. The videos + materials are now all available online. github.com/BPLIM/Worksh...
(Also including cool talks by @s3alfisc.bsky.social, @sebkrantz.bsky.social, and others.)
Very disrespectful to do that at HQ!
My original poast didn't get much love (🥲), but co-opting the data.table print method for base #rstats data.frames is fairly straightforward. bsky.app/profile/gmcd...
(Ofc there are many other advantages to DT, but just sticking with the print method for now.)
I think the main issue is that many people, quite reasonably tbf, don't like the default base data.frame print method...
But this is easy to override! gist.github.com/grantmcdermo...
I think the main issue is that many people, quite reasonably tbf, don't like the default base data.frame print method...
But this is easy to override! gist.github.com/grantmcdermo...
Institutions FTW
Can't wait for that Grand Slam decider in Paris on March 14.
* touches earpiece
Hold on, I'm getting new information...
Not even that. Why take a lineout outside the 22, when you've got the opposition under the kosh and at probable risk of a card?
Not to rub it in, but since we're on bad tactical decisions... you know that Rassie would have called for more scrums when the Scottish front row were giving aways penalties and on those warnings.
Scottish boxkick for MOTM.
Check out the new paper! And please please please send us both gut reactions and harsh criticism.
Okay, okay! I guess I have to actually try this out now @apoorvalal.com.
I made a Ghola
Mainly the fact that I didn't think of it 😅
I thought it would be cool to try something lightweight via R's native C API. But if someone figures out a nice way to port Positron's ragg-based functionality then I'd fully support that. Mostly, I just think we need to move on from httpgd & co.
I spell out the motivation in the README. The _tl;dr_ version is that I'm trying to avoid some tiresome `httpgd` CRAN issues. `jgd` is intended as a lightweight (and hopefully robust) alternative that could be integrated into the main extension in the future. Help and testers welcome!
#rstats In very non-Superbowl news, here's an experimental 📦 for nice graphics display and UX in VS Code (and other potential front-ends).
github.com/grantmcdermo...
<Andrew Baker voice> Upper hemicontinuity, please.
Cool idea, but you'd need at least 30 of each for the central limit theorem to lock in, which will blow through your tokens.
Why code like yourself when you can code like someone else?
In seriousness, there's obviously value in having good "community" templates. But I do think there's a lot of embedded skill in the structure of applied projects (not just the code, but the flow of the analysis).
bsky.app/profile/gmcd...
🤔 I don't think it would be the package source.
In the above code snippet, you need to load the languageserver package before running .vsc.attach(). But that should happen automatically if you execute any lines of code from VS Code (Cmd + Enter). Maybe worth raising an issue on the arf repo?
This should work:
bsky.app/profile/gmcd...
Agree, it's very good and my default for personal use (alongside R.nvim).
But our primary compute/coding interface at work is a vscode.dev -alike deployment environment. So I still use VS Code a lot and rely on the "traditional" extension model.
DuckDB is just the default. You can pass through any backend supported by DBI.
The other differences (I'm guessing?) are that we use a few acceleration tricks to speed up computation and calculate robust SEs. I'd need to compare the docs. No harm having multiple 📦 options, though ;-)
