Oh wow. So are you lined up to be a long haul driver then? Surely you are manly enough. We have a huge shortage of drivers right now. Maybe you should talk to a trucker a little bit. The job they do is important and they are proud of what they do. But they are treated horribly.

Yes of course we're talking about BEV trucks. What does that have to do with reefer trailers?

What are you talking about? All the major manufacturers are currently selling electric trucks of that size and range in Europe. There's a guy documenting daily long haul driving in Europe with electric trucks. Google for electric trucker or elektrotrucker.

And to head off the inevitable comments, yes European trucks are as big or bigger than American ones. And yes the distances driven are just as long as American routes. Infrastructure for changing is much better than in the US of course, and improving.

I use GitHub as a simple public-facing repository, that part is pretty solid. I do all the work, including merging and actions, locally. I simply don't use GitHub's pull request mechanism. I did discover that if someone does submit a pull request, I can do the pull and merge locally and when I push back to my GitHub repo, GitHub automatically detects the pull request was pulled and closes it without using any of the web interface.

It depends on how you use git. My primary working repositories are all local, and not readable or writable by anyone else (nor should they ever be). I push my working branches to GitHub regularly, so others can pull from them. My collaborators on various projects do the same thing. I could push anywhere that's appropriate. A corporate or publicly-accessible Forgejo instance, GitLab, or even just a folder on my web server.

In my naivete I thought this sort of local repo, public repo split is how git was designed to work. Pull requests could take any form, really, provided commit messages meet your requirements (this commit closes issue #foo), and it's simply a matter of git pull. Sure I have to add remotes to my local git repo, and possibly create local branches to review the pull request commits, but that's not too hard. git gui's like gitg come in handy for navigating numerous branches and remotes. The author could have done that in the time it took him to write a complaint about GitHub. And like I said, github actions can be made to run locally in each collaborator's local repo.

git is decentralized. Development need not stop when GitHub has problems, and it should be trivial to move off of GitHub if that was necessary. Of course, maybe I just use git wrong. And sure I can understand that corporate development doesn't really mesh that well with git's distributed model, hence the use of GitHub as a crutch.

While I understand his frustration, this is git. Your repo is always local so you can always work with it without relying on a central service. In fact there are ways to run GitHub actions locally. And it can pull and merge from your local command line. I get the convenience of GitHub. But if you're choosing to be dependent on GitHub for everything, then I can't really blame Microsoft for your inability to do work.

Possibly, much like how many small farms hire out herbicide application. The biggest issue is that the electric weeder is slow and requires multiple passes. And all farmers require weed control about at the same time. But one benefit to the electric weeder is, depending on the crop, it could be applied much later in the season to control late flushes of weeds. Herbicides will injure crops that are past a certain stage of growth. The later in the season, the more risky it is to apply herbicides.

Not quite sure where your numbers come from. Glyphosate is typically between $5 and $6 CAD a litre, and a applications are anywhere from 0.3 to 0.7 l/ac (messed up units, yes i know but that's what we use). So chemical cost is extremely low, $2 to $4 per acre not counting labor and fuel. Application is extremely fast, more than 100 acres per hour.

The electric weeder is expensive, slow and costly to operate currently. But I'm hopeful this will improve. You're right it's a prohibitively expensive pill to swallow currently.

Definitely adjuvants and surfactants are a big health unknown. Glyphosate itself seems quite safe. Three generations of farmers have used it and have been exposed in far higher amounts than many of these sick people blaming their cancer on glyphosate. But although pesticide active ingredients are highly regulated and tested for safety, adjuvants and surfactants are not. Many of them contain organic solvents that could be carcinogenic. Manufacturers need not tell you anything about their formulation. It's a real wild west.

As a farmer who uses pesticides it boggles my mind that Bayer is selling diquat to consumers! Diquat is a lot more toxic than glyphosate (but a lot safer than paraquat).

But diquat is safer to use it around trees as it won't kill them. It's a contact chemical that burns leaves (quickly). It's not translocated into the plant's roots, so if the roots continue to grow it won't kill the plant. If defoliating the poison oak will kill it, then diquat will work well. Be sure to wear PPE and don't let it on your skin and don't breath in the mist. Always wear a respirator.

These days I get a lot of mileage from git bash. And windows finally has a real terminal emulator instead of that really limited console window.

Seems a bit silly to deliberately not include solar as a part of electricity generation data centers need. And with the billions of dollars expected to be generated by these data centers, large battery installations make a lot of sense. And indeed this would be happening but the trump administration has essentially forbid them from doing it. I know if one large company that was planning to involve solar but trump "encouraged" them to just gas instead.

Regardless of the power source data centers are massive heat producers, dramatically heating local environments. Now with big noisy gas plants polluting it's a double whammy. Very forward thinking.

The FCC has no authority to mandate and enforce net neutrality yet they do have authority to ban imports of routers. Very interesting.

Rating the truth as "troll?" Wow. really classy.

Most computers didn't have scsi at the time. This was before USB so Parallel port it was. And on those days most people had parallel port printers. So you plugged the printer into the zip drive. I can't remember what the limitations where. I'm sure you couldn't print at the same time as accessing the drive. Linux even supported it.