Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
audidude
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
18 ms
·
181.
▲
by
audidude
10y ago
You are likely miss-remembering. The extraction of the toolkit from GIMP was done as the early pioneering of GNOME. Before that, it wasn't really a toolkit. I mean, it was an in-application toolkit, but that is very different from a us
182.
▲
by
audidude
10y ago
> As a gentoo user I would say that the ABI break may still worth it if it can enable a lot of application continuing to work with just a recompile, right? Yes, just a recompile in all the cases we've really discussed. However, if w
183.
▲
by
audidude
10y ago
> Am I wrong, or does this sound like GNOME's trying to be a more central runtime and subsume parts of a linux distro in full. I don't think so, but GNOME does have a long history of diving down the stack and fixing problems wh
184.
▲
by
audidude
10y ago
>> we have evidence we can do faster on the GPU with various shaders than any of us can do with hand written assembler these days > While true, the same shader can be written and incorporated in an engine written in C. This is not
185.
▲
by
audidude
10y ago
> I see a lot of Gnome projects started then abandoned, only to see a new project doing exactly the same thing being built from scratch afterwards. For instance, they are working on a new IDE Gnome builder, who the hell needs this when m
186.
▲
by
audidude
10y ago
> For a fundamental library like this devs should at least keep core api stable for a long time, and release unstable components seperately. This is something we'd like to get to (say external widget libraries). But it requires, gue
187.
▲
by
audidude
10y ago
If GNOME forked GTK, there would no longer be a GTK.
188.
▲
by
audidude
10y ago
> Lets not forget that Freedesktop was actually founded by Havoc Pennington while working at RH on desktop matters. Frankly Freedesktop do not exist to actually foster interoperability. it exists to whitewash RH decisions. This is ludicr
189.
▲
by
audidude
10y ago
GTK development is done by the people that show up to do the work and contribute patches. That happens to be, by and large, GNOME developers. The best way to affect GTK development is to either 1) show up for hackfests (like this week in To
190.
▲
by
audidude
10y ago
GNOME's runtime will certainly ship an up to date GTK. However, there is nothing stopping someone from creating another runtime (or even doing a gtk.org runtime) that is more conservative in nature. And if you use a compiler toolchain
191.
▲
by
audidude
10y ago
If we were going to completely rely on flatpak to solve our problems, we would be able to break ABI every 6 months w/ each GTK release. But that is not a tennable solution today (or likely ever). Distributions ship desktops which will
192.
▲
by
audidude
10y ago
FWIW, Qt has been bumping major versions more often than us as well. It really comes down to ensuring that developers are shipping a known quantity. They should be shipping with a set of libraries that were actually tested. It's unreas
193.
▲
by
audidude
10y ago
This is a completely valid viewpoint, and one we can discuss tomorrow at the hackfest. Thanks for sharing.
194.
▲
by
audidude
10y ago
> One thing regarding theming: I quite like theme engines that implement the drawing code in C because there's a lot more flexibility and room for performance. As a long time C and assembly hacker, I certainly know the feeling. Howe
195.
▲
by
audidude
10y ago
> I was always a fan of the older linux model: x.1 = unstable, x.2 = stable, x.3 = unstable, x.4 = stable. This certainly came up in our discussions... I think many people were left with a bad taste in their mouths due to trying to decod
196.
▲
by
audidude
10y ago
> That said, if Gtk3 has only been considered stable since 3.20, then more appropriate versioning/communication might have been useful, but I doubt that's what you're saying. The theming API is what I was regarding as stab
197.
▲
by
audidude
10y ago
The situation with 4.0 not being 4.x is most certainly the most contentious part of the discussion so far. It is also subject to change (it's only been a few hours so far of us discussing this). That said, if we can't guarantee th
198.
▲
by
audidude
10y ago
You could have a system that has broken software instead? But seriously, giving multiple years between the major versions is a lot of time in between for applications to port forward (or they can choose the version they want to stay on) and
199.
▲
by
audidude
10y ago
Considering this was half a day at our first hackfest of the season, I'm not surprised it doesn't sound fully fleshed out. Nor should it be this early. I'm mostly just surprised how much steam it's picked up on the comme
200.
▲
by
audidude
10y ago
We considered doing something like x.y up to z.0. But that would require that developers bump their soname multiple times if we want them to port before the toolkit is considered long term stable. It's an awful lot of work to put on de
201.
▲
by
audidude
10y ago
It turns out if you want modern features you pretty much have to change everything that was done in the drawing model in gtk2.
202.
▲
by
audidude
10y ago
> 2. Applications that have been linked for 4.2 on a system with 4.2 dev files installed will still run when the system gtk4 is 4.4. But you're not allowed to build a 4.2 app anymore once 4.4 is on the system. This means, the 4.2 .s
203.
▲
by
audidude
10y ago
Drawing with cairo-gl/glitz/etc was never really faster than drawing on the CPU. I think it's more likely that we'd use the image surface (backed by pixman) and texture uploads. If we are hitting a path where we expose t
204.
▲
by
audidude
10y ago
Thank you so much for writing this post. I know it must have taken quite a bit of time to put together. I don't think all the reasons about the choices we've made were necessarily accurate, but the post is so valuable on it's
205.
▲
by
audidude
10y ago
Agreed. It seems wildly out of date. I'll track down who has access to the site and see if we can update it during the hackfest in a couple weeks.
206.
▲
by
audidude
10y ago
I am trying to not come off as lecturing. My apologies if it was interpreted as such. You were making claims and I'm simply trying to provide examples of how other peoples computing experience might not match your own. > Okay so aft
207.
▲
by
audidude
10y ago
If your platform is X11, Wayland, or Mir :)
208.
▲
by
audidude
10y ago
> Usually when there are accessibility issues you add options to deal with that, you don't change everything for a relatively tiny percentage of your user base. Would you make all your widgets have max contrast and double the font s
209.
▲
by
audidude
10y ago
Have a bug number? Link to the driver issues? I've worked on a lot of systems, including popular virtual machines display implementations (the most likely system to hit the SVGA mode) and have not seen this. I have, however, seen compo
210.
▲
by
audidude
10y ago
Contrary to what people seem to think, just because GTK+ compiles on Windows and OSX, doesn't mean we are trying to be a cross-platform toolkit. Many GTK+ developers consider GTK+ to be a platform in it's own right, not a portabil
More ›