Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

TimescaleDB raises $40M

blog.timescale.com

Post reply on HN
Print view View original

121–130 of 143 posts

Re: TimescaleDB raises $40M

#121

Post by cperciva »

Croftengea wrote: post #118
cperciva wrote: post #95

Earlier quoted context omitted.

they betted Just in case you're not a native English speaker: The verb "to bet" is irregular and the past tense is simply "they bet" rather than "betted" (which would be far more logical).

Thanks for pointing out! You're right, I'm not a native speaker. Some dictionaries list it as an alternative form though: https://www.collinsdictionary.com/dictionary/english/bet

Right, the dictionary is not your friend here. It is true that "betted" is occasionally used... but we're talking maybe 1% of usage, and mostly in older text. I recommend sticking with "bet".

Re: TimescaleDB raises $40M

#122

Post by staticassertion »

woofie11 wrote: post #89
akulkarni wrote: post #70

Earlier quoted context omitted.

Timescale Co-founder here. Happy to address your concerns! 1. Monetization strategy This funding round is actually a sign that our business model is working really well. To quote Redpoint Ventures, who led this funding round: "The [Timescale] team capitalized on their significant community momentum last year, with their cloud business being one of the fastest-growing database businesses we have seen in the past 20+ y…

> Most companies (including open-source companies) actually have both open-source and proprietary software, but the proprietary software is often hidden inside private repos. The difference with Timescale is that we have made the source code for our proprietary software available (on Github), even allowing users to modify it (eg "right to repair), and made all of our software free (ie no paid software features). So I…

The response didn't seem marketing heavy at all and directly addressed all of the points...

I see posts like yours all the time - attacking companies who believe in open source but know that the existing situation can and will lead to abuse by huge players in the market. It sounds like they have a very happy medium.

I find posts like this very frustrating because you almost never see the same kind of standards for proprietary software. People get less pushback for closed source than they do for "90% open, with restrictions on the last 10%".

As for AGPL dual license, have you tried selling AGPL software before? Even dual licensed, you've just added a massive roadblock - and it's no better than a custom license anyways, since it implies one.

Not to mention you've completely broken any path from "I'm a free user" to "I'm a paying user" - someone has to decide upfront to pay. Given that this is the most significant "win" for open source software (try before you buy, easy to inspect and get started with) it's kind of ridiculous how often I see it suggested.

Let's say I work for a company willing to pay for software. I have a hackweek where I want to try out TimescaleDB, in a world where it's AGPL or, upon payment, dual licensed. That's now dead in the water - I can't use it, AGPL is banned at every company I've worked at and we're not going to pay for me to try it out for a hackweek project.

Re: TimescaleDB raises $40M

#123

Post by prepend »

> open source (“open core”, to be precise)

This is bad. Just be precise and don’t try to conflate open source with proprietary stuff. It’s ok to not be OSS, lots of good software is non-OSS.

It’s only bad to say you’re one thing and be another.

Re: TimescaleDB raises $40M

#125

Post by benn0 »

drchaim wrote: post #111

Congrats to the tsdb team. I've tried the database extension months ago and it works perfect for my use case standalone. I just need to integrate it with Django, which is not easy given the current schema of the database and the way Django creates defaults autoincrements and PK, but I'm sure there will be a workaround for that.

I ran into the same problem trying to pair it with Django. From what I remember, some manipulation of primary key constraints in the schema could get them to coexist (although you lose any enforcement of unique PKs, so there's the potential for things to go bad). We ended up moving to FastAPI, so don't have this problem anymore.

Re: TimescaleDB raises $40M

#127

Post by Scarbutt »

dataviz1000 wrote: post #99
akulkarni wrote: post #70

Earlier quoted context omitted.

Timescale Co-founder here. Happy to address your concerns! 1. Monetization strategy This funding round is actually a sign that our business model is working really well. To quote Redpoint Ventures, who led this funding round: "The [Timescale] team capitalized on their significant community momentum last year, with their cloud business being one of the fastest-growing database businesses we have seen in the past 20+ y…

Lately, I've been studying machine learning, from point zero, with a focus on time series analysis. Two months in already completed a course on Python and another book on Pandas, several hundreds of hours later in the fourth chapter in a book I paid for on deep learning and time series analysis they provided me with the most important information I needed: there is no evidence deep learning works better than traditio…

I prefer 'esoteric' programming languages too, they are better. Experience has taught that ecosystem is way more important for shipping stuff, so stick mostly to mainstream ones.

Re: TimescaleDB raises $40M

#128

Post by akulkarni »

spmurrayzzz wrote: post #87
akulkarni wrote: post #75

Earlier quoted context omitted.

I also recall that when we [Timescale] first did our benchmarks vs Mongo for time-series, our use of MongoDB for time-series beat Mongo's own benchmarks :-) That's probably not something most companies would do for benchmarking, but we take ours seriously :-)

I appreciate all the work it takes to do them and document them. Doesn't go unnoticed I promise you.

Thank you :-)

Re: TimescaleDB raises $40M

#130

Post by the_optimist »

AzzieElbab wrote: post #61
shin_lao wrote: post #17

Earlier quoted context omitted.

TimescaleDB isn't an alternative to KDB+. KDB+ is more a programming platform than a database.

I just do not want to be forced to use kdb/k/q ever again

Can you provide a discussing on why / why not? Not necessarily here, but somewhere? Very interested to hear.
Post reply on HN