Hacker Newsnew | past | comments | ask | show | jobs | submit | sixthDot's commentslogin


Way more suspicious star count looks to be from Zig[1]. That's based on their weird GitHub repo history[2].

In fact the initial negative campaigns initiated by the creators of Zig and Odin against V (and then turned on other languages like C3[4] and Zen C[5]), appeared to have been based on jealousy over supporter donations and GitHub stars.

Zig, has among the weirdest GitHub star history of any language repo seen. Stalled or lower GitHub popularity, then sudden explosion in stars after the release of numerous AI ebooks on Amazon (mid to late 2024). The release of the mostly AI ebooks, were very oddly close together, as if by contract or bounty. Just a strange timeline. Even when Zig moved to Codeberg and their GitHub repo was "frozen", was getting hundreds of stars per month (despite over 3,000 open issues) for a long time, which made no sense.

On the other hand, the vlang repo has always been rated in or near the top 10 of language repos[3] (per year), based on stars, since close to its beginning (from 2019).

Lastly, stars on GitHub are often checked and purged. It's not like Github personnel don't look. A major indicator of fake stars, is that the repo does not have matching activity, contributors, or forks. For instance, like V (when it came into existence), Zen C (4K stars since 2025) had a sudden burst in stars. Allowing it to nearly catch a long time repo like C3 (5K stars since 2019). Does V or Zen C, by gaining stars quickly or having more stars (than a 2019 competitor) mean they are fake?

It's the other indicators that are important too, not just star counts or fan jealousy over other repos having higher star counts.

[1]: https://github.com/ziglang/zig

[2]: https://ossinsight.io/collections/programming-language

[3]: https://ossinsight.io/collections/programming-language/trend...

[4]: https://github.com/c3lang/c3c

[5]: https://github.com/zenc-lang/zenc


your links don't back up your claims

The truth can not simply be blanked out. Others can not be responsible for refusal to read, research, or any denial of reality.

[1] Zig on GitHub has 3,042 open issues (as of this post)

Link: https://github.com/ziglang/zig/issues

[2] Tracking of Zig's strange star history

Link: https://ossinsight.io/analyze/ziglang/zig#overview

Note: historical changes in stars given to Zig, per month and year, have been recorded

[3] Vlang has (for years) been ranked as a near or top 10 GitHub repo based on stars

Link: https://ossinsight.io/collections/programming-language/trend...

Note: vlang's quick rise and continual popularity is widely known for creating jealousy and resentment among its rivals

[4] Zen C's star history compared to C3

Link: https://ossinsight.io/compare/c3lang/c3c/zenc-lang/zenc#over...

Note: Zen C's quick rise in stars and emerging popularity as a new competitor to Zig and C language alternative


I think Pentium will still be supported. i486 refers to very old 32 bits CPU (80486). The article is not clear but by default I tend to think that i586 and i686 will still be supported.


"Pentium" also refers to a 30-year range of CPUs with very different capabilities. I suspect that removing (say) P5-specific kludges would also not cause too much grief given it's over thirty years old and dates from about the same time as the newer 486s. At some point you need to clean out the cruft a bit.


Support for the Pentium isn't going away now, certainly, and nobody's announced plans to drop it from the Linux kernel, but every architecture has a time horizon.


When a team is so much into its own littke bubble, it does not realize anymore the shit they are doing


This work on system of weight:

> For each option and criterion, you assign a rating (0–10). Each criterion has an importance weight (1–5 stars). Decidit multiplies rating × weight and sums the values – the option with the highest score wins.

Is this really made for people who lack self-discipline or maybe just a website made for a portfolio ?


So eventually that would be used to poison communications, just in case of Iranian would use that old channel, which then would also mean that it's been cracked a while ago.

That's absurd but I like this kind of little stories.


> When a wealthy artist bought the island [...]

Not an artist. British businessman and Winter Olympian. See https://en.wikipedia.org/wiki/Keith_Schellenberg.


Also the C API is a bit the poor child. Plenty of useful options (or even opt passes !) are not available.


I think a large part of this comes from the fact that the expressiveness of LLVM’s C++ APIs does not translate well into a “plain old C” style interface. Many of the abstractions and extension points are simply awkward or impractical to expose in C.

On top of that, there is little incentive for contributors to invest in the C API: most LLVM users and developers interact with the C++ API directly, so new features and options tend to be added there first, and often exclusively. As a result, the C API inevitably lags behind and remains a second-class citizen.


If only that was only about emitting byte code in a file then calling the linker... you also have the problem of debug information, optimizers passes, the amount of tests required to prove the output byte code is valid, etc.


Another one bites the dust


Ah, ah, ah, ah, staying alive, staying alive


The bigest anoyance nowadays (in the EU at least) is rather the cookie policy agreement. "View the list of our 258 partners", etc.


I find the Consent-O-Matic extension pretty good in dealing with that.


I refuse to engage with EU cookie banners, even programmatically.


Use private mode browsing, click the easy option of allow all, and rejoice that cookies are cleared when you close the tab.


The cookies will still be correlated with each other, and your behavior will still be sent offsite for aggregation by ad identity companies, then linked back to your non-private browser behavior via IP, or browser fingerprinting, or any site you log into, etc.


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: