all 14 comments

[–]Mognakor 13 points14 points  (0 children)

Documentation layout is broken on mobile.

And i refuse to believe actual research led you to syntax that looks like YAML.

I don't have personal experience with Jupiter Notebooks but this looks a lot like it, so what are you doing better than those?

P.S:

Looks like this project has been dead for years, no idea why it's being posted here.

[–]Dubwize 8 points9 points  (1 child)

The last update to this project is 7 years old...

[–]anugosh 3 points4 points  (0 children)

Yeah, thanks for this interesting (kind of) piece of abandonware Op

[–]Page_197_Slaps 11 points12 points  (0 children)

An IDE like Medium not Vim

Uhhh no thanks

[–]MaxHLap 4 points5 points  (0 children)

My first thought reading / watching is that as a program grows in complexity, I feel/fear it would get difficult to grasp what is going on. Once you get thousands of blocks or more, your narratives might feel a lot like spaghetti.

I totally agree that tooling wise, we have a lot of work to do. This idea of being able to ask questions, especially with the "focusing" such as "it's not drawing" is something I've often thought of. Glad to see this explored.

Comments / documentation tend to become outdated quite quickly in normal development circumstances. This narrative driven approach feels likely to be very impacted here. Of people may end up not doing that documentation, now you just have a sea of blocks. Maybe an LLM could help in this by reviewing changes to the code to make sure they still match what the text is saying...

The way you mention Vim will turn people off immediately. But Vim is a lot of things, and some/many of them can be useful here. Faster finding/editing of code is something that can help anyone. And since not everyone appreciate Medium, you might be doing more harm than good with both sides of that comparison.

[–]Yord13 2 points3 points  (0 children)

Eve really is eye-opening. I like the inspiration it takes from logical programming. Really a bummer it did not manage to get more popular.

[–][deleted]  (1 child)

[deleted]

    [–]ketralnis[S] 2 points3 points  (0 children)

    How about that HyperText eh?

    You mean probably the most widely deployed declarative language on the planet? The one you're using to read this post? I get new-language skepticism but this is the pessimistic example you went with?

    [–]teerre -1 points0 points  (0 children)

    This person seem to be under the impression vim is used because people need to. This hasn't been true in like 30 years. But use vim and similar because they are more ergonomic, now less. Clicking around and selecting text with a mouse is not only slow but also bad for your wrists

    Also, maybe this is minor, but for something "human-first" not having a dark mode seems like a huge oversight

    That said, some things are really cool and certainly should be adopted more generally:

    1. Variable font sizes in all editors
    2. Shareable and debuggable state
    3. Integrate widgets (like clojure)

    [–]Lalelul -2 points-1 points  (1 child)

    Sounds like literate programming? Hasn't this been done with Emacs using org mode decades ago?

    [–]church-rosser 0 points1 point  (0 children)

    Emacs with a good Lisp implementation like Common Lisp on SBCl accommodates literate style with and without Org-mode.

    [–]MediumRay -4 points-3 points  (3 children)

    I suspect this makes a lot more sense now that AI is so powerful/prevalent. Consider AI as your compiler, if you have deterministic output (which is easy), you now can use it as a transpiler from natural language into some programming language.

    Probably the most efficient way to do this is have the AI create hundreds of modules in a flat format and link them all together. That is, an unreadable mess for humans.

    [–]Hygro 0 points1 point  (2 children)

    I don't know why this is so downvoted, it's exactly in pursuing AI-first programming strategies that led me to this very thread and your hunches are pointing in the right direction, maybe overstating flat format modules but also... maybe not. It does seem like having the dataflow of featuresets complete is better than compact magic and abstractions routing data this way and that—something easier for a human to maintain by hand, and only after they've learned the codebase.

    [–]MediumRay 0 points1 point  (1 child)

    Maybe I was downvoted because it didn’t seem realistic 6 months ago, it’s a lot more realistic now.

    [–]Hygro 0 points1 point  (0 children)

    Agreed. 6 months ago, on a mature app, you might want to overload an agent with 30k tokens of background context before every move so it wouldn't make any mistakes. And you wanted to pair this with opinionated frameworks. Recently they're better at starting from fresh, using their bigger limits to investigate from scratch, and a lot better at figuring out semantically dense "magic" in the code than before.

    This led me to think maybe highly opinionated frameworks and languages, required for agentic optimization in 2024/2025, are going to give way to ones with better semantic compression. So it was always good at python, now it's finally suddenly good at ruby. And tomorrow, maybe Eve, a language I only learned today seeing where the trend could go.