Most active commenters
  • kragen(10)
  • dcminter(6)
  • kstrauser(3)
  • ajb(3)
  • monocasa(3)

←back to thread

224 points mshockwave | 41 comments | | HN request time: 0.929s | source | bottom
1. alephnerd ◴[] No.44502181[source]
Interesting but complementary foray into owning the end-to-end pipeline of chip design, fabrication, and packaging - especially for embedded use cases.

MIPS has also hitched it's horse to RISC-V now, and I am seeing a critical mass of talent and capital forming in that space.

replies(2): >>44502288 #>>44503638 #
2. kragen ◴[] No.44502288[source]
The critical mass of talent and capital forming in the RISC-V space happened in 02019 at Alibaba: https://www.cnx-software.com/2019/07/27/alibaba-unveils-xuan...

AFAIK MIPS still hasn't shipped a high-end processor competitive with the XuanTie 910 that article is about. And I think the billions of RISC-V microcontroller cores that have shipped already (10 billion as of 02022 according to https://wccftech.com/x86-arm-rival-risc-v-architecture-ships...) are also mostly not from MIPS.

replies(4): >>44502616 #>>44502618 #>>44503499 #>>44504041 #
3. garblegarble ◴[] No.44502616[source]
off-topic but: I've noticed you prefix years with a zero in your HN comments. First I thought it was just a typo, but I see you've made several comments like that. Is there some significance, or are you just raising awareness of the year 9999 problem?
replies(3): >>44503103 #>>44503441 #>>44505071 #
4. nine_k ◴[] No.44502618[source]
(BTW why do you write years with a leafing zero? Do you expect these post to still matter past year 9999?)
replies(1): >>44503384 #
5. rrakow ◴[] No.44503103{3}[source]
I think that's some "Long Now Foundation" meme.
replies(1): >>44503363 #
6. dcminter ◴[] No.44503363{4}[source]
That. Personally I think it's performative nonsense, but you have to admire the commitment to it.
replies(3): >>44503566 #>>44503788 #>>44504330 #
7. dcminter ◴[] No.44503384{3}[source]
...and if he does, why does he then consider the year 99999 to be out of reach? As I understand it the idea is to promote "long term thinking" but I really don't see how this affectation is actually supposed to achieve anything beyond mildly irritating/confusing the reader.

At least the Long Now Foundation stuff comes with that context built-in.

https://longnow.org/

replies(1): >>44503512 #
8. acdha ◴[] No.44503441{3}[source]
It’s the Long Now Foundation’s convention - a bit cultish but harmless.

https://longnow.org/ideas/long-now-years-five-digit-dates-an...

9. hulitu ◴[] No.44503499[source]
> AFAIK MIPS still hasn't shipped a high-end processor competitive with the XuanTie 910 that article is about

The last high end MIPS was in the SGI times, 30 years ago.

replies(2): >>44503625 #>>44505447 #
10. ndiddy ◴[] No.44503512{4}[source]
Good point, I will start the Longer Now foundation and start adding two zeroes to the front of all my years.
replies(1): >>44508367 #
11. kstrauser ◴[] No.44503566{5}[source]
I suspect it’s counterproductive, though, like deliberately not using pronouns and always referring to someone by name. The intent might be to draw attention to the author’s cause, but it’s more likely to come across that the author just writes weirdly.
replies(1): >>44503605 #
12. dcminter ◴[] No.44503605{6}[source]
Eh, I also think it's harmless, and lends a certain "brand" to their posts - which are usually quite good otherwise. Better to be weird than dull, right?
replies(2): >>44503893 #>>44504986 #
13. kragen ◴[] No.44503625{3}[source]
Yes, but their claims over the last few years have been that their RISC-V implementations will be super fast, not like all those pikers, because they're using MIPS microarchitectural techniques. And so far I haven't seen them ship anything that substantiates that.
14. ajb ◴[] No.44503638[source]
It's an interesting comparison because MIPS used to occupy the niche that RV does now - an ISA that anyone could implement.

Lots of companies had their own mips implementation, but still might use an implementation from mips-the-company because even if you have your own team, you probably don't want to implement every core size that you might need. But then for some reason lots of them switched to using ARM, within a few years (in some cases getting an architecture licence and keeping their CPU team).

It seems like RV has a more stable structure, as the foundation doesn't licence cores, so even if one or two of the implementors die it won't necessarily reflect on the viability of the ecosystem

