Slashdot is powered by your submissions, so send in your scoop


Forgot your password?
Compare cell phone plans using Wirefly's innovative plan comparison tool ×

Comment Re:It's been dying since KDE3 (Score 1) 512

I didn't want to debate whether Gnome was a failure or a success with GP. That's subjective depending on what exactly you mean. I think had Maemo been a success Gnome would be on a few billion devices. Gnome itself isn't to blame for the failure of Maemo but it certainly contributed. The fact that Android doesn't run Gnome and that Tizen is based on EFL is what the Maemo failure cost them. They are cut out of the market they wanted. Sure they are dominant in the Linux desktop market but during the Gnome 2 days they saw how limited that was and would be.

  Mobile is about 4x the size of desktop. Linux desktop is a tiny share of desktop (about 1%). Getting most of 1% of 1/5 of the market, depends on your point of view.

Comment Re:We're All Dying (Score 1) 512

-- If you want to see responsiveness try gnome2 applications either locally or remotely and compare them to the current ones locally even with a video card accelerating things for you.

Sure. Try your experiment. Have several video streams going in different windows and rapidly move the windows relative to one another. Or try anything else that requires a high framerate and lots of video information.

-- Blaming network transparency is just a distraction from losers who wouldn't know how to get their stuff running well on any platform. It never had anything to do with responsiveness because local applications get to use local sockets.

Network transparency in the proper sense doesn't exist on modern interfaces. If you mean how they fake it then yes that has an impact on performance. We've talked about this before. You can't safely directly render to X11's compositor without a high risk tearing. The application can't tell the compositor how to render and so half rendered content gets displayed. That's not ignorance it is deep design. To solve this applications render to a buffer and then do a memory copy. The speed of the memory bus is going up, but much more slowly than resolutions so this problem has gotten worse not better since Wayland started.

High performing applications need to control the rendering process cheaply.

Comment Re:How to advocate for desktop dev in a phone worl (Score 1) 512

The foisting of mobile on everybody was a solution to how to leverage network advantages over a huge range of physical typographies. Whole classes of problems like maintaining phone contact lists (what's Bill's mother's phone number since he goes over to her place every other Wednesday night) are simply gone. Literally billions of new people have a programable high powered digital device in the last decade who did not before. Among the 1st world who had computers they not only have a computer somewhere in the house but they have a fully internet capable device with them 24x7.

Newer in this case is vastly better. Its not even remotely close. Mobile is the source of the massive performance gain. Now desktop now has to adapt to mobile. That's not some pointless quest for shiny but rather trying to keep desktop relevant.

Comment Re:It's been dying since KDE3 (Score 1) 512

Gnome transition was a different thing. Gnome foundation made a clear choice after Maemo's failure that flexibility for mobile not parity with Windows was the top priority. You may not agree with the choice but that wasn't just bells and whistles. Gnome 3 may be a failure. But the success of iOS shows that their idea could have worked were it better executed.

Comment Re:We're All Dying (Score 1) 512

Users like systemd its old school admins who are throwing a fit. Users mostly want graphical responsiveness it is old school Unix guys that don't think responsiveness is worth losing network transparency (which they don't really have anymore even with X). Users want mobile integration it is old school Linux guys (hey you are old school now) that want a more classic desktop.

The problem isn't users but a small subset of users that are disproportionately on /.

Comment Re:We're All Dying (Score 1) 512

The canonical hacker breed if fine. The kids are doing all sorts of exciting web based stuff. They grew up in an environment where windows was stagnant, and the desktop apps on it were cumbersome and deeply entrenched. Web was vibrant, mobile is vibrant and the gaming platforms are vibrant. Same way our generation doesn't have a bunch of the mainframe / mini hackers who loved to reconfigure the OS directly because well by the time we came up mainframes and minis were dying and no one was letting a 12 year old play with one.

Comment At UMinn (Score 0) 225

UMinn was the center for gopher. I remember when the WWW came out I figured that built in indexing (think the Yahoo of the 1990s) was more important than graphics and Gopher would remain the dominant platform. Some school loyalty but mostly one of the worst predictions of my life. Gopher was quite good. The web would be a more educated place today had it remained gopher / nnews. But porn and advertising were too much for good content to beat.

Comment Re:Saturation (Score 1) 170

I think we do have that kind of software.

1) Presentation software, sales systems like powerpoint are way more advanced
2) Interactive books (iBooks)
3) Photo viewers and browsers to replace albums
4) Shopping experience websites (tablet users love the interactive shopping experience)
5) Tablet gaming
6) Note taking

I'd say that's a pretty successful. Apple's statistics show that their tablets are still heavily used. Where they have had problems is creating incentives for upgrades.

Comment Re:Saturation (Score 2) 170

One of the big upsides of Android is hardware diversity. Device manufacturers can easily customize the device for markets and sub markets. The downside is you have hardware diversity induced by easy customization and thus support is expensive and complicated. Two sides of the same coin.

Comment Re:I assumed this was already a default (Score 1) 924

netcat is the sort of thing that likely you would want to "save state" by recording running commands and reissue.

The best way to save state for an editor is to have them write the file out during save of state for the reason you mentioned. This sort of autosaving is for example implemented in OSX for precisely the reason it allows the process manager to decide between multiple potential editors. The other possibility would be to save state by
a) If the file is unchanged allow the editor to reload
b) If the file has changed, dump the contents. Since both emacs and vim maintain a temp file they will make the temp version available on restart.

Comment Re:security best practice? (Score 1) 924

The scenario is a situation where the admin doesn't want processes that take 100% for a couple hours or likely 100% for a couple minutes. 100% for a couple seconds might be iffy but just slip through. If a job is capable of tying up the system for hours it should in most cases be scheduled not run by an end user.

Neither is a bad or a good thing in and of itself its whether the use case fits the admin's (or really the owner's) desired usage for their system.

Nice is a more primitive form of process management. Nice should be absorbed are replaced.

Slashdot Top Deals

You might have mail.