Avilinha

That's a good point

Getting the user level installer... Basically it installs in your user folder instead of the common program folder in C: ...

Yeah, rules are rules :D

They still need to install it (I think) just the updates you can do without bothering them... The biggest risk vector, by far, are the extensions (and pip, npm packages) one might install (without admin privileges)

Positron (and vscode) can be updated without admin rights if you install the "user level" instead of system level...

Of course, updating it without the approval of IT dep could be a risk vector (but also is the delaying the update of security features...)

Which filter will catch it though??

mas groelandia tá pelo top 10, senão top 5...

as minhs top 3 sao somalia, latvia e lituania... nao necessariamente nessa ordem... :)

ok this is good

Why stop there, English survives well with a single article..

vc que fez a foto?
muito boa

GitHub - elbersb/tidylog: Tidylog provides feedback about dplyr and tidyr operations. It provides wrapper functions for the most common functions, such as filter, mutate, select, and group_by, and pro... Tidylog provides feedback about dplyr and tidyr operations. It provides wrapper functions for the most common functions, such as filter, mutate, select, and group_by, and provides detailed output f...

github.com/elbersb/tidy...

excerpt of code containing: Tidylog can be especially helpful in longer pipes: summary <- mtcars %>% select(mpg, cyl, hp, am) %>% filter(mpg > 15) %>% mutate(mpg_round = round(mpg)) %>% group_by(cyl, mpg_round, am) %>% tally() %>% filter(n >= 1) #> select: dropped 7 variables (disp, drat, wt, qsec, vs, …) #> filter: removed 6 rows (19%), 26 rows remaining #> mutate: new variable 'mpg_round' (double) with 15 unique values and 0% NA #> group_by: 3 grouping variables (cyl, mpg_round, am) #> tally: now 20 rows and 4 columns, 2 group variables remaining (cyl, mpg_round) #> filter (grouped): no rows removed

reminds of tidylog...
(quite useful with joining or filtering the data...)
having said that, I find much better not to attach the package, and explicitly use tidylog::filter(...) when I need the logging
feedback...

something like loaf warden* --> lord (according to the history of english podcast...)

* old english cognates of such terms...

id say about 88%

which tool/language did you use to produce this chart? Looks great!

The upstairs neighbour Peter?? (There should be a mnemonic for pluto right?)

num é o contrário? o Epstein ajuda a esposa a fazer o Chomsky a gostar de jazz?

a "versão extendida" tem um toque especial bsky.app/profile/brux...

Heheh, it did pop at my feed yesterday actually... I was going to tell the OP to check it out but when I saw you here, I thought I better let you bring the good news

I suppose stealing intellectual property for profit is an even better form of flattery??

Are you, by any chance, writing another R linter??

yeah, not the best ui... but you can click the image to zoom in, then it is readable

Oh. That's fast

I'd say you all lost a great opportunity of calling it prositon! 😅😬

What do you mean by downloader button? A shiny button that reproduces and exports the plot??

rafucko, sempre quis te perguntar, desde os tempos do facebook... por que o seu logo (antigo) era igualzinho o logo do mustafa gemüse kebab?

november >>> all other months!

It is a Human controlling it from the living room (no joke)

That's great. I've been trying to reduce the amount of tokens sent. I've come across some discussion about it, but can't find it right now, in any case is there some best practices around that? What seems to do a big difference is unchecking some tools (MCP?) that are on by default.

This shouldnt even be an option... it should be default (and only behaviour... ) right?