"It can only be the thought of verdure to come, which prompts us in the autumn to buy these dormant white lumps of vegetable matter covered by a brown papery skin, and lovingly to plant them and care for them. It is a marvel to me that under this cover they are labouring unseen at such a rate within to give us the sudden awesome beauty of spring flowering bulbs. While winter reigns the earth reposes but these colourless green ideas sleep furiously."
If you do get arrested, just call your lawyer. Hopefully, they have a landline (or something that looks like a landline to the phone doing the collect calling...)
The "no context" is not an inescapable consequence of the infamous 140-character medium -- the web has a useful, low-character, way to spread context: links. With bit.ly and similar services, embedding links to longer reports is easy.
Set up Firefox and Firebug, and you have a wonderful console for programming right from the browser. You can do fun animations, effects, and various cool things.
And showing it to friends is as easy as uploading to a host...
The Dojo toolkit is going to get some love this SoC -- these things might be making their way into your machine even without you knowing it...
Markup Previews, 3D effects and Drag&Drop form editor are all among the SoC projects this year.
1. GDM -- why would distributions work extra-hard just so you could install "your choice" of a login screen? Because it's "bloated"? How bloated is GDM? What computers can't handle it? How were they configured? After all, after you log-in, GDM does nothing, so all its dirty pages would just get paged to swap, and that would be that. A little bit of swap space? Is that the problem? How old is the laptop? Because on my 4-year-old laptop, it works fine.
2. Desktop applets -- I'm pretty sure it is easy to turn off any desktop applets. After all, half of them support "remove from panel" natively, and the ones that don't are pretty easy to disable, if you're that hard-core. It is probably not cost-effective for distros to invest that much maintainance on something that nobody uses. "Has no battery"? So this old laptop is powered by love and harmony?
3. Ah, life wouldn't be complete without a rant against Python, complete with implying that Python programmers are drooling idiots because otherwise they would have chosen a "real" programming language like C. But wait, there's more! After doing a back-of-the-envelope analysis of Python's performance problems (sans the envelope, of course), there's also a clear explanation of how to solve them. Never mind that the VM is loaded just once because of how executable pages work under linux.
And these days, there's an alternative. Get an eeePC or equivalent. For 300$, there's no longer need to resurrect your old laptops with crappy battery life.
These laws are outdated as any law dealing with technology might become. We have cameras everywhere, and they will record things, and these things will be on the internet. Are you seriously going to hunt down every YouTube or Flickr picture that has your face in it? Or are you going to accept that just like people can *gasp* walk down the street and *SEE YOU*, well, the street (or people's vision) just got bigger. You can see everyone in the world, everyone can see you, and you know what? It's not such a big deal.
I decided that the license tries to be intentionally unclear -- even the "commercial" license. "Domains and sub-domains"? What if I'm distributing a non-open-source web application? And what does "developer license" mean? I mean, if people develop against the GPL3 version, can they deploy against the commercial version? Wouldn't that mean that any company could buy just one license and put it on the build-distribution machine?
The licensing model scared me away. Now I am extremely glad to have been scared away.
Ext looks to be a pretty good library -- but it's not for anyone who wants to know what's in the future of the development, and who hopes to not get screwed over.
Why should I buy two machines? Why shouldn't I compile when I'm on the road? It makes perfect sense to close the gap between laptops and desktops, and keep just laptops and "servers".
When I bought my laptop, I shopped specifically for when which can serve me well as a desktop. I had to compromise on disk space, though frankly 40GB is not that big a compromise, but most other features are exactly what I would choose for a desktop -- and it wasn't even that expensive (if you figure in the cost of the monitor, the 3-year warranty from a well-known company and the value of the computer not going down when the power is out for a few hours, in fact, it is cheaper than buying a comparable workstation).
Ummmm....you could do what the site suggested, and use a browser which receives weekly-monthly security updates (like, say, Firefox) rather than one which has bi-yearly updates (like IE).
Why did the bank not do this *before* the thieves got their hands on the plans? Surely, it could anticipate the likelihood and hire the security specialists when they installed the safe. In fact, banks do. This is what we mean by "security by obscurity doesn't work".
People are forgetting that the web browsers are meant to render a page *in the way that helps the user the most*, not the way the "original maker intended"...
These browsers (based on IE, but that's an implementation detail) give users a way to "auto type" words into a search engine. I don't see how this is, in any way, "hijacking content". If users don't want this, then they won't use these systems. And if they do, who is the "site owner" to tell them how to render the HTML she sends them?
First of all, let me just say that the person who designed the mbox format should be shot without a trial. I can just imagine what went on in his head "hmmm....I have to find some format for RFC8222 messages together. Oh, I know! I'll just throw them in one big file. Wait, but how will I know where e-mails end? What's one of the popular words in English? From! I'll use "From " to distinguish e-mails, and let people quote from-lines". Really!
MBox is also very little suited to programs like MH or PMS, because it's very dangerous to store offsets into mbox files.
MH has its own format, which is particularily cool because you can have e-mails and folders in the same folder.
Other formats inclue ZODB (if you read all your e-mail in Python, of course;-), or a plain old database (cool feature: no need to retrieve headers the mailer won't show).
Python's C source is written by Python programmers - they value elegant code.
I know a lot of people who were struck by the clarity in the Python sources. It's pretty easy
to understand and modify. Heck, I fixed a bug after using Python for two weeks.
Slashdot Mirror
"No wireless. Less space than a nomad. Lame."
"It can only be the thought of verdure to come, which prompts us in the autumn to buy these dormant white lumps of vegetable matter covered by a brown papery skin, and lovingly to plant them and care for them. It is a marvel to me that under this cover they are labouring unseen at such a rate within to give us the sudden awesome beauty of spring flowering bulbs. While winter reigns the earth reposes but these colourless green ideas sleep furiously."
Taken from http://en.wikipedia.org/wiki/Colorless_green_ideas_sleep_furiously#Attempts_at_meaningful_interpretations
If you do get arrested, just call your lawyer. Hopefully, they have a landline (or something that looks like a landline to the phone doing the collect calling...)
The "no context" is not an inescapable consequence of the infamous 140-character medium -- the web has a useful, low-character, way to spread context: links. With bit.ly and similar services, embedding links to longer reports is easy.
"They're made of meat."
"Meat?"
http://home.earthlink.net/~paulrack/id82.html
Apparently, only in doing business with Russians?
When Dell came to Israel, a similar (I imagine) spiel has got him started negotiating for building a Dell R&D center here.
I suggest the "andapony" tag to apply to this, and similar, fluff pieces.
Teach him JavaScript.
Set up Firefox and Firebug, and you have a wonderful console for programming right from the browser. You can do fun animations, effects, and various cool things.
And showing it to friends is as easy as uploading to a host...
The Dojo toolkit is going to get some love this SoC -- these things might be making their way into your machine even without you knowing it... Markup Previews, 3D effects and Drag&Drop form editor are all among the SoC projects this year.
How do things like that get modded "insightful"?
1. GDM -- why would distributions work extra-hard just so you could install "your choice" of a login screen? Because it's "bloated"? How bloated is GDM? What computers can't handle it? How were they configured? After all, after you log-in, GDM does nothing, so all its dirty pages would just get paged to swap, and that would be that. A little bit of swap space? Is that the problem? How old is the laptop? Because on my 4-year-old laptop, it works fine.
2. Desktop applets -- I'm pretty sure it is easy to turn off any desktop applets. After all, half of them support "remove from panel" natively, and the ones that don't are pretty easy to disable, if you're that hard-core. It is probably not cost-effective for distros to invest that much maintainance on something that nobody uses. "Has no battery"? So this old laptop is powered by love and harmony?
3. Ah, life wouldn't be complete without a rant against Python, complete with implying that Python programmers are drooling idiots because otherwise they would have chosen a "real" programming language like C. But wait, there's more! After doing a back-of-the-envelope analysis of Python's performance problems (sans the envelope, of course), there's also a clear explanation of how to solve them. Never mind that the VM is loaded just once because of how executable pages work under linux.
And these days, there's an alternative. Get an eeePC or equivalent. For 300$, there's no longer need to resurrect your old laptops with crappy battery life.
Not anymore, in any case.
These laws are outdated as any law dealing with technology might become. We have cameras everywhere, and they will record things, and these things will be on the internet. Are you seriously going to hunt down every YouTube or Flickr picture that has your face in it? Or are you going to accept that just like people can *gasp* walk down the street and *SEE YOU*, well, the street (or people's vision) just got bigger. You can see everyone in the world, everyone can see you, and you know what? It's not such a big deal.
I decided that the license tries to be intentionally unclear -- even the "commercial" license. "Domains and sub-domains"? What if I'm distributing a non-open-source web application? And what does "developer license" mean? I mean, if people develop against the GPL3 version, can they deploy against the commercial version? Wouldn't that mean that any company could buy just one license and put it on the build-distribution machine?
The licensing model scared me away. Now I am extremely glad to have been scared away.
Ext looks to be a pretty good library -- but it's not for anyone who wants to know what's in the future of the development, and who hopes to not get screwed over.
So, a girl from California beats a robot. How is this news?
Does anyone know which patent it actually was, just so we can look at it and see how idiotic it is?
This is why my e-mail is accessed through secure (https) webmail.
Why should I buy two machines? Why shouldn't I compile when I'm on the road? It makes perfect sense to close the gap between laptops and desktops, and keep just laptops and "servers".
When I bought my laptop, I shopped specifically for when which can serve me well as a desktop. I had to compromise on disk space, though frankly 40GB is not that big a compromise, but most other features are exactly what I would choose for a desktop -- and it wasn't even that expensive (if you figure in the cost of the monitor, the 3-year warranty from a well-known company and the value of the computer not going down when the power is out for a few hours, in fact, it is cheaper than buying a comparable workstation).
It most definitely wasn't. Buffy, Season 5, Episode 16, "The Body", the famous Tara/Willow kiss.
"Strong like an amazon". Look it up!
Wouldn't you get roughly the same thing by just glueing some display to the RAM, for something like a quarter of the price?
Ummmm....you could do what the site suggested, and use a browser which receives weekly-monthly security updates (like, say, Firefox) rather than one which has bi-yearly updates (like IE).
Article
Why did the bank not do this *before* the thieves got their hands on the plans? Surely, it could anticipate the likelihood and hire the security specialists when they installed the safe. In fact, banks do. This is what we mean by "security by obscurity doesn't work".
These browsers (based on IE, but that's an implementation detail) give users a way to "auto type" words into a search engine. I don't see how this is, in any way, "hijacking content". If users don't want this, then they won't use these systems. And if they do, who is the "site owner" to tell them how to render the HTML she sends them?
First of all, let me just say that the person who designed the mbox format should be shot without a trial. I can just imagine what went on in his head "hmmm....I have to find some format for RFC8222 messages together. Oh, I know! I'll just throw them in one big file. Wait, but how will I know where e-mails end? What's one of the popular words in English? From! I'll use "From " to distinguish e-mails, and let people quote from-lines". Really!
;-), or a plain old database (cool feature: no need to retrieve headers the mailer won't show).
MBox is also very little suited to programs like MH or PMS, because it's very dangerous to store offsets into mbox files.
MH has its own format, which is particularily cool because you can have e-mails and folders in the same folder.
Other formats inclue ZODB (if you read all your e-mail in Python, of course
PS.
IMAP is *evil*. It's way, *way* bloated.
Python's C source is written by Python programmers - they value elegant code.
I know a lot of people who were struck by the clarity in the Python sources. It's pretty easy
to understand and modify. Heck, I fixed a bug after using Python for two weeks.