Probabil voi lua și hate pentru această postare, dar pe bune că nu înțeleg unele prețuri din România. Am observat de mult că în majoritatea locurilor avem aceleași prețuri ca în Vest, deși salariile nu sunt la același nivel, dar în ultimul timp parcă se exagerează. Și pe bune că nu înțeleg de unde scot unii comercianți asemenea tarife.

Să vă dau numai câteva exemple. Și da, știu că sunt cherry-picked, dar în marea majoritate a bunurilor și serviciilor, trendul este același.

1. Merg cu copilul meu și încă două familii, fiecare cu copiii lor, la un loc de joacă. Cum stăm mai mult, se face ora prânzului și zicem să mâncăm acolo. Trecem peste „o sticlă de Cola la jumătate - 17 lei”... că nah, zici că e moft Cola. Dar o apă la jumătate este 15 lei. Mâncarea, la fel: 1 mic - 10 lei. O porție de cartofi prăjiți (din aceia congelați, nu vă imaginați că a stat cineva să îi curețe) - 15 lei. Asta, desigur, pe lângă prețul de intrare la acel loc de joacă. Și, știu... „Poți să mergi într-un parc cu copilul”, dar nu asta e scopul postării. Ca să nu mai vorbim că în multe țări, când te așezi la masă, primești apă gratuit. Da, apă de la robinet filtrată, dar ți se aduce fără ca măcar să o ceri. Eu nu am fost la un restaurant la mine în oraș unde măcar să existe această opțiune.

2. În ultimul timp am călătorit de câteva ori cu avionul. În aeroporturile din România, o sticlă de apă la jumătate costă 12, poate chiar 15 lei. În aeroportul din Barcelona, 2 sticle la jumătate de litru sunt cam 3 euro (da... era o ofertă unde luai două sticle).

3. Tarifele la sală iarăși sunt fenomenale. Și nu vorbesc de Worldclass, unde hai să zici că ai și piscină sau saună. Vorbesc de GymOne, o sală normală, fără nimic deosebit: 220 de lei pe lună. O sală echivalentă în Barcelona este 35 de euro... și primești apă gratuit.

4. Poți să spui: „Nah... servicii... cumpără de la supermarket”. Dar și aici prețurile nu sunt mai mici comparativ cu Spania sau Franța. La unele produse găsești, într-adevăr, aici mai ieftin. La altele am găsit dincolo mai ieftin. Nu am stat să fac o comparație clară (sigur se găsește pe undeva pe internet), dar îmi amintesc de o ofertă la Pringles - 2 cutii la 2,90 euro. La noi, o cutie este 9 lei.

5. Cafeaua, atât la cafenele, cât și to-go. Iar îmi amintesc de o întâmplare din Barcelona. Un cappuccino to-go, cafea foarte bună: 2,20 euro. Da, găsești și mai scump... pe la 3 euro. La noi, 12 lei dacă ești norocos...

Și exemple ar mai fi. Nu are rost să le trec pe toate. Dar sunt curios care credeți voi că este explicația pentru care prețurile sunt la fel ca în Occident la majoritatea produselor, dar salariile sunt mult mai mici. Și de ce unii comercianți au adaosuri comerciale atât de exagerate.

Sau poate am eu ceva... poate așa este normal.

Later Edit: Am uitat sa mai mentionez unele restrictii arbitrare. De exemplu, la Cinema City, au biletul de familie pentru animatii (in cazul meu, un adult si un copil). Merg cu copilul la film, la o animatie si mi se spune "Este doar pentru filmele dublate, pentru cele in engleza nu se aplica". Pe bune?

Not long ago, I launched DrakoFlow, an open-source tool for generating diagrams using DSL code.

Since then, I have fixed some bugs, added a few features, and released a Visual Studio Code extension. This makes it easier to visualize diagrams directly in your editor, without needing to open the online editor.

The extension is not yet published in the official marketplace, but that is planned. Until then, it can be downloaded directly from GitHub and installed manually.

As always, any feedback is welcome. I would like to improve DrakoFlow, so feel free to reach out if something isn't working or if there is a feature you think would be useful.

And if you find the project interesting, a ⭐ on GitHub is appreciated.

You can find more details at https://pazvanti.github.io/DrakoFlow/

https://preview.redd.it/wmgd0vfo28ah1.png?width=2554&format=png&auto=webp&s=5eea41e8abec8aa1e3e0300595169fb3c5a8ceae

