453 karma · joined February 9, 2021
In my comment I was using the former.
I'm not really sure what you're on about me "misinterpreting" something. The author of the article claimed to not have personal criticisms, and I was pointing out that there's a standard interpretation of those words that is true.
Also I learned nothing about Jarred's life from this post, so I don't understand that point. That he lives or lived in San Francisco I guess, and didn't go to university?
I don't know what you're getting at with your final paragraph, I feel like he's in a pretty good position to assert something he probably did or did not do.
I've realised from the comments under this post that many people seem to desire some sort of performative "professional" communication style from people above all else. I don't know why people care about this so much and I don't think I care to know.
I'm sure Andrew could've switched out every word in the post and still conveyed the same meaning, and perhaps offended the peanut gallery's sensibilities a little less, but why should he?
In the example I was originally replying to, suppose Andrew had instead said "Jarred showed poorer than desired management abilities" and "Employees disliked working at Oven". Approximately the same message is communicated, a little watered-down maybe, but who's gaining from this tone-policing? Certainly not us, the readers. And I don't see how this affects how "professional" this is, unless "professional" is just performative nonsense and nothing to do with the substance of the text?
So that's a no, you won't make the attempt to engage with it with any other frame of mind?
>> Now I see him in the same category as a Musk like character.
Do you not see this as an overreaction? Andrew writes one (perhaps overly) blunt article about someone who publicly attempts to tarnish his project's reputation and you view it the same as the worst living human?
It's actually intended that your function doesn't try too hard to validate it's input types, and just that it will malfunction and crash when it gets something it doesn't know how to handle, because the supervision tree will rescue it and your program can continue, albeit without whatever input caused the malfunction.
This obviously isn't ideal for many types of software, but for complex backend servers and other long-running operations it works really well.
Of course this is not a guarantee to eliminate bugs, but it's a factor that reduces them more than you'd think when coming from a different programming paradigm.
Their support has been very responsive and helpful every time I've contacted them so I'd be surprised if they wouldn't have helped the GP.
It does seem like most people completely ignore the obvious harms caused by AI when talking about using LLMs for programming, as though somehow it is disconnected from the other deployments of the technology.
Despite the fact I have contributed only a small number of PRs and bug reports to Ghostty, and I don't think my absence would be notable to the maintainers, I still feel compelled to boycott the product unless Mitchell clarifies his stance on Vercel's alignment with the Israeli government.
I'd always hoped that Mitchell would be the odd exception to the disagreeable politics of the billionaire class. I'd previously hoped his ongoing association with DHH (and his abhorrent views[1]) was just a result of prior friendship and not an indication that he'd aligned himself with the ruling class. Alas, this is certainly not a good look.
[1]: I was going to link a specific blog post here but upon investigation I was blown away by how awful his entire blog is. The titles of posts are bad but please read past each one to discover a whole new level of awful. https://world.hey.com/dhh
The video ends in a place where I suspect even further advances could still be made.
I don't even disagree with the post, I just don't like seeing shallow dismissals where someone could've actually put effort in to make a point. So I did the same.
In my experience, ergonomics in Zig means something other than ergonomics in many other languages. In plenty of languages, ergonomic code is basically just writing as few characters as possible and being able to achieve complex logic with little boilerplate. In Zig, it feels good to be able to compose the conceptually simple language features into an optimal solution to your problem, even if it results in code that is maybe not aesthetically pleasing on first glance.
I'm not going to declare that this solution is ergonomic or not, you can't always tell just by looking at Zig code whether using it is ergonomic, but by that same logic we shouldn't dismiss it off hand.