Childish or no, anti-AI sentiment is ubiquitous and growing. From a PR perspective there’s a lot to gain in the short term by picking the “anti-AI” lane. And you can always change your mind later.
Surveys show that 60% of US adults don't like it which means 40% either don't care or do. I'd advise not getting your ideas about sentiment towards it from places like HN which are very biased and unrepresentative places of anything. I find the anti crowd increasingly to be hateful and close-minded and it is disappointing because I have a lot of friends in it. There's a moral puritanism which gives people feelings th…
The post has a lot of incel "well you're ugly and noone wants you anyway" energy
I think the article kind of gives you the energy you enter the reading with. My take away was closer to "This is what we tried, this is the sentiment they gave back, then this is what happened, here's what I think of Jarred's way of working, glad they now use Rust, good riddance", but then I also apply this slightly unholy strategy of applying charitable reading when reading personal blog posts, and I worship neither…
>> I think the article kind of gives you the energy you enter the reading with.
No, not really. I know nothing about either of the people involved, and after reading the article I came away with an extremely negative opinion of the author. They are using their position as the leader of a language to attack and denigrate someone who used that language for years, donated to it, and eventually decided to move on.
> You can argue whether we need the term "transpiler," but a source-to-source compiler is a compiler. That's true today, but compiling was historically was defined as getting source code (human readable) to bytecode (machine runnable without an interpreter). Some people didn't like that definition, and consequently the waters have been murkied. Just like with eg crypto. Or real time.
How historical? Compilers that have translated from a source language into C and have left the C-to-bytecode translation to another compiler have been around for a long time, as have compilers that translated from a source language to Assembly
I'm not sure what your point is, we all already acknowledged that people have been using the term differently, consequently changing the definition of the word over the years
The Fuzzilli PR was merged on Nov 20. The acquisition was announced on Dec 3. A big holiday was in the middle. The teams no longer interacted after the acquisition, and in prior interactions the Bun team would've been correct in saying they weren't fuzzing. So Jarred isn't wrong, and Andrew also isn't wrong.
Andrew was wrong. He stealth edited his post to hide it. https://news.ycombinator.com/item?id=48854921
I'm aware he edited it, but the original version isn't wrong, either. Just like Jarred's
> We fuzz Bun's runtime APIs 24/7 using Fuzzilli, the JavaScript engine fuzzer used by V8 & JavaScriptCore
isn't wrong, even though that was only being done for the last 5-6 months of Zig Bun, and not the previous 5 years when they were accruing all of their tech debt.
> Two, I actually don't have any personal criticisms of Jarred That’s quite a statement to make at the end of a post that seems to contain little else…all just thinly veiled. Saying someone has „beginner energy“ but reframing it as a faux positive (this person fails and thus learns) Or saying the grapevine says someone is a „stinky manager“? Basically I’m not saying this person is bad it’s just that I need to bring u…
I'm quite confused by this. Is calling someone a "stinky manager" a personal attack? It's funny that we can't differentiate the person from his "job". I work with some shitty managers, but I don't hold it against them on a personal level...
Man these are some impressive mental gymnastics... yes its an insult, made very public. It, and the rest of the insults, are very disrespectful and reflects very poorly on andrew and paints him as petty and childish
But it wasn't full of praise for Zig. It specifically pointed out that his project written in zig was full of memory safety bugs, and said that there was no way to get around that if the project stayed with zig. It's ludicrous!
He never said impossible, just hard. But how is this news? Memory safety bugs are one of (if not the) main source of bugs in C/C++ and also Zig, and Rust's main claim to fame is that it makes it easy to catch these issues at compile time. I feel his criticisms of Zig are fairly uncontroversial.
Memory safety is a source of bugs in languages without garbage collection and/or whatever rust does, however memory safety is not THE source of bugs. If it were then we'd expect code written in JavaScript or Python (memory safe languages) to have zero bugs, and that's definitely NOT the case. When you get the hang of C and C++ memory bugs are not very common compared the normal bugs that all software has. They still can happen but people have gotten the idea that every C program is riddled with them without seeming to realize that code written in C is the foundation for almost everything and has been for a long time. Compilers, operating systems, device drivers, network stacks, core utilities, even games are all written in C or C++ and we are not drowning in killer memory related bugs.
There are astute comments about the post's tone elsewhere in this thread[0] But this killed my hopes for Zig. The drama is fun, and Andrew is maybe even admirable in his earnest, but this just isn't the kind of professionalism needed for a serious project. I know that's boring and uninspired, but that's what I want my tech stack and it's management to be. Also, maybe Jarred was a net negative, but bun was also a real…
By what metric is bun a "really big project"? It seems to have less than 5 consistent contributors. It's not a very popular npm package there's just a larger focus on gaming github stats.
The usecase itself is js on the backend, seems unaligned with zig.
Is calling someone a "stinky manager" a personal attack? yes!
Stinky manager != stinky person
an attack is not personal because it encompasses the whole person, but because it targets an aspect of that person. for an attack to be not personal it would have to target a category of people.
"software developers are stinky managers" is not a personal attack. neither is "managers are stinky", but "you/he/she/etc are something" is personal. it may not be an attack though if it is still part of a generalization: "you are a stinky manager because all software developers are stinky managers". but the article is not making that generalization, and therefore it's not just personal but also an attack.
> Yes there are ways around it if you have patience, but what the heck!! https://forgejo.org/docs/latest/user/agit-support/
Worth noting that while it's absolutely unfortunate that we're hitting this Forgejo design flaw, AGit honestly is just a better workflow, and I (Zig core team member here, full push access to the upstream repo) have started using it for pretty much all of my PRs. There are a couple of small things I'd like to see improved about Forgejo's implementation of AGit, but IMO it fundamentally makes so much more sense than t…
I agree. It would be very interesting to see a forjego config-mode/fork/clone/alternative with AGit as the main (or _only_) contribution workflow!