Not long ago, I launched DrakoFlow, an open-source tool for generating diagrams using DSL code.

Since then, I have fixed some bugs, added a few features, and released a Visual Studio Code extension. This makes it easier to visualize diagrams directly in your editor, without needing to open the online editor.

The extension is not yet published in the official marketplace, but that is planned. Until then, it can be downloaded directly from GitHub and installed manually.

As always, any feedback is welcome. I would like to improve DrakoFlow, so feel free to reach out if something isn't working or if there is a feature you think would be useful.

And if you find the project interesting, a ⭐ on GitHub is appreciated.

You can find more details at https://pazvanti.github.io/DrakoFlow/

https://preview.redd.it/4l4sqxnsd78h1.png?width=2559&format=png&auto=webp&s=51cc68eeb99dd76bf24e53de7a73755ff0e40a77

Nu cu mult timp in urma am lansat DrakoFlow, un tool open-source pentru generat diagrame cu cod DSL.

De atunci am rezolvat unele bug-uri, am mai adaugat cateva functii in plus si am lansat si extensie de Visual Studio Code. Astfel devine mai usor sa vizualizezi diagramele direct in editorul tau, fara sa fie nevoie sa deschizi editorul on-line.

Extensia inca nu este publicata in magazinul oficial, dar urmeaza si asta. Pana atunci poate fi descarcata direct de pe Github si instalata manual.

Ca de obicei, orice feedback este bine venit. Doresc sa imbunatatesc DrakoFlow, asa ca nu ezitati sa scrieti daca ceva nu merge sau daca este ceva functionaltiate care crezi ca ar fi utila.

Iar daca vi se pare un proiect interesant, o⭐pe Github este apreciata.

Mai multe detalii gasiti pe https://pazvanti.github.io/DrakoFlow/

First of all, I am not sure if this breaks the 2nd rule or not. If it does, I will remove the post. It is not a library that directly contributes to TypeScript, but something that is language-agnostic, written in TypeScript.

Anyway, I wanted to share a project I’ve been working on called DrakoFlow.

https://preview.redd.it/9cx2jmscjp5h1.png?width=2559&format=png&auto=webp&s=4f3967b119e3b9e526b3e5987039c7e319fe4f53

For a long time, I’ve had the idea to build a text-to-diagram tool. I regularly use tools like PlantUML for documentation, but I always wanted something that felt more modern, interactive, and elegant. I wanted a tool where the diagram wasn't just a static output image, but a highly interactive canvas that remains closely tied to the code. My daily work is as a backend developer (mostly writing Java), so building a highly interactive client-side web app was a massive departure from my usual comfort zone. I decided to use this project as a practical way to learn TypeScript.

Since my frontend and UI/UX knowledge was limited, I used AI as a collaborative partner. It helped me bridge the gap where my TypeScript skills fell short (themes, UI/UX, optimizing some of the more complex layout/rendering algorithms and wherever my software engineering skills were not good enough)

What makes DrakoFlow different?

DrakoFlow runs entirely client-side. There is no backend server, which means your data and diagrams never leave your machine—making it fully privacy-first.

Here are the key features I’ve managed to implement so far:

• Bidirectional Sync & Drag-and-Drop: You can write the declarative DSL to generate shapes, but you can also drag components manually on the canvas. The engine automatically rounds and serializes those new coordinates (x and y) back into your code editor in real-time.
• Gutter Highlighting: Hovering over a component in the SVG highlights its exact definition line in the code editor, making navigation in large diagrams very fast.
• PlantUML Translator (Beta): You can paste existing PlantUML code directly into the importer to translate it into DrakoFlow’s native DSL.
• Multiple export options, including interactive HTML player export: Instead of just exporting static PNGs or SVGs, you can export your diagram as a self-contained .html file. This single file can be opened anywhere and retains panning, zooming, tag-filtering, a minimap, and a read-only code viewer.
• Serverless Sharing: Because there is no database, you can share diagrams by copying the URL. The app compresses the entire diagram state and encodes it directly into the URL hash parameter.
• Snap to Grid: Features an adjustable snapping grid to keep manually moved elements clean and aligned.
• Subsystems & Nesting: Supports grouping microservices and components using standard UML Package folder blocks or VerticalContainer structures.

Stack

• Languages: Pure TypeScript, compiled to plain JS (runnable offline, straight from a local file).
• UI/Rendering: Vanilla DOM and SVG APIs (no heavy external rendering frameworks).

