auxym

zfs/btrfs snapshot and then rclone that snapshot?

It seems you're talking about about self-hosting a website or web-app that you are developing for the public to use.

My vision of self-hosting is basically the opposite. I only self-host existing apps and services for my and my family's use. I have a TrueNAS box with a few disks, run Jellyfin for music and shows, run a Nextcloud instance, a restic REST server for backing up our devices, etc. I feel like the OP is more targeted this type of "self hosting".

The other infuriating thing is that the search filters appear to be deliberately non-functional and interpreted as mere suggestions. Distance, price and listing date, for example. Try filtering for new listings in the past week and you will get plenty of old stuff.

I'm in eastern Canada, and unfortunately, FBM has completely overtaken the previous leader for online classifieds, which was kijiji (owned by ebay). So if you want to to buy/sell used goods, FBM is pretty much your only option around here.

All correct. To add, the main problem with ceramics is their fragility under tensile stresses. Spinning at high speeds puts the blades into tensile stress, which tends to "open up" microscopic defects in the crystal structure and cause complete failure.

Some researchers from the academic lab where I work have been working on a turbine configuration in which ceramic turbine blades undergo compressive, instead of tensile, stresses in rotation: https://www.exonetik.com/turbo Interesting stuff, but it's a huge challenge to bring entirely new jet engines, as TFA mentions, to certification and market.

Agreed, I like to have a "general use" environment to use for various one-off interactive python sessions, scripts or jupyter notebooks.

And no Pink Floyd fans.

Gapless is definitely a must for any music enthusiast, I believe.

I use Jellyfin btw, it does support gapless.

I'm not japanese, but in the english speaking manufacturing industry, I've heard it pronounced like "show slay", as you suggest.

Yes, idiot proof would be a correct translation. Or more literally, since "détrompe couillon" is a noun, an "idiot proofer", or "idiot-proofing feature".

Correct.

A 10% error can be calibrated out if it is constant (in practice it probably varies a bit with temperature).

But for measuring thermocouples or strain gauges, for example, 50 mV (your example) can be 100-500% of the signal, which becomes impractical to calibrate-out (due to maximum output levels, etc).

For these applications, Vos is one of the first things to look at. Another one is the temperature coefficient on the gain. High frequency noise metrics such as CMRR and PSRR are sometimes important if you're looking at high frequency signals, but most of the time mechanical phenomena don't have much interesting content above a few 100s of Hz, and high frequency PS or CM noise can be removed by a simple high pass filter.

Since December, Trump has repeatedly "joked" on social media about Canada being the 51st US state and Trudeau being a "Governor".

The whole thing is pretty stupid, but Trump is so chaotic that chances of bad things happening are feeling somewhat above zero.

> The "scientific" Python stack has horrible mixtures of C/C++/Cython

Don't forget a whole lot of FORTRAN :)

JuliaSim looks interesting! From my understanding, it's 100% proprietary/commercial, but built on top of the open source https://github.com/SciML/ModelingToolkit.jl?

I nominate Molex SL. 2.54 mm for easy fit on breadboards and such (EH is 2.5 mm), can fit multiple connectors side by side (just like "dupont" connectors), they have latches (molex KK, for example, has no latch) and many variants: wire to wire, wire to board, panel mount, shrouded and unshrouded. And they are pretty cheap and available (from digikey and co).

> Have you ever read large electronic schematics? That's basically it .. except all the important things have to be identified by text anyway, because it's a massive challenge to the imagination to come up with two hundred different pictograms.

As a mechanical engineer who works with Labview and Simulink, as well as more conventional code (python mostly), that is indeed a very good description. First glance at a large labview program feels very much like first glance at a large and complex electronics schematic. Lots of wire everywhere and you're not even sure where to start.

I think a nice "best of both worlds" approach is a graphical "high level" view which shows the flow of data, at least for "data transformation" kind of programs, and code for the low level logic (what actually happens in the blocks). Sort of like nodal editors in Blender and NLE apps. Fortunately Simulink makes it easy to drop in a Matlab function call, Labview not so much (need to get into C FFI or use a really old version of .net or something).

The thought I have about spreadsheets (might have read that on here), is that spreadsheets make the data visible and hide the code. Text-based programming hides the data but shows the code. I'm not sure what something that makes both code and data first class and visible would look like, but I'd be curious for sure (for engineering type applications at least). Best I've found so far (and what I actually for a lot of data processing tasks) is a Jupyter notebook making plentiful use of df.head() and df.plot().

> Things like MAVLink prove it very clearly.

Can you expand on the issues with MAVLink? I thought it was reasonably designed, as far serial protocols go.

That is specifically sigma-delta type ADCs: https://www.analog.com/en/resources/technical-articles/sigma...

The Vancouver SkyTrain also uses LIMs.

My first thought as a mechanical engineer is whether this could be useful for PID controllers. Getting a usable derivative value for the "D" term is often a challenge because relatively small noise can create large variations in the derivative, and many filtering methods (eg simple first-order lowpass) introduce a delay/phase shift, which reduces controller performance.

In the hakko line, fx-951 is the step-up which uses a heater and sensor in the tip (t15/t12 tips).

The alternative, for a hobbyist, would be something like this new iFixit iron, the Pinecil, Miniware TS80/TS100 or one of the variety of chinese irons from amazon and Aliexpress that take Hakko T12 tips (Quicko and similar).

On the high-end, professional side, it's JBC and Metcal. Expensive.

Same, the first thing I looked for is what tip it uses.

I want to like the miniware, pine, etc irons, but I'd really like being able to buy T15 tips from my local electronics supplier, who carries Hakko.

If the product isn't sucessful and/or ifixit stops producing tips for whatever reason, a perfectly good iron is effectively bricked.

It's called UART, to the best of my knowledge.

Can you expand on why you are so much against ARM?

nomacs can preview raw files on linux

https://nomacs.org/

Yep, I live in eastern Canada, and cars here typically don't reach end-of-life due to engine mileage, but due to the frame eventually being too rusted.

I'm really not a "truck guy", but it seems to me from the outside that the price of the F150 and similar pick-ups has been really jacked up since they are now a "status symbol" in many areas. Plus, the standard bed is super small and can't even fit a 4x8 flat.

If I were switching occupation to a plumber (or something) and looking for a work vehicle, I'd be strongly considering closed vans like Transit, Sprinter or Nissan NV. Or a plain old minivan as some have suggested. I hear many of them can fit a 4x8 with seats removed.

Nim's maintainer agrees with you I believe, and the API is as you suggest (volatileLoad and volatileStore): https://nim-lang.org/docs/volatile.html

However, under the hood, Nim compiles to C. So these are macros that typecast to volatile, does the read (or write), then casts back to non-volatile.

(Small plug for my nim project that is somewhat related to OP: https://github.com/EmbeddedNim/svd2nim)

From my understanding, the only thing volatile does (IIRC this is implementation specified as the standard is vague) is prevent the compiler from optimizing out reads or writes when it thinks they are "useless". That is, is tells the compiler "this memory location may change independently of that the code is doing, so you always need to read or write it when I say so".

Atomicity is sort of a different thing. You might need things like critical sections (disable interrupts) or memory fencing for the read-modify-write cycle.

The built-in nbconvert tool can already do that. Maybe not the most beautiful output by default, but you can give it custom CSS or latex template (for PDF output) via CLI flags.

Yes, unless there's a de laval nozzle inside that thing, which I wouldn't expect.

If you've ever used a compressed air gun from a compressor or at a tire fill station, it's also very likely choked flow, sonic exit speed.