Attrs would not replace your record array. IIRC you can supply slots so it might be useful for converting raw data into your numpy types, but I suspect you'd find the overhead in function calls problematic
If you want easier than recarray and almost as fast I think you're in pandas-ville
It's interesting to me that dataclasses seemed to be a slimmed down attrs but in practice I find it replaces namedtuple not attrs
For my use the key is how easily you can add simple conversion of values to attrs. IIRC this was intentionally omitted from dataclasses. For a 1-off using a factory with a dataclass is easy but repeated uses send me back to attrs
Yeah, I think namedtuple's popularity (recommended in this link) was a mistake. It's sole modern use case should be to turn tuples used as an unnamed struct into a named struct while preserving tuple indexing for backward compatibility.
Most people don't need, say, a[-3] as an alias for a.field_name.
Otherwise, for those who want the standard library, use a dataclass with frozen=True for immutability.
- R packages are much more likely to include compilation of C libraries, which can cause grief if you're not experienced enough to install specific libs that might be newer than eg what apt provides
- library(package) imports the full package into the global namespace (from package import *) which is fine for small projects but scales poorly
Anaconda largely handles the first problem if you can constrain you package use to its ecosystem though.
For my anecdata the worst R package wasn't any worse than a python package that needed gdal, but I had to deal with these problems easily 5 times more often
They're supposed to be tuned but often aren't, as many motorcyclists can attest to
Further the muni often lacks resources to fix this in a timely manner after reporting. In some cases you see states effectively throw up their hands and say "if it doesn't detect you can just run the red"
My first job was as a sys admin, and I was explicitly told that they hired me because my eyes didn't glaze over when the interview covered their static ip network
The thing is, that was then. Now suggesting a static ip immediately begs the question of what wouldn't you use dns to solve the problem instead.
Dns doesn't solve all cases but it does now cover a significant number. The industry has changed enough that I no longer expect anyone who doesn't have some background with networking specific concerns to know this stuff
I couldn't tell you if this is a net positive, but it definitely feels less relevant to my day-to-day than being competent with whatever DSL your CI pipeline uses
dhcp. Boring, simple, and insufficient for professional work imo. Not a problem for a largely static home network
At work "the ricoh guy" manages the printers. You can access them by name (wins) or ip. I think that's a good enough solution, but it focuses all the static ip work to one small team (possibly 1 person) and to everyone else it's some characters you effectively copy paste once per laptop refresh. No networking knowledge necessary
To be clear, it's not that I think these skills lack value or practical application in lots of professional settings, it's that I think their relative position to other things has gone down
A typical modern home printer is connected to WiFi and uses that to reach the cloud where most of the actual implementation for printing lives. So, yes.
My mother's (5+ year old) all-in-one colour printer etc. will cheerfully scan a page and email it to her, because of course although the sensors turning the page into image data are physically in the scanner, all the actual software she's using is "in the cloud" so sending her an email is no harder than turning it into a downloadable ("saved") PDF.
Growing up in US public schools cursive was mandatory in ~5th grade in my district. Then shortly after (6th grade? 7th?) it became optional and the vast majority of my peers quit writing it
I persisted because I actually preferred it, only to be actively encouraged by teachers collecting longer written assignments to write _normally_ on account of my cursive being harder to read
It didn't end up mattering - computers and printed assignments were rapidly becoming the norm. I always thought teaching cursive was a strange choice
It may be worth noting that the legibility of my penmanship is generally poor. I wonder if perhaps emphasizing legibility has similar positive effects on developing brains...
For a long while I ran testing and had zero issues.
Warning: if you're used to PPA life in Ubuntu Debian doesn't offer an equivalent that I'm aware of. EDIT sibling comments indicate home brew might solve this.
The problem with Debian is you can't usually pick "a thing" from another channel, you mostly have to fully commit. Testing is great until it isn't and anecdotally sid/unstable never fixed that for me - I just had to learn to build the occasional package from source
Ultimately I'm a lot happier having gone on that journey but it can feel very arduous the first few times apt doesn't have a recent enough version of something available
WASM Gawk wrapper script in a web browser with relevant information about schema grammar / template file would allow for alternate display formats beyond cli text (aka html, latex, "database report output", cvs, etc )
If you want easier than recarray and almost as fast I think you're in pandas-ville