https://nira.com/ does this to an extent. They pivoted away from usefyi which provided a way to connect multiple corporate services like Dropbox, gsuite drive, etc and see everything in one place.
Sorry, I ended up thinking far beyond helping employee send a departure message when the original comment mentioned a SaaS service for it in my head and disregarded the context.
I was thinking of a tool which would help companies departure employees smoothly. One thing that involves in departuring an employee is removing their access to the internal services related to the company. That's why I mentioned nira. It solves one key part of departuring an employee.
That quotation reminds me of one of my favorite refutations of the idea of directed evolution. A popular misconception is that evolution is directed towards making each species faster, stronger, and more intelligent. That may be true for some high-visibility examples during stable conditions. As soon as a cataclysm hits, it's the low-maintenance generalists who survive to repopulate the world.
80s - 90s where the era where quantity, volume and network externalities became more important than quality or even capabilities. There were good reason for that to happen, of course.
Concerning Zmacs completion allegedly being much better, GNU Emacs would complete M-x i-d-m to insert-departure-message, but there are three other possibilities in my current session.
Symbolics was fundamentally the victim of an inferior performance doubling time. Their performance increased at a rate noticeably slower than more mainstream processors.
That meant that their massive advantage in running lisp evaporated in just a few years between the mid 80s and 1990.
This was coupled with an inability to simplify their product. The first Symbolics machine we ordered at the CRL at NMSU in '84 had to have a guy with a graduate degree from UT come light it up. The SUN 2 that arrived at the same time had everything preinstalled and just needed me to plug in a few cables and turn on the power switch. The complexity of the Symbolics was reflected in the maintenance contract prices and in the fact that you generally had to deliver an entire OS and dev tool chain image to deliver any program (a so-called world build).
A few performance improvement doubling times later, Sun was the darling of the startup world and you could buy all of Symbolics for the price of a few of their maintenance contracts. Sun had been able to hitch a ride on the broader base of the 68000 processors from Motorola and then was able to improve the Sparc processor at a much faster tempo than Symbolics could cycle their own design.
Of course, about 15 years later, Sun fell victim to similar pressures and business model problems when the Sparc development team couldn't maintain tempo against Intel. Intel's primary advantage was broad market adoption which funded faster design cycles. Sun also had locked in on large banks by that time (how they survived the .com crash) and couldn't get back out to the broader market.
So it wasn't really that the flood came to the desert ... it was that Symbolics was focused on the wrong problem because they thought they had all the answers.
14 comments
[ 2.6 ms ] story [ 48.7 ms ] threadStart with Gmail and slack add-ons and role it from there.
Given the nature of the process, better pick one-time payment and maybe add a corporate plan.
Why does this not exist for legal purposes?
> Protect company documents from unauthorized access
And the tagline:
> Nira is a real-time access control system that provides visibility and management over who has access to company documents in Google Workspace.
Not sure how that remotely resembles being able to have text macros.
I was thinking of a tool which would help companies departure employees smoothly. One thing that involves in departuring an employee is removing their access to the internal services related to the company. That's why I mentioned nira. It solves one key part of departuring an employee.
To think we were giving eCards away for free in the 90s.
80s - 90s where the era where quantity, volume and network externalities became more important than quality or even capabilities. There were good reason for that to happen, of course.
That meant that their massive advantage in running lisp evaporated in just a few years between the mid 80s and 1990.
This was coupled with an inability to simplify their product. The first Symbolics machine we ordered at the CRL at NMSU in '84 had to have a guy with a graduate degree from UT come light it up. The SUN 2 that arrived at the same time had everything preinstalled and just needed me to plug in a few cables and turn on the power switch. The complexity of the Symbolics was reflected in the maintenance contract prices and in the fact that you generally had to deliver an entire OS and dev tool chain image to deliver any program (a so-called world build).
A few performance improvement doubling times later, Sun was the darling of the startup world and you could buy all of Symbolics for the price of a few of their maintenance contracts. Sun had been able to hitch a ride on the broader base of the 68000 processors from Motorola and then was able to improve the Sparc processor at a much faster tempo than Symbolics could cycle their own design.
Of course, about 15 years later, Sun fell victim to similar pressures and business model problems when the Sparc development team couldn't maintain tempo against Intel. Intel's primary advantage was broad market adoption which funded faster design cycles. Sun also had locked in on large banks by that time (how they survived the .com crash) and couldn't get back out to the broader market.
So it wasn't really that the flood came to the desert ... it was that Symbolics was focused on the wrong problem because they thought they had all the answers.