DEC/Compaq/HP had working handheld systems running Linux in 2000, starting with the Itsy [1] and moving on to versions of the Compaq iPaq and HP Jornada 720. The kdrive X server was written for these machines. I was running the same software stack on a ruggedized tablet that we manufactured.
> And the portability for XLST 1.0 is almost perfect/gives identical results (up to DOM equivalency eg. attribute ordering, and even beyond) in my experience.
Not my experience, they all have different ideas of what the current node is at any one point in the execution of a script.
To a first approximation, no one cares about open source drivers when most PCs are running Windows and servers running Linux don’t care about Intels GPUs
This won’t solve the biggest challenge/problem, which is lack of talent for staffing the fab. In Arizona they had to import a bunch of temp workers from Taiwan just to train the locals. We don’t have the skills. If you want to involve the government, maybe we should be training units of the military to make their own chips.
That’s the specific problem a well organized governmental body can address. Funding research through university and private R&D lab grants and spreading/licensing the knowledge to domestic companies. Fund grants for universities and scholarships to spread that further. Invest in multiple startups attacking the problem at different levels in the stack (semi manufacturing has a LOT of inputs).
There are loads of ways you can effectively steer an economy to stimulate growth while also meeting geopolitical needs through effective and liberal application of the national purse. DOGE seems to have different ideas about the value of such programs.
How many workers do we need? TSMC has 80k workers all in. 15-24 there is about 3 million US NEETs. I think that we could have a 10 year plan to get 80k people with EE/CE/NanoTech Eng/ChemEng/etc degrees. Make college free, or hell even a stipend for people to pursue "Critical Careers", heavily fund Phds in the same areas for US Citizens, and we will see workers with the skills.
This is the wrong way to look at it. The people in the US that you would want working in semiconductors aren't NEETs. They are at Facebook/Google/Jane Street/Citadel/McKinsey.
If I am a capable person working on delivering node improvements dealing with smaller and smaller challenges as the physics issues become quantum - I will eventually start to ask myself: why am I working on the hardest physics problems in the private sector for 150k/yr, when I can transition to Facebook or Jane Street, work equally (if not less) as hard and make 500k/yr?
The US has plenty of smart people. I'd argue more that the wealth inequality gap makes it _incredibly_ difficult to justify working for less, even in a field you love, when you can make top 1-4% of income doing something else.
The cost of assets (especially housing, schooling, and health care) is a huge problem, and your example is a poignant one. More funding could sway a few people in that pipeline to go towards semi-conductors, but the majority of workers aren't Jane Street quality, they are technicians and engineers doing lots of highly skilled "grunt" work.
Personally I think the other half of the problem, Big Tech paying so much might be solving itself right now, excepting really only the very very top.
When Silicon Valley was cheap enough to live in that people could casually start a company in their garage... Then people didn't have to relentlessly optimize for short term comp.
Today you have to work at FANG to afford a garage in the Bay area.
Look at the insane salaries/equity going to AI researchers. Those at the cutting edge of semi manufacturing/design are likely completely capable of reproducing the skills sets of those people- how do they not cut and run?
If the government has to provide the funds, so be it, make those jobs valuable enough and the skills will be there.
Is that true? I thought a lot of semi-conductor work is borderline blue-collar factory work and physical labor.
What you’re describing is in the R&D area and also not physically dependent on being colocated in a fab. So we should have an easier time finding that talent, although we’re probably underpaying them now, as you point out.
The most salient issue with Intel in the past 10 year was their constant delay of the 10nm node process. While TMSC was constantly pushing down the Node size, Intel struggled and ceded a lot of ground to AMD & Apple. At the same time Intel struggled to develop a competitive 5G radio, and GPU.
These are all downstream of R&D. If your fab cannot shrink it's node size, then you won't get the most profitable orders.
I’m not sure it would have made a difference if they hit 10nm faster. Apple has always wanted to make its own chips. Some marginal efficiencies wouldn’t dissuade them from investing in themselves. And it’s not like Intel was going to start a consumer PC business…
Yep, Apple buying PA Semi was an indicator of their intention all those years back. I suspect intel was just hoping they would fail at their ambitions.
The metro systems in London and Paris extend outside the areas strictly defined as those cities, the populations served are only slightly smaller than that of Moscow.
Of course they do in Moscow too, the metropolitan/commuter areas exist in most big cities. Seems to be about 8 million less than Moscow for Paris, 6 million less for London, based on what Wikipedia currently says about the respective metropolitan areas.
For what it's worth, I lived in London for some time and its commuter rail system is much less integrated and much more confusing (with different companies, incompatible tickets and so on). In the city it's fine, though the tube isn't very comfortable (except for, ironically, its oldest lines which have luxuries such as ventilation).
> with different companies, incompatible tickets and so on
They have all been using the same tickets for a while now, and of course it has been all Oyster for more than a decade as well. I’ve been commuting using Thameslink or Southeastern without trouble for about as long.
[1] https://en.wikipedia.org/wiki/Itsy_Pocket_Computer
reply