If gasoline engines burned their fuel as efficiently as possible, they would produce three by-products: water vapor (H2O), carbon dioxide (CO2) and nitrogen (N2).
Unfortunately, engines do not run perfectly, and as a result, they also produce three by-products commonly referred to as the "terrible trio" of automotive pollutants. This trio includes the following:
* Carbon monoxide (CO) – An odorless, tasteless, poisonous gas, carbon monoxide can cause a variety of health problems and even death. Many urban areas experience critically high levels of carbon monoxide, especially during the cold winter months when engines take longer to warm up and run cleanly
* Unburned hydrocarbons (HC) – Responsible for causing a variety of respiratory problems, unburned hydrocarbons can also cause crop damage and promote the formation of smog
* Oxides of nitrogen (NOX) – Like unburned hydrocarbons, oxides of nitrogen cause respiratory problems and promote the formation of smog
It’s impossible to install XCode without an Apple account. It’s only distributed through the Mac App Store, and downloads from Mac App Store require an Apple ID. And even XCode beta downloads are locked behind an Apple login.
You can install XCode CLI dev tools without an Apple account, which comes with clang and swift for example. With this, you can build most Mac software, but I don’t think you can run Swift tests without a full XCode.
As the sibling comment notes, you can install GCC/llvm and whatever other open source tools and build Mac software without full XCode.
You can also install Apple container support without an Apple account.
Xcode is also available as a standalone download from developer.apple.com, which requires an account too, but at least it's way more reliable than downloading from the store.
It’s because when placed inside the engine bay, the large wiring harness is shorter, which is not only cheaper, but also shorter wiring helps with the consistency of electrical timing and reduces noise.
Yes they do. They can tolerate engine bay heat, but not exhaust heat. They are usually shielded from getting soaked.
Some Mazdas put the metal-cased engine computer in a plastic air box that feeds cold air from the front, to help ensure the engine computer stays cool enough.
In general, I believe the cooling airflow from the frontal air and the cooling fans keeps engine bay in check.
Yeah, on the Cummins the ECU is mounted on the intake side of the engine away from the exhaust and turbo and toward the front right under the fuel injection pump so it gets lots of cooling air.
This thread is interesting to me 'cause I'm also a software guy and recently took a job dealing with building fighter jets and the amount of engineering going into the wiring and computers on those things is insane. It's been a very interesting learning experience.
> If it's so bad for gamblers, why don't they stop?
Because harm does not guarantee control.
When it becomes compulsive, it’s not a simple cost-benefit choice anymore. People can know it’s hurting them and still feel driven to keep doing it.
The dopamine rush of gambling means the brain can get stuck chasing relief, hope, or reward, despite also knowing that it is destructive.
> If gambling orgs do something that you know causes harm, why isn't the a legal sense of responsibility?
Because it’s not that easy to prove responsibility in the face of powerful money lobbying and victim-blaming. Shame and stigma around addiction means people don’t come forward. Freedom argument comes in that not everyone who gambles is an addict, so restricting it takes freedom away. The same argument is used to push the personal responsibility angle.
Ultimately I think the way the gambling orgs cover their ass is by advertising gambling addiction helplines and adding small disclaimers to call those lines if you have a problem: “that’s it, legislators, we are clearly giving them the tools to help themselves, and that shows us exercising responsibility. Bombarding gamblers with offers is simply marketing and creating engagement for our business, you can’t make that illegal.”
Do they have moral responsibility to not exploit addicted gamblers? I would argue, yes, they do. But unless you prohibit all gambling marketing, how would you accomplish this moral responsibility even if the gambling company agreed it had it? It’s not like addicts identify themselves or that you can filter your marketing easily to people without problems. This is why the solutions have been on outlawing the whole thing, because it’s really hard to operate as a business without the societal cost.
I disagree with the downvotes, but let me put it differently: if you don’t understand, have reviewed and be ready to own all of LLM output (the thoughtful part), then you aren’t owned the time to read them. If you didn’t try to reign in the verbose slop that’s the default for LLMs, I don’t want to read it.
Maybe the poster is running a local LLM.. you’d think that a SOTA model would have surmised that an overnight MacOS upgrade can only be a minor version.
Apple container CLI configures internal domains (`container system dns`) by adding an internal resolver and it worked for me when I specified an actual domain previously handled by external DNS and it showed up as a custom resolver.
Your AWS backup snapshots must go one-way (append-only) to a separate AWS account, to which access is extremely limited and never has any automated tools connecting to with anything other than read access. I don’t think it costs more to do that—-but it takes your backups out of the blast radius of a root or admin account compromise OR a tool malfunction. With AWS DLM, you can safely configure your backup retention in the separate AWS account and not risk any tools deleting them.
Terraform is a ticking time bomb. All it takes is for a new field to show up in AWS or a new state in an existing field, and now your resource is not modified, but is destroyed and re-created.
I will never trust any process, AI or a CD pipeline, execute `terraform apply` automatically on anything production. Maybe if you examine the plan for a very narrow set of changes and then execute apply from that plan only, maybe then you can automate it. I think it’s much rarer for Terraform to deviate from a plan.
Regardless, you must always turn on Delete Protection on all your important resources. It is wild to me that AWS didn’t ship EKS with delete protection out of the gate—-they only added this feature in August 2025! Not long before that, I’ve witnessed a production database get deleted because Terraform decided that an AWS EKS cluster could not be modified, so it decided to delete it and re-create it, while the team was trying to upgrade the version of EKS. The same exact pipeline worked fine in the staging environment. Turns out production had a slight difference due to AWS API changes, and Terraform decided it could not modify.
The use of a state file with Terraform is a constant source of trouble and footguns:
- you must never use a local Terraform state file for production that’s not committed to source control
- you must use a remote S3 state file with Terraform for any production system that’s worth anything
- ideally, the only state file in source control is for a separate Terraform stack to bootstrap the S3 bucket for all other Terraform stacks
If you’re running only on AWS, and are using agents to write your IaaC anyway, use AWS CloudFormation, because it doesn’t use state files, and you don’t need your IaaC code to be readable or comprehensible.
I’ve been using scroll back search for 15+ years with Terminal.app and iTerm2, and there’s no way that’s not the job of the terminal. You don’t know how good that is until you use it.
It’s a shame that version 1.2.x got abandoned and didn’t receive any important bug fixes. That has severely cut my trust into this project. It’s been over 4 months since the last 1.2.3 release, so the memory leak when using Claude is not addressed, my Ghostty crashes are not addressed (crash reporter doesn’t work), I don’t even bother looking at the issues anymore, as I know I am not getting the fixes for a long time.
And I’m not running a critical piece of productivity software on a nightlies channel!
I'm not doubting your personal experience, but I find the crashes you mentioned surprising; I have never once, since v1.0.1, had Ghostty crash. Tbf I use it with tmux, so I'm not exercising some of its capabilities. But with tmux, I have at any given time 5-7 sessions, each with 2-5 windows, some with panes.
Datapoint: I’m running nightly now because the latest 1.2 release has a known crash-on-wake bug when disconnecting an external monitor. Accordingly the issue tracker it was fixed months ago, but it’s not in a release. The nightly is stable though.
Didn’t realize how may projects use libghostty, will try cmux one of these days.
reply