More momentum? Are you mad, man? Are you saying that it's easier to move a more "massive" (technical definition) object? Work requires a force to be exerted, and the force required is (very basically) distance times mass.
File-type inheritance. XML is probably ideal. Yes, you'd need to change the spec. But just disregard that for a while. This doesn't have to be XML.
GIF, JPEG, PNG, PSD, TIFF, BMP... all are image formats. All display an image. They have slightly different purposes (TIFF for excellent quality, JPEG for effective compression), but the point is that they share the same purpose, mostly. Why not an XML 'Image' DTD that defines the interface for interacting with an image. So I can write a utility in Perl, Java, C - whatever - to read images. They don't all use the same format, they all extend it, adding functionality (the JPEG type would have the ability to set the compression level in the image). So you don't lose any functionality -- it's there if you want it.
There could be a sub-interface on the Image type -- the VectorImage. I can also write a program which handles VectorImages -- maybe Illustrator, SVG, and Freehand documents. But you can still treat all these as pure images, if you like
This has probably been thought of before. What do people think?
Am I the only one who gets the impression from this book, and similar titles, that they're simply attempting to profit from popular conceptions of the internet as something borderline-legit? Full of unpalatable, revolutionary types hob-nobbing with disgruntled geeks intent on wreaking havoc... This is certainly the message many people are getting, from the popular media especially.
Is it perhaps time for a code rewrite in Sendmail, or maybe a quiet, dignified retirement? It appears, from empirical evidence, that Sendmail is insecure by design. And that's not a good idea for a mail server, in today's world of spam
I'm not convinced that web-developers need a knowledge of HTTP. Even sessions can be handled very transparently with newer web-dev languages/dialects like PHP and JSP. Sure, it is a benefit to have an understanding, but the average developer is better off putting his work into understanding Dreamweaver or Photoshop.
Web-development does not require a knowledge of HTTP, and this is the way it should be. You shouldn't need to understand ASCII, etc., to use a word-processor.
What I'd like to know is how the RIAA determine the extent of the file swapping. It's easy enough to determine whether you're sharing -- do a search, note IPs.
But they seem to claim that some sharers are more active than others. Is the ISP releasing records and logs, as well as client identification details? Are they legally obliged to?
This sounds nice and ideological. In keeping with that, it'll be Aspect-Oriented, written in Lisp, and written by smiling students straight out of image libraries
This is a disappointing move for Linux and Trillian users alike, but it shows some pretty shrewd reasoning from Microsoft.
Unlike most other communication systems, IM relies on your friends being on the same network as you. By building up a web of contacts, you have created a huge amount of inertia. I currently use MSN Messenger (I started a few years back) in tandem with Jabber, and it would be extremely difficult for me to switch.
It would be an almost irresistible move for Microsoft to start charging individual users for use of the service. Is that likely? It's Microsoft.
Corporations are the people Open-Source needs to get on its side. (And, I might add, the OS community is doing a very good job here). They give a project name-recognition, thousands of users, good infastructure, and credibility. PostgreSQL will hopefully begin to compete seriously with Oracle. Another feather in the Open-Source cap.
In the argument against software patents, it is often said that they will be to the advantage of large corporations, who will use them against smaller outfits. They don't come much bigger than Microsoft, or smaller than Eolas. Which makes this case slightly ironic.
OS/2's failure was in no small part due to the lack of native applications. It was just assumed that Windows binaries worked, which they did. But then, there was no advantage to running OS/2. Linux would do well to bear it in mind.
A suggestion: sending limitations
on
Replacing SMTP?
·
· Score: 1
The primary problem with Spam is its automated, bulk, impersonal nature. It wouldn't be so bad if a sales rep personally wrote you a letter. That would be almost tolerable, and would protect against delugest of spam. To prevent the former, could it help to add an extension to SMTP making it impossible to send more than, say, 10 e-mails of identical (or very similar) content per server per day. Mailing lists? These are formalised on an opt-in basis, and dealt with specially.
Re:Nice to see the sideswipe at .NET (not)
on
Nat Demos Dashboard
·
· Score: 4, Insightful
It's maybe a little ironic that large portions of the OS community are generally against C# and Mono, as it is a Microsoft technology. Mono is an OS clone of a mainly proprietary technology.
This possibly goes without saying, but it is none too difficult to create a far better solution, for considerably less money, by buying components individually. Mini-itx.com is a good place to start. $1,200 for this is, frankly, too expensive.
This means that 9% of companies have already made a concrete decision based on a case yet to reach the courts. How many more companies are having doubts? How many more companies will change their position when this receives more coverage? How many more companies intend to change their policies in the future? How many companies are deciding that they are right to stay with Windows in the near future? How much is this hurting Linux's image?
9% is the tip of the iceberg. And gung-ho is the last thing the Linux community should be
This could potentially increase the proliferation of democracy as voting should become easier, more reliable and cheaper to administer, if handled carefully.
It might be of more benefit to everyone if the GTK people focussed instead on overall useability, which is lacking in many places. Once the interface is as refined as, say, that of OS X, we can concentrate on the eye-candy.
Slashdot Mirror
More momentum? Are you mad, man? Are you saying that it's easier to move a more "massive" (technical definition) object? Work requires a force to be exerted, and the force required is (very basically) distance times mass.
A suggestion.
File-type inheritance. XML is probably ideal. Yes, you'd need to change the spec. But just disregard that for a while. This doesn't have to be XML.
GIF, JPEG, PNG, PSD, TIFF, BMP... all are image formats. All display an image. They have slightly different purposes (TIFF for excellent quality, JPEG for effective compression), but the point is that they share the same purpose, mostly. Why not an XML 'Image' DTD that defines the interface for interacting with an image. So I can write a utility in Perl, Java, C - whatever - to read images. They don't all use the same format, they all extend it, adding functionality (the JPEG type would have the ability to set the compression level in the image). So you don't lose any functionality -- it's there if you want it.
There could be a sub-interface on the Image type -- the VectorImage. I can also write a program which handles VectorImages -- maybe Illustrator, SVG, and Freehand documents. But you can still treat all these as pure images, if you like
This has probably been thought of before. What do people think?
Am I the only one who gets the impression from this book, and similar titles, that they're simply attempting to profit from popular conceptions of the internet as something borderline-legit? Full of unpalatable, revolutionary types hob-nobbing with disgruntled geeks intent on wreaking havoc... This is certainly the message many people are getting, from the popular media especially.
Is it perhaps time for a code rewrite in Sendmail, or maybe a quiet, dignified retirement? It appears, from empirical evidence, that Sendmail is insecure by design. And that's not a good idea for a mail server, in today's world of spam
Web-development does not require a knowledge of HTTP, and this is the way it should be. You shouldn't need to understand ASCII, etc., to use a word-processor.
What I'd like to know is how the RIAA determine the extent of the file swapping. It's easy enough to determine whether you're sharing -- do a search, note IPs.
But they seem to claim that some sharers are more active than others. Is the ISP releasing records and logs, as well as client identification details? Are they legally obliged to?
For nothing? No... "Nothing's ever a complete waste of time -- it can always serve as a bad example"
Good. Open-source rocks
Open-source sucks
This sounds nice and ideological. In keeping with that, it'll be Aspect-Oriented, written in Lisp, and written by smiling students straight out of image libraries
Released, too, under a virulent license like the GPL? Would the governments have to release sources of their modificiations?
This is a disappointing move for Linux and Trillian users alike, but it shows some pretty shrewd reasoning from Microsoft.
Unlike most other communication systems, IM relies on your friends being on the same network as you. By building up a web of contacts, you have created a huge amount of inertia. I currently use MSN Messenger (I started a few years back) in tandem with Jabber, and it would be extremely difficult for me to switch.
It would be an almost irresistible move for Microsoft to start charging individual users for use of the service. Is that likely? It's Microsoft.
I wonder how much MIT paid VA Software today...
A Good Thing(tm)
Corporations are the people Open-Source needs to get on its side. (And, I might add, the OS community is doing a very good job here). They give a project name-recognition, thousands of users, good infastructure, and credibility. PostgreSQL will hopefully begin to compete seriously with Oracle. Another feather in the Open-Source cap.
In the argument against software patents, it is often said that they will be to the advantage of large corporations, who will use them against smaller outfits. They don't come much bigger than Microsoft, or smaller than Eolas. Which makes this case slightly ironic.
As a by-the-way, Eolas is the Irish-language word for 'knowledge'.
Free software: Free as in speech, not beer. GNU's zealotry seems exactly the opposite of this.
Time for them to climb down from their ivory towers and grow up
OS/2's failure was in no small part due to the lack of native applications. It was just assumed that Windows binaries worked, which they did. But then, there was no advantage to running OS/2. Linux would do well to bear it in mind.
The primary problem with Spam is its automated, bulk, impersonal nature. It wouldn't be so bad if a sales rep personally wrote you a letter. That would be almost tolerable, and would protect against delugest of spam. To prevent the former, could it help to add an extension to SMTP making it impossible to send more than, say, 10 e-mails of identical (or very similar) content per server per day. Mailing lists? These are formalised on an opt-in basis, and dealt with specially.
It's maybe a little ironic that large portions of the OS community are generally against C# and Mono, as it is a Microsoft technology. Mono is an OS clone of a mainly proprietary technology.
...Almost like a certain Operating System
This possibly goes without saying, but it is none too difficult to create a far better solution, for considerably less money, by buying components individually. Mini-itx.com is a good place to start. $1,200 for this is, frankly, too expensive.
This means that 9% of companies have already made a concrete decision based on a case yet to reach the courts. How many more companies are having doubts? How many more companies will change their position when this receives more coverage? How many more companies intend to change their policies in the future? How many companies are deciding that they are right to stay with Windows in the near future? How much is this hurting Linux's image?
9% is the tip of the iceberg. And gung-ho is the last thing the Linux community should be
Lunch paid for by Microsoft? We could perform an en-masse, real-life slashdot on them!
This could potentially increase the proliferation of democracy as voting should become easier, more reliable and cheaper to administer, if handled carefully.
It might be of more benefit to everyone if the GTK people focussed instead on overall useability, which is lacking in many places. Once the interface is as refined as, say, that of OS X, we can concentrate on the eye-candy.