essenciary

Please join the free beta, would really appreciate your feedback!

Thank you! For now, yes - but we'll add support for other languages next, starting with Python and R.

Shiny and Dash are web frameworks for coding data dashboards. With GenieCloud there is no need to code: with the visual UI builder you can create powerful data dashboards (that automatically work on mobile and desktop) by draging-and-dropping rich UI elements like dropdowns, sliders, plots, etc to create data apps in minutes.

For sure! All the files of the app will be editable in the code editor allowing for powerful customization. The goal is to make building data apps quick and easy, but without compromising powerful editing features for users that are comfortable with coding.

Planning on having support for Python in around 3-4 months!

There will be a free "Community" tier, for single users and one public app. A "Developer" tier, priced between $49-$99/mo depending on usage (up to 3 private apps). Then a "Team" subscription including up to 10 private apps and max 5 users for $250-500/mo. And finally, an "Enterprise" tier with unlimited apps, up to 20 user pe team, and custom support and integrations for $30-50K/year.

> when using Rust, you can write a unit test function right next to the function you are testing.

I'm not sure that this is a good thing? With Julia you can also write doctests which work great, but having a separate test set as a Julia _project_ offers a lot of flexibility. For instance, we're now developing a Julia wrapper for Playwright to build end-to-end/UI tests which themselves have multiple dependencies. Having a test _project_ allows having as complex test cases as needed, with properly managed dependencies out of source. How would you handle that with an approach like Rust's?

A test project means that you can easily extend the testing capabilities of Base Julia - for Genie we use ExtendedTestSet which actually allows us to pick and run only some of the tests. Take a look at that.

I hope this helps.

Thanks for the input, Genie creator here. I appreciate sharing your experience and I'd like to get a bit more info about the issues you had please.

0) Yes, this is an issue I confronted early on. Precompilation can take long on small machines, causing setups like Heroku's to kill the app. The solution (which granted should be maybe better documented) is to set the `EARLYBIND` env variable to `true` - this will allow Genie to bind to the port very early so Heroku will love it. (On second thought, maybe this should be the default in production)

1) ...

2) I don't understand the issues with auth, db, cookies, sessions, etc? Genie has built in support for handling (encrypted) cookies and sessions and plugins like GenieAuthentication (or GenieAuthorisation) and SearchLight provide straightforward features. Have you used these?

3) Really weird about the 30s update, haven't heard of this from other users. What's your computer configuration if I may ask? Can't comment on vim, I/we use VSCode.

Re deployment: * are you running the app in "prod" environment? * are you serving the assets via a reverse proxy like Nginx/Apache?

---

I do agree that using a language and a framework you know and used many times before would have been much quicker to build, but that's the case with all new tech. Besides the learning curve of a new language and a new framework, Genie and Julia are quite young and granted there's a myriad of things that we need to build, invent and develop :-) We enjoy doing it and solving this kind of problems and I'm sorry that unlike us, you had a hard time. Thanks again for sharing your experience and maybe check us out in 1y or so, the ecosystem is maturing fast but some things just take time (Python is 30y old right?).

Yeah, there is code set up in the page to add a code sample for each tab in the ecosystem. It's a matter of content (adding it).