Back
Siavosh Zarrasvand

Siavosh Zarrasvand

@siavoshzarrasvand

I build teams that program computers, with a focus on distributed event-driven applications.
46
Joined July 2023
Load previous page…

Thank you buddy, hopefully you join at some point!

Definitely would love to! I've never been anywhere in the East. Think about documenting your journey on a blog. I'm your first reader if you decide!

Even works with two dashes, from what I can see. Maybe even one.

Yeah, seems to be there is a case of MD injection here, which if true, might be possible to lead to an MDX injection, at which point your cookies are mine ;-)

Lol, @marc is this a feature, or a bug? Three consequitive dashes seems to make text an MD header, or similar?

Wonder if it's just the Markdown parser doing that

Even works with two dashes, from what I can see. Maybe even one.

Yeah, seems to be there is a case of MD injection here, which if true, might be possible to lead to an MDX injection, at which point your cookies are mine ;-)

That was a Markdown feature we shouldn't support. Fixed now

Why I had to go to Mongo: I really needed something that was "json first". I got 3000 different fields/keys, but my largest documents only have 100 fields at most. So a huge number of the fields only appear in a sub-set of the documents.

True Marc's use cases have simple requirements, but that is true for most newbies. In a way I'd say Mongo is better for newbies doing simple stuff than experienced engineers building complex apps...

Lol, @marc is this a feature, or a bug? Three consequitive dashes seems to make text an MD header, or similar?

Wonder if it's just the Markdown parser doing that

Even works with two dashes, from what I can see. Maybe even one.

Yeah, seems to be there is a case of MD injection here, which if true, might be possible to lead to an MDX injection, at which point your cookies are mine ;-)

That was a Markdown feature we shouldn't support. Fixed now

Pretty interesting discussion going on here!

I’ve been using Mongo (via Mongoose) for a while and I tried SQLite recently.

I like SQLite for the standardised way of building databases. With MongoDB, there’s no real best practice and everything is open to interpretation

Yes exactly. And sometimes your data looks exactly like that, which makes it hard to retrofit into SQL.

It does. Best not to change database types midway into the project anyway

Reddit for sports? Reddit is agnostic, you could probably just create a subreddit for sports there...

Thank you for the feedback. But no.

That is the reason I historically stayed away from Mongo but they’ve improved and either way, I need a document store (jsonb in PG won’t do).

Newbes can use Mongo, Marc Lou has built 20 startups on Mongo and makes 300k. He was very novice when he started.

Fair play if they've fixed the issues

I'm curious what kind of use case you have where jsonb won't work considering Postgres typically benchmarks well (ironically, better than Mongo) when dealing with jsonb data

And yeah I'm not saying it's not possible. You can be successful with any DB choice really and Marc's use cases work fine with Mongo (I don't know all of his apps, but most of the ones I've seen either don't have persistence requirements or have pretty simple data models that can basically be stored in anything including Mongo), but I typically don't recommend Mongo to new people because I've seen a lot of folks shoot themselves in the foot trying to force relational data into a document format just because they don't know any better

What I mean by that is that it's really easy to look at Mongo if you don't have a lot of experience and think "oh yeah, I can represent everything I could ever hope to store in a database using a JSON doc" even if there might be relationships between entities that are better off in a typical RDBMS and not a document DB. I mean, I've seen people do wild shit like attempt to represent an entire social graph for a user in a mongodb document. That's where the danger is in my view.

Why I had to go to Mongo: I really needed something that was "json first". I got 3000 different fields/keys, but my largest documents only have 100 fields at most. So a huge number of the fields only appear in a sub-set of the documents.

True Marc's use cases have simple requirements, but that is true for most newbies. In a way I'd say Mongo is better for newbies doing simple stuff than experienced engineers building complex apps...

Lol, @marc is this a feature, or a bug? Three consequitive dashes seems to make text an MD header, or similar?

Wonder if it's just the Markdown parser doing that

Even works with two dashes, from what I can see. Maybe even one.

Yeah, seems to be there is a case of MD injection here, which if true, might be possible to lead to an MDX injection, at which point your cookies are mine ;-)

That was a Markdown feature we shouldn't support. Fixed now

Pretty interesting discussion going on here!

I’ve been using Mongo (via Mongoose) for a while and I tried SQLite recently.

I like SQLite for the standardised way of building databases. With MongoDB, there’s no real best practice and everything is open to interpretation

Yes exactly. And sometimes your data looks exactly like that, which makes it hard to retrofit into SQL.

It does. Best not to change database types midway into the project anyway

Is totally fine if you use SQLite.

Have a look at Mongo as well, it is a really good database and surprisingly easy to run yourself. I actually recently switched all my databases from SQLite to Mongo.

I'm not doing programmatic SEO though... I'm doing the old vanilla, based on purely my content.

At this point Google just sucks, plain and simple. Again, I get more traffic from Baidu alone, or Yandex alone, or Bing alone.

And the quality of the traffic is okay, people coming through organic search from other avenues than Google spend a fair bit of time on the websites.

Home
Search
Messages
Notifications
More