We did a deal with IBM back in the day to adapt our tech as the code generation for enterprise java beans.
The commercial guy I dealt with made it very clear that a primary concern was IBM not being humiliated and shafted like their MS dealings. It colored our commercial arrangements, which had to include "break glass" arrangements for them to gain full access to our source code.
How to not learn from your mistakes and actually make them worse. I wonder how many valuable alliances they lost just because of that fear. Whoever was willing to sign was already probably not going to be a threat.
To be fair, source code escrow was for a long time a standard feature of contracts between small/medium software companies and large enterprises.
It's actually one of the reasons that open source took off in the early 2000s - if the source was already available all you needed to do was come up with a legal agreement that says something to the effect of "EnterpriseCo has a limited license to use SmallCo's software which reverts to full rights in the event that SmallCo is unable to carry out its obligations", with no need to bother arranging (and paying for) escrow.
That made it easier and cheaper to deal with open source companies, and made escrow seem weird and expensive by comparison. But in the 90s it was almost universal in those sort of contracts.
I worked all summer and was able to buy a TRS 80. I could not afford the cassette storage so I'd just type my programs in line by line to run them each time. They were pretty simple.
A snake like line drawer that crashed when it hit the screen edge, stuff like that. I was 12 or 13 and didn't have any mentors but I did know some BASIC from a school program. Really loved that machine.
If you have an enormous addressable market then it can pay to build awareness as quickly as possible. Having lots of enthusiastic users will do that. Having a useful free tier is a pretty uncontroversial way to get those users.
Plenty of apps do this - looking at the first browser tab I have open I see gmail which does exactly this.
For a pure client app like an iphone app, you don't have any real "per user" costs, so there are no concerns about going under from the costs of attempting this. It would be very different if you had to pay for server capacity.
When I started at IBM back in the 80s in NZ, there were plenty of 1403 printers still in operation, though no 1401 CPUs.
Since they were old even then, and NZ was something of a computing backwater (on a training course I met a guy who's territory of 3 or 4 floors of the world trade center had more machines than my territory of half of the North Island) there were no formal training courses on them, and I was on my own with the manuals and the insights of the gray beards in the company lunch room.
It wasn't until I found Ken Shirrif's magnificent animated explainer https://ibm-1401.info/KenShirriff-1403Animation.html many decades later that I really understood how the machines I had been fixing worked.
I'm reasonably good with clay targets. I would expect that if I was actually asked to take on drones I would need to do some practice on drones before I'd be good at them too. Drones are more expensive than clay targets but they're not particularly expensive and considering the situation I'd be willing to pay the price of a few drones to learn how to shoot them down down in a controlled setting where it's safe.
Shotguns have very short range: if I'm expected to be taking down a drone with a shotgun things are really bad at that point my life is alread in danger. if I hit I may save my life.
The commercial guy I dealt with made it very clear that a primary concern was IBM not being humiliated and shafted like their MS dealings. It colored our commercial arrangements, which had to include "break glass" arrangements for them to gain full access to our source code.
reply