The project is completely free and open-source. Because the PlantUML translator is still in beta, some complex structures might need manual tweaking, but I am actively working on improving it.

I would love to get your feedback on the DSL syntax, usability, or any features you think would make the tool more useful for your daily documentation workflow!

Live Site (you can try it directly in the browser): https://pazvanti.github.io/DrakoFlow/

Github Repo: https://github.com/pazvanti/DrakoFlow

Hi everyone, I wanted to share a project I’ve been working on called DrakoFlow.

https://preview.redd.it/3sjdbrze8p5h1.png?width=2559&format=png&auto=webp&s=0f4cfd345e622edcee99577897614fdb42007347

For a long time, I’ve had the idea to build a text-to-diagram tool. I regularly use tools like PlantUML for documentation, but I always wanted something that felt more modern, interactive, and elegant. I wanted a tool where the diagram wasn't just a static output image, but a highly interactive canvas that remains closely tied to the code. My daily work is as a backend developer (mostly writing Java), so building a highly interactive client-side web app was a massive departure from my usual comfort zone. I decided to use this project as a practical way to learn TypeScript.

Since my frontend and UI/UX knowledge was limited, I used AI as a collaborative partner. It helped me bridge the gap where my TypeScript skills fell short (themes, UI/UX, optimizing some of the more complex layout/rendering algorithms and wherever my software engineering skills were not good enough)

What makes DrakoFlow different?

DrakoFlow runs entirely client-side. There is no backend server, which means your data and diagrams never leave your machine—making it fully privacy-first.

Here are the key features I’ve managed to implement so far:

• Bidirectional Sync & Drag-and-Drop: You can write the declarative DSL to generate shapes, but you can also drag components manually on the canvas. The engine automatically rounds and serializes those new coordinates (x and y) back into your code editor in real-time.
• Gutter Highlighting: Hovering over a component in the SVG highlights its exact definition line in the code editor, making navigation in large diagrams very fast.
• PlantUML Translator (Beta): You can paste existing PlantUML code directly into the importer to translate it into DrakoFlow’s native DSL.
• Multiple export options, including interactive HTML player export: Instead of just exporting static PNGs or SVGs, you can export your diagram as a self-contained .html file. This single file can be opened anywhere and retains panning, zooming, tag-filtering, a minimap, and a read-only code viewer.
• Serverless Sharing: Because there is no database, you can share diagrams by copying the URL. The app compresses the entire diagram state and encodes it directly into the URL hash parameter.
• Snap to Grid: Features an adjustable snapping grid to keep manually moved elements clean and aligned.
• Subsystems & Nesting: Supports grouping microservices and components using standard UML Package folder blocks or VerticalContainer structures.

Stack

• Languages: Pure TypeScript, compiled to plain JS (runnable offline, straight from a local file).
• UI/Rendering: Vanilla DOM and SVG APIs (no heavy external rendering frameworks).

The project is completely free and open-source. Because the PlantUML translator is still in beta, some complex structures might need manual tweaking, but I am actively working on improving it.

I would love to get your feedback on the DSL syntax, usability, or any features you think would make the tool more useful for your daily documentation workflow!

Live Site (you can try it directly in the browser): https://pazvanti.github.io/DrakoFlow/

Hi everyone, I wanted to share a project I’ve been working on called DrakoFlow.

https://preview.redd.it/qtl42d2w3i5h1.png?width=2559&format=png&auto=webp&s=7dca16bc6478364a4a06abe09f072f6783bd1f97

For a long time, I’ve had the idea to build a text-to-diagram tool. I regularly use tools like PlantUML for documentation, but I always wanted something that felt more modern, interactive, and elegant. I wanted a tool where the diagram wasn't just a static output image, but a highly interactive canvas that remains closely tied to the code. My daily work is as a backend developer (mostly writing Java), so building a highly interactive client-side web app was a massive departure from my usual comfort zone. I decided to use this project as a practical way to learn TypeScript.

Since my frontend and UI/UX knowledge was limited, I used AI as a collaborative partner. It helped me bridge the gap where my TypeScript skills fell short (themes, UI/UX, optimizing some of the more complex layout/rendering algorithms and wherever my software engineering skills were not good enough)

What makes DrakoFlow different?

DrakoFlow runs entirely client-side. There is no backend server, which means your data and diagrams never leave your machine—making it fully privacy-first.

