bregma

My experience is it takes 100 hours to buck, split, haul, and stack the 7 or so cords of wood it takes to heat my house. A cord is 4 feet by 4 feet by 8 feet. The total time includes time it takes to sharpen the saw, and time it takes for trips to the gas station for gas for the saw and the splitter. Time for replacing the handle on the maul or the oil in the splitter is extra.

But that 100 hours is using a hydraulic splitter. Hand-splitting using a maul takes several hours longer. But it keeps you twice as warm: it heats you once when you split it and once when you burn it.

I got some burly maple ends that even my 22-ton hydraulic splitter can't handle. Toss 'em into the woods, let nature take care of 'em.

Ah, sweet summer child.

When the days you have to break the ice on the dog's water bowl in the morning come, you will quickly learn what kinds of wood there are and what you want to burn for heat.

For example, if you choose a lot of paper birch (it splits easily, lights easily, and smells nice while burning) you will quickly get to know all the local firefighters after all your chimney fires.

I don't burn softwood because hardwood is a much better fuel as a primary heat source, especially when you live in a mixed forest. Sugar maple, red oak, birch, and beech. Beech is the best: straight grain, good density, but less common where I live.

The trick to splitting hardwood, other than avoiding burls and knots, is to shave off chords around the outside of the buck. If you tried radial cuts or splitting on the diameter, well, best of luck with getting a season's wood split in one year. Chords around the circumference for about 50% of the buck, thenif you're lucky the core will split on the diameter.

Also, use a maul with fat cheeks and no edge rather than an axe. It's the right tool for the job.

The political right is obsessed with minimizing Type II error. They feel it's better to miss good research results than to have the wrong people performing the research or chasing the wrong ideas to start with (a false negative) and the further to the right they are on the spectrum, the more important minimizing the wrong people and ideas becomes. This leads to less discovery and successes because more research gets falsely rejected at the funding level.

The political left, of course, is the opposite and obsesses over Type I error. Accepting the wrong people and ideas is less important than getting good results. This leads to things like Lysenkoism, but also tends to reject less successful research, given the other checks and balances built into a healthy system.

Well, there is legislation before Committee to mandate open APIs that any accredited institution can use. As a consumer you will not be eligible, but you will be allowed to pay some third-party to pull your data from your bank and save it in their database, after which maybe they might allow you to download it in their proprietary format should they choose.

Me, I use plain-text accounting (hledger) that automatically imports the CSVs from my bank and categorizes transactions automatically, and I wrote some quick scripts using Python to import the PDFs from my brokerages and paystubs. It's not automated pulls but I only have a handful of accounts so it's really not a pain to manually pull statements once a month and run the import scripts. It takes me longer to reconcile everything to the penny then it does to do the imports, and it's a whale of a lot faster than manually entering through GNUCash. Plus, it's plain text so all you need is vim, git, and the command line.

It's not at all difficult if you have gained the basic survival skill of cooking. I mean, take a couple egg yolks in a double boiler, add the juice of a lemon, whisk until it's thick then add butter. 10 minutes and you can use a bowl over the pot of boiling water you're poaching your eggs in if you don't have a double boiler for your camp stove in the wilderness.

But that's still more of a hassle than putting the carton of that yellow plastic liquid in the microwave for a minute and a half. People will prefer their slops and the farmer brings it right to you; what could possibly be a better life?

Not only is it an ELF binary, but it is ironically a static ELF binary.

On QNX the process spawning is done by sending a message to the userspace process manager, which creates a new process table entry and queues up its initial thread. When its initial thread gets a timeslice its entry point may be the dynamic loader (as specified in the PT_INTERP segment) which then does all the dynamic linking as the spawned process or it might be some other entry point like with a statically-linked executable.

So on QNX, the spawned process does all the dynamic linking. The spawning process just sends an asynchronous message to the process manager and then gets on with things in a very deterministic manner as befitting a hard realtime system.

There's what's legal, and then there's what the border guard with a hemorrhoid flareup decides to do on the spot. One pain in the butt can cause you a lifetime of pain in the butt even if it wasn't the intent of any legislator.

Birth control was illegal in the USA until the late 1960s (other than condoms, which is what sailors used with prostitutes). It takes a while for changes to propagate through society.

Also, consumer credit was illegal until the same time period, and only legalized for people with vaginas in the mid-1970s. That alone might have made all the difference with marriage and fertility (which after all are only mildly related).

Imagine how your choices would expand if unlike your mother, you did not need to become Mrs. John Doe to be able to move out of your father's house.

Neither Rust nor Zig are appropriate at this time for certified functional safety. Given the definition of the languages is "it does what one particular implementation of its compiler, runtime, and standard library does at this time" it's not possible to construct a workable safety case for their use.

Enthusiam and neat ideas are not sufficient to certify a development tool for functional safety.

