To slash someone in hockey means to strike them with the blade of your stick, usually the lower legs. If the ref sees you do it, it's a two minute minor penalty.
It kind of is "broke". The only reason to have initials prefixing class names is because Objective-C doesn't support namespaces - or at least it didn't the last time I fooled around with it.
The availability might be. There are many, many movies not available via BitTorrent, which tends by its very nature to only offer what's currently popular.
Django is just a pleasure to work with. Congratulations to these guys for creating such a well thought-out and hugely productive framework. Now if only it would become more established and bulked up a bit so we could mostly ditch a certain other Enterprise Edition set of technologies...
Re:We need to go in the other direction
on
Chrome Vs. IE 8
·
· Score: 1
In all honesty, desktop apps aren't going anywhere. The big deal with web apps is not for you, Joe Homeuser, but for the enterprise, where things like salesforce.com, Taleo, and so forth are becoming real alternatives. Having a stable, "multitasking" browser (so to speak) is very important for these emerging apps.
You are correct. Linux, Windows, and pretty much all modern operating systems implement copy-on-write.
Re:Non-Tech Percent of Web Traffic from Chrome
on
Google Chrome, Day 2
·
· Score: 2, Insightful
Apparently it has no Mozilla code at all - UA strings have no bearing on reality. So don't get your hopes up.
Re:Non-Tech Percent of Web Traffic from Chrome
on
Google Chrome, Day 2
·
· Score: 1
Well, in all fairness, the Mac version is supposedly coming soon. You can even subscribe to a mailing list and get news updates about it. But that said, your point is a good one.
Yeah, but my point was, a lot of people are going to be looking at this source code, so the hope is that such shenanigans would be quickly noticed and removed.
I know you were joking, but I'd actually love to get into proofreading as a means of supplementary income. However, I have no idea how to get into it, exactly. Suggestions?
You are correct, and my simplification was a bit much. But I'm sure you realise that the switch is very lightweight compared to a full process switch, simply due to the large amount of state information, mapped address space, etc. etc. This is particularly true on Windows, where a process context switch takes orders of magnitude longer - their own documentation refers to "cheap" threads and "expensive" processes.
As an aside, this is one reason why MS has pushed multithreading so hard as a design pattern. The Unix tradition is of course multiprocessing, and Linux was designed with very fast context switching as a priority. Linus's antipathy towards threads has its roots in this distinction.
In theory, Chrome should run very well on Unix and Unix-like operating systems, and maybe less so on Windows.
It's all open source, so at least the browser itself won't be up to any nastiness. I don't see how they'll be able to track you beyond what they're doing now. The whole thing really does seem like a way to build a proper platform for delivering web apps - I guess Google is tired of being held back by the relative lameness of the current crop of browsers, which is understandable. Why Mozilla or Apple didn't go with a multiprocessing model for tabbed browsing in the first place is beyond me.
Note to "samzenpus": when writing reviews about terrible books, it's a good idea to be grammatically correct. You don't put, commas in the middle of sentences, like this one. Nor should you misuse apostrophe's like I just did there. I hate to be so preachy, but what could be quite funny was rendered practically unreadable.
One of the whole points behind threading is that there isn't any state to maintain. Same with the context switches. You seem to be thinking of multiprocessing, for which your comments are true, not multithreading.
Yeah, plus rumour has it Gecko's api is baroque in the extreme. Anyway, given Google's deal with Firefox (the default search engine stuff), it's nice to see they've made their decision on what appears to be purely technical terms, rather than political ones.
Going with Webkit is an interesting choice. It seems like there are a lot of minor browsers using it rather than Gecko these days. Even Gnome's Epiphany has switched, I do believe.
You can't pack heat in a lot of countries that are orders of magnitude more peaceful than the US (Canada, all Scandinavian countries, etc. etc.) Your entire made-up "argument" reads like a hallucination.
No, I don't think it's derogatory at all, just a rather inexact term. Python isn't interpreted in the sense that, say, bash is, as it compiles to bytecode. So it's tough to use "interpreted" to describe both.
Javascript doesn't have an interactive prompt (that I know of), nor can it be executed with #!/usr/bin/foo. But it's commonly referred to as a scripting language. Same with all the ECMAScript derivatives, such as ActionScript. Are they not scripting languages, then? They fail both of your tests.
Slashdot Mirror
To slash someone in hockey means to strike them with the blade of your stick, usually the lower legs. If the ref sees you do it, it's a two minute minor penalty.
It kind of is "broke". The only reason to have initials prefixing class names is because Objective-C doesn't support namespaces - or at least it didn't the last time I fooled around with it.
The availability might be. There are many, many movies not available via BitTorrent, which tends by its very nature to only offer what's currently popular.
Django is just a pleasure to work with. Congratulations to these guys for creating such a well thought-out and hugely productive framework. Now if only it would become more established and bulked up a bit so we could mostly ditch a certain other Enterprise Edition set of technologies...
In all honesty, desktop apps aren't going anywhere. The big deal with web apps is not for you, Joe Homeuser, but for the enterprise, where things like salesforce.com, Taleo, and so forth are becoming real alternatives. Having a stable, "multitasking" browser (so to speak) is very important for these emerging apps.
You are correct. Linux, Windows, and pretty much all modern operating systems implement copy-on-write.
Apparently it has no Mozilla code at all - UA strings have no bearing on reality. So don't get your hopes up.
Well, in all fairness, the Mac version is supposedly coming soon. You can even subscribe to a mailing list and get news updates about it. But that said, your point is a good one.
Well, I'll probably read some of it, yeah. And so will around 100,000 other people. It's a Google project, not some kid's worthless SourceForge junk.
Interesting - that makes a lot of sense then. Thanks for the informative post.
Yeah, but my point was, a lot of people are going to be looking at this source code, so the hope is that such shenanigans would be quickly noticed and removed.
I know you were joking, but I'd actually love to get into proofreading as a means of supplementary income. However, I have no idea how to get into it, exactly. Suggestions?
You are correct, and my simplification was a bit much. But I'm sure you realise that the switch is very lightweight compared to a full process switch, simply due to the large amount of state information, mapped address space, etc. etc. This is particularly true on Windows, where a process context switch takes orders of magnitude longer - their own documentation refers to "cheap" threads and "expensive" processes.
As an aside, this is one reason why MS has pushed multithreading so hard as a design pattern. The Unix tradition is of course multiprocessing, and Linux was designed with very fast context switching as a priority. Linus's antipathy towards threads has its roots in this distinction.
In theory, Chrome should run very well on Unix and Unix-like operating systems, and maybe less so on Windows.
It's all open source, so at least the browser itself won't be up to any nastiness. I don't see how they'll be able to track you beyond what they're doing now. The whole thing really does seem like a way to build a proper platform for delivering web apps - I guess Google is tired of being held back by the relative lameness of the current crop of browsers, which is understandable. Why Mozilla or Apple didn't go with a multiprocessing model for tabbed browsing in the first place is beyond me.
Note to "samzenpus": when writing reviews about terrible books, it's a good idea to be grammatically correct. You don't put, commas in the middle of sentences, like this one. Nor should you misuse apostrophe's like I just did there. I hate to be so preachy, but what could be quite funny was rendered practically unreadable.
One of the whole points behind threading is that there isn't any state to maintain. Same with the context switches. You seem to be thinking of multiprocessing, for which your comments are true, not multithreading.
Apple holds multiple multitouch patents, actually.
Yeah, plus rumour has it Gecko's api is baroque in the extreme. Anyway, given Google's deal with Firefox (the default search engine stuff), it's nice to see they've made their decision on what appears to be purely technical terms, rather than political ones.
Going with Webkit is an interesting choice. It seems like there are a lot of minor browsers using it rather than Gecko these days. Even Gnome's Epiphany has switched, I do believe.
You can't pack heat in a lot of countries that are orders of magnitude more peaceful than the US (Canada, all Scandinavian countries, etc. etc.) Your entire made-up "argument" reads like a hallucination.
...says the guy with the 1.2 million-something uid.
Slashdot has always run stories like this. I guess you weren't around for the coverage of the 2000 elections.
I stand corrected - thanks very much.
So what about ActionScript? ;)
No, I don't think it's derogatory at all, just a rather inexact term. Python isn't interpreted in the sense that, say, bash is, as it compiles to bytecode. So it's tough to use "interpreted" to describe both.
Javascript doesn't have an interactive prompt (that I know of), nor can it be executed with #!/usr/bin/foo. But it's commonly referred to as a scripting language. Same with all the ECMAScript derivatives, such as ActionScript. Are they not scripting languages, then? They fail both of your tests.
That's not true of the main, stable version of Ruby (MRI 1.8.x), though its true of Ruby 1.9 and some alternative implementations.
Thanks, I wasn't aware of that. Of the languages listed, the only ones I have extensive experience in are Python and Perl.
Agreed about the uselessness of the distinction, too.
Haha, excellent, thanks for the info.