Here are the key features I’ve managed to implement so far:

• Bidirectional Sync & Drag-and-Drop: You can write the declarative DSL to generate shapes, but you can also drag components manually on the canvas. The engine automatically rounds and serializes those new coordinates (x and y) back into your code editor in real-time.
• Gutter Highlighting: Hovering over a component in the SVG highlights its exact definition line in the code editor, making navigation in large diagrams very fast.
• PlantUML Translator (Beta): You can paste existing PlantUML code directly into the importer to translate it into DrakoFlow’s native DSL.
• Multiple export options, including interactive HTML player export: Instead of just exporting static PNGs or SVGs, you can export your diagram as a self-contained .html file. This single file can be opened anywhere and retains panning, zooming, tag-filtering, a minimap, and a read-only code viewer.
• Serverless Sharing: Because there is no database, you can share diagrams by copying the URL. The app compresses the entire diagram state and encodes it directly into the URL hash parameter.
• Snap to Grid: Features an adjustable snapping grid to keep manually moved elements clean and aligned.
• Subsystems & Nesting: Supports grouping microservices and components using standard UML Package folder blocks or VerticalContainer structures.

Stack

• Languages: Pure TypeScript, compiled to plain JS (runnable offline, straight from a local file).
• UI/Rendering: Vanilla DOM and SVG APIs (no heavy external rendering frameworks).

The project is completely free and open-source. Because the PlantUML translator is still in beta, some complex structures might need manual tweaking, but I am actively working on improving it.

I would love to get your feedback on the DSL syntax, usability, or any features you think would make the tool more useful for your daily documentation workflow!

Live Site (you can try it directly in the browser): https://pazvanti.github.io/DrakoFlow/

Hi everyone, I wanted to share a project I’ve been working on called DrakoFlow.

https://preview.redd.it/y75kq9yu3i5h1.png?width=2559&format=png&auto=webp&s=7c83b642c6aa2aa94947df69a651dbb304f7d25b

For a long time, I’ve had the idea to build a text-to-diagram tool. I regularly use tools like PlantUML for documentation, but I always wanted something that felt more modern, interactive, and elegant. I wanted a tool where the diagram wasn't just a static output image, but a highly interactive canvas that remains closely tied to the code. My daily work is as a backend developer (mostly writing Java), so building a highly interactive client-side web app was a massive departure from my usual comfort zone. I decided to use this project as a practical way to learn TypeScript.

Since my frontend and UI/UX knowledge was limited, I used AI as a collaborative partner. It helped me bridge the gap where my TypeScript skills fell short (themes, UI/UX, optimizing some of the more complex layout/rendering algorithms and wherever my software engineering skills were not good enough)

What makes DrakoFlow different?

DrakoFlow runs entirely client-side. There is no backend server, which means your data and diagrams never leave your machine—making it fully privacy-first.

Here are the key features I’ve managed to implement so far:

• Bidirectional Sync & Drag-and-Drop: You can write the declarative DSL to generate shapes, but you can also drag components manually on the canvas. The engine automatically rounds and serializes those new coordinates (x and y) back into your code editor in real-time.
• Gutter Highlighting: Hovering over a component in the SVG highlights its exact definition line in the code editor, making navigation in large diagrams very fast.
• PlantUML Translator (Beta): You can paste existing PlantUML code directly into the importer to translate it into DrakoFlow’s native DSL.
• Multiple export options, including interactive HTML player export: Instead of just exporting static PNGs or SVGs, you can export your diagram as a self-contained .html file. This single file can be opened anywhere and retains panning, zooming, tag-filtering, a minimap, and a read-only code viewer.
• Serverless Sharing: Because there is no database, you can share diagrams by copying the URL. The app compresses the entire diagram state and encodes it directly into the URL hash parameter.
• Snap to Grid: Features an adjustable snapping grid to keep manually moved elements clean and aligned.
• Subsystems & Nesting: Supports grouping microservices and components using standard UML Package folder blocks or VerticalContainer structures.

Stack

• Languages: Pure TypeScript, compiled to plain JS (runnable offline, straight from a local file).
• UI/Rendering: Vanilla DOM and SVG APIs (no heavy external rendering frameworks).

The project is completely free and open-source. Because the PlantUML translator is still in beta, some complex structures might need manual tweaking, but I am actively working on improving it.

I would love to get your feedback on the DSL syntax, usability, or any features you think would make the tool more useful for your daily documentation workflow!

