zznneezznnee

Before you compare your work to that of others you really need to know how much time was spent on both and normalize accordingly.

Additionally, many individuals in our industry have zero life outside of hacking on their software. It's difficult if not impossible to be competitive with someone spending every waking hour practicing their craft without doing the same.

Thanks for sharing this link, in lieu of watching that I wouldn't have had any idea Phil stole SEA's code to create pkarc/pkzip.

I still remember running the self-extracting pkz204g.exe on MS-DOS, and never heard of SEA or encountered their software. That's really unfortunate.

I imagine it was just a product of UNIX/academia being somewhat isolated from the general public/BBS world. Before GNU/Linux basically nobody using PCs had access to UNIX-like systems, and probably wouldn't have known of tar's existence.

My older sibling exposed me to tar indirectly by granting me access to their university-provided dialup UNIX account where they ran `elm` for email access, and this happened long after I had been using BBSs for years with my PC.

Never saw a tar file in all my years of PC-based BBS usage. GNU/Linux and Freebsd are largely responsible for the general public accessing *NIX-like systems. BBSs (and their file sharing) were a thing before those existed.

This is nonsense, a NACK is nowhere near the table-flip you're portraying here.

The kernel maintainers don't necessarily want your code.

Additional shit in mainline increases the maintenance burden. If the code isn't putting upstream maintainability above all else in its implementation, then it's generally not getting merged unless someone wasn't paying attention or some other forces compelled an exception.

Alex's first reply reads like he's willfully ignoring that aspect of the NACK. It's not a coding style issue, it's a HAL issue. Upstream isn't interested in maintaining a HAL and living with the impedance mismatch from day zero. The driver can stay out of tree. This is just about code getting into mainline.

I'm personally very happy to see the gpu subsystem maintainers paying attention and having the maturity to know a fool's errand when they see it.

Anyone know what the status is of CastAR? Haven't seen any updates for a while now...

This dichotomy of depressives vs. optimists seems flawed to me. My optimism is often what creates the unmet expectations which lead to depression.