4 ms·
Heh, that is actually a name we considered, and as a name on its own, I like it a lot. But we also needed a name for the individual instances. We also found th
by kentonv 6y ago
Heh, that is actually a name we considered, and as a name on its own, I like it a lot.
But we also needed a name for the individual instances. We also found that the people who "got" the product were the ones who thought of it in terms of object-oriented programming (an object is an instance of a class). So we ended up gravitated towards "objects".
But I dunno, naming is hard. "Workers State" may in fact have been a better name!
- eastdakota 6y agoDefinitely the hardest product to name I can remember.
- pier25 6y agoFrom a pragmatic point of view the idea seems to be allowing stateful workers. Objects seems more like an implementation detail. Anyway, thanks again for working on this. I'm sure I'm going to use those once they come out of beta!
- athriren 6y agoworkers state is more memorable, mainly because of the double entendre.