Live Site (you can try it directly in the browser): https://pazvanti.github.io/DrakoFlow/

Hi everyone, I wanted to share a project I’ve been working on called DrakoFlow.

https://preview.redd.it/v57udd6gz25h1.png?width=2559&format=png&auto=webp&s=40030c8205e475c8db4f0dee795687de1214009f

For a long time, I’ve had the idea to build a text-to-diagram tool. I regularly use tools like PlantUML for documentation, but I always wanted something that felt more modern, interactive, and elegant. I wanted a tool where the diagram wasn't just a static output image, but a highly interactive canvas that remains closely tied to the code. My daily work is as a backend developer (mostly writing Java), so building a highly interactive client-side web app was a massive departure from my usual comfort zone. I decided to use this project as a practical way to learn TypeScript.

Since my frontend and UI/UX knowledge was limited, I used AI as a collaborative partner. It helped me bridge the gap where my TypeScript skills fell short (themes, UI/UX, optimizing some of the more complex layout/rendering algorithms and wherever my software engineering skills were not good enough)

What makes DrakoFlow different?

DrakoFlow runs entirely client-side. There is no backend server, which means your data and diagrams never leave your machine—making it fully privacy-first.

Here are the key features I’ve managed to implement so far:

• Bidirectional Sync & Drag-and-Drop: You can write the declarative DSL to generate shapes, but you can also drag components manually on the canvas. The engine automatically rounds and serializes those new coordinates (x and y) back into your code editor in real-time.
• Gutter Highlighting: Hovering over a component in the SVG highlights its exact definition line in the code editor, making navigation in large diagrams very fast.
• PlantUML Translator (Beta): You can paste existing PlantUML code directly into the importer to translate it into DrakoFlow’s native DSL.
• Multiple export options, including interactive HTML player export: Instead of just exporting static PNGs or SVGs, you can export your diagram as a self-contained .html file. This single file can be opened anywhere and retains panning, zooming, tag-filtering, a minimap, and a read-only code viewer.
• Serverless Sharing: Because there is no database, you can share diagrams by copying the URL. The app compresses the entire diagram state and encodes it directly into the URL hash parameter.
• Snap to Grid: Features an adjustable snapping grid to keep manually moved elements clean and aligned.
• Subsystems & Nesting: Supports grouping microservices and components using standard UML Package folder blocks or VerticalContainer structures.

Stack

• Languages: Pure TypeScript, compiled to plain JS (runnable offline, straight from a local file).
• UI/Rendering: Vanilla DOM and SVG APIs (no heavy external rendering frameworks).

The project is completely free and open-source. Because the PlantUML translator is still in beta, some complex structures might need manual tweaking, but I am actively working on improving it.

I would love to get your feedback on the DSL syntax, usability, or any features you think would make the tool more useful for your daily documentation workflow!

Live Site (you can try it directly in the browser): https://pazvanti.github.io/DrakoFlow/

Hi everyone, I wanted to share a project I’ve been working on called DrakoFlow.

https://preview.redd.it/oo91fxrcy25h1.png?width=2559&format=png&auto=webp&s=63ec181b8d279fb4582229966506850dfab55c4f

For a long time, I’ve had the idea to build a text-to-diagram tool. I regularly use tools like PlantUML for documentation, but I always wanted something that felt more modern, interactive, and elegant. I wanted a tool where the diagram wasn't just a static output image, but a highly interactive canvas that remains closely tied to the code. My daily work is as a backend developer (mostly writing Java), so building a highly interactive client-side web app was a massive departure from my usual comfort zone. I decided to use this project as a practical way to learn TypeScript.

Since my frontend and UI/UX knowledge was limited, I used AI as a collaborative partner. It helped me bridge the gap where my TypeScript skills fell short (themes, UI/UX, optimizing some of the more complex layout/rendering algorithms and wherever my software engineering skills were not good enough)

What makes DrakoFlow different?

DrakoFlow runs entirely client-side. There is no backend server, which means your data and diagrams never leave your machine—making it fully privacy-first.

Here are the key features I’ve managed to implement so far:

