Passing of Joe Mancuso(github.com)
github.com
Passing of Joe Mancuso
https://github.com/MasoniteFramework/masonite/discussions/853
18 comments
I suspect, based only on approximate age, timing of his death, and location, that this is the same guy: https://www.gofundme.com/f/in-loving-memory-of-coach-joe-man...
No mention of the software work, but he sounds like a pretty upstanding guy and a huge loss to his family and community.
No mention of the software work, but he sounds like a pretty upstanding guy and a huge loss to his family and community.
I see he has airborne patches in those pics. My friend that served in Afghanistan developed two distinct and simultaneous brain tumors (ultra rare). I suspect it was the burn pits. He told me how he was burning hundreds of iPads and everything electronic in open pits there as they were pulling out and that the smoke screwed him up (he told me shortly after getting back). Then ten years later he's diagnosed with the brain tumors (now).
Burn pits? Burning iPads? Is this standard procedure? Just curious.
Just a reminder how responsible healthy people can just go early.
So easy to forget
So easy to forget
Yeah or how wars are...terrible for everyone?
Good find! Profile pics match as well.
This is a lovely message, I hope I get a message like that posted on my open source project when my time comes.
I've always felt like the code I write is a piece of myself; a monument to leave behind for others to admire and interact with once I'm gone.
For me, software development creates an unmatched feeling of alignment. The idea that you could be dead and still share this feeling of alignment with others from beyond the grave is uplifting.
I suppose some people could say similar things about artworks, films or books. For some people, it's code.
Many people appreciate beautiful art, films, books, buildings even; but few people appreciate beautiful code. I think it's partly because most people have never seen beautiful code and partly because beautiful code doesn't pay the bills when maintenance work is billed by the hour... Probably why it's rare to begin with; though generally, open source provides a refuge from this by removing (or reducing) the financial incentive.
I've always felt like the code I write is a piece of myself; a monument to leave behind for others to admire and interact with once I'm gone.
For me, software development creates an unmatched feeling of alignment. The idea that you could be dead and still share this feeling of alignment with others from beyond the grave is uplifting.
I suppose some people could say similar things about artworks, films or books. For some people, it's code.
Many people appreciate beautiful art, films, books, buildings even; but few people appreciate beautiful code. I think it's partly because most people have never seen beautiful code and partly because beautiful code doesn't pay the bills when maintenance work is billed by the hour... Probably why it's rare to begin with; though generally, open source provides a refuge from this by removing (or reducing) the financial incentive.
> Many people appreciate beautiful art, films, books, buildings even; but few people appreciate beautiful code. I think it's partly because most people have never seen beautiful code and partly because beautiful code doesn't pay the bills when maintenance work is billed by the hour... Probably why it's rare to begin with; though generally, open source provides a refuge from this by removing (or reducing) the financial incentive.
I think there's a a bit more of fundamental difference. For art, film, and books, the output isn't really intended to be functional as much as aesthetic. Buildings do also have function, but they're also visually striking even to those who aren't architects. Software usually has some functional goal beyond just aesthetics, which for most people makes the code a means to an end rather than the end itself. Most people generally don't spend a lot of time appreciating the individual pigments of a painting or the engineering behind making the skeleton of the building that ensures it stands up either.
I think there's a a bit more of fundamental difference. For art, film, and books, the output isn't really intended to be functional as much as aesthetic. Buildings do also have function, but they're also visually striking even to those who aren't architects. Software usually has some functional goal beyond just aesthetics, which for most people makes the code a means to an end rather than the end itself. Most people generally don't spend a lot of time appreciating the individual pigments of a painting or the engineering behind making the skeleton of the building that ensures it stands up either.
I am just hearing of Masonite through this post, unfortunately (RIP Joe.) Now I am interested in it for a personal project I've been thinking of. Will development continue for this and are all the pieces in place to keep this project alive or will it fade to dust now?
It's MIT licensed. So just use it if it interests you.
He looks so young in the github profile picture.
My condolences.
Reminds me that life is short. We should all be thankful and make the most of what we have.
Reminds me that life is short. We should all be thankful and make the most of what we have.
>Paying my dues to the dirt
Morbid humor is underrated. RIP Joe.
Morbid humor is underrated. RIP Joe.
Phew, pretty young guy
Thanks for including the context in the title.
RIP, Joe
RIP, Joe
But the tone of this message from his peers and the fact that this man kept working and contributing to open source (and software in general) until the end is deserving of more than 0 comments on hn.
My condolences to the family, friends and best of luck to the rest of the team that is working on (t)his framework.
RiP Mr Joe Mancuso.