verstra

joined 2 years ago
[–] [email protected] 3 points 2 years ago

That you can easily use JOIN after you've already used LIMIT or GROUP BY.

[–] [email protected] 7 points 2 years ago (3 children)

As a developer of the compiler from prql to sql, I can say that I'm working on a new language because I know SQL quite in-depth.

It seems ok on surface, but there are many inconsistenties that you either learn to live with or don't even know are there until they trip you.

[–] [email protected] 3 points 2 years ago* (last edited 2 years ago) (1 children)

Cool. Any idea how would i use this with rustc?

[–] [email protected] 9 points 2 years ago (8 children)

What's up with the cartoon characters on this blog?

I've seen a few posts and they are generally of decent quality and technical contents, but I'm a bit weirded out by the children's illustrations.

[–] [email protected] 2 points 2 years ago

I prefer the pomsky syntax. https://pomsky-lang.org/

[–] [email protected] 2 points 2 years ago

Oh manually copying is worse than the other three options, because it will not retain the history of commits

[–] [email protected] 1 points 2 years ago (1 children)

And the employees are volunteering? It needs some plan for profitability, otherwise no investor will touch it.

[–] [email protected] 2 points 2 years ago

Empty commit message. Yes it's possible. Yes it's as bad as the cli tries to prevent it

[–] [email protected] 0 points 2 years ago

Wait, a company? Isn't this an open source project? Is there a plan for a revenue stream?

[–] [email protected] 3 points 2 years ago (3 children)

Wait, a company? Isn't this an open source project? Is there a plan for a revenue stream?

[–] [email protected] 2 points 2 years ago (2 children)

There is little difference between the three options you mentioned.

The only difference I can think of is that if you fork a repo on github, it will keep track of that and list the new repo undef the forks of the original one.

view more: ‹ prev next ›