5 ms·

How have you managed to make an argument about embedding a web browser about GNOME? As it were, GNOME's IDE (which I wrote) uses 0% CPU at idle.

killin_dan 10y ago
Gedit is fantastic. Thanks for all the work on it. I used it for years before VS Code, and I still use it outside of work on my personal projects. Amazing how much work you can get done by just typing the damn code into the editor, sometimes. However, writing typescript in vscode genuinely changed the way I think about editors. It's a smalltalkish sort of feeling where my code (at least the textual level) lives and breathes in the editor, automatic tooltips that are actually relevant, etc. Idk. I like both.
- audidude 10y ago
  I work on Builder, not Gedit. However, Gedit does get various features as we push them up into Gtk/GtkSourceView. The overview map is one such example. The pixelcache in GtkTextView enabling smooth 60fps scrolling is another.
aidenn0 10y ago
To be fair, the conversation had already shifted to X11/Wayland. GNOME does have a history of starting over from scratch every few years; you probably had a good reason for writing Builder instead of working on Anjuta, and that's just the way the GNOME community seems to do things. This makes people, especially power users, disproportionately angry because when you rewrite something, it will be different (that's sort of the whole point);this is compounded by the fact that at the beginning it will be feature-poor compared to the older system. "Why did you replace X with Y? With X, I could configure it to treat mouse-button-3 as mouse-button-2, but only when my USB mouse was not attached and I wasn't holding down any modifier keys." See also: https://xkcd.com/1172/ https://xkcd.com/1172/ Before I did any serious software development, I was on that side of the table being frustrated (I still cry a little inside any time I remember Galeon. Rest in Peace, my favorite browser). I can also neither confirm nor deny that my windows are being decorated by sawfish and that I wrote a compositor in librep so that I could get modern features while using it.
- audidude 10y ago
  > GNOME does have a history of starting over from scratch every few years; The GNOME project will be 20 years old in a couple of months. So while it might feel like "every few years", we really don't change direction all that often. As you can imagine, those that show up to do work have a great deal of say in where the project goes. > you probably had a good reason for writing Builder instead of working on Anjuta, and that's just the way the GNOME community seems to do things. > This makes people, especially power users, disproportionately angry because when you rewrite something You've sort of made my argument for not changing Anjuta over the years. We knew the amount of stuff that had to be changed would leave both the code-base and UI looking very little like Anjuta. Best to let people continue using it in the mean time. > (I still cry a little inside any time I remember Galeon. It lives on as Epiphany and is the primary driver of the WebKitGtk backend.

killin_dan 10y ago

Gedit is fantastic. Thanks for all the work on it. I used it for years before VS Code, and I still use it outside of work on my personal projects. Amazing how much work you can get done by just typing the damn code into the editor, sometimes. However, writing typescript in vscode genuinely changed the way I think about editors. It's a smalltalkish sort of feeling where my code (at least the textual level) lives and breathes in the editor, automatic tooltips that are actually relevant, etc. Idk. I like both.

audidude 10y ago
I work on Builder, not Gedit. However, Gedit does get various features as we push them up into Gtk/GtkSourceView. The overview map is one such example. The pixelcache in GtkTextView enabling smooth 60fps scrolling is another.

aidenn0 10y ago

To be fair, the conversation had already shifted to X11/Wayland. GNOME does have a history of starting over from scratch every few years; you probably had a good reason for writing Builder instead of working on Anjuta, and that's just the way the GNOME community seems to do things. This makes people, especially power users, disproportionately angry because when you rewrite something, it will be different (that's sort of the whole point);this is compounded by the fact that at the beginning it will be feature-poor compared to the older system. "Why did you replace X with Y? With X, I could configure it to treat mouse-button-3 as mouse-button-2, but only when my USB mouse was not attached and I wasn't holding down any modifier keys." See also: https://xkcd.com/1172/ https://xkcd.com/1172/ Before I did any serious software development, I was on that side of the table being frustrated (I still cry a little inside any time I remember Galeon. Rest in Peace, my favorite browser). I can also neither confirm nor deny that my windows are being decorated by sawfish and that I wrote a compositor in librep so that I could get modern features while using it.

audidude 10y ago
> GNOME does have a history of starting over from scratch every few years; The GNOME project will be 20 years old in a couple of months. So while it might feel like "every few years", we really don't change direction all that often. As you can imagine, those that show up to do work have a great deal of say in where the project goes. > you probably had a good reason for writing Builder instead of working on Anjuta, and that's just the way the GNOME community seems to do things. > This makes people, especially power users, disproportionately angry because when you rewrite something You've sort of made my argument for not changing Anjuta over the years. We knew the amount of stuff that had to be changed would leave both the code-base and UI looking very little like Anjuta. Best to let people continue using it in the mean time. > (I still cry a little inside any time I remember Galeon. It lives on as Epiphany and is the primary driver of the WebKitGtk backend.