I am so sick of this kind of thing. Each time someone discovers a coinage like this they think themselves clever. But it's not clever, it's trite and juvenile, and it's been done a million times before.
Bushshit, BusHitler, Sheeple, Shrubya, Chimpy, etc. They've all been beaten into the ground.
Lay off the name calling, present your ideas calmly and without the rhetoric and hysteria and people might start to take your ideas seriously. Keep it up and you'll be instantly dismissed as just another radical lefty wacko.
Simple: "The next Slashdot story will be ready soon, but subscribers can beat the rush and see it early!"
I thought that message on their site was hillarious, personally. Clearly they have a geek running their server. It's good to see companies approve of mirroring/bittorrent, etc.
I usually just end up turning on the DVD player a couple minutes before I'm ready to watch and leave the TV off. Then I go off, use the restroom, grab my food, etc. When I get back it's played through all those no-skip sections and reached the main menu, so I can just turn the TV on and start.
But yes, I agree. It would be nice to just skip those parts.
Yes, I could definitely see voice bindings in Emacsen for the more obscure but still occasionaly useful commands.
Also, so much of programming now is simply navigating around a large source base, a task which is orthogonal to modifying or writing the code. I could easily imagine saying, "go to SomeClass dot someMethod"... type type type (while cursor over a method call)... "go to definition"... type type type... "find callers. go to first caller."... type type type, build... "go to first error"... type type type, etc.
Many of these features where present in some form in previous versions of the standard, albiet as extensions. The main change is that these features have been promoted from extensions to the core.
There are perhaps some other fairly minor differences as well, but by and large, I'd expect that for those cards that already supported those extensions, it's just a matter of the vendors updating the drivers.
IIRC, there have also been draft versions of the 2.0 spec for a while, or at least the various major pieces. And seeing as how all of the major hardware vendors have representatives on the ARB, none of the final 2.0 spec should be coming as a suprise to any of them.
I'd mod you up if I still had mod points. When I first saw this, I was wondering how it was different from simply interpolating the pixels of the image. But I think you're right in that it must be superresolution; I'd thought about applying that technique to video before.
Once you've figured out the registration or spatial offset between each frame, it's pretty much just a matter of applying a reconstruction filter to the samples from all of the images adjusted for position to get back a better approximation to the original signal.
I believe it was NASA who originally developped the superresolution techniques to refine the fairly low resolution images they got back from early probes.
I've been studying C# for kicks lately and it's starting to grow on me. When I first saw it, I dismissed it as being so similiar to Java that the old Perlis quote ("A language that doesn't affect the way you think about programming, is not worth knowing.") came to mind and I might as well stick to Java which I'm already proficient at.
But recently I'd wanted to write some Windows GUI programs with native GUI and Delphi's not really viable anymore. So I decided to give C# a second chance and it's growing on me. My opinion now is that it's probably what I'd use if I had to write a GUI program for windows and didn't mind it being non-portable.
Some things that intrigue me are: almost braindead easy interop with native C/C++ DLL's (no scary JNI stuff necessary), native GUI with GUI builder in VS, delegates and an event model, a comprehensive library, fast startup time (the JIT compiler caches data between runs), and it looks like a normal EXE (and can contain resources so it shows an app icon in Explorer, etc.)
So yes, I like that I can write a program which from my perspective is written in a clean, modern, high-level garbage collected language. Users see a program that looks and feels like a plain old fashion Windows app like they're used to. If that's your goal it's a good tool for the toolbox. I'm more of a "right tool for the right job" kinda guy and to me, C# fits the bill for some niches.
For true portability or raw speed, I'd look elsewhere of course. I don't think I'll be porting my renderer from C++ to C# anytime soon. Likewise, I'll be sticking with Java for big enterprise WebApps.
I don't think machine learning is needed for this problem.
FlashBlock. already does something like you suggested with a button allowing the content to loaded. It just replaces all Flash with a placeholder that you can click to load. The newest versions add a whitelist of sites to allow (e.g. Homestar). Since there are relatively few sites with a legitimate need for Flash, it works quite well in practice.
The page says "Sorry, no Firefox 0.9 installer yet.", but I've found it works fine for me with 0.9.x.
And then next time they needed a calculator: - Hey, anyone have a calculator? - Here's mine. - Oh, that one again. er.. nevermind, I'll find someone else.
Back when I was in school, I used to find myself in the same situation, except I'd usually skip to the "okay" and afterwards offer to show them, at which point they'd usually decline. It usually worked pretty well, until a couple of friends plus my little brother finally took me up on my offer to show them, and before long they refused anyone elses.
Re:Hmmm,. I wonder if it is very nVidia centric?
on
GPU Gems
·
· Score: 1
I've looked over this book and I'm planning on getting a copy of it, even though I prefer vendor-neutral API's (and use ATI hardware myself) when I actually do real-time stuff. From what I've seen, yes, most of the pieces of example code are Cg or nVidia oriented. The concepts are pretty universal however, and shouldn't be too difficult to adapt.
sub e_rater { my $essay = shift; my $len = length ( $essay );
return 5 if $len > 4000; # Too windy return 6 if $len > 3000; # Just right return 5 if $len > 2000; return 4 if $len > 1000; return 3 if $len > 700; # Too short return 2 if $len > 300; return 1 if $len > 100; return 0; # Nothing there }
Very nice! I've had Jensen's original paper on subsurface scattering, and of course the bit in his book for some time now, but I'd missed the papers on accelerating it for practical use in a production environment.
Thanks for posting the relevant links on your site and welcome to my friends list.
Interface vs. Implementaiton Simplicity
on
Google Updates Its Face
·
· Score: 3, Informative
Before it was a simplistic search engine
Erm... I think the submitter was mistaking interface simplicity for implementation/functional simplicity. Google's a brilliant example of interface simplicity, but I doubt it's nearly so simple behind the facade. They also seem to nicely follow the rule of least suprise.
Indeed. I used to run CP/M on an Apple ][+ clone through a Z-80 daughter-board. I'd certainly call that a personal computer.
Additionally, I could have sworn hearing that their'd been some controversy that not only did MS clone CP/M, but that even some of the Digital Research copyright strings found their way into the original MS-DOS.
Not really. Unless I'm much mistaken, I imagine that you could simply set your NAT device to forward the port range to another machine. When a successful knock is performed (and assuming the NAT device uses a web administration interface like most little routers), that machine could then issue the appropriate HTTP requests to the NAT device's web administration to open and forward a port to an internal machine. Should be easy enough.
Indeed, yes. That's the single biggest issue I have with Swing. As a graphics programmer, I can't abide by aliasing in any form, and it seems like the default fonts for the Swing L&F are handpicked to alias as much as possible. (Look at any letter "y" in a Swing app to see what I mean.) It's almost painful for me to look at a Swing app. I'd be fine with using the Swing L&F if only they'd make it so I could antialias the text. I'm even okay with the Java antialiaser; anything's better than no antialiasing!
<rant> I've looked into it in the past, and found that there is no way to globally turn it on. I'd hoped that since Swing is supposed to be light-weight, I could just turn on anti-aliasing for the heavy-weight frame and it would trickle down. Instead, the only way to get antialiasing in Swing is to subclass each widget, and override the paint method to enable antialiasing and then chain to the superclass's paint method. Worse, that only works for simple widgets. For compounds like drop-down boxes, you end up with the button being anti-aliased while the list is aliased because it uses the standard list widget. Alternatively, I know there are alternate L&F's that provide this, but then anyone using the program has to install it. And even then, I'm locked into a single L&F if I want antialiasing. I can't switch L&F's (to the Windows one, say) and preserve antialiasing. Grrr... </rant>
I know I'm repeating myself (I mentioned this on the other comment in this subthread) but there's a good article on the Eclipse site about the SWT resource management philosophy.
Is there any reason GIVEN for this? Or is Java reinventing the wheel yet again, only to discover a way to wrap native widgets, and let the GC manage their death....
This article explains their reasoning pretty well. Short summary: GC finalization doesn't guarantee order, while the order of disposal is important to the OS. You can write extra code to try and order the disposal, but in the end that's difficult, tedious and error prone and slows down the code considerably.
I find this interesting, considering that, not too long ago, the Eclipse consortium offered to join with Sun (and even change to a less threatening name if need be). Sun however, turned them down.
Personally, I like the direction that Eclipse is going. I tried Forte once and it just didn't feel right. Eclipse however, has been fantastic since I found it and started using it as my work IDE. (My whole project team adopted it as well.) It has made coding Java a pleasure as no other IDE (in any language) has, and has led to me using Java as a development language for personal projects where I otherwise would have used C or C++. I've largely given over using XEmacs for coding Java. I'm also impressed by the speed of the Eclipse development cycle with new milestones coming out approximately every month. I always get this kid-in-the-candy-shop feeling checking out the New and Noteworthy page with each new milestone.
Slashdot Mirror
I am so sick of this kind of thing. Each time someone discovers a coinage like this they think themselves clever. But it's not clever, it's trite and juvenile, and it's been done a million times before.
Bushshit, BusHitler, Sheeple, Shrubya, Chimpy, etc. They've all been beaten into the ground.
Lay off the name calling, present your ideas calmly and without the rhetoric and hysteria and people might start to take your ideas seriously. Keep it up and you'll be instantly dismissed as just another radical lefty wacko.
This has been done before. Google for one of the many copies of the "Cat User's Manual". I like the original better, actually.
Simple: "The next Slashdot story will be ready soon, but subscribers can beat the rush and see it early!"
I thought that message on their site was hillarious, personally. Clearly they have a geek running their server. It's good to see companies approve of mirroring/bittorrent, etc.
I usually just end up turning on the DVD player a couple minutes before I'm ready to watch and leave the TV off. Then I go off, use the restroom, grab my food, etc. When I get back it's played through all those no-skip sections and reached the main menu, so I can just turn the TV on and start.
But yes, I agree. It would be nice to just skip those parts.
Yes, I could definitely see voice bindings in Emacsen for the more obscure but still occasionaly useful commands.
... type type type (while cursor over a method call) ... "go to definition" ... type type type ... "find callers. go to first caller." ... type type type, build ... "go to first error" ... type type type, etc.
Also, so much of programming now is simply navigating around a large source base, a task which is orthogonal to modifying or writing the code. I could easily imagine saying, "go to SomeClass dot someMethod"
Many of these features where present in some form in previous versions of the standard, albiet as extensions. The main change is that these features have been promoted from extensions to the core.
There are perhaps some other fairly minor differences as well, but by and large, I'd expect that for those cards that already supported those extensions, it's just a matter of the vendors updating the drivers.
IIRC, there have also been draft versions of the 2.0 spec for a while, or at least the various major pieces. And seeing as how all of the major hardware vendors have representatives on the ARB, none of the final 2.0 spec should be coming as a suprise to any of them.
I'd mod you up if I still had mod points. When I first saw this, I was wondering how it was different from simply interpolating the pixels of the image. But I think you're right in that it must be superresolution; I'd thought about applying that technique to video before.
Once you've figured out the registration or spatial offset between each frame, it's pretty much just a matter of applying a reconstruction filter to the samples from all of the images adjusted for position to get back a better approximation to the original signal.
I believe it was NASA who originally developped the superresolution techniques to refine the fairly low resolution images they got back from early probes.
I've been studying C# for kicks lately and it's starting to grow on me. When I first saw it, I dismissed it as being so similiar to Java that the old Perlis quote ("A language that doesn't affect the way you think about programming, is not worth knowing.") came to mind and I might as well stick to Java which I'm already proficient at.
But recently I'd wanted to write some Windows GUI programs with native GUI and Delphi's not really viable anymore. So I decided to give C# a second chance and it's growing on me. My opinion now is that it's probably what I'd use if I had to write a GUI program for windows and didn't mind it being non-portable.
Some things that intrigue me are: almost braindead easy interop with native C/C++ DLL's (no scary JNI stuff necessary), native GUI with GUI builder in VS, delegates and an event model, a comprehensive library, fast startup time (the JIT compiler caches data between runs), and it looks like a normal EXE (and can contain resources so it shows an app icon in Explorer, etc.)
So yes, I like that I can write a program which from my perspective is written in a clean, modern, high-level garbage collected language. Users see a program that looks and feels like a plain old fashion Windows app like they're used to. If that's your goal it's a good tool for the toolbox. I'm more of a "right tool for the right job" kinda guy and to me, C# fits the bill for some niches.
For true portability or raw speed, I'd look elsewhere of course. I don't think I'll be porting my renderer from C++ to C# anytime soon. Likewise, I'll be sticking with Java for big enterprise WebApps.
No, I think that would be MS -underestimated.
I don't think machine learning is needed for this problem.
FlashBlock. already does something like you suggested with a button allowing the content to loaded. It just replaces all Flash with a placeholder that you can click to load. The newest versions add a whitelist of sites to allow (e.g. Homestar). Since there are relatively few sites with a legitimate need for Flash, it works quite well in practice.
The page says "Sorry, no Firefox 0.9 installer yet.", but I've found it works fine for me with 0.9.x.
Hey! I still have to find out how Bilbo got that ring! (j/k)
No, we still need one more series before we reach Trek's Seven.
Yes, but HP gave engineers the calculator they needed.
And then next time they needed a calculator:
- Hey, anyone have a calculator?
- Here's mine.
- Oh, that one again. er.. nevermind, I'll find someone else.
Back when I was in school, I used to find myself in the same situation, except I'd usually skip to the "okay" and afterwards offer to show them, at which point they'd usually decline. It usually worked pretty well, until a couple of friends plus my little brother finally took me up on my offer to show them, and before long they refused anyone elses.
I've looked over this book and I'm planning on getting a copy of it, even though I prefer vendor-neutral API's (and use ATI hardware myself) when I actually do real-time stuff. From what I've seen, yes, most of the pieces of example code are Cg or nVidia oriented. The concepts are pretty universal however, and shouldn't be too difficult to adapt.
Very nice! I've had Jensen's original paper on subsurface scattering, and of course the bit in his book for some time now, but I'd missed the papers on accelerating it for practical use in a production environment.
Thanks for posting the relevant links on your site and welcome to my friends list.
Before it was a simplistic search engine
Erm... I think the submitter was mistaking interface simplicity for implementation/functional simplicity. Google's a brilliant example of interface simplicity, but I doubt it's nearly so simple behind the facade. They also seem to nicely follow the rule of least suprise.
Indeed. I used to run CP/M on an Apple ][+ clone through a Z-80 daughter-board. I'd certainly call that a personal computer.
Additionally, I could have sworn hearing that their'd been some controversy that not only did MS clone CP/M, but that even some of the Digital Research copyright strings found their way into the original MS-DOS.
Not really. Unless I'm much mistaken, I imagine that you could simply set your NAT device to forward the port range to another machine. When a successful knock is performed (and assuming the NAT device uses a web administration interface like most little routers), that machine could then issue the appropriate HTTP requests to the NAT device's web administration to open and forward a port to an internal machine. Should be easy enough.
Indeed, yes. That's the single biggest issue I have with Swing. As a graphics programmer, I can't abide by aliasing in any form, and it seems like the default fonts for the Swing L&F are handpicked to alias as much as possible. (Look at any letter "y" in a Swing app to see what I mean.) It's almost painful for me to look at a Swing app. I'd be fine with using the Swing L&F if only they'd make it so I could antialias the text. I'm even okay with the Java antialiaser; anything's better than no antialiasing!
<rant> I've looked into it in the past, and found that there is no way to globally turn it on. I'd hoped that since Swing is supposed to be light-weight, I could just turn on anti-aliasing for the heavy-weight frame and it would trickle down. Instead, the only way to get antialiasing in Swing is to subclass each widget, and override the paint method to enable antialiasing and then chain to the superclass's paint method. Worse, that only works for simple widgets. For compounds like drop-down boxes, you end up with the button being anti-aliased while the list is aliased because it uses the standard list widget. Alternatively, I know there are alternate L&F's that provide this, but then anyone using the program has to install it. And even then, I'm locked into a single L&F if I want antialiasing. I can't switch L&F's (to the Windows one, say) and preserve antialiasing. Grrr... </rant>
I know I'm repeating myself (I mentioned this on the other comment in this subthread) but there's a good article on the Eclipse site about the SWT resource management philosophy.
Is there any reason GIVEN for this? Or is Java reinventing the wheel yet again, only to discover a way to wrap native widgets, and let the GC manage their death....
This article explains their reasoning pretty well. Short summary: GC finalization doesn't guarantee order, while the order of disposal is important to the OS. You can write extra code to try and order the disposal, but in the end that's difficult, tedious and error prone and slows down the code considerably.
I find this interesting, considering that, not too long ago, the Eclipse consortium offered to join with Sun (and even change to a less threatening name if need be). Sun however, turned them down.
Personally, I like the direction that Eclipse is going. I tried Forte once and it just didn't feel right. Eclipse however, has been fantastic since I found it and started using it as my work IDE. (My whole project team adopted it as well.) It has made coding Java a pleasure as no other IDE (in any language) has, and has led to me using Java as a development language for personal projects where I otherwise would have used C or C++. I've largely given over using XEmacs for coding Java. I'm also impressed by the speed of the Eclipse development cycle with new milestones coming out approximately every month. I always get this kid-in-the-candy-shop feeling checking out the New and Noteworthy page with each new milestone.
I'd always figured it was a pun on the word "flashback". Just a collection of followups and flashbacks to previous stories.