SpartanJ
Joined 16 years ago
Joined 16 years ago
Here's the explanation: https://github.com/SpartanJ/ecode/?tab=readme-ov-file#source...
In my opinion, Sublime’s biggest gap is that it’s not open-source, and there aren’t many (if any) open-source alternatives that match its feature set, performance, and unique user experience, Sublime just feels especially nice. Zed comes closest, and I think it’s fantastic, but it’s VC-backed, so their focus on profitability will likely shape the user experience over time (as some users are already noticing). Every editor has its pros and cons, and preferences vary, but there’s always room for innovation. Even subtle differences can add up to a significantly better user experience. With ecode, I’m aiming to deliver a polished, enjoyable experience while subtly innovating on common editor features. That said, ecode is opinionated in some ways, so it won’t suit everyone, though it’s highly customizable and configurable.
> And congrats on your project, looks interesting.
Thanks! =)
ecode can handle big files, though it's not specifically designed for that. I just tested it with the largest text file I could find (760MB), and it worked just fine (searches included). The editor is designed with performance in mind, taking a similar approach to Zed (custom GPU-accelerated renderer, fully native C++ code, heavily multi-threaded, etc.). The biggest challenge is forming a community of collaborators, solo developing such a project in my free time is a huge task. So if anyone is interested, please contact me =)
I'm looking for collaborators, if someone is interested please message me.
Having said that, I'm working on an alternative GPU accelerated and retained-mode GUI called eepp (https://github.com/SpartanJ/eepp/) while I work on a new code editor similar to Zed called ecode (https://github.com/SpartanJ/ecode). The framework still needs a lot of work but presents some ideas that might be interesting to some. Retained-mode GUIs are a complex beast and it's hard to achieve simplicity (I think immediate-mode GUIs can't be beaten in that regard, but they have their own downsides). So I invite anyone interested in GPU accelerated GUIs to take a look at my projects (online demos are available), I'm looking for collaborators! (sadly C++ isn't very appealing these days, but my code-base is huge and I can't write everything from scratch in a new fancy and cool language).
> I have carefully set up my desktop environment the way I like it, specifically the way menus are displayed, colours, fonts, icons, keyboard shortcuts, notifications. Ecode does not even make a single attempt to adhere which was not acceptable when Winamp came out and certainly not acceptable in 2023.
I understand what you want, but it's not an easy task I it's not something I care anymore. It's technically possible to create a theme that looks almost exactly like anyone's desktop but I don't think it is worth it. eepp, the underlying technology behind ecode is more like HTML+CSS. All the styling is done via CSS and the layouting with XML, and it's more similar to the web technology than native desktop widgets (such thing stopped to be a thing in every OS except macOS).
> Stop "skinning" software, it is literally easier to do nothing and then the software will automatically do the correct thing and follow the rules.
Then you don't understand the problem.
> When I paste in text, it only shows squares, afaict only a few scripts like Latin or Cyrillic work.
The README file clarifies this. For the moment I don't support wide-characters (Chinese, Japanese, Korean, etc) and the editor only supports UTF-8. I'll add support for it at some point. Wide-characters are only supported in the terminal for the moment.
> The input method editor does not work correctly, I can't see what I'm typing.
I guess you're referring to IME support. It's still pending.
> Unusable, into the rubbish bin it goes.
I have no problem with critics, but this is not the way to have a conversation about an open-source application. At least take the time to read the README and understand that this is work in progress. Such comments like yours are a waste of time.