Re: Possible to fix glaring Gjs API issues before GNOME 4?
- From: Travis Reitter <travis reitter collabora co uk>
- To: Nikita Churaev <lamefun x0r gmail com>
- Cc: desktop-devel-list <desktop-devel-list gnome org>
- Subject: Re: Possible to fix glaring Gjs API issues before GNOME 4?
- Date: Wed, 27 Feb 2013 15:51:38 -0800
On Wed, 2013-02-27 at 23:26 +0400, Nikita Churaev wrote:
OK, so it seems that GNOME has a serious aim on making GNOME/JavaScript
the preferred platform for new newbies.
I'd just like to reiterate that the idea isn't that JavaScript is
preferred for new developers or "smaller" applications (what would be
the cut-off?). We're going to encourage JavaScript for all new
applications (regardless of who's writing them), both for core GNOME and
third-party.
The bigger the differences between a new developer's environment and the
average core GNOME developer's, the less often core developers will run
the same code as new/third-party developers, the less they'll have to
run into the same bugs, file and fix them, and thus the less polished
our development environment will be for new developers.
Maximizing the overlap between "new" and "core" developers is key to
making GNOME a great development environment.
However, there are some API issues that make Gjs confusing, and bad
for PEOPLE.
New developers are also people :)
These issues apply to everyone, and I agree with you, they should be
fixed. Have you filed bugs for each of them? That's the safest bet that
they will get fixed. Contributing comments and code to those bugs are
also great ways to push them forward. And you'll be notified when the
bugs change state.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]