replies(1): >>44508909 #
15. kstrauser ◴[] No.44503893{7}[source]
I guess, unless the offputting:goodness ratio gets lopsided and makes people start ignoring them.

Frankly, something about that leading 0 makes me grit my teeth and stop reading. I can't explain why it affects me like that. Perhaps I'm the only one who does, although threads like this seem to pop up whenever they post so I don't think so. If HN had a mute button, I'd probably use it just because it annoys me to that level.

Edit: And now that we're talking about it, they seem to have the need to mention a specific year way more than most, as though deliberately looking for opportunities to draw attention to themselves. Oof. That just made it about 10x more grating to me.

replies(2): >>44503976 #>>44504268 #
16. dcminter ◴[] No.44503976{8}[source]
I do get where you're coming from; for me I think it interrupts the way I scan text - a date would be unconsciously absorbed but these stand out as abnormal artefacts requiring full attention.
replies(1): >>44504397 #
17. Findecanor ◴[] No.44504041[source]
It was some time ago that MIPS did announce that they had competitive RISC-V cores and had signed customers for them: LG and in the automotive sector. I'd think those should be taped out by now, but who knows...

I think the C910 looks better on paper than it performs in practice. I hope that isn't the case for MIPS.

replies(1): >>44504072 #
18. kragen ◴[] No.44504072{3}[source]
Do you have any details?
replies(2): >>44504116 #>>44504882 #
19. Findecanor ◴[] No.44504116{4}[source]
I can only refer to MIPS' own press releases, unfortunately. They mention 4-wide OoO, RV64GH + Zbb + Zba. no V.

That is a frustrating pattern in the RISC-V world. Many companies that boast having x wide cores with y SPECint numbers but nothing that has been independently verified.

replies(1): >>44504204 #
20. kragen ◴[] No.44504204{5}[source]
No V sounds like a bad sign for performance. Do they have any part numbers?
21. tonyedgecombe ◴[] No.44504268{8}[source]
You aren’t the only one, it interrupts the flow when I’m reading.
22. kragen ◴[] No.44504330{5}[source]
It doesn't require any special commitment because it doesn't cost me anything. Certain people do post a lot of really boring comments about it, but I'm not the one posting those comments, and I don't care about those people's opinions, so I don't care.

I don't believe I'm actually doing those people any injury, so while they're obviously free to continue requesting different formatting of my posts, I'm free to ignore them.

I think it's important for people to be able to complain about things that bother them, for the reasons described in https://news.ycombinator.com/item?id=44501817. In that thread, we were discussing a different commenter requesting that an author please not use AI for editing his own books, although the request was made in a particularly obnoxious fashion. Consider "Please don't play your music so loud at night", "Please don't look at my sister", or "Please don't throw your trash out your car window". But "please format your dates differently" doesn't seem like a very important request, even if it were phrased politely, to the point that it makes me (and, as I've seen, others) think less of the people who are making it.

If my date formatting really bothers them, they're free to stop reading the site. After having looked at their comment histories, I wish some of them would, because the only thing they ever post are similarly vacuous complaints. If people had to choose between reading a site where I posted and they didn't, and a site where they posted and I didn't, 100% of people would choose the former. (Others do occasionally post something worthwhile, but nothing that inspires me to wonder how I could earn their admiration.)

So, these days, I can easily ignore it.

Especially the day after this comment of mine got voted up to +151: https://news.ycombinator.com/item?id=44491713

replies(2): >>44504435 #>>44507392 #
23. kstrauser ◴[] No.44504397{9}[source]
Yeah, that's a great way of explaining it. Every time, it raises an exception in my mental parser and I have to go back and consciously evaluate it. Then I see that it's the same person who got me yet again, and I grit my teeth.
24. avhception ◴[] No.44504435{6}[source]
Every time I encounter it, I think to myself: ah, that guy again. Always brings a little smile to my face. Keep it up!
replies(1): >>44504946 #
25. monocasa ◴[] No.44504882{4}[source]
Adding to what was said, it also suspiciously looks like a MIPS core with a RISC-V frontend strapped to it sort of like Qualcomm did with their Nuvia AArch64 core. Particularly stuff like the soft fill TLB from m-mode looks just like MIPS coprocessor 0.
replies(2): >>44504956 #>>44505019 #
26. kragen ◴[] No.44504946{7}[source]
Thanks!
27. ajb ◴[] No.44504956{5}[source]
There's nothing especially wrong with using an existing backend design and transitioning it to another ISA; a number of teams did that from mips->arm and had success with the result. Of course, if you ship too early you may be missing some features.
replies(1): >>44507273 #
28. andrekandre ◴[] No.44504986{7}[source]
idk, i personally was confused by it; i thought they were referencing some node number or referencing some other thing and got hung up on it....
29. kragen ◴[] No.44505019{5}[source]
Yeah, my understanding was that shipping a high-performance MIPS core with RISC-V instruction decoding was precisely their plan. It sounded like a pretty good plan, really. But did they manage to actually ship one? Did you get a look at a datasheet?
replies(1): >>44507255 #
30. ◴[] No.44505071{3}[source]
31. chasil ◴[] No.44505447{3}[source]
Loongson was making them until recently.

