I've never felt this much behind as a programmer. The profession is being dramatically refactored as the bits contributed by the programmer are increasingly sparse and between. I have a sense that I could be 10X more powerful if I just properly string together what has become available over the last ~year and a failure to claim the boost feels decidedly like skill issue. There's a new programmable layer of abstraction to master (in addition to the usual layers below) involving agents, subagents, their prompts, contexts, memory, modes, permissions, tools, plugins, skills, hooks, MCP, LSP, slash commands, workflows, IDE integrations, and a need to build an all-encompassing mental model for strengths and pitfalls of fundamentally stochastic, fallible, unintelligible and changing entities suddenly intermingled with what used to be good old fashioned engineering. Clearly some powerful alien tool was handed around except it comes with no manual and everyone has to figure out how to hold it and operate it, while the resulting magnitude 9 earthquake is rocking the profession. Roll up your sleeves to not fall behind.
Until ~2015, GitHub Pages hosted over 2 million websites on 2 servers with a multi-million-line nginx.conf, edited and reloaded per deploy. This worked incredibly well, with https://t.co/DcP1J23VVj ranking as the 140th most visited domain on the web at the time.
uv 0.5.0 is out now 🚢🚢🚢
We did 30 releases without a breaking change, so this release contains a handful of them that we've accumulated over the past few months.
Many aimed at improving correctness.
R/Pharma "Call for Talks" now open!
https://t.co/IMLE8aSNNp
Submission Form:
https://t.co/mIk3SDlFii
Deadline July 21st📷
Virtual Gathering Oct 29th-31st!⏰
Free registration will open later this Summer!
#rinpharma#pharmaverse#rshiny#opensource#rstats#python@posit_pbc
If you are running into broken GitHub integrations today, it's because GitHub issuecomment IDs have just passed the maximum value of i32.
For example @rustlang's rfcbot is currently out of commission with an i32 overflow.
@JosiahParry @jdatap@kennedymwavu i have not! I will join - https://t.co/BIAQghNX6q is where I'm at for learning exercise for a fast way to get dependencies that touches string handling since the datastructure for deps in the packages db is ridiculous. Also: https://t.co/cbuW2gxBYU - Ludicrous speed!
@JosiahParry @jdatap@kennedymwavu To expand on this, it would likely be hard/incompatible to handle multiple shiny processes/event loops within a single r process, so you still need spawning new r processes, proxying port etc, which can be done, but is better suited for parallel friendly languages like go/rust
@JosiahParry @jdatap@kennedymwavu Most likely you'd be better off just traditionally handling routing, the biggest extra lift is when you want routing and scaling/load balancing. You could even modify the work you've done for plumber routing in rust to be able to handle shiny.
@kennedymwavu @JosiahParry @jdatap I think websockets are a very minimal part of the real value proposition of shiny though, which is the combo of an extremely elegant reactive framework + the widget ecosystem within and on top.
Everyone who used #rstats dput() from time to time should try the constructive 📦 because it puts out strings that you can actually read + use w/o endless reformatting. Thanks @antoine_fabri