What comes to mind is that there is no free lunch in life. If you save coding time, you pay for it with compute cycles and vice-versa.
But there should be an objective way of measuring this. Since this is a very technically sophisticated group, wouldn't it make sense to have a table comparing memory usage, disk usage, and speed for a few standard setups before making a decision to switch to any other library? Fernando On 04/25/2013 09:59 AM, John Spencer wrote: > On 04/24/2013 09:31 PM, Alexis López Zubieta wrote: >> Hello everyone: >> >> I'm a student of informatics sciences in the University of Informatics >> Sciences of Cuba. I belong to a free software project that aims to >> provide to the cuban user a stable, functional and lightweight operative >> system. We have been working on it for a while and recently we made our >> 4th release. We use as desktop environment a fork of LXDE that we call >> "Guano" > > nice ! do you have a project page set up somewhere ? > for sabotage linux, i pretty much also ended up forking lxde, however > it's only a handful of bugfixes to this day. > > https://github.com/rofl0r/sabotage > >> but as we are a reduced team (6 members only) the balance >> between productivity and time is crucial to us. In this aspect the >> combination of C and Gtk don't show the best numbers, so we where > > depends on which numbers you look. when you look at memory consumption > and speed, you won't get lower numbers than with C. > > however *GTK* is pretty bloated and depends on the horrible glib > framework which inhibits robust programs: > https://bugzilla.gnome.org/show_bug.cgi?id=674446 > > OTOH what the LXDE leaders currently have in mind is even worse: > > now they want to use C++ (!) and Qt (!). > > Qt is over 100 MB of compressed sources and takes hours to build, it's > full of templates (yay duplicated code in binaries! yay debug builds > which consume gigabytes of RAM to link!), OOP (dynamic allocation > everywhere) and thus the next gen LXDE will turn into a giant hairball, > basically the next KDE. > > btw, according to the wikipedia entry about razor-qt, that one already > consumes more than 100MB of RAM to simply show the panel and a wallpaper... > on sabotage linux i do the same with lxpanel, and mem consumption is > 20MB for the entire system: http://i.imgur.com/Lz7Ov.png (early > screenshot, here's a newer one: http://i.imgur.com/2k4Hvzh.png which > doesnt show ram consumption tho) > >> studding the possibility of creating our on lightweight desktop >> environment in order to improve the architecture of LXDE and make it >> more scalable, functional and integrated. But is not wise to start >> another project and duplicate efforts, instead of that we want to join >> forces with you to create a fully functional and lightweight desktop >> environment. > > unfortunately you won't achieve this with mainline LXDE, they're heading > down the road of bloat nowadays. > >> >> We have done some research and we have some ideas and workforce that >> could be useful to the cause. In my opinion we must gather and plan the >> next step in order to make this transition quick and clean. I propose to >> start a new thread in both mailing lists and coordinate a live chat >> meeting. > > if you want to chat join #sabotage @ irc.freenode.net > > > ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
