Warning: include_once(/home/sankarshan/sankarshan.randomink.org/blog/wp-content/plugins/wp-super-cache/wp-cache-phase1.php): Failed to open stream: No such file or directory in /home/sankarshan/sankarshan.randomink.org/blog/wp-content/advanced-cache.php on line 10
Warning: include_once(): Failed opening '/home/sankarshan/sankarshan.randomink.org/blog/wp-content/plugins/wp-super-cache/wp-cache-phase1.php' for inclusion (include_path='.:') in /home/sankarshan/sankarshan.randomink.org/blog/wp-content/advanced-cache.php on line 10
Deprecated: Return type of WP_Theme::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/class-wp-theme.php on line 554
Deprecated: Return type of WP_Theme::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/class-wp-theme.php on line 595
Deprecated: Return type of WP_Theme::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/class-wp-theme.php on line 535
Deprecated: Return type of WP_Theme::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/class-wp-theme.php on line 544
Deprecated: Return type of WP_REST_Request::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/rest-api/class-wp-rest-request.php on line 952
Deprecated: Return type of WP_REST_Request::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/rest-api/class-wp-rest-request.php on line 972
Deprecated: Return type of WP_REST_Request::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/rest-api/class-wp-rest-request.php on line 984
Deprecated: Return type of WP_REST_Request::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/rest-api/class-wp-rest-request.php on line 995
Deprecated: Return type of WP_Block_List::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/class-wp-block-list.php on line 151
Deprecated: Return type of WP_Block_List::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/class-wp-block-list.php on line 175
Deprecated: Return type of WP_Block_List::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/class-wp-block-list.php on line 164
Deprecated: Return type of WP_Block_List::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/class-wp-block-list.php on line 186
Deprecated: Return type of WP_Block_List::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/class-wp-block-list.php on line 138
Deprecated: Return type of WP_Block_List::offsetExists($index) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/class-wp-block-list.php on line 75
Deprecated: Return type of WP_Block_List::offsetGet($index) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/class-wp-block-list.php on line 89
Deprecated: Return type of WP_Block_List::offsetSet($index, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/class-wp-block-list.php on line 110
Deprecated: Return type of WP_Block_List::offsetUnset($index) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/class-wp-block-list.php on line 127
Deprecated: Return type of WP_Block_List::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/class-wp-block-list.php on line 199
Deprecated: Optional parameter $criteria declared before required parameter $revision_history is implicitly treated as a required parameter in /home/sankarshan/sankarshan.randomink.org/blog/wp-content/plugins/jetpack/_inc/lib/class.media.php on line 290
Deprecated: Optional parameter $post_url declared before required parameter $height is implicitly treated as a required parameter in /home/sankarshan/sankarshan.randomink.org/blog/wp-content/plugins/jetpack/class.jetpack-post-images.php on line 781
Deprecated: Optional parameter $value declared before required parameter $param is implicitly treated as a required parameter in /home/sankarshan/sankarshan.randomink.org/blog/wp-content/plugins/jetpack/_inc/lib/class.core-rest-api-endpoints.php on line 2397
Deprecated: Optional parameter $value declared before required parameter $param is implicitly treated as a required parameter in /home/sankarshan/sankarshan.randomink.org/blog/wp-content/plugins/jetpack/_inc/lib/class.core-rest-api-endpoints.php on line 2415
Deprecated: Optional parameter $value declared before required parameter $param is implicitly treated as a required parameter in /home/sankarshan/sankarshan.randomink.org/blog/wp-content/plugins/jetpack/_inc/lib/class.core-rest-api-endpoints.php on line 2446
Deprecated: Optional parameter $value declared before required parameter $param is implicitly treated as a required parameter in /home/sankarshan/sankarshan.randomink.org/blog/wp-content/plugins/jetpack/_inc/lib/class.core-rest-api-endpoints.php on line 2471
Deprecated: Optional parameter $value declared before required parameter $param is implicitly treated as a required parameter in /home/sankarshan/sankarshan.randomink.org/blog/wp-content/plugins/jetpack/_inc/lib/class.core-rest-api-endpoints.php on line 2489
Deprecated: Optional parameter $value declared before required parameter $param is implicitly treated as a required parameter in /home/sankarshan/sankarshan.randomink.org/blog/wp-content/plugins/jetpack/_inc/lib/class.core-rest-api-endpoints.php on line 2631
Deprecated: Optional parameter $value declared before required parameter $param is implicitly treated as a required parameter in /home/sankarshan/sankarshan.randomink.org/blog/wp-content/plugins/jetpack/_inc/lib/class.core-rest-api-endpoints.php on line 2660
Deprecated: Optional parameter $value declared before required parameter $param is implicitly treated as a required parameter in /home/sankarshan/sankarshan.randomink.org/blog/wp-content/plugins/jetpack/_inc/lib/class.core-rest-api-endpoints.php on line 2678
Deprecated: Optional parameter $slug declared before required parameter $attr is implicitly treated as a required parameter in /home/sankarshan/sankarshan.randomink.org/blog/wp-content/plugins/jetpack/class.jetpack-gutenberg.php on line 690
Deprecated: Optional parameter $type declared before required parameter $args is implicitly treated as a required parameter in /home/sankarshan/sankarshan.randomink.org/blog/wp-content/plugins/jetpack/modules/widgets/rsslinks-widget.php on line 175
Deprecated: Optional parameter $type declared before required parameter $required_field_text is implicitly treated as a required parameter in /home/sankarshan/sankarshan.randomink.org/blog/wp-content/plugins/jetpack/modules/contact-form/grunion-contact-form.php on line 3279
Deprecated: register_widget_control is deprecated since version 2.8.0! Use wp_register_widget_control() instead. in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/functions.php on line 4861
Deprecated: register_sidebar_widget is deprecated since version 2.8.0! Use wp_register_sidebar_widget() instead. in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/functions.php on line 4861 Where have all the GNOME fans gone ? | Random thoughts and serendipity Deprecated: preg_split(): Passing null to parameter #3 ($limit) of type int is deprecated in /home/sankarshan/sankarshan.randomink.org/blog/wp-content/plugins/jetpack/_inc/lib/class.media-summary.php on line 349
Deprecated: preg_split(): Passing null to parameter #3 ($limit) of type int is deprecated in /home/sankarshan/sankarshan.randomink.org/blog/wp-content/plugins/jetpack/_inc/lib/class.media-summary.php on line 349
Deprecated: preg_split(): Passing null to parameter #3 ($limit) of type int is deprecated in /home/sankarshan/sankarshan.randomink.org/blog/wp-content/plugins/jetpack/_inc/lib/class.media-summary.php on line 349
Barring some initial discussions, there hasn’t been much progress with regards to GNOME at the event. The CfP has been out for a while and there hasn’t been any forward movement on the GNOME Mobile stuff as well.
Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/wp-db.php on line 3031
16 thoughts on “Where have all the GNOME fans gone ?”
Hi!
I was once Arabic gnome translation coordinator, I ditched Linux completely and I am using Windows XP.
Sorry! But I need a working OS..
Ditched it for KDE. Developing for QT beats GTK by miles and miles.
Do you know that gconf development was stopped like 10 years ago because dconf will replace gconf. And do you know that dconf development was stopped for 2 or 3 years? That’s why.
Oh, forget the add the history of a new canvas widget. Please check out the canvas development trolls on gtk devel list.
GNOME become only a corporation made project. The code become ugly and only python or mono may have a chance to simplify the development. The codebase is old and in plain C. May be cute but is hard to make it back and GNOME starting from GNOME 2.16 seems stagnating, very small improvements (which start with Cairo + XGL) that give no intention to feel that something is changing.
gnome fans tend to defect to kde or lose interest completely when their (usually very good ideas, mockups etc) are rejected out of hand (see the osx menubar patch for gtk, dying topaz section on gnome-look.org).
gtk development has also stunted the growth of the gnome community, as it is so backwards and X like.
I still use GNOME exclusively and greatly appreciate it, but I think it must be said that the GNOME community focused on minor UI details for far to long.
Polishing had been much in need and was greatly beneficial for a time, but it started to look like GNOME was going nowhere fast.
Nonetheless, _I_ am _greatly_ excited about some of the ideas I’ve seen proposed for GNOME 3 in the last few weeks.
Where did all the brightest go? Macintosh. Like Gnome (values usability high) but it’s more polished and finished, bundled with great software.
Are you considering to pull your post now? 🙂
@Arafat then ditch XP if you need a working OS. Baring the legal issues with creating content/code using that OS it’s stability after many years is STILL not so great.
Krog has a point. QT is very VERY easy to write. While I like to do thinks in python where QT and GTK are pretty close to being just as easy as the other one, if I was writing in C++ I would probably go for QT.
As far away from Jeff Waugh and the rest of the pro-Microsoft faction in GNOME as we could get.
GNOME is a Microsoft-sponsored assault on Free Software.
I’ve been bouncing back and forth (as a user, not a developer) between GNOME and KDE for a while. I’ve done lots of Qt/C++ coding and some Clutter coding, so I am familiar with GLib-style C APIs. I must say that I like Qt/C++ a lot better. I haven’t tried GTKmm, though. Python levels the playing field considerably, but Python has its own set of issues. I think GNOME 3.0 should be taken as an opportunity to do some really innovative things, similar to what KDE did with KDE 4. I’ve been using KDE 4.1 since it was in beta (maybe earlier), and I hate going back to KDE 3. I would love to see GNOME do something similar.
Interesting post and some of the replies, a little visceral, but fairly accurate. I think that the issue with stagnating technologies and a dislike of doing objects in C seem to be the biggest issues. I have been a long term Gnome user but after learning C++ and developing in it, it just makes GObject based C seem, well, clunky.
I installed KDE4 the other day, with KDevelop I managed to knock up a simple paint program (usually the first thing I do with a new toolkit/language) and was surprised by how much easier it was when compared to Gnome. I dislike the checkbox mania of KDE but QT wins hands down against GTK for development ease/power.
For 3.0 PLEASE make a big thing about doing objects in an object based *language* (C++). Yes, Python does objects, but it is a scripting language, and I find myself wanting to use the languages I love/know rather than the latest and greatest intepreted language.
@Nick: What about gtkmm and gnomemm?
Now that Qt is going LGPL, what about some discussion about porting GnomeLibs to Qt for Gnome 3.0. This would unify the Toolkit layer in the desktops going forward. Since there was already a planned break in API/ABI compatability for Gnome 3, I see this as a significant step forward for Gnome.
A collection of jottings on various issues that excite no one else
Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/wp-db.php on line 3031
Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/Requests/Cookie/Jar.php on line 63
Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/Requests/Cookie/Jar.php on line 73
Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/Requests/Cookie/Jar.php on line 89
Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/Requests/Cookie/Jar.php on line 102
Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/Requests/Cookie/Jar.php on line 111
Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40
Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51
Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68
Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82
Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/sankarshan/sankarshan.randomink.org/blog/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
Hi!
I was once Arabic gnome translation coordinator, I ditched Linux completely and I am using Windows XP.
Sorry! But I need a working OS..
Ditched it for KDE. Developing for QT beats GTK by miles and miles.
Do you know that gconf development was stopped like 10 years ago because dconf will replace gconf. And do you know that dconf development was stopped for 2 or 3 years? That’s why.
Oh, forget the add the history of a new canvas widget. Please check out the canvas development trolls on gtk devel list.
GNOME become only a corporation made project. The code become ugly and only python or mono may have a chance to simplify the development. The codebase is old and in plain C. May be cute but is hard to make it back and GNOME starting from GNOME 2.16 seems stagnating, very small improvements (which start with Cairo + XGL) that give no intention to feel that something is changing.
gnome fans tend to defect to kde or lose interest completely when their (usually very good ideas, mockups etc) are rejected out of hand (see the osx menubar patch for gtk, dying topaz section on gnome-look.org).
gtk development has also stunted the growth of the gnome community, as it is so backwards and X like.
I still use GNOME exclusively and greatly appreciate it, but I think it must be said that the GNOME community focused on minor UI details for far to long.
Polishing had been much in need and was greatly beneficial for a time, but it started to look like GNOME was going nowhere fast.
Nonetheless, _I_ am _greatly_ excited about some of the ideas I’ve seen proposed for GNOME 3 in the last few weeks.
Where did all the brightest go? Macintosh. Like Gnome (values usability high) but it’s more polished and finished, bundled with great software.
Are you considering to pull your post now? 🙂
@Arafat then ditch XP if you need a working OS. Baring the legal issues with creating content/code using that OS it’s stability after many years is STILL not so great.
Krog has a point. QT is very VERY easy to write. While I like to do thinks in python where QT and GTK are pretty close to being just as easy as the other one, if I was writing in C++ I would probably go for QT.
As far away from Jeff Waugh and the rest of the pro-Microsoft faction in GNOME as we could get.
GNOME is a Microsoft-sponsored assault on Free Software.
I’ve been bouncing back and forth (as a user, not a developer) between GNOME and KDE for a while. I’ve done lots of Qt/C++ coding and some Clutter coding, so I am familiar with GLib-style C APIs. I must say that I like Qt/C++ a lot better. I haven’t tried GTKmm, though. Python levels the playing field considerably, but Python has its own set of issues. I think GNOME 3.0 should be taken as an opportunity to do some really innovative things, similar to what KDE did with KDE 4. I’ve been using KDE 4.1 since it was in beta (maybe earlier), and I hate going back to KDE 3. I would love to see GNOME do something similar.
Interesting post and some of the replies, a little visceral, but fairly accurate. I think that the issue with stagnating technologies and a dislike of doing objects in C seem to be the biggest issues. I have been a long term Gnome user but after learning C++ and developing in it, it just makes GObject based C seem, well, clunky.
I installed KDE4 the other day, with KDevelop I managed to knock up a simple paint program (usually the first thing I do with a new toolkit/language) and was surprised by how much easier it was when compared to Gnome. I dislike the checkbox mania of KDE but QT wins hands down against GTK for development ease/power.
For 3.0 PLEASE make a big thing about doing objects in an object based *language* (C++). Yes, Python does objects, but it is a scripting language, and I find myself wanting to use the languages I love/know rather than the latest and greatest intepreted language.
@Nick: What about gtkmm and gnomemm?
Now that Qt is going LGPL, what about some discussion about porting GnomeLibs to Qt for Gnome 3.0. This would unify the Toolkit layer in the desktops going forward. Since there was already a planned break in API/ABI compatability for Gnome 3, I see this as a significant step forward for Gnome.