Lesson for naming features: never use terms such as "new engine" or "fast protocol" as they age poorly. Use codenames.
Timeline
Post
Remote status
Replies
9
@niconiconi Also do not ever put Simple in your protocol name, it'll jinx it.
@lanodan @niconiconi don't even protocol it, too many never receive the spec or the implementation love anyway
@lanodan @niconiconi universal serial port, high speed.
[CW]
Content warning
Programming reference
Show
Hide
Content warning
Programming reference
.
@niconiconi this goes for everything (unless it's a city and you want to constantly ironically remind visitors of the old history of its foundation)
relatedly, i was just thinking how a long time ago an FPS clan i was in died and some of the members wanted to restart it and decided to put phoenix-branded stuff on it all in reference to the renewal and i never rejoined because with that short-sighted naming decision i didn't think they'd be around long
relatedly, i was just thinking how a long time ago an FPS clan i was in died and some of the members wanted to restart it and decided to put phoenix-branded stuff on it all in reference to the renewal and i never rejoined because with that short-sighted naming decision i didn't think they'd be around long
@niconiconi Ethernet
Fast Ethernet
Very Fast Ethernet
Ultra Fast Ethernet
Super Fast Ethernet
Extremely Fast Ethernet
Fast Ethernet
Very Fast Ethernet
Ultra Fast Ethernet
Super Fast Ethernet
Extremely Fast Ethernet
@niconiconi NTFS/NT-Kernel 👀
@niconiconi and when you deprecate something, do not move it to thing-legacy because it will not be the last.
@niconiconi /me looks at "high frequency" radio and "fast" ethernet