https://www.theregister.com/2025/05/06/loongson_inspur_cloud...

replies(1): >>44505744 #
32. kragen ◴[] No.44505744{4}[source]
Yes, but MIPS wasn't.
33. monocasa ◴[] No.44507255{6}[source]
No datasheet, but their commits to opensbi have been extremely enlightening wrt s and m modes.
replies(1): >>44507311 #
34. monocasa ◴[] No.44507273{6}[source]
> a number of teams did that from mips->arm and had success with the result.

Do you have any examples? Apple Silicon cores took pieces of the pwerficient cores, and everything else I know of either tweaked an official ARM design or started more or less from scratch.

replies(1): >>44510412 #
35. kragen ◴[] No.44507311{7}[source]
Aha! I never would have thought to look there!
36. dcminter ◴[] No.44507392{6}[source]
> I don't care about those people's opinions, so I don't care.

This was stronger before you edited in the longer paragraphs telling us that you look through their comment histories.

Look, you do you, but I'd rather hear your passionate promotion of the leading zero approach since you apparently know it irritates people.

Edit: PS Isn't it interesting that the comment that you are justly proud of doesn't have any dates in it? :)

replies(1): >>44509906 #
37. hypercube33 ◴[] No.44508367{5}[source]
This whole line of conversation and use of the leading zero reminds me of The Church of MOO from the old internet.
replies(1): >>44508595 #
38. dcminter ◴[] No.44508595{6}[source]
Huh, I know about Bob Dobson et al, but MOO-ism somehow escaped my notice back in the day.

http://textfiles.com/occult/MOOISM/

I have some retro-reading to do.

39. bobmcnamara ◴[] No.44508909[source]
> an ISA that anyone could implement.

You want to burn your initial capital on lawyers? This is MIPS we're talking about.

40. kragen ◴[] No.44509906{7}[source]
Well, I thought maybe I should care, even if the request was unreasonable; but then I looked at some of the irritated people's comment histories, and breathed a sigh of relief.

Generally the comments I'm proud of tend to have more dates rather than less dates, because often they either provide verifiable information about things that have happened in the past at specific times, or cite specific sources, including the publication date. I think comments like that are more valuable than comments that simply take a position or state a complaint.

Consider, for example, this overview of the historical development of delay slots in RISC architectures https://news.ycombinator.com/item?id=44503609, or this discussion of what GlobalFoundries' prospects for developing a 7nm node really were when they abandoned it https://news.ycombinator.com/item?id=44503245, or this summary of the causes for the antibacterial properties of honey and the evidence for its astounding shelf-stability https://news.ycombinator.com/item?id=44495658, or this brief history of the ideology of pre-Satoshi cryptocurrencies https://news.ycombinator.com/item?id=44471683.

These are all within the last week. I'm pleased with how each of those comments came out, and, although the last one went relatively unnoticed (probably because it was deep in a contentious thread), all of the others were very well received.

However, presumably not by the sort of people who are more interested in how other people format their comments than they are in biochemistry, archaeology, or computer architecture. Which is fine with me. Different people have different interests, and some people evidently have a very strong interest in how other people format their dates, and don't have much to contribute on topics like computer architecture. Possibly this isn't the right site for them, and if so, they'll figure that out sooner or later, and go criticize other people's comment formatting elsewhere.

Sooner, I hope, because I'm really not interested in their opinions.

41. ajb ◴[] No.44510412{7}[source]
Here is one: https://en.wikichip.org/wiki/cavium/microarchitectures/vulca...

I don't know the details of how much rework they had to do.

As I understand it cavium still sells processors but only directly to hyperscalers.

Ironically Cavium may have gone through the same process with their previous design, but given that they then acquired this one from broadcom, perhaps it didn't go very well! I have no concrete information though.