A reason to not distribute a library as a binary is for cross platform support, this allows a library to technically be compiled and used in some other platform; with that said, there are assumptions about having the same system calls (or that the library only handles abstract things that don’t hook into a specific architecture), with that said, making cargo smarter and adding in the option to bundle some prebuilt libraries to be pulled for compatible platforms could speed some compile time (at the likely cost of build size, etc).
Distributing a library as source isn't some weird rust paradigm, take BOOST for example, which is a large library for C++, and is usually distributed as source (but Linux distros may bundle prebuilt binaries; it is generally intended that you will compile it and use it as a shared library), actually a lot of compiled languages distribute their libraries as source, it also allows you to read their source if you need to see exactly how they're doing something). I don't believe there is anything preventing someone from using shared libraries in rust, although they do seem to be less common. Another reason to distribute a library as source is for licensing.
The unstable versioning..... Ya, that is definitely annoying, and likely tied to the limited resources available for sustainment for various projects. With that said, compared to C/C++ many of these libraries are something that one might role their own or use in house libraries. Now for Tokio... You don't have to use it for async, although you probably will want to (see: https://blog.poespas.me/posts/2024/05/24/rust-async-std-and-tokio-comparison/), I do wish there was a nice way to depend on a library and substitute some of its dependencies (aka Tokio); with that said, part of the cargo idea is that you don't view these libraries as part of your source code for review (although, auditors would likely disagree, so acrediting with the inclusion of many in accredited libraries would probably not be fun)
This is so true, heck I've even 'baked' some custom PCB boards in the oven to do some cheap reflow... Every man belongs in the kitchen, that's where all the big boy tools are
And this is why we can’t have nice things; it sounds terrible, but there should be a limit for how responsible we as a society need to be for the actions of individuals.
Not just this, most (?all?) browsers now support viewing standard PDF documents… So, they shouldn’t even need to installing anything as long as they aren’t using IE…
I believe Mozilla was heavily involved with the creation of Rust, although that has now been transitioned to the Rust Foundation; not sure if that impacts them and/or what other projects they might have
Rust's cargo is great, I'd say it would be best to make the switch sooner rather than later once your code base is established. The build system and tooling alone is a great reason to switch
Honestly executives and board members who receive performance bonuses and golden parachutes should carry extra liability, such that these perks can be denied or even clawed back (and used to help the damages) when their decisions have these sort of outcomes. Nothing wrong with making more when things go well, but if you're going to take a larger piece of the pie, then you need to be prepared to take a smaller piece when things go wrong (aka, cut executive pay before layoffs, etc.).
Man, I wish more places would do this; the current prices just aren't worth it, I'd rather go to a bar or city run concert with some groups for casual hangouts and then stream the expensive stuff
Honestly, we need to replace social security numbers if we insist on using them as a form of identification (they never were designed for this); they follow a pattern (which is publicly available) and can be partially predicted without knowing too much about the individual. They were originally for Social Security only (hence their name), but then the IRS decided to use them for ID and then others followed suit, and we got to where we are now
what software are you using and how is the class structured? It sounds like this might be a rotating group of students all using the same ipads? Does the school have access to some sort of storage medium that requires unique (per student) login credentials that the students could save their files to?
Deleted my previous comment as it was cursed somehow and inserted constant spaces....
The middle one here looks a lot like a tick to me, likely in the nymph phase; also a quick search for 'bird mite' also included a good number of images of ticks as well (I had included a screenshot with some circled). You might be able to send them to your local agriculture department to be formally identified if you wanted to.
I agree with this, could also be tick larva (really young ticks, they go through a multihost lifecycle). If you're finding a bunch of those extra tiny ones, I suspect you walked through a nest and picked them up (good news is I believe that nymphs are less likely to carry any diseases (key term is less)). Good luck, those are a pain to spot, I'd spend a bunch of time checking everyone over throughly, the diseases that ticks can cary are no joke (then be extra alert for a while to make sure no weird rashes show up, such as the traditional lyme disease bullseye).
I never received this survey and I fly Southwest specifically because I found their boarding process to be less of a hassle (for a single traveler who doesn't care where they sit). The only way I could see this being beneficial is if they board people in order of assigned seat in such a way as to optimize time to seat, not the BS boarding that other airlines do to try and maximize price of fair, otherwise they will have lost the whole reason I like(d) to fly them... Their simplier, no bs, boarding process.
P.S.
I really don't get people liking to pidgen hole themselves to a specific spot for any of these things, just makes it easier to inflate the prices later
A reason to not distribute a library as a binary is for cross platform support, this allows a library to technically be compiled and used in some other platform; with that said, there are assumptions about having the same system calls (or that the library only handles abstract things that don’t hook into a specific architecture), with that said, making cargo smarter and adding in the option to bundle some prebuilt libraries to be pulled for compatible platforms could speed some compile time (at the likely cost of build size, etc).
Distributing a library as source isn't some weird rust paradigm, take BOOST for example, which is a large library for C++, and is usually distributed as source (but Linux distros may bundle prebuilt binaries; it is generally intended that you will compile it and use it as a shared library), actually a lot of compiled languages distribute their libraries as source, it also allows you to read their source if you need to see exactly how they're doing something). I don't believe there is anything preventing someone from using shared libraries in rust, although they do seem to be less common. Another reason to distribute a library as source is for licensing.
The unstable versioning..... Ya, that is definitely annoying, and likely tied to the limited resources available for sustainment for various projects. With that said, compared to C/C++ many of these libraries are something that one might role their own or use in house libraries. Now for Tokio... You don't have to use it for async, although you probably will want to (see: https://blog.poespas.me/posts/2024/05/24/rust-async-std-and-tokio-comparison/), I do wish there was a nice way to depend on a library and substitute some of its dependencies (aka Tokio); with that said, part of the cargo idea is that you don't view these libraries as part of your source code for review (although, auditors would likely disagree, so acrediting with the inclusion of many in accredited libraries would probably not be fun)