• Bidirectional Sync & Drag-and-Drop: You can write the declarative DSL to generate shapes, but you can also drag components manually on the canvas. The engine automatically rounds and serializes those new coordinates (x and y) back into your code editor in real-time.
• Gutter Highlighting: Hovering over a component in the SVG highlights its exact definition line in the code editor, making navigation in large diagrams very fast.
• PlantUML Translator (Beta): You can paste existing PlantUML code directly into the importer to translate it into DrakoFlow’s native DSL.
• Multiple export options, including interactive HTML player export: Instead of just exporting static PNGs or SVGs, you can export your diagram as a self-contained .html file. This single file can be opened anywhere and retains panning, zooming, tag-filtering, a minimap, and a read-only code viewer.
• Serverless Sharing: Because there is no database, you can share diagrams by copying the URL. The app compresses the entire diagram state and encodes it directly into the URL hash parameter.
• Snap to Grid: Features an adjustable snapping grid to keep manually moved elements clean and aligned.
• Subsystems & Nesting: Supports grouping microservices and components using standard UML Package folder blocks or VerticalContainer structures.

Stack

• Languages: Pure TypeScript, compiled to plain JS (runnable offline, straight from a local file).
• UI/Rendering: Vanilla DOM and SVG APIs (no heavy external rendering frameworks).

The project is completely free and open-source. Because the PlantUML translator is still in beta, some complex structures might need manual tweaking, but I am actively working on improving it.

I would love to get your feedback on the DSL syntax, usability, or any features you think would make the tool more useful for your daily documentation workflow!

Live Site (you can try it directly in the browser): https://pazvanti.github.io/DrakoFlow/

Hi everyone, I wanted to share a project I’ve been working on called DrakoFlow.

https://preview.redd.it/yy0n312mn25h1.png?width=2559&format=png&auto=webp&s=4838e52f023f2ee79aaea16d061d563f9433acdd

For a long time, I’ve had the idea to build a text-to-diagram tool. I regularly use tools like PlantUML for documentation, but I always wanted something that felt more modern, interactive, and elegant. I wanted a tool where the diagram wasn't just a static output image, but a highly interactive canvas that remains closely tied to the code. My daily work is as a backend developer (mostly writing Java), so building a highly interactive client-side web app was a massive departure from my usual comfort zone. I decided to use this project as a practical way to learn TypeScript.

Since my frontend and UI/UX knowledge was limited, I used AI as a collaborative partner. It helped me bridge the gap where my TypeScript skills fell short (themes, UI/UX, optimizing some of the more complex layout/rendering algorithms and wherever my software engineering skills were not good enough)

What makes DrakoFlow different?

DrakoFlow runs entirely client-side. There is no backend server, which means your data and diagrams never leave your machine—making it fully privacy-first.

Here are the key features I’ve managed to implement so far:

• Bidirectional Sync & Drag-and-Drop: You can write the declarative DSL to generate shapes, but you can also drag components manually on the canvas. The engine automatically rounds and serializes those new coordinates (x and y) back into your code editor in real-time.
• Gutter Highlighting: Hovering over a component in the SVG highlights its exact definition line in the code editor, making navigation in large diagrams very fast.
• PlantUML Translator (Beta): You can paste existing PlantUML code directly into the importer to translate it into DrakoFlow’s native DSL.
• Multiple export options, including interactive HTML player export: Instead of just exporting static PNGs or SVGs, you can export your diagram as a self-contained .html file. This single file can be opened anywhere and retains panning, zooming, tag-filtering, a minimap, and a read-only code viewer.
• Serverless Sharing: Because there is no database, you can share diagrams by copying the URL. The app compresses the entire diagram state and encodes it directly into the URL hash parameter.
• Snap to Grid: Features an adjustable snapping grid to keep manually moved elements clean and aligned.
• Subsystems & Nesting: Supports grouping microservices and components using standard UML Package folder blocks or VerticalContainer structures.

Stack

• Languages: Pure TypeScript, compiled to plain JS (runnable offline, straight from a local file).
• UI/Rendering: Vanilla DOM and SVG APIs (no heavy external rendering frameworks).

The project is completely free and open-source. Because the PlantUML translator is still in beta, some complex structures might need manual tweaking, but I am actively working on improving it.

I would love to get your feedback on the DSL syntax, usability, or any features you think would make the tool more useful for your daily documentation workflow!

Live Site (you can try it directly in the browser): https://pazvanti.github.io/DrakoFlow/

https://preview.redd.it/njiowlvfh15h1.png?width=2559&format=png&auto=webp&s=8a687deaebb0534629073bd9475090847b2347dc

