Right but it still gets put into boxes and flown over by a 747. Of course it‘s more complicated than that, but most contenders for complex machines are much more built in-place, and not a complete 'product' being assembled.
I‘d probably call it the most complex commercially available machine. You can‘t buy a Space Shuttle, or an LHC. You can buy a TSMC lithography machine, and it‘ll be delivered to you in much the same way as other equipment.
Also, I think the axis it‘s probably most complex on is precision of individual parts and of their combination. Arguably chips themselves are more precise as their 'parts' are so small, but they are much more homogeneous compared to the EUV machine, where tons of different materials and part sizes need to combine.
I can‘t imagine Apple doesn‘t have capacity booked well in advance, and their suppliers aren‘t going to stiff them because they‘d lose those long-term contracts. Sure, if the shortage lasts a year or more, there‘ll be issues, but if it‘s short term they might be fine.
This isn‘t your main point, but the iPhone absolutely was the biggest revolution since the Internet. The world before it is wholly different to the world after it. AI looks to have a similar impact, but just like the iPhone it‘ll be a few years before everyone realizes the world has changed.
Too expensive maybe, or just not effective anymore as they used up any available training data. New data is generated slowly, and is massively poisoned with AI generated data, so it might be useless.
Wouldn‘t that be the opposite of aligning incentives? Unions want the workers to do well, stockholders want the company to do well. The company paying people less is better for stockholders, worse for employees obviously. So that seems like an awful idea.
Yeah this is exactly it, you might think you are close but you actually just started, and the actual work is still to come.
Whether you want to push through the initial honeymoon phase, where you are done with the fun part that you started the project for, and do all the rest around it that makes it an actual 'product', is up to you.
This is exactly what we do for the Factorio modding API docs. The docs are embedded inside the codebase, alongside the classes and methods that implement the functionality the docs describe.
So they are written and adjusted as the functionality is implemented, they can be reviwed alongside the code PRs. The CI builds the docs and makes sure there are no issues.
The format is a custom one, which is parsed and converted into JSON for language servers and into the API website. Not sure how you‘d test the docs content, but this parser is tested for sure.
I work on the game. The debug library was disabled for other security holes that were brought to our attention, so it wouldn‘t be related to this, but I thought it was interesting to mention.
I believe the change was not mentioned in the changelog as an attempt at 'security through obscurity', trying to avoid people getting any ideas before the update is wide-spread. Not sure that helps any, but still.
Factorio disabled bytecode loading in response to this. Bytecode did allow for some cool stuff like writing mods in a preprocessor language that spits out Lua bytecode, but ultimately the security issues were more important to address.
Almost all of the debug library was made unavailable to mods as well, for similar security reasons.
The source is not publicly available, no. It‘s still being actively developed and sold after all. There isn‘t really much of a barrier between engine and 'scripting', it‘s all custom and integrated.
The reason there are so few bugs is that there is a ton of effort spent on squashing them! The approach is basically to fix any reported issue if in any way reasonable.
No VC money, just three people developing a game they‘d like to play themselves, and it grew organically from there, financed by the money made from selling the game.