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

maybe thats what made him so upset


yeah if i had to speculate, it likely helped lead to this breaking moment


something i have always observed, is how considerate Ted Tso's writing always is, but more than that, how consistent this property has been for so many decades.

its quite funny to me that ext4 very much mirrors him in that regard. its underpinning damn well everything, but you'd never know about it because it works so well.


> how considerate Ted Tso's writing always is

This is less true when T'so asks questions at conferences, of course.

https://www.theregister.com/2024/09/02/rust_for_linux_mainta...

https://www.youtube.com/watch?v=WiPp9YEBV0Q&t=1529s


perhaps the suffering of the printer devs is karmically 'paid back' by the physical suffering of printers around the globe, thus keeping everything in balance.


> dealing with an 8051 isn't something I'd inflict even on my worst enemy

surely armed with a C compiler + LLM, this is a non problem nowadays?


to be fair he bought it before chatgpt was released, and it has changed the landscape quite a bit.


the zeitgeist hungers for loanwords


8.3 naming scheme too


digital circuit design strikes me as a risky gambit for a career, given that almost everyone who ive bumped into in that industry was invariable not actually doing any design, but rather was tasked with writing test cases and verifying the functionality of some specific logical block.

tests are ofcourse very important, but fact of the matter is, bright smart and arrogant young engineers-to-be are very eager to show everyone how much better their version of the 'thing' is, and desperately want to write their version of the thing: they don't want to verify someone else's version of the thing.

if we're being honest, how many people do you really need to do the design of some hardware feature? realistically the design can be done by one person.

so you might have one lead designer, delegates each block to 10 guys, and everything else is basically 'monkey work' of writing up the state machine logic, testing it, and hooking it all up.

and now lets count the number of companies that can put up the capital for tape-out: amd, intel, arm, nvidia, meta, aws, google chips, apple, and lets say plus 50 for fintechs, startups, and other 'smaller' orgs.

so if you want to do design, you might be competing for... lets say 3 lead designers per org on avg, 3 * 50 = 150 silicon design spots for the entire globe. to add, a resource in such scarce supply will no doubt be heavily guarded by its occupants.

i did this calculation back when i was still in uni. i'll never know if it paid off, or if it was even rooted in logic, but i remember thinking to myself back then: "no way in hell am i gonna let these old guys pidgeon hole me into doing monkey work with a promise of future design opportunities." arrogant, yes, but i can't say i regret my decision judging from the anecdotes i get from friends in the hardware world.


> and now lets count the number of companies that can put up the capital for tape-out: amd, intel, arm, nvidia, meta, aws, google chips, apple, and lets say plus 50 for fintechs, startups, and other 'smaller' orgs.

And basically anyone who has a job in tech [1] or someone who just pulled their salary out of the ATM has enough money to do a tapeout with the cash in their hand [2] or chinese students for basically free[3]. Of course, for _some_ scopes of tapeout. These are older nodes and you have limited area. But you might not need anything fancy for your design.

The rest of the post, I think has a bunch of misunderstandings or wrong facts, but I don't work in the field, (ish) so I might be as clueless as you and I need to get back to my day job so I won't try countering you just yet.

[1] https://wafer.space/ [2] https://app.tinytapeout.com/calculator?tiles=1&pcbs=1 [3] https://ysyx.oscc.cc/docs/en/


3 designers per silicon org is a ludicrous underestimate


Yes, one of the ludicrous statements. I would invite him to take a look at OpenTitan for example and see how many designers work there on that thing.


some additional thoughts:

i think that, for digital design to be interesting, the cost of entry must be lowered by probably orders upon orders of magnitude.

the google skywaterpdk thing, whatever it is (or was?), did produce a great deal of hobbyist designs and proved that there really isn't anything special about rtl - infact, its really quite monotonous and boring.

which is a good attitude to have, really. lots of hobbyist designs got cranked out quickly on what, as i understood, was a very obsolete pdk from two decades ago.

but its fundamentally still too expensive and too limited. open source software 'blew up' because

1. the cost of entry was free...

2. ...for state of the art tools.

its not enough to be free, or open source. it also has to be competitive. llvm/gcc won the compiler world because they blew the codegen of proprietary compilers out of the water, ofcourse being open source it became a positive feedback loop of lots of expert eyeballs -> better compiler -> more experts look at it -> better compiler -> ...

for digital design to become interesting, you can't trick the kids: they want the same tech the 'big boys' are using. so, what scope is there to make it economical for someone like Intel carving out some space for a no-strings-attached digital design lottery?

i get the impression that, unlike for most manufacturing processes, the costs of silicon digital electronics increases every year, and the amortisation schedule becomes bigger, not smaller.

so if anything, it seems that the more high tech silicon manufacturing becomes, the smaller the pool of players (who have the ever-increasing capital expenditure necessary) becomes, which should indicate that the opportunities for digital design work are actually going to be shrinking as time goes on.


"Unalive GNU/Linux"


I've never heard of it doing rm -rf, but apparnetly it did try to launch nethack under certain unknown preprocessor conditions:

https://feross.org/gcc-ownage/?1?1

https://gcc.gnu.org/pipermail/gcc/2002-January/074450.html


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: