Hacker News Reader

Comment by NoraCodes | Hacker News Reader

I think it's a big deal. I keep seeing things like that and getting kind of excited - "is this a new corporate-supported Linux distro? something cooler?" - and it never is. It sucks.

View on HN

I agree. Words matter and have specific meanings. I'm tired of words being subverted for other purposes. Like "chemical free". So, you're telling me it contains...nothing? Or organic foods which has absolutely nothing to do with the meaning of organic from a chemistry standpoint. Conflating terms like this is purposeful misinformation with the intent to confuse and mislead (usually so you can charge more because the consumer thinks they're getting something different than what they're actually being peddled). The most charitable I could call it would be anti-consumer.

From a cursory look at WorkOS, it's not an OS. It's at best an app framework.

$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.

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

Speaking of weird ways to name something, why did you write it as $WORK? It doesn't look like it's publicly traded.

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).

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.

That's why I always put both $DEITY and $DIETY in my .bashrc file.

I support ${DEITY}, to cover the use case when there isn't one.

Reply on news.ycombinator.com