HN user

tiledjinn

75 karma
Posts0
Comments39
View on HN
No posts found.

Either the one little Timmy wanted, or the one the clerk tells her is selling fast (whether or not it's selling fast).

- Put an expiration date on the storefront and make it clear that your software is not guaranteed to continue working after date X.

This software is not guaranteed beyond 0 Unix time.

- Have your server source code (stripped down of proprietary stuff) ready for public release at EoL.

This isn't viable, and i would expect anyone on this site to understand that. it's roughly equivalent to saying "just make facebook stripped of proprietary code and ready for the public to run"

- Allow customers to reverse engineer the binaries and communication protocol after EoL.

This is a reasonable path forward, but likely a non-starter in the US for political reasons. I understand that "stop killing games" is an EU thing.

- Package dedicated server binaries with the game and allow customers to connect to it via a LAN or direct IP option.

See point 2. This is nonsensical.

inferior mechanisms frequently gain popularity, despite whether people who adopt them would be better off if they didn't.

people shouldn't use measuring cups either; since scales are more accurate, faster, and involve less cleanup. and yet.

no, it's a failed concept. frequently you'll find effectively shell scripts that couple workflows to some graphical environment for spurious reasons -- except they're baked with bad assumptions about state in that environment as outlined in the article.

if you want knuth's literate programming, just comment liberally per that guidance.

or carry forward with them and print your retractions later. vOv

ECS is an architecture proposed by the same group that has said "if you know you're not going to use that memory again, just allocate over it". For certain domains, this is a superior solution to management than more costly cleanup. Re-initializing an allocator and leaving behind old data in now uninitialized memory is a lot faster than doing anything with that memory.

For type safety, entities define mapping of types [components are types]. The whole point of ECS is effectively managing types and ensuring correctly typed data is operated on.

Significant equity or extremely green staff. And those will only work for a short period of time.

The only other plausible reasons that wont lead to massive attrition in the short term are around political extremes (eg Ukranians signing up for high risk jobs with long hours and little pay to defend their country) or some sort of legacy (you're a medical company with a plausible cure for cancer).

If you're in this situation, find funding to for the team you need or start winding down. Asking the question implies your staff will be better off if you shutter the company.

i got:

investor mark

put in 'check' which is apparently related 0% to investor. clearly the author has bad experiences in seeking funds

[dead] 3 years ago

Probably avoiding people who simultaneously say "where are all the females" and "women aren't discriminated against because I've never seen that discrimination".

The important thing is to understand domains and the scope of your knowledge. For some concerns, I am the smartest person in the room. For others, I'm absolutely not.

If you persistently feel like you're the smartest person in the room, either you have an exceptionally large number of mentoring opportunities or you need to do some introspection. Almost certainly the latter.

lenovo makes better workhorses than apple. you seem to be attributing the plateau of necessary machine performance to apple's quality. the reality is that for general computation no one really needs more machine than was produced in ~2010.

you simply don't need to upgrade computers like you did in the 90s and early 2000s.