• 0 Posts
  • 362 Comments
Joined 2 years ago
cake
Cake day: July 31st, 2023

help-circle




  • The goal of the healthcare system should be to treat people.

    The goal of a good healthcare system is to treat people. The goal of ours is to treat the rich to another yacht. Healthcare providers bill far above cost for profit, knowing that either the insurance or the patient will have no choice but to eat the cost. Insurance providers use high healthcare costs to justify high policy prices and then do unethical shit to avoid paying out.

    The hospitals make money. The insurance company makes money. The shareholders and corporate owners make money. The people needing healthcare get screwed.

    The system is, unfortunately, working as intended for those who benefit from it being the way it is.





  • Sure, but knowing ICE took your kid doesn’t really do much to help get them back.

    ICE is now an extrajudicial secret police with even less oversight than the actual police. Even if someone knows ICE kidnapped their relative, nobody in the current administration is going to hold them accountable if they decide to lie and say “no we didn’t”. It took months to get back Abrego Garcia, and that was with the public eye on the situation and the entire Democratic Party pressuring them. For every one Abrego Garcia, there are thousands of people who are still unjustly locked up in a concentration camp.



  • One option is to use embedded structs:

    type UnmarshalStruct struct {
        Foo string
    }
    
    type MarshalStruct struct {
        UnmarshalStruct
        FieldYouDontWantUnmarshaled string
    }
    

    When marshaling, you would marshal MarshalStruct. Because UnmarshalStruct is embedded, json.Marshal automatically includes all the fields from UnmarshalStruct.

    When unmarshaling, you would unmarshal UnmarshalStruct and then create a new MarshalStruct like this:

    var unmarshaled UnmarshalStruct
    err := json.Unmarshal(&unmarshaled)
    if err != nil {
        panic(err)
    }
    
    return MarshalStruct {
        UnmarshalStruct: unmarshaled
    }
    

    Although, if I may ask: why do you not want a field to be unmarshaled? You could always just set it back to the zero value after unmarshaling, which is a lot easier of a solution.








  • Look, I’m not saying the wheel is wrong. It rotates, but what if two people try to turn the wheel at the same time, in opposite directions?

    What if—instead of risking misuse of the wheel—we have a my_wheel::Wheel, which only one person can rotate at any given time? The multiverse could enforce this safety at compile time by making it impossible for there to exist a universe where two people both think they own the right to rotate the wheel. In fact, it could even make it impossible for me to lend out the wheel to more than one person at a time.

    And, maybe… we could make the wheel even better. Cars rest on top of wheels, sure. But what if I wanted to make a car that rests on top of other cars? If we rotate the super-car’s wheels, we don’t want to make the sub-cars flap around—we want the sub-car wheels to rotate. It would be more future-proof to make a Wheel trait, then to make RubberTyre implement Wheel. Then, if we ever needed to make cars into wheels, we could have them also implement Wheel—but delegate the responsibility of rotating to their own wheels.

    In fact, we should make it into a whole library. Our other projects could need wheels. Mr. Mittens might need them eventually!