Hacker News Reader

Comment by xupybd | Hacker News Reader

I like to get paid for my work. Most people do. There is nothing disgraceful about that.

I don't see any difference between deno as a company and your SAAS bernard.app.

My SaaS is not an open source project nor a language runtime. How would you feel if Go, Elixir or Rust (just to name a few) were run by a company that depends on their success, so try to push aggressively new features and mindshare, often with disastrous result?

Are Go, Elixir or Rust developers working for free? There is a difference between getting paid to work on open source, and structuring an open source company as a VC-backed startup that needs to grow fast or die.

I guess everyone has already forgotten about Docker, Inc.

This is a bad analogy, it is more like if the Tokio runtime was built by a VC backed business which is really not that bad.

Honestly the anti business sentiment on HN is just becoming annoying. Get shamed when not building OSS, get shamed if you take VC money, etc. People are supposed to be saints that work for free so you can then take that and build your own proprietary stuff? Seriously...

Precisely. So much of the negativity in this thread (and elsewhere) weirdly conflates Deno with a language.

Deno is an open source runtime for TypeScript (and JavaScript and WASM). One that has been delightful, in my experience, for system scripting, build tooling, and CLI apps.

Deno Deploy is a hosted runtime that is very similar, but not open source.

The complaining in this thread reads to me like people complaining that the company that makes AWS Lambda also makes DynamoDB.

This new Deno KV is a fantastic addition to both of their runtimes. Dead simple, no need to sign up for some other service, works out of the box in either case.

But nobody is forcing you to use it. You don't have to opt out of it. If you don't like it, then you can go use all the other database layers that you could before this announcement.

A bit of a tangent, but I looks at your link to Bernard. Aren't there a lot of broken link-checking services out there already? Curious to learn what your USP is, and/or your approach to competing in a saturated market.

None that seem vaguely close to my vision. And one killer feature I would like to focus on (though it's on the roadmap for post-launch) is the ability to notify you if an URL of yours stops being accessible, i.e. you forgot, after a redesign, to set up a redirect from the old URL to the new, which is a nightmare for both users and your SEO.

I've seen that happen countless times, and no service I've tested was able to monitor for that use case satisfactorily and/or at that price point.

In other words, my goal is to create a service to uphold Berners-Lee's "cool URIs don't change" mantra.

https://www.w3.org/Provider/Style/URI.html

Reply on news.ycombinator.com