21–30 of 34 posts
Disclosure: I have no affiliation with them :). I’m just a fanboy at this point.
Too bad it's electron. I'm working on a just-for-fun markdown editor using GtkSourceView and GtkWebkit and, despite a slight learning curve getting familiar with gtk, it's been a pleasure to work on. Ugh...electron? Really??
Thank You for the TL;DR. Hate it too ;-)
I currently migrate from ghostwriter[0] to VNote[1] (both are Qt-based). VNote look very nice, but some refactoring needed + some features (that I'm waiting for) still missed. Hope, VNote development will be active, as it's developer[2] promised on HN[3].
[0] https://github.com/wereturtle/ghostwriter
[1] https://github.com/tamlok/vnote
Too bad it's electron. I'm working on a just-for-fun markdown editor using GtkSourceView and GtkWebkit and, despite a slight learning curve getting familiar with gtk, it's been a pleasure to work on. Ugh...electron? Really??
See, there's always more to complain about. I don't think your comment is productive here. Electron is not a perfect choice but what exactly does your comment add to the discussion about "just for fun" projects?
The OP is not singing the praises of Electron, in which case criticism about it would be welcome. They're trying to show off something they built. If a kid shows you a drawing they're proud of, do you criticize the drawing for not having a good color palette? (Rhetorical: It's not appropriate to do so, unless they're specifically asking for that kind of feedback)
Earlier quoted context omitted.
People are entitled to their opinions, and they are entitled to share them on HN. There are plenty of reasons to like Electron, and there are also plenty of reasons to say "ugh, Electron". Instead of saying "Let's keep this sort of comment off HN" because you happen to disagree with the guy's opinion, why not just ask him why he's so dead set against using Electron for this sort of app? People usually have strong opi…
We all know why one might prefer something over Electron. It's just a worthless comment. "Ugh, the color blue! Me no likey!" Does it really matter why they don't like blue, or whether I agree with them?
I wish it could replace the formatting syntax as you type, like Typora [1] does. The document becomes much cleaner to read while still being efficient to write.
Too bad it's electron. I'm working on a just-for-fun markdown editor using GtkSourceView and GtkWebkit and, despite a slight learning curve getting familiar with gtk, it's been a pleasure to work on. Ugh...electron? Really??
These kinds of dismissive comments make me wonder if the writer ever created anything of substance in their life. For example, notice how this project is actually accessible for people to try today. Building something in the privacy of localhost is pretty worthless if you think it equips you with the power of judgement. That's the easiest part of building something. Congratulations on your unreleased hobby project th…
But here's the thing. My current Markdown editor is Typora. Visually, it's all I want. But on the performance side, well, you can feel it's powered by Electron.
So I'm going to give a go to Abricotine (I mean, it's even open source, so that's great!). But I really want a markdown editor than can render a 100Ko file without difficulties.
Edit: Now that I've tested it, it's effectively way faster than Typora on the files I regularly uses. So I'll probably switch right way.
Earlier quoted context omitted.
"More efficient" how? At saving developer time? At producing shippable end products? At debugging? Will using GTK result in a better product that increases the end-user's "efficiency" more? Or will it really result in the developer shipping a product with 1/10th the features, or nothing at all?
Funny how you mentioned nothing of the computing resources required to run any of these. Sometimes it's alright to spend more time creating a product when the end result uses less CPU and less memory. It's not all or nothing.
I guess it's a mindshare thing and a learning curve thing.. I guess markdown is good enough for the vast majority of cases.. but when it isn't, it becomes a pita..
Is the editor really a problem to solve for Markdown? Philosophically I regard Markdown as a language in the text-only-editor-unimportant family. I recently built a (simple, only works for me) filter for pandoc that allows for formulas in Markdown tables. org-mode features is what Markdown is missing, but without the marriage to the editor. At the same time: an editor like this makes Markdown more accessible for non-…
I don't think it's a "problem to solve" i think it's an opportunity to grasp.
I love markdown and can read it just fine without an editor like this, but I, and many others, find it useful to have headings actually be darker and bigger. There's value to those typographical changes. There's value to links being a different color. Having an editor that can provide your eyes with helpful things.... helps.