In urma cu mai mult timp mi-a venit idea sa fac un tool gen PlantUML, dar cu o structura mai buna, un editor mai capabil si mai multe functionalitati. La inceput am tot experimentat si treptat s-a conturat ceva cat-de-cat OK. Dar lipsa de timp si faptul ca eu sunt Back-end (Java) dev, nu de TypeScript au facut lucrurile sa progreseze destul de lent.

In cele din urma am zis sa bag si AI ca sa ajute (mai ales la chestii gen theme-uri, UI/UX, unde nu imi ieseau algoritmii si documentatie). Unii poate o sa fiti anti si o sa imi iau hate, dar asta este. Pe mine m-a ajutat sa lansez proiectul mai repede.

Inainte sa incep sa il promovez mai puternic, am zis sa scriu aici despre el si sa cer feedback. Proiectul este open-source, are editor disponibil online (merge complet in browser fara sa necesite instalare) si vine cu functionalitati utile si interesante. Mai jos cateva:

Limbaj DSL usor de inteles (parere personala) care permite realizarea de diagrame usor si rapid

Editor cu code highlight, aduagat component dintr-un library, documentatie detaliata

Theme-uri globale cat si override la theme per-element

Export ca PNG, SVG cat si player HTML care poate fi embedded in alte pagini de documentatie

Documentatie markdown per-element

Ajustare manuala a elementelor daca algoritmul nu le aranjeaza cum vrei

Import PlantUML (WIP, inca are multe probleme)

Anyway, astept feedback, pareri, sugestii de feature-uri noi, etc.

DrakoFlow: https://pazvanti.github.io/DrakoFlow/

https://preview.redd.it/ymaxt40atv4h1.png?width=2559&format=png&auto=webp&s=1b2525add827cacbad699c433ae940f5e2dd1ec2

In urma cu mai mult timp mi-a venit idea sa fac un tool gen PlantUML, dar cu o structura mai buna, un editor mai capabil si mai multe functionalitati. La inceput am tot experimentat si treptat s-a conturat ceva cat-de-cat OK. Dar lipsa de timp si faptul ca eu sunt Back-end (Java) dev, nu de TypeScript au facut lucrurile sa progreseze destul de lent.

In cele din urma am zis sa bag si AI ca sa ajute (mai ales la chestii gen theme-uri, UI/UX, unde nu imi ieseau algoritmii si documentatie). Unii poate o sa fiti anti si o sa imi iau hate, dar asta este. Pe mine m-a ajutat sa lansez proiectul mai repede.

Inainte sa incep sa il promovez mai puternic, am zis sa scriu aici despre el si sa cer feedback. Proiectul este open-source, are editor disponibil online (merge complet in browser fara sa necesite instalare) si vine cu functionalitati utile si interesante. Mai jos cateva:

• Limbaj DSL usor de inteles (parere personala) care permite realizarea de diagrame usor si rapid
• Editor cu code highlight, aduagat component dintr-un library, documentatie detaliata
• Theme-uri globale cat si override la theme per-element
• Export ca PNG, SVG cat si player HTML care poate fi embedded in alte pagini de documentatie
• Documentatie markdown per-element
• Ajustare manuala a elementelor daca algoritmul nu le aranjeaza cum vrei
• Import PlantUML (WIP, inca are multe probleme)

Anyway, astept feedback, pareri, sugestii de feature-uri noi, etc.

DrakoFlow: https://pazvanti.github.io/DrakoFlow/

Yes, I know how this title sounds, but bare with me.

I made an Android app for managing your loyalty cards. I made it firstly for me after I got frustrated with the Klarna app. I added everything I wanted and than some. It is completely free, no ads, no tracking no in-app purchases. I don't intend to make money from it, but it still feels good to have people use my app.

After launch, things looked good. The number of users was steadily growing, mostly due to the fact that I wrote on Reddit and my LinkedIn profile about the app. Nothing major, but I did reach 200 active users (I know it does not seem much, but for me it is).

I got feedback from many people and implemented new features based on their requests. I think more than 10 people requested features (one even wrote me an email on how much he likes the app, but wants a new feature to make it perfect).

But for the past month, the number of users had plutoed at around 250. To make things worse, I go a 2-star rating (all others are 5-star) with a cryptic "doesn't work." review, but did not provided any feedback even though I responded and asked for details so I can solve any issues he is having (I could not find any issues).

And now, I am stuck. How could I increase the visibility, the number of users, the number of people rating the app. I had more feature requests than ratings, so not even all the people that requested features left a review.