So C++ is "wrong" because it doesn't work like something that came along 40 years later and you used first?

The problem does not appear to be in C++.

There are two kinds of programming languages: the kind everyone complains about and the kind nobody uses.

Python3 is what, 15 years old?

C++ has std::sort() and std::stable_sort(). You should write what you mean, and you should know and understand your tools. Blaming the tool for your ignorance marks you as significantly less than an artisan.

I work maintaining the toolchain and language runtimes for a commercial safety-certified embedded operating system. I am deeply familiar with C and C++ because I live it and breathe it every day and have done so for over 40 years.

Most of our customers use C, probably for historic reasons but also because it is much much easier to reason about and that becomes very important when auditing for functional safety certification. If someone's life depends on your software, you really want to be able to reason about its correctness because orange jumpsuits enhance no one's complexion.

Many of customers are now using C++. From the problems they have reported, well, they just shouldn't. It's not that it is a bad language (it isn't) or that it is inherently unsafe (it really isn't: exceptions are safer than propagating return values as long as you use them in exception conditions, because not catching one will return you to a designed safe state very quickly, and RAII is the best thing since sliced cheese). It's that cutting and pasting from Stack Overflow, and now vibe coding, makes for massive codebases that are next to impossible to reason about. I now see a lot of problems from customers where my first reaction is "don't write code like that" and "you can write bad JavaScript code in any language, can't you?". While it butters my bread and I enjoy the language, I really recommend against using C++ for safety-certified embedded software. Stick to C.

ISO/IEC 14882 contains many uses of the word "deprecation", including all the sections of Appendix D that explicitly lists all of the deprecated and removed features of the language and library.

It was a new feature. Over 30 years ago now. Template metaprogramming was even featured in the ARM.

It's a matter of latency vs. throughput.

I don't know about the typical HN contributor but I personally lack the cash to but all the stocks in the S&P. There are 503 stocks tracked in the S&P 500 index. It would cost about 2.8 million USD to buy 100 shares (one board lot) of each if you were naive enough to weight your purchases that way. If you were to weight the stocks differently (eg. total market capitalization of each company) the amount would be higher.

Or, I can pick up 100 shares of an index ETF for a few thousand and have someone else do all the work for me including rebalancing and doing all the other required calculations (lot tracking and cost basis calculations etc.).

Drones are haploids so probably nothing. I suspect you'd need the full chromosome set to get the full developmental effect of the royal treatment.

Given that when a hive goes queenless the workers start laying eggs including in the royal chambers they're desperately building, and since the workers are unfertilized all of the eggs are haploids that hatch into drones, it has probably happened many times throughout apian history. No drag queens have been spotted.

When you get down to it, there is no better way to display text than to use a text display.

No amount of cartoons or colourful bouncy animation of pictures on the screen can replace simply displaying text when what you need to do is display text on the screen. And it turns out that text is a really good way to display information.

A picture is worth a thousand words but why would you use 1000 words when only one or two will do?

A thrombus is a blood clot in a distal blood vessel. When it becomes dislodged it becomes known as an embolism which, if it settles in a pulmonary or coronary artery, can rapidly become fatal. The chances of this happening are greatly increased in the elderly and those with known circulatory problems.

C'mon litle guy. You can make yourself famous. Be brave and let go of the wall of that leg vein. Say good bye to that comfy cankle and enter into your full glory.

I have 3 weeks left, but outside of work I've already been divorced from anything technological invented this century. I've been living in a log cabin in the woods for over a quarter century. This essay does hit home.

21 days left. I don't plan to look back.

> I reckon most folks have made a git oopsie and needed to re-clone a repo at least once in their career.

And I recon this is the default workflow for most people most of the time.

When I worked at a Linux distro I worked with one device maker who told me in confidence that 90% of their revenue came from Linux-based shops and they only needed a one-person support team. They had a 20 person support team for the remaining 10% of revenue coming from Windows-based shops.

Where I work now the top 10 customers are Linux shops. They probably account for 80% of our revenue. The remaining hundreds of customers are more evenly split between Linux and Windows.

So I guess it depends very much on what industry you're in. For consumer games it might be Windows, but outside of financials and administrative realms and into the world of embedded it's a heckuva lot of Linux. Support costs tend to be lower, and you really only have to target Red Hat and Ubuntu.

It's because crowing about Rust is like sending dick pics. I suspect it's the same part of the brain responsible with the same neural pathways stimulated.

If one woman can produce a baby on 9 months, why can't you get 9 women pregnant and produce a baby in one month?

    There are more things in heaven and earth, Horatio,
    Than are dreamt of in your philosophy

You've probably been churning out possibly malformed code for years. Now you're becoming aware of your shortcomings. This is usually considered the transition from intermediate- to senior-level programmer.