Right now I have a Sony DSC S50. Its not top of the range or anything, but it takes nice snaps and has very nice output IMHO. But I had to buy a 64M card to store enough images at full resolution to make it worth it. Now imagine that scaled up. The sony has 2.1 M pixels. So I'd need 8 times the storage capacity. That's a half a gig of RAM in a digital camera...
Of course the trade off is superb image quality (assuming that its actually any good) - as good as PCD format by the sounds of things. But I still think that anyone _that_ seriously into photography should probably be just using film in the first place:-)
The following is one of the most often heard falacies of the napster case:
I do mind if Napster loses on the grounds that music file exchange is against the law. I will be dependent on music file exchange to advertise my music to listeners who might then buy a CD from me direct. You _cannot_ argue people into liking music. You have to play it for them and see if they like it... if music exchange over the net is forbidden that leaves only radio- and it's damned impossible to get on radio, even if you _are_ a major label act (but not 'doing tonnage').
If you want to share your music with people then do so! Send it to mp3.com or one of the many other legal mp3 hosting web sites. Or host it on your own web site. There is absolutely nothing stopping artists (fledgling and otherwise) from doing this.
I guess they've done their research on this. For me I do travel some, but never for more than about a week, and my V has never run flat. This makes me extremely happy to not have to keep replacing batteries.
Before I graduated from Durham University I took a summer internship at a small company in London (that has now pretty much been subsumed by a larger company). The things I learned there were amazing and much more interesting to me than the things I learned on my degree course: SQL optimisation, C++, shell scripting, Windows MFC programming, etc. And I went back fairly unhappy about my course.
I graduated the next year and joined that company, and did more of the same - SQL, C++, MFC, etc. Eventually I quit that company and went out on my own doing web development on a freelance basis, and did more fun stuff - Perl, HTML, more databases, etc.
Now I've finally come full circle. This year I started working on an implementation of the XML Path language, XPath, in Perl. Lo and behold, I became so glad that I never threw out all my old text books. I needed to go and re-learn parsing and algorithm optimisation, and all that stuff I thought was mostly irrelevant for the work I was doing. I've actually now re-read most of my old text books, and all of them are still relevant today.
So the point is two things:
1. The stuff you are learning will serve you for life. The fun stuff you learned as an intern somewhere will probably serve you for part of your career, but not likely all of it, unless you're happy to go into management!
2. Have fun while you're an undergrad. Go to parties. Get drunk. Have lots of sex if you can. Make friends. The most important part of University life is the social aspect, not the learning. The relationships you form at Uni should be ones you form for the rest of your life. Its very hard to find people on the same intelectual level as you in your home town. Thats not the case with Uni. Take advantage of that. As far as the learning goes - don't skip classes. Learn what you can but don't let your parents or peers push you too hard. Keep your textbooks and the learning can be re-done at a later stage.
I'll try and remember that next time I update my kernel:-) [uptime in the 100+ days region now]
On a more serious note, wouldn't any attacker be immediately blocked as soon as the chains come up, or would his connection be allowed because it already exists? Behind my 64k link I can't see anyone doing much serious if the former is the case. But if the latter is the case, I would worry a bit more about it.
I think a reply to this needs to be said, (and moderated up) because nobody else is saying this:
Be grateful for the support that companies are giving us. Because we really need it. I know, I know, it's not in fashion to have the assistance of companies; but really, we can use the help. The IBM Linux commercial even admits it: Linux has found an ally from an unexpected source.
A lot of people will debate the question of whether we really need it or not, based on the previous attempts to jump on the bandwagon without joining the team properly. We've come this far mostly without "their kind" of commercial support.
Where are the figures behind claims that GNOME is bloated? Are you talking about when you used Enlightenment as your window manager? What?
OK, looking at my system right now, I have a panel running charpick, a clock, the pager, and cpumemusage. Each is consuming well over 1 Meg of RAM, and the pager is consuming over 2. Come on! Thats a CLOCK for christ sake!!! I used to have an Amiga with 512k of RAM, and I could fill the screen with about 30 clocks, and all would run in perfect sync and I'd have ram left to play with.
GTK+ code is beautiful
I'm not going to touch that one with a 6 foot barge pole. Try using a real nice GUI framework some time.
First of all, ObjC started out just on NeXT. That made it fairly niche stuff, as you wouldn't find any hobbyists or Universities developing on that platform due to the expense of it. And you didn't find it running on probably 99% of the general computers out there, like Windows machines or other Unix machines.
The second thing was that despite the ease of development, ObjC was slower than C++ at the time. C++ used a vtable for method dispatch (static dispatch), whereas ObjectiveC was a truly dynamic dispatch system, which while being a better design overall, raised a lot of criticism that meant that a number of people didn't take up the usage of the language because of non-investigative bias (i.e. hearing this in a newsgroup post and basing everything on it). Nowadays ObjC has method dispatch caching code that makes it almost as fast as C++ vtables.
Another point is the lack of compilers. And not just free compilers either.
Then there's the runtime library issue: C++ programs link to static programs that don't require anything extra. ObjC programs require a runtime Objective C library (at least they did last time I looked at ObjC). This is offputting if the OS you are shipping for doesn't come with that by default. Note that this is not disastrous so don't flame me on it - its just something I've been told about that people have issues with.
Finally there's the strange syntax, which doesn't really follow C-like calling convention. It's [Object method:param namedparam2:param2value] is unlike anything anyone has seen in C before, whereas C++ at least was mostly just an extension of the struct idea. Of course you could go on arguing about this forever, such as the fact that Objective C is easier to debug because you can see what are method calls very clearly due to the syntax, and the named params are better. But all that is history now. People don't like to change the way they work, thats why Perl appeals to both C programmers and shell programmers alike - because the cognitive dissonance is low.
The first, which may not be viable, is to use that PCMCIA port to your advantage with either a wavelan card (distance is then limited to 800m outdoors) or perhaps one of those funky small Iomega drives (I forget what they are called right now).
The second thought is perhaps explore writing direct to tape somehow. I see that most digital video cameras have the ability to take pictures too now, although I don't know how good the photos are, and they can store many many more pics than a digital camera.
Of course both these solutions suffer from a lack of pre-built interface to the camera, so that you'll have to work out yourself. But considering you've built most of this thing already, I'm assuming that isn't too big a deal:)
Reminds me of an old Gary Larson cartoon, of parents watching kids playing on their consoles while in a thought-bubble above their heads are their dream "Employment Ads" sections:
Wanted: Super Mario player, $70,000 plus benefits
Can you rescue the princess? Join our team: $80,000.
See the latest netcraft addendum to the stats though... They found that most of those boxes are Linux+Apache boxes running massive virtual hosting. In fact register.com is responsible for (I can't recall the exact figure, but something line...) 20% of those numers, and they are just hosting default templates saying this site hasn't been uploaded yet. While in a way that's good for Linux+Apache ("Linux can easily host thousands of virtual domains"), it doesn't give any indication of the number of unique machines running linux. And neither does the number of unique IP addresses for similar reasons.
First of all, the other post here marked "The Human Approach" is a very important part of a burgeoning mailing list. But the other stuff is already available in the "better" version of ezmlm: ezmlm-idx. So get that instead.
The idx version not only allows you to create a web archive of the list that's dynamically updated, but it also allows you to strip HTML posts, remove "bad" attachments (above a certain size, certain attachment types, etc) and a bunch of wonderful moderation options.
Because this technology is totally wrong, and pretty much unsupported. JSP 1.1 is better, but even that is not nearly as nice as the really new technologies coming from Cocoon and AxKit (link below).
Yes, I'm biased, but I truly believe that the next generation web site will have to think about a lot more than just generating dynamic content quickly. And these products implement both dynamic and static content using separate presentation logic in a sensible manner.
I've actually spoken to Ingo in depth about TUX already. In fact I know the answer to my own question, but figured others would be interested.
Note though that once TUX gets integrated into Apache, its stuck with Apache's process model, its API and all the other overhead in there. Needless to say, its going to be a lot slower, and I'd be willing to bet that it wouldn't offer any significant performance improvement over Apache 2.0's MPM.
Besides, I doubt very much that the ASF will incorporate TUX. Read their list archive some time (new-httpd), and you'll see how strict they are about patches for the sake of performance (e.g. the SGI 10x speedup patches were rejected).
Would you ever advocate using TUX as a real life web server?
Think of a high availability environment, where you are building a highly dynamic application such as an e-commerce system. Would you even think of using TUX in such a situation, or would you go with the far more sensible Apache + mod_backhand + (pick one of mod_perl, php, or servlets)?
The problem is, its all too easy to generate web server software that can withstand a high "hit" rate. But the pressures on web servers, and particularly web developers, lie in completely different areas: Time to market, ease of development, and configuration capability.
I do wish pillars of the community would read the documentation before making posts like this;-)
Ghostscript's ps2pdf output format uses Flate compression where requests for LZW compression are made. This is in the documentation, and is that way because of the patent problems.
GS's ps2pdf generally produces pdf files around the same size as (or only slightly larger than) Acrobat's Distiller.
Slashdot Mirror
Right now I have a Sony DSC S50. Its not top of the range or anything, but it takes nice snaps and has very nice output IMHO. But I had to buy a 64M card to store enough images at full resolution to make it worth it. Now imagine that scaled up. The sony has 2.1 M pixels. So I'd need 8 times the storage capacity. That's a half a gig of RAM in a digital camera...
:-)
Of course the trade off is superb image quality (assuming that its actually any good) - as good as PCD format by the sounds of things. But I still think that anyone _that_ seriously into photography should probably be just using film in the first place
Is to get both an ioniser and a deioniser and stick them in opposite ends of the room, turn them up to full whack and let them battle it out!
Then in another room, get a humidifier and a dehumidifier and do the same.
Makes for hours of entertainment, far better than Quake.
I do mind if Napster loses on the grounds that music file exchange is against the law. I will be dependent on music file exchange to advertise my music to listeners who might then buy a CD from me direct. You _cannot_ argue people into liking music. You have to play it for them and see if they like it... if music exchange over the net is forbidden that leaves only radio- and it's damned impossible to get on radio, even if you _are_ a major label act (but not 'doing tonnage').
If you want to share your music with people then do so! Send it to mp3.com or one of the many other legal mp3 hosting web sites. Or host it on your own web site. There is absolutely nothing stopping artists (fledgling and otherwise) from doing this.
I guess they've done their research on this. For me I do travel some, but never for more than about a week, and my V has never run flat. This makes me extremely happy to not have to keep replacing batteries.
And don't forget Google's web page caching facility. Its going to maintain that page for a good long time...
I graduated the next year and joined that company, and did more of the same - SQL, C++, MFC, etc. Eventually I quit that company and went out on my own doing web development on a freelance basis, and did more fun stuff - Perl, HTML, more databases, etc.
Now I've finally come full circle. This year I started working on an implementation of the XML Path language, XPath, in Perl. Lo and behold, I became so glad that I never threw out all my old text books. I needed to go and re-learn parsing and algorithm optimisation, and all that stuff I thought was mostly irrelevant for the work I was doing. I've actually now re-read most of my old text books, and all of them are still relevant today.
So the point is two things:
1. The stuff you are learning will serve you for life. The fun stuff you learned as an intern somewhere will probably serve you for part of your career, but not likely all of it, unless you're happy to go into management!
2. Have fun while you're an undergrad. Go to parties. Get drunk. Have lots of sex if you can. Make friends. The most important part of University life is the social aspect, not the learning. The relationships you form at Uni should be ones you form for the rest of your life. Its very hard to find people on the same intelectual level as you in your home town. Thats not the case with Uni. Take advantage of that. As far as the learning goes - don't skip classes. Learn what you can but don't let your parents or peers push you too hard. Keep your textbooks and the learning can be re-done at a later stage.
Install Perl, be happy. :-)
I'll try and remember that next time I update my kernel :-) [uptime in the 100+ days region now]
On a more serious note, wouldn't any attacker be immediately blocked as soon as the chains come up, or would his connection be allowed because it already exists? Behind my 64k link I can't see anyone doing much serious if the former is the case. But if the latter is the case, I would worry a bit more about it.
Anyone who went to the Perl conference and saw Damian Conway speak about this will appreciate the phrase "IN CONSTANT TIME!"...
How do you edit those PDF docs?
Be grateful for the support that companies are giving us. Because we really need it. I know, I know, it's not in fashion to have the assistance of companies; but really, we can use the help. The IBM Linux commercial even admits it: Linux has found an ally from an unexpected source.
A lot of people will debate the question of whether we really need it or not, based on the previous attempts to jump on the bandwagon without joining the team properly. We've come this far mostly without "their kind" of commercial support.
Where are the figures behind claims that GNOME is bloated? Are you talking about when you used Enlightenment as your window manager? What?
OK, looking at my system right now, I have a panel running charpick, a clock, the pager, and cpumemusage. Each is consuming well over 1 Meg of RAM, and the pager is consuming over 2. Come on! Thats a CLOCK for christ sake!!! I used to have an Amiga with 512k of RAM, and I could fill the screen with about 30 clocks, and all would run in perfect sync and I'd have ram left to play with.
GTK+ code is beautiful
I'm not going to touch that one with a 6 foot barge pole. Try using a real nice GUI framework some time.
The second thing was that despite the ease of development, ObjC was slower than C++ at the time. C++ used a vtable for method dispatch (static dispatch), whereas ObjectiveC was a truly dynamic dispatch system, which while being a better design overall, raised a lot of criticism that meant that a number of people didn't take up the usage of the language because of non-investigative bias (i.e. hearing this in a newsgroup post and basing everything on it). Nowadays ObjC has method dispatch caching code that makes it almost as fast as C++ vtables.
Another point is the lack of compilers. And not just free compilers either.
Then there's the runtime library issue: C++ programs link to static programs that don't require anything extra. ObjC programs require a runtime Objective C library (at least they did last time I looked at ObjC). This is offputting if the OS you are shipping for doesn't come with that by default. Note that this is not disastrous so don't flame me on it - its just something I've been told about that people have issues with.
Finally there's the strange syntax, which doesn't really follow C-like calling convention. It's [Object method:param namedparam2:param2value] is unlike anything anyone has seen in C before, whereas C++ at least was mostly just an extension of the struct idea. Of course you could go on arguing about this forever, such as the fact that Objective C is easier to debug because you can see what are method calls very clearly due to the syntax, and the named params are better. But all that is history now. People don't like to change the way they work, thats why Perl appeals to both C programmers and shell programmers alike - because the cognitive dissonance is low.
Anyway, I hope that helps.
For more information on Objective C, apple provides free Objective C documentation (which I believe is based the original NeXT docs) at http://developer.apple.com/techpubs/macosx/System/ Documentation/Developer /Cocoa/ObjectiveC/ObjC.pdf.
Thats not scary... You're simply capturing words or options, optionally between quotes while allowing for quote escaping, using \".
Try doing that in one line with any other language and still make it as efficient as a Perl regex...
Please note that the W3C does not publish standards, it publishes recommendations.
This is a common and easy misunderstanding to make.
The first, which may not be viable, is to use that PCMCIA port to your advantage with either a wavelan card (distance is then limited to 800m outdoors) or perhaps one of those funky small Iomega drives (I forget what they are called right now).
:)
The second thought is perhaps explore writing direct to tape somehow. I see that most digital video cameras have the ability to take pictures too now, although I don't know how good the photos are, and they can store many many more pics than a digital camera.
Of course both these solutions suffer from a lack of pre-built interface to the camera, so that you'll have to work out yourself. But considering you've built most of this thing already, I'm assuming that isn't too big a deal
Reminds me of an old Gary Larson cartoon, of parents watching kids playing on their consoles while in a thought-bubble above their heads are their dream "Employment Ads" sections:
Wanted: Super Mario player, $70,000 plus benefits
Can you rescue the princess? Join our team: $80,000.
See the latest netcraft addendum to the stats though... They found that most of those boxes are Linux+Apache boxes running massive virtual hosting. In fact register.com is responsible for (I can't recall the exact figure, but something line...) 20% of those numers, and they are just hosting default templates saying this site hasn't been uploaded yet. While in a way that's good for Linux+Apache ("Linux can easily host thousands of virtual domains"), it doesn't give any indication of the number of unique machines running linux. And neither does the number of unique IP addresses for similar reasons.
This stupidity is easily solved by using object detection, rather than browser detection. Theres lots of resources on the web documenting it.
First of all, the other post here marked "The Human Approach" is a very important part of a burgeoning mailing list. But the other stuff is already available in the "better" version of ezmlm: ezmlm-idx. So get that instead.
The idx version not only allows you to create a web archive of the list that's dynamically updated, but it also allows you to strip HTML posts, remove "bad" attachments (above a certain size, certain attachment types, etc) and a bunch of wonderful moderation options.
Try it.
Leave, and go to a site like kuro5hin, where submissions are voted on by the users of the site.
Personally I read both slashdot and kuro5hin.
Because this technology is totally wrong, and pretty much unsupported. JSP 1.1 is better, but even that is not nearly as nice as the really new technologies coming from Cocoon and AxKit (link below).
Yes, I'm biased, but I truly believe that the next generation web site will have to think about a lot more than just generating dynamic content quickly. And these products implement both dynamic and static content using separate presentation logic in a sensible manner.
I've actually spoken to Ingo in depth about TUX already. In fact I know the answer to my own question, but figured others would be interested.
Note though that once TUX gets integrated into Apache, its stuck with Apache's process model, its API and all the other overhead in there. Needless to say, its going to be a lot slower, and I'd be willing to bet that it wouldn't offer any significant performance improvement over Apache 2.0's MPM.
Besides, I doubt very much that the ASF will incorporate TUX. Read their list archive some time (new-httpd), and you'll see how strict they are about patches for the sake of performance (e.g. the SGI 10x speedup patches were rejected).
Would you ever advocate using TUX as a real life web server?
Think of a high availability environment, where you are building a highly dynamic application such as an e-commerce system. Would you even think of using TUX in such a situation, or would you go with the far more sensible Apache + mod_backhand + (pick one of mod_perl, php, or servlets)?
The problem is, its all too easy to generate web server software that can withstand a high "hit" rate. But the pressures on web servers, and particularly web developers, lie in completely different areas: Time to market, ease of development, and configuration capability.
Remember that most linux distros ship with older ghostscripts. So the answer is yes. Use GS6.
I do wish pillars of the community would read the documentation before making posts like this ;-)
Ghostscript's ps2pdf output format uses Flate compression where requests for LZW compression are made. This is in the documentation, and is that way because of the patent problems.
GS's ps2pdf generally produces pdf files around the same size as (or only slightly larger than) Acrobat's Distiller.