Re:WorkOS – Building blocks for quickly adding enterprise fe...
by linux2647 on Thursday May 12, 2022 @09:52AM
(#31354188)
$WORK’s corporate values, etc are distilled into an “OS”. It’s been that way since it was a startup, but I still find calling it an “OS” weird.
[ Parent
| on HN ]
Re:WorkOS – Building blocks for quickly adding enterprise fe...
by netizen-936824 on Thursday May 12, 2022 @10:45AM
(#31354968)
I don't understand how you can say
>values, etc are distilled into an “OS”.
When its literally not an Operating System. Its an application, no? It runs in user space on top of a real Operating System
Re:WorkOS – Building blocks for quickly adding enterprise fe...
by lawrencevillain on Thursday May 12, 2022 @11:17AM
(#31355422)
Speaking of weird ways to name something, why did you write it as $WORK? It doesn't look like it's publicly traded.
Re:WorkOS – Building blocks for quickly adding enterprise fe...
by blooalien on Thursday May 12, 2022 @11:49AM
(#31355872)
To a programmer or scripter, an uppercase $WORD starting with a dollar sign often denotes a variable. Thus, $WORK could denote any sort of work, or if you're religious, you might worship a $DIETY (but which one we don't know without asking, so it's "variable" information).
Re:WorkOS – Building blocks for quickly adding enterprise fe...
by pavlov on Thursday May 12, 2022 @04:03PM
(#31359526)
Sadly this script that depends on a supreme being will probably break in production because the correct spelling is $DEITY...
I guess supernatural dependencies are frowned upon these days anyway.
Re:WorkOS – Building blocks for quickly adding enterprise fe...
by bradknowles on Friday May 13, 2022 @01:27AM
(#31363676)
I support ${DEITY}, to cover the use case when there isn't one.
Re:WorkOS – Building blocks for quickly adding enterprise fe...
by spicybright on Thursday May 12, 2022 @08:57PM
(#31361953)
That's why I always put both $DEITY and $DIETY in my .bashrc file.