Hacker Newsnew | past | comments | ask | show | jobs | submit | DazWilkin's commentslogin

I live in a community in the Pacific Northwest that was built in 2018 and (almost) every home (22/23) has (Carrier) heat pumps; for some unknown reason, the other has heated floors.

Many of us are proponents of heat pumps thanks to reduced costs and emissions *but* we've not had a generally good experience possibly (!) as a result of bad installation and definitely due to limited numbers of indoor heads (if I close my main bedroom door, the rest of my upper floor has no heating/cooling).

There's always someone in the community frustrated that their house is too cold/hot, that the condensation drains are blocked and water is running down an interior wall, that an indoor head or the condenser is having problems, or that there's unexplained coolant leak.

People moving into the community are inheriting issues with at least 2 homes having to augment/replace the system. To save breaking into the walls, this often necessitates putting the power, coolant and drainage lines on the outside of the house and then boxing the result.

We're saving money on monthly bills (probably; we don't have a comp) but many of us have spent quite some $$$ on maintenance and replacement equipment.


Looks like poor installation.

I've spent 1.5 years in a brand-new building with Mitsubishi heat pumps. It had some initial trouble with a faulty electronic component, but afterwards it worked quite fine, needing little if any attention.


If there are no consequences to bad behavior, bad people will behave badly.

None of these people will ever suffer any consequences for this.


Well done!

Having user-challenges with kubefor.ge.

Clicked "Deployment" and then tried "Create metadata node" but it errors:

Missing config in qA_PQ-QAe8tznselScKge Node qA_PQ-QAe8tznselScKge has no values configured.

And:

Overlapping Nodes Node "deployment" overlaps with "undefined".


Thank you! I'll double check the schema objects for metadata node, most likely some issues with how I have it defined.

For the overlapping nodes, I'll also throw an issue for both of those in GH :)

Did you like anything in particular or have a feature in mind that would make this better to you?

--- edit ---

For the metadata node warning, it was stating that the node is created but does not have values inside of it.

--- edit 2 ---

resolved the get.kubefor.ge/latest issue with: https://github.com/kubenote/KubeForge/issues/1 and removed undefined + improved warnings with: https://github.com/kubenote/KubeForge/issues/2


Same behavior when I run the container locally.

Issues with `get.kubefor.ge/latest`:

Manifest does not match provided manifest digest sha256:a4d6b4a9513289be1c1349afff46f7c87a5ac8513cbd8b66de350f26442d14bf

Works with:

ghcr.io/kubenote/kubeforge:latest

get.kubefor.ge@sha256:a4d6b4a9513289be1c1349afff46f7c87a5ac8513cbd8b66de350f26442d14bf


Not only are my AI chats more personal than my Google searches but with these false friends reporting this information back to Google's (and others') advertising engines, suggests to me that this will become a more accurate, more difficult to avoid and thus bigger business for Google.


Congratulations!

Having tried several times myself, I know first hand how difficult it is to make money from our things.

Well done you!


Podman uses Dockerfiles too.

Dockerfiles is the language for specifying a set of instructions for building container images.


It's not a very good one, but it is ubiquitous (it's also better if you remember to include the right syntax marker that enables heredocs):

    # syntax=docker/dockerfile:1
I suspect that the GP was really asking "why not use a different tool", like buildah <https://buildah.io>, buildpacks <https://buildpacks.io>, nix <https://nix.dev/tutorials/nixos/building-and-running-docker-...>, kaniko <https://github.com/GoogleContainerTools/kaniko>, ko <https://github.com/ko-build/ko>, bazel <https://github.com/bazel-contrib/rules_oci>, apko <https://github.com/chainguard-dev/apko>, or other tools.

Each of those has tradeoffs compared to Dockerfiles (I have no need for bazel, but if I did, then adding `rules_oci` might be a win-win, rather than using a Dockerfile). If I used Nix, then the Nix dockerTools would be a huge win (I don't use Nix). If I were shipping Go programs, `ko` would likely be a good baseline.


Buildah is the only serious alternative in my opinion.

You lose automatic layer caching, but in exchange you can use the same tools (RUN, ADD, etc) within a much more powerful shell environment.

I wrote a Buildah wrapper that uses a shell script harness to polyfill the familiar Dockerfile syntax while adding several extra goodies - mainly the ability to bake runtime arguments (mounts, ports...) into the image. Very handy!


Buildah's ability to mount the container in an unshare environment is pretty magical for copying stuff in and out of it.

That said, in the end I'd still rather build containers with something other than an imperative sequence of commands, so my heart is going to be forever with nix2container and bazel's rules_oci.


When I've used buildah and kaniko, I still handed them a Dockerfile.


It also happened 3 days ago!


This really resonates with me.

Your insight is helpful almost as much as knowing that other people like me are out there too.

I think (!?) I've finally let go of a project that I've been working on for a couple of years.

A key tenet of the project (which I frequently forgot) was that it was a way for me to learn|refine technical skills and to keep me entertained|occupied.

The project certainly achieved those objectives for me and I'm a better person for doing it.

Good luck to you and I hope you continue to succeed!


Insurers buy insurance (reinsurance) in an attempt to offload excess risk.

In your follow-up example, they could reinsure much of the $200B so that they're only liable for a small(er) part of the losses.

The calculation is thus whether they can pay the premiums on the excess (and accept reinsurers' contractual terms) and still make money.


Thank you!

My maternal grandmother lived with kidney disease and my mother and (maternal) aunt both had kidney disease too and have both had kidney transplants (ironically each from their partner).

A good friend had a kidney transplant too from her twin sister which means that she has negligible anti-rejection medications.

My mother's transplant was more than 10 years ago. She's had issues including, as a consequence of being immuno-supressed, cancer from Epstein-Barr virus (she recovered) but she's otherwise enjoying her 80s with her several grands and a great.

My father (her donor) continues to thrive and has had no obvious negative consequences to his life-saving gift.

They still bicker!!

My sister, cousins and I have our creatinine and potassium levels monitored.

I had an elevated potassium test recently and it's depressing to be reminded how fragile life is. In my case, a follow up test appears to indicate that the prior test was exceptional (and I think can be explained).

We have 2 kidneys but only one heart, liver etc. and so, while there's an evolutionary benefit, experience suggests that people do just fine with one kidney.

To every brave and selfless person who's donated an organ, you have my utmost respect and gratitude.

Fun fact: kidney transplant recipients generally have 3 kidneys: the OGs and the donated kidney


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: