As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Every time I load a browser tag in Chrome on my mac, the application forks another process. This seems to be different from how firefox or Safari work. What was the reason why Google stayed away from multi-threading in this case? The problem to be solved here (rendering multiple pages at once would seem in my mind to be a prime candidate for muti-threading, or?
Running each page (or tab) in a separate process allows Chrome to provide a bit more security against page rendering bugs, as well as browser plug-ins that run within a process. Basically, if one page crashes, it won't affect other tabs. Instead, you'll get an "Aw Snap!" message.
From the docs:
We use separate processes for browser tabs to protect the overall
application from bugs and glitches in the rendering engine. We also
restrict access from each rendering engine process to others and to
the rest of the system. In some ways, this brings to web browsing the
benefits that memory protection and access control brought to
operating systems.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
IndexedDB API on node.js will be very useful for some app.
Why IndexedDB is not available in node.js?
IndexedDB API does not depend on DOM, even though it does use some DOM error and event style.
It's possibly because IndexedDB is part of a different body of standards. Node.js is just ECMAScript (via Google's V8) along with their own API. Also, it may not help that IndexedDB is still in "Draft."
But, more likely it's for the same reason Node.js doesn't offer any database drivers: it's not trying to solve those problems. It's just trying to offer the APIs that assist someone who does want to solve and implement them.
And, for that, it appear at least one such project has already started: indexeddb-js. But, also have a look through IndexedDB in the NPM Registry.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I am learning Node.js and am currently studying WebSockets. As I understand it, Socket.io was intended to address inconsistent support that the various browsers had with WebSockets...If you check out caniuse WebSockets, it appears that WebSockets currently has practically full support. Can anyone explain why I should use Socket.io versus WebSockets in this case?
It handles graceful degradation for you to numerous technical alternatives to get bi-directional near-time communication flowing (web sockets, ajax long polling, flash, etc)
As of March 2013 that site lists web sockets at 61% support. This is not "practically full".
As of September 2021 that site lists web sockets at 98% support. All modern browser's support Websockets.
It handles browser inconsistencies and varying support levels for you
(these first 2 things are basically the same value created by jQuery, to put it in perspective)
It includes additional features beyond bare bones web sockets such as room support for basic publish/subscribe infrastructure and things like automatic reconnect
AFAIK it is more popular and easier to get help with than vanilla web sockets, at least at the moment.
However, just like there is VanillaJS for the jQuery haters, if you prefer using the official standard web socket APIs directly, by all means, knock yourself out.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Several sites (I remember Yahoo did this too, back when I used my Yahoo account) such as Bank of America show a SiteKey or similar image the user chooses after they enter their username, but before they enter their password. Ostensibly, this ensures the login page is unique to each user, and therefore a phisher can't just show a static login page that looks like the bank's site, but what's stopping them from simply hitting the bank's site in the background and forwarding the image (or other security challenge) right to the user? I'll grant, it makes the phisher's job slightly harder, but it really doesn't seem that valuable to me. What's the rationale for this behavior?
If a single server keeps hitting their site requesting the images for different userids (especially one where the users haven't logged in from before), it will be pretty suspicious, so it's harder for a Phisher to hide.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I could not find anywhere on google information about Spotify Apps that would say anything about the future plans of this expansion, in particular, if it would be possible to publish your own app somewhere on the future Spotify App Store or something similar to that. Does anybody know if this feature is in the future development plans of the company?
The process for getting your application published on the App Finder is here:
https://developer.spotify.com/technologies/apps/process/
Specifically, we request you submit a concept to us first so we don't end up with duplicate apps, then once that's approved the process is fairly standard - you make the app, we make sure it's good enough for the App Finder, then it gets published.
If you've already started to make an app, no matter - just submit it as a concept anyway and we can work from there.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I want to build a new desktop environment for linux like KDE or GNOME, not that much complex, i just want a new windowing system, a new desktop, just like that with some simple functionalities.
But the problem is i don't know where to start. Is it possible to use toolkits like Qt or wxWidgets for this purpose or should i start from anything other? I can program in languages c, c++, java ...
Is this X11 or X Window System have any relation with this. Can anybody tell me where should i start.
Desktop environments on Linux consist of many interconnected components. You should start by reading about how existing desktop environments work: what components they contain, and how they work together.
The information you need is on the internet. Look at Wikipedia (for example, the Desktop environment page, Windowing system and X Window System pages). Look at freedesktop.org, and its Specifications page. Google for other information.
The fact that you're asking questions about whether X11 or X Window System has any relation to this task indicates that you don't yet have a good understanding of the main software components of a Linux desktop. Luckily, that problem is easy to solve: you just have to do some reading.