Hacker Newsnew | past | comments | ask | show | jobs | submit | wdanilo's commentslogin

Hi! Some friends of mine, ex-YC founders were drowning in a flood of emails from investors and clients. To save themselves, they built an internal tool that worked so well, they decided to package it into an app (I was helping them a little bit).

There is a bunch of tools that allow you to create summaries, help writing replies, etc, but Blinkfeed builds the UI/UX around these concepts, delivering something way more refined than anything I've seen. What do you think about it?


Congratulations, Arnaud! I really like the idea of your tool. I was using many tools to track dev productivity in the past – with all kind of charts and plots. Somehow, I never got answer to the question "what do we really spend time on? Is this mostly bug fixing, delivering new features, and how does it affect our KPIs?". I like that Echoes focuses exactly on that.

I've got one question – would it be possible in the future to generate some kind of alerts for the managers when for example the technological debt is growing above some threshold?


Thank you! We do get asked about alerts, both on metrics (as in your example) and on allocation (for example when the activity is significantly and durably diverging from the current expectations).

We haven’t started work on this but it’s very likely to happen at some point indeed.


Thank you for the nice words, we do our best! <3

Regarding collaboration, absolutely! Unicorns are born only from group effort :) Join our Discord at https://discord.gg/enso and let's have a chat!


That's right, we will be able to cut it down in the future. Let me explain why:

1. Enso compiler bases on GraalVM which is 400Mb (packed)[1].

2. The package contains GraalVM implementations of Python[2], R[3], and JavaScript[4] compilers, which weight 150Mb, 70Mb, and 50Mb respectivelly.

3. The package contains OpenCV library, as Enso has built-in bindings for it, which is 200Mb.

4. The rest (approx 200Mb) are core Enso libraries and tooling.

We will be able to cut it down in the future as soon as we release Enso Marketplace which would allow you to install these things on-demand.

[1] https://github.com/graalvm/graalvm-ce-builds/releases/tag/vm...

[2] https://github.com/oracle/graalpython

[3] https://github.com/oracle/fastr/releases/tag/vm-21.1.0

[4] https://github.com/oracle/graaljs


Btw, I think it's a good time to also announce that we have just started an "Enso Partnership Program" – long story short, if you have an idea of what you want to build on top of Enso, we'd like to help you deliver it! <3 Just tell us what you want to build by filling up this form (https://airtable.com/shrsnx2mJuRn0MxIS) and we will provide you with:

1. Dedicated Enso Expert. We will assign you with a dedicated Enso Expert from our side who will be responsible to help you build your use case and guide you step by step in case you have any problems.

2. Priority Bug Fixing. Enso is currently in alpha stage, so it contains bugs and is rough around the edges. We are working really hard on improving it, but bugs will occur. In case any bug will prevent you from progressing, we will focus on resolving it ASAP. It would normally mean, that you should expect fixing it in hours / days after reporting it!

3. Project Delivery Guidance. We want to guide you how to get your project on track and how to progress trough all of its stages, from the initial planning, trough prototyping, till releasing the working version. Based on our experience, it is best if you will have design / progress calls with the assigned Enso Expert once a week. Normally, 30 minutes call should be more than enough to be sure that everything goes according to the plan.

4. Extended Support. We know how important it is to get help when you are building things. We will try to reply to your questions in max 1 hour after you ask them. Of course, we are not able to cover all timezones right now, but we will do our best, especially in the range of 8 am - midnight CET.

5. Enso stuff. We would love to share with you how we appreciate that you are building things on Enso. We would love to send you some cool Enso stuff (like t-shirts, stickers, hoodies).


We're looking forward to your feedback! <3


Luna was our early prototype and it indeed had significant performance problems. Our new JIT compiler is able to execute the graphs really fast (in fact, in many cases we are up to 80x faster than Python nowadays: https://github.com/enso-org/benchmarks).

However, sometimes we see that the WebGL is super-slow on some machines. May I ask you for more details, please? The important bits would be whether you experience the slowdown when using the IDE (like dragging, zooming) or when waiting for data to be computed? In both cases, we would be more than thankful for an issue containing machine spec: https://github.com/enso-org/enso/issues .

Enso should work for you with the same visual performance as in this video (this was recorded on a few years old MacBook Pro): https://youtu.be/fQvWMoOjmQk . If its not this smooth, we need to investigate it, because this is something system / machine specific.

There is unfortunately no other way for us to improve and progress from alpha to beta, so we will be very thankful for help here! <3


I think you should hire a couple of game developers. With the small scale that Enso is operating at, there should not be having bottlenecks in the graphics layer. A game developer can easily scale the app to support millions of nodes trivially on a 2021 desktop.


Thank you! We hope for it as well. We really hope that Enso would eventually become applicable to a much broader space than Alteryx is applicable nowadays. In fact, Enso already provides much more powerful toolset in many cases, like unstructured data processing, true polyglot support, high-performance visualizations, interactivity, true batch-mode, etc. On the other hand, we are aware that there are still bugs and that our onboarding is far from perfect.

Anyway, I would really love to chat more with you about these cases if you'd like too! We are looking forward to work with companies in this space and we are providing them with a very special deals now, including lifetime discounts, dedicated team members building highly tailored libraries, and helping solving data-related problems! If that sounds interesting to you, please write to me a short message at wojciech.danilo@enso.org ! :)


No, it's not. TBH, we were not aware about it until recently, when someone from our community mentioned this project. It looks not maintained anymore nowadays, but I think it's a good idea to reach out to its authors, tell "hi" and chat about our co-existence! I'll do it :)


Fwiw there was a commit in June 2020


Thank you! And of course, everything (but the Cloud management) is Open Source on our end! You can find our custom WebGL rendering engine here (https://github.com/enso-org/ide/tree/develop/src/rust/ensogl), our event FRP handling system here (https://github.com/enso-org/ide/blob/develop/src/rust/lib/fr...) , and other related libraries here (https://github.com/enso-org/ide/tree/develop/src/rust/lib). They have pretty good documentation and a lot of example demo scenes, however, in case you'd struggle with using them, join our chat (https://discord.gg/enso) and we'd love to help you getting started! <3


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: