5 ms·

Can you elaborate?

47 10y ago
Probably refering to the diagram from their github page[1] [1] https://github.com/prasmussen/glot https://github.com/prasmussen/glot Pet Peeve: There is no way to post ASCII diagrams on HN
- deleted 10y ago
  [deleted]
- eatsfoobars 10y ago
  snippets.glot.io glot.io run.glot.io ┌──────────────────┐ http ┌──────────────────┐ http ┌──────────────────┐ │ glot-snippets │◀─────────│ glot-www │─────────▶│ glot-run │ └──────────────────┘ └──────────────────┘ └──────────────────┘ │ │ │ http │ │ http │ ▼ ▼ ▼ ┌──────────────────┐ ┌──────────────────┐ ┌ ─ ─ ─ ─ ─ ─ ─ ─ ─ │ couchdb │ │ postgresql │ docker │ └──────────────────┘ └──────────────────┘ └ ─ ─ ─ ─ ─ ─ ─ ─ ─ Almost works. I just pasted it as code.
  - dublinben 10y ago
    I'd say it works quite well. That looks perfect.
- throwanem 10y ago
  Indent each line by four or more spaces. The markup documentation is linked from the FAQ, and the FAQ is linked from the bottom of each page.
baldfat 10y ago
People not using a relational DB drives me nuts when it clearly is the right tool for the job. Possibly that is his issue. Something that is a perfect match for a relational DB and instead use a "NON-SQL" DB for a project.
alexkavon 10y ago
Yes. Usually when I build an application I'd use a single database. While I don't think in the end it would matter for PostgreSQL or CouchDB, two databases is a bit much. Just curious as why they use two databases that can accomplish the same task (from what I can tell from my limited digging into the project).

Can you elaborate?

47 10y ago

Probably refering to the diagram from their github page[1] [1] https://github.com/prasmussen/glot https://github.com/prasmussen/glot Pet Peeve: There is no way to post ASCII diagrams on HN

deleted 10y ago
[deleted]
eatsfoobars 10y ago
snippets.glot.io glot.io run.glot.io ┌──────────────────┐ http ┌──────────────────┐ http ┌──────────────────┐ │ glot-snippets │◀─────────│ glot-www │─────────▶│ glot-run │ └──────────────────┘ └──────────────────┘ └──────────────────┘ │ │ │ http │ │ http │ ▼ ▼ ▼ ┌──────────────────┐ ┌──────────────────┐ ┌ ─ ─ ─ ─ ─ ─ ─ ─ ─ │ couchdb │ │ postgresql │ docker │ └──────────────────┘ └──────────────────┘ └ ─ ─ ─ ─ ─ ─ ─ ─ ─ Almost works. I just pasted it as code.
- dublinben 10y ago
  I'd say it works quite well. That looks perfect.
throwanem 10y ago
Indent each line by four or more spaces. The markup documentation is linked from the FAQ, and the FAQ is linked from the bottom of each page.

baldfat 10y ago

People not using a relational DB drives me nuts when it clearly is the right tool for the job. Possibly that is his issue. Something that is a perfect match for a relational DB and instead use a "NON-SQL" DB for a project.

alexkavon 10y ago

Yes. Usually when I build an application I'd use a single database. While I don't think in the end it would matter for PostgreSQL or CouchDB, two databases is a bit much. Just curious as why they use two databases that can accomplish the same task (from what I can tell from my limited digging into the project).