$Work pays for GitHub, so the implicit solution offered is "take my money and make your service reliable"
Readit Newsjpitz commented on Days since last GitHub incident github-incidents.pages.de... · Posted by u/AquiGorka
It would be great to have an alternative to Terraform that uses a bit more advanced provider (at last for AWS). Does OpenTofu use that same provider?
The providers for tofu are by design the same as for terraform.
Also, for large providers like AWS, GCP, Azure, etc - these are often largely authored by the hyperscaler themselves, for better or worse.
jpitz commented on Removing juries: 'A move towards an authoritarian state' theguardian.com/law/2025/... · Posted by u/binning
When I see juries in American movies it always seems like a bit of an joke and manipulating them is a common plot theme. Just very random, the opposite of what I expect from an justice system. Many non-authoritarian states don't use them. Most of Europe and India for instance.
I don't think the boring reality of most jury trials would make for an interesting screenplay.
To every commenter offering incredulity or sarcasm at the apparent obviousness of this advice:
A great swath of us did not possess the social intelligence to arrive at this conclusion independently upon our arrival in the workforce. I didn't. I got lucky.
It's really frustrating when you need to fix old code and the dev environment is gone. Some of that stuff just isn't replaceable, or it's a whole bunch of extra work, as you had to do to get back to square one.
It isn't 100% clear from the Voyager documentaries how much of the dev environments were destroyed/lost between projects being canceled. I tried to get the Voyager source but it isn't classified as a government record that would be subject to FOIA, which is frustrating. (nothing to do with security, just IP)
In my experience, pretty much anything relating to spaceflight is gonna be lumped under ITAR and restricted from general disclosure.
jpitz commented on Are hard drives getting better? backblaze.com/blog/are-ha... · Posted by u/HieronymusBosch
jpitz commented on Software update bricks some Jeep 4xe hybrids over the weekend arstechnica.com/cars/2025... · Posted by u/gloxkiqcza
I own a Jeep Wrangler, and you're right the electronics are terrible. The rest of the vehicle is really solid though. The only problems I've had with it in three years are electronic in nature. And I've really pushed it to the limits: Colorado Passes, Utah Dessert, Montana backroads. I drove it to the Arctic Ocean and back on the Dempster.
Still there is no excuse for how terrible the electronics are in Jeep / Dodge (I'm assuming all Chrysler) vehicles. And it's been that way for decades.
I owned a Jeep 4XE, and I was glad the day we sold it, and I'm doubly glad today. The electronics and software were crap, and the powertrain was simply insufficient. At one point, they issued a notice that amounted to 'it might catch on fire, keep it away from your house.'
That's the point: non-dependant tasks can run concurrently in Airflow. In sh/BAsh/dgsh dependant tasks can also run concurrently, as in tar cf - . | xz.
Ok. thank you!
Apache Airflow solves a very different problem. Its DAGs are static dependencies between sequentially executed processing steps, whereas the DAGs of dgsh express live direct data flows.
Do you mean to say that two non-dependant tasks in an Airflow DAG aren't able to concurrently execute? Thats not my experience. I'm also confused by the use of 'static' in this context.
In charity, I think there is actually a product opportunity for improvements to the standard shell histfile.
I've often been frustrated by my history not being easily shared between concurrent terminals, difficulties in searching, and lack of other metadata such as timestamp, duration and exit code.
Although I suspect this repo was vibe-coded so far, I think there's a promising problem to solve here.
Then you should look at https://atuin.sh/ although I am not certain about exit code.