Slashdot Mirror


User: waslap

waslap's activity in the archive.

Stories
0
Comments
5
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 5

  1. The big looser is... on How Facebook and Oculus Could Be a Great Combination · · Score: 1

    ... future kickstarters. Enthusiasts will invariably be skeptical about a sellout down the line before throwing cash at kickstarter again

  2. Re: Non-free Nvidia driver already at 4.4 on Open Source AMD Driver Now Supports OpenGL 3.3 — and It's Getting Faster · · Score: 1

    You must be extremely unlucky. We have supplied hundreds of linux based systems with only nvidia gpu's to customers and never once bricked a system. To be frank, installing an nvidia driver on linux is a non-event regardless of the distribution.

  3. Re: Flex was dead in the water years ago on Ask Slashdot: How Do You Choose Frameworks That Will Survive? · · Score: 1

    Flex/flash allows persistent sockets obviating polling which architecturally made a world's difference back then and to a certain degree still does for a certain class of applications.

  4. Yellow Marker on Document Management For Research With Annotation? · · Score: 1

    If potential document annotation s/w creators reads this: please build in a feature that simulates the ubiquitous yellow marker for PDF documents. Would have made my life much easier studying for the SCJP.

  5. I second this on Hope For Fixing Longstanding Linux I/O Wait Bug · · Score: 5, Interesting

    I am overjoyed that my suspicions have finally been vindicated. I've been working 10+hours a day on linux for the last 13years and you tend to get in tune with your environment (i can still today recite my DOS bootup tune on my XT even though I haven't worked on it for 20 years:-) and some time ago after installing a new flavour of linux I immediately started complaining to fellow workers that something has gone wrong in the kernel but it was not annoying enough to really do something about it; you start living with it. It manifests sometimes when I compile - my system simply locks up for 20-30 seconds which is something I never experienced before. I'd say it happens once out of every 50 compiles of the same program with gcc. During such occurrences, I can't access anything on my desktop which annoyes me cause I typically switch to another kterm session to prepare to run the build whilst compiling (to keep up the productivity and all that). I have also seen strange ratios of i/o to cpu wait in 'top' nowadays but can probably ascribe that to CPU's that just became ridiculously fast and the way top calculates its scores. Nevertheless, I've mumbled over and lambasted i/o wait in Linux ever since a very specific time in the past and even though I haven't noted the exact date, I'm sure its related to this. Anyway, I found this intrigueing enough to create a slashdot account after years to share my joy that the bugs days are hopefully numbered now.