Originally posted by leipero
View Post
Announcement
Collapse
No announcement yet.
GNOME 3 Might Be Too Resource Hungry To Ever Run Nicely On The Raspberry Pi
Collapse
X
-
Originally posted by oleid View Postshow us your code, and then we keep talking.
- Likes 2
Comment
-
Direct effects (not of radiation) of CoC, political correctness, outreachy programs, discrimination of majority in favor of (some) minorities and other "innovations" to "boost" code/software quality. And a new metrics of stupidity and a recipe for a guaranteed disaster. Scary!!
- Likes 2
Comment
-
Originally posted by Pawlerson View Post
I think he meant they're male 'virgins' who didn't have sex in their entire life. It would explain few things.
Comment
-
I have been using Ubuntu on my laptop since version 11.04 (a ThinkPad x220 purchased in june 2011).
i have always read many complaints about Unity but to me it worked fine. In 2014 I upgraded my laptop to 16GB ram and a 1TB 850 EVO and since than I have been unable to find a good reason to spend $1+k on a new machine.
Well, after moving from Unity back to Gnome on 18.04 I can finally say my main machine is no longer fast enough. What bothers me the most is the keyboard input delay. And Gnome on Wayland (I tried that hoping to improve things) crashes almost daily.
After reading the article and the thread I believe there is indeed something wrong with Gnome 3. Time to try a different DE and keep the laptop a while longer until laptops with quad cores and capable of at least 32GB RAM become an affordable reality.
Comment
-
I haven't personally owned a laptop before but I've used some owned by others for applications that required other operating systems (a windows 10 toshiba, an apple macbook, etc...).
In terms of CPU usage, gnome-shell has always been fast enough when I had an intel core2duo with 4GB ram desktop and became faster when I upgraded to a skylake corei5 with 16GB ram. The only bottleneck was always the GPU. The Fermi and kepler cards were too slow for gnome-shell and GTK+ CSD windows and that is one reason I never liked CSD windows. Upgrading to 1050Ti pascal card heavily improved performance.
The only issues I still see are memory usage issues. But I believe those will improve since gnome usage is increasing with Ubuntu/Endless using recent gnome versions. More testing coverage normally exposes bugs much faster and naturally pushes for improvements.
Gnome 3.26 and 3.28 are already much better than 3.16 and 3.18 but there is much room for improvement.
Comment
-
Originally posted by ebassi View PostNo, that's absolutely broken culture, and this is why people stop contributing to free software.
- Likes 1
Comment
-
Originally posted by johanb View PostYes JavaScript is fine as a scripting language, however writing a shell is not a place where I'd consider it to be a good place to use a scripting language for similar reasons to why it's not a good decision to write it in python or to write the core of a game engine with it.
Comment
-
Originally posted by Weasel View PostI'm personally sick of seeing projects that are similar, one written in proper language like C, one written in some obscure crap with "scripting features" in a bloated language like JS (instead of say, Lua), and then the latter using up 10 times more memory, taking up 10 times more disk space, etc etc.
Comment
-
Originally posted by cynical View PostThe language was brilliant for its time, but broken by modern standards in significant ways.
C is also not broken by definition. Broken are the programmers that lack knowledge about proper programming skills. People that have never programmed to save clock cyclles, ram, space, performance and speed. Of course these things doesn't need to be driven religious here, but performance still matters.
Rather than speaking about optimizing code, these "so called developers" nowadays say "hardware is cheap", "harddisk space is cheap" as an excuse for their bad coding capabilities.
And clearly JS does not belong into a Desktop shell!. For what ? Eating up all resources ? To use JS to code a few extensions (which says that there is a problem with the overall functionality of the shell per se) ? Or to make the entire desktop crawl like hell ?
Compare Gnome3 with e.g. AROS or MorphOS. Both systems are entirely written in C., They boot up within seconds (a blink with the eye) on ancient rotten hardware. Clicking on an Icon to launch the program is another blink with the eye and the software is loaded up.
For the person saying "show me the code and we can talk".
The code is all there. It has been abandoned for underperformant technology. Gnome has always been like this. Replacing things before they even come to a mature level.
gnome-config replaced by gconf2. gconf2 wasn't even able to mature and got replaced by dconf (or was it called zerconf). The aim was to use it even for system configuration. Luckely no one bothered using it. Bonobo got nuked, BonoboUI got nuked, Bonobo-Config got nuked, Corba got nuked and so on. Of course some technology makes sense and others not. Replacing some of the code to unify things is good too. But Gnome had all of that.
And now ?
With Gnome3 we got 4 new paths for Gnome.
1) Gnome3
2) MATE Desktop as a fork or continuation of Gnome2
3) Cinnamon Desktop as a highly configured version of Gnome Shell + a fork of Nautilus and a few other tools
4) Not entirely a Fork or something but the "Gnome Fallback" option - that by definition - should have gone years ago but still kept because they hope to get moved off people back
A Desktop is a clean area with icons, a top or bottom bar, an application launcher thingy that eats around 0.1% of the overall CPU time, takes less than 10mb of Ram (make it 50mb for HiDPI stuff) and does nothing else. I don't want it to go in some sort of expose kind of feature, when I want to access the program launching bar and have all my connected monitors (3 in my case) go to that expose feature too, just because gnome shell wants it like that and make my critical software go off for a few seconds because of the expose stuff.
And again C may be old - but it's the proper language to achieve this. Learn to code, learn to allocate and free memory, learn how to use a debugger. Performance matters even on old hardware. Get off with the attitutde that "hardware is cheap". Firstly it may be cheap - but it's not YOU who buys me the new hardware and secondly get some sense for our environment and all the plastic and electronic junk we create.
- Likes 5
Comment
Comment