d'uh. I suggested it happens for dead people at hospital when they're still warm. Murdering people and then dragging the corpse off to hospital to collect a cash reward isn't really going to fly - for one the corpse isn't going to be in the best of condition, secondly, they'll notice the "lack of natural causes" involved in the death.
yup, they're economists basing everything around economics.
They could have combined their findings with other areas of expertise - such as common sense - by saying "people are just fucking lazy, so we find that by making organ donation on death the default option, there will be many more organs available that used not to be collected because people were too lazy to fill out the donation form, they'll still be too lazy to fill out the opt-out form".
Any theory that ignores all but one aspect of human nature is ultimate self-serving. In this case, making money for someone.
this is worse that usual, I read the article (well, skimmed through it) and all the guy is saying is: Chrome is built on some libraries that you can pick and chose and build your own programs using. So if you need a http server or xml lib or any other of the myriad bits that Chrome needs, there's a nicely set up way of getting all those for free, and cross platform. Then he describes the library-picker tool and how it can create project files for various platforms to make your life easier.
But all the comments in/. are:
why would you build it on big old bloated Chrome (I assume the browser);
but that's what java was designed for;
but that's way bigger than libc;
So google now want us to write plugins instead of HTML5
and so on, no-one really got what the article was about, thinking its somehow building programs inside Chrome, or using Chrome as a kind of new webkit.
Pathetic. I blame the editoral summary TBH, but the kids here just got to a new low in not RTFA.
nothing about plugins - its about leveraging the libraries than Chromium uses to build Chrome. In that, you can leverage those same libraries to build whatever you like. Its got fuck all to do with plugins, or Chrome itself for that matter.
firstly they aren't using Chrome as a platform, they're using the libraries that Chrome uses to build their apps, also that the chromium dev kit lets you specify which libraries you want to use, and thirdly they're using C++ to build their code so the bits they don't use just don't get compiled into the final program. And of course, they're using c++ instead of some crappy bloated other system that comes with every manner of crap already installed in the language or an interpreted mess that is bloated to hell anyway.
So tell me, what's so wrong with their approach - using cross platform libraries that just happen to be written by the Google boys?
thing is, the advertisers will never do that - simply because their business model relies on tracking impressions and so forth. Hence they have to serve the ads on their own web platforms.
This is the main reason I block ads - the page I'm viewing usually hangs while its contacting the ad (he, one of the many ad) platforms to return some cookie-harvesting ad monster with all kinds of analytics processed on the back end.
Get rid of that and they have nothing to offer, and as long as there is any comms to the ad serving site, even if its just analytics, they can be blocked.
I think its stupid, as it only gives me ads for shit I no longer want, and no ads targetted for typical users of the site I'm viewing (I recall Webhostingtalk having an ad policy where they directly sold ads on their site, and the images were hosted on their site - they attracted advertisers by giving out the profile and quantity of users who came to their site, I assume that's considered obsolete nowadays, but I thought it was the moist effective way of doing it).
an alternative is Fuppes, from sourceforge, it is a simple DLNA server that works very well. The only disadvantage I have with it is that it doesn't prevent Windows from sleeping when its streaming (I have Windows set to sleep after an hour of inactivity so halfway through a 2-hour movie, I'd have to nudge the mouse) which is a pretty major problem.
It looks like a dead project but the author said it wasn't, but I still couldn't build it, even on its native Linux platform. Still, if you run it on Linux or have different power settings, it works.
yes and no - whilst XBMC is an awesome media client, it also does have a little bit of server code tucked away insode it, so you can load it up, and use it to stream stuff across a DLNA link very easily.
It has 2 problems with using it in this way - first there is no "run headless" mode, and 2nd, it doesn't stop Windows from going to sleep when it wants.
Its a common fallacy that server side stuff if just shuffling disk to network, hence the (current, but fading) popularity of node.js
What I find in all systems that are not trivial is that the middle tier gets a lot of processing bundled into it - read that disk or DB data, and fiddle with it, often combining it with other data sources and then send it down to a client. That fiddling requires quite a bit of processing.
Its one reason why Microsoft went as native-code as it did a couple of years back, their 'Casablanca' project (now released as C++ REST Services) because someone measured how much electricity their cloud services were sucking up with managed code (and to be fair,.NET is less resource intensive than many script-based languages) and they needed something more efficient. (Either that or someone noticed how seriously faster C WWS web services were compared to.NET WCF services:-) )
All the places I've worked that do serious stuff, base their distributed services over 3 tiers - the usual web presentation (or sometimes thick desktop) calling a middle tier business logic layer that calls the DB. The middle tier does all the heavy lifting, so its never just IO shuffling.
I'm sure many websites simply call a web server that calls a DB and does the mapping of data to UI in the client via javascript, but its not the most efficient way of presenting that, especially if there's a lot of data, or it needs processing.
Maybe there;'s a distinction to be made between the "website" devs and the "professional" devs in the type of systems they develop. I think its a shame the "website" style where everything is placed in the web server (bad security choice that) should be designed with 3 tiers from the start, and for these types of system, a C++ based service layer is not any more difficult than any other language to develop for..NET, its easy to develop for, which is why everyone seems to be using it. Its not nice when it goes wrong (like the bug I struggle with today - reading event log entries returns null on my colleague's box, for no F*** good reason.. damn you Microsoft) but even Microsoft knows its their RAD tool, not the one that should be used for performance or resource efficient systems. To put it another way,.NET is the new Visual Basic - where VB used to be used,.NET fills that gap. The trouble is, it also attempts to fill every other gap (but I guess VB devs back in the day used to do that anyway)
I think you have me confused with someone else.....
I do serious software, where my skill with the tools mean I don't have such a productivity hit as others who need java or.net to keep up. I prefer C/C++ but I do turn my hand to quite a few different technologies as appropriate.
as many people do - get a copy of an app inspector - I recommend Addons Detector - and use it to see what dev tools were used for build the apps on your phone. You'll be surprised to see just how many were built with the NDK. All the fast and responsive games are at least.
so Reactive Programming is basically syntactic sugar making event handling a bit easier.
Fair enough... though I can't help thinking of Node.js and all those callbacks being heralded as a new revolution in programming when I hear about this stuff. As an old fart, I know there's nothing really new... just kids who think they need any new paradigm because they never had the balls to learn how the old stuff worked.
a load of bollocks. This "its only the plugin, everything else about Java is completely secure, don't worry" is just sticking your head in the sand.
There are loads of programs that are exploitable, and they get fixed - no-one says "its fine" with them, why would any part of Java be different. If there is an exploit, and you have a java app that connects to the internet or otherwise is accessible, then its a potential exploit waiting to happen.
That the plugin is a bad idea, and that it allows these exploits to be abused with almost trivial effort does not mean everything else is somehow magically 100% secure. Stop spreading that dangerous FUD. Someone might believe you, not bother patching and end up as part of a botnet.
Java is insecure, get it patched, keep it patched. (just like everything else).
as opposed to Java where even if you are the perfect programmer, your code is still insecure, which until Oracle decides to release some patches, can result in your company getting hacked and massive damage being inflicted.
Mind you, if you're running Java code at a company, you've already inflicted massive damage. I would welcome my new hacker overlords if they could rid me of the Enterprise Java code my company insists on using.
Anyway, you're thinking of C. No-one writing C++ uses scanf or any of the other C runtime calls, not for a decade or so.
so are the Dells. The 30Hz thing is down to the cabling required to get the data sent to the panel - HDMI 1.4a will only support 30Hz.
You'll need display port for 60hz.
Anyway, its not just Dells that are coming out - look at the Lenovo Pro2840m or the Asus's PB287Q which is touted as a "gaming monitor" with low latency and 60Hz refresh.
I don't know, but there's a lot of solar energy in space that doesn't get reduced by an atmosphere. That said, why not fusion - Voyager was powered by a little plutonium, so its not like we can't send the required materials up there.
Chances are we'll be needing a moonbase before we get to the asteroids for anything other than science.
the point was that BSD licences aren't some sort of black hole into which companies will take and give nothing. Even if a company does do that, it doesn't mean that the project won't gain from it regardless.
Slashdot Mirror
d'uh. I suggested it happens for dead people at hospital when they're still warm. Murdering people and then dragging the corpse off to hospital to collect a cash reward isn't really going to fly - for one the corpse isn't going to be in the best of condition, secondly, they'll notice the "lack of natural causes" involved in the death.
yup, they're economists basing everything around economics.
They could have combined their findings with other areas of expertise - such as common sense - by saying "people are just fucking lazy, so we find that by making organ donation on death the default option, there will be many more organs available that used not to be collected because people were too lazy to fill out the donation form, they'll still be too lazy to fill out the opt-out form".
Any theory that ignores all but one aspect of human nature is ultimate self-serving. In this case, making money for someone.
this is worse that usual, I read the article (well, skimmed through it) and all the guy is saying is: Chrome is built on some libraries that you can pick and chose and build your own programs using. So if you need a http server or xml lib or any other of the myriad bits that Chrome needs, there's a nicely set up way of getting all those for free, and cross platform. Then he describes the library-picker tool and how it can create project files for various platforms to make your life easier.
But all the comments in /. are:
why would you build it on big old bloated Chrome (I assume the browser);
but that's what java was designed for;
but that's way bigger than libc;
So google now want us to write plugins instead of HTML5
and so on, no-one really got what the article was about, thinking its somehow building programs inside Chrome, or using Chrome as a kind of new webkit.
Pathetic. I blame the editoral summary TBH, but the kids here just got to a new low in not RTFA.
WTF? You didn't read the article did you.
nothing about plugins - its about leveraging the libraries than Chromium uses to build Chrome. In that, you can leverage those same libraries to build whatever you like. Its got fuck all to do with plugins, or Chrome itself for that matter.
someone didn't read the article....
firstly they aren't using Chrome as a platform, they're using the libraries that Chrome uses to build their apps, also that the chromium dev kit lets you specify which libraries you want to use, and thirdly they're using C++ to build their code so the bits they don't use just don't get compiled into the final program. And of course, they're using c++ instead of some crappy bloated other system that comes with every manner of crap already installed in the language or an interpreted mess that is bloated to hell anyway.
So tell me, what's so wrong with their approach - using cross platform libraries that just happen to be written by the Google boys?
thing is, the advertisers will never do that - simply because their business model relies on tracking impressions and so forth. Hence they have to serve the ads on their own web platforms.
This is the main reason I block ads - the page I'm viewing usually hangs while its contacting the ad (he, one of the many ad) platforms to return some cookie-harvesting ad monster with all kinds of analytics processed on the back end.
Get rid of that and they have nothing to offer, and as long as there is any comms to the ad serving site, even if its just analytics, they can be blocked.
I think its stupid, as it only gives me ads for shit I no longer want, and no ads targetted for typical users of the site I'm viewing (I recall Webhostingtalk having an ad policy where they directly sold ads on their site, and the images were hosted on their site - they attracted advertisers by giving out the profile and quantity of users who came to their site, I assume that's considered obsolete nowadays, but I thought it was the moist effective way of doing it).
yes, you're giving other drivers too much credit.
If they get arrested for reading text messages, you can be 100% sure too many morons will be using it to read and post facebook messages.
At least the idiots who post "just hit a child while driving, he houlda looked both ways first lol" can be easily prosecuted.
either that or "yay Dart, I love Dart, let me hype it up as much as possible with some slightly vague claim that I can say was a mistake".
Pah. Let me know when they make NaCl more ubiquitous in browsers.
Often its because the closed-source project doesn't leave feature decisions to developers, most of them are decided upon through user requirements.
Now Windows, that's a different beast - that's gone full circle back to where ego matters.
Whilst at Microsoft, his job was as a salesman ... that's the very definition of bullshit.
an alternative is Fuppes, from sourceforge, it is a simple DLNA server that works very well. The only disadvantage I have with it is that it doesn't prevent Windows from sleeping when its streaming (I have Windows set to sleep after an hour of inactivity so halfway through a 2-hour movie, I'd have to nudge the mouse) which is a pretty major problem.
It looks like a dead project but the author said it wasn't, but I still couldn't build it, even on its native Linux platform. Still, if you run it on Linux or have different power settings, it works.
yes and no - whilst XBMC is an awesome media client, it also does have a little bit of server code tucked away insode it, so you can load it up, and use it to stream stuff across a DLNA link very easily.
It has 2 problems with using it in this way - first there is no "run headless" mode, and 2nd, it doesn't stop Windows from going to sleep when it wants.
Its a common fallacy that server side stuff if just shuffling disk to network, hence the (current, but fading) popularity of node.js
What I find in all systems that are not trivial is that the middle tier gets a lot of processing bundled into it - read that disk or DB data, and fiddle with it, often combining it with other data sources and then send it down to a client. That fiddling requires quite a bit of processing.
Its one reason why Microsoft went as native-code as it did a couple of years back, their 'Casablanca' project (now released as C++ REST Services) because someone measured how much electricity their cloud services were sucking up with managed code (and to be fair, .NET is less resource intensive than many script-based languages) and they needed something more efficient. (Either that or someone noticed how seriously faster C WWS web services were compared to .NET WCF services :-) )
All the places I've worked that do serious stuff, base their distributed services over 3 tiers - the usual web presentation (or sometimes thick desktop) calling a middle tier business logic layer that calls the DB. The middle tier does all the heavy lifting, so its never just IO shuffling.
I'm sure many websites simply call a web server that calls a DB and does the mapping of data to UI in the client via javascript, but its not the most efficient way of presenting that, especially if there's a lot of data, or it needs processing.
Maybe there;'s a distinction to be made between the "website" devs and the "professional" devs in the type of systems they develop. I think its a shame the "website" style where everything is placed in the web server (bad security choice that) should be designed with 3 tiers from the start, and for these types of system, a C++ based service layer is not any more difficult than any other language to develop for. .NET, its easy to develop for, which is why everyone seems to be using it. Its not nice when it goes wrong (like the bug I struggle with today - reading event log entries returns null on my colleague's box, for no F*** good reason.. damn you Microsoft) but even Microsoft knows its their RAD tool, not the one that should be used for performance or resource efficient systems. To put it another way, .NET is the new Visual Basic - where VB used to be used, .NET fills that gap. The trouble is, it also attempts to fill every other gap (but I guess VB devs back in the day used to do that anyway)
Java.. no need for that anywhere IMHO :-)
wha? .net? me?
I think you have me confused with someone else.....
I do serious software, where my skill with the tools mean I don't have such a productivity hit as others who need java or .net to keep up. I prefer C/C++ but I do turn my hand to quite a few different technologies as appropriate.
as many people do - get a copy of an app inspector - I recommend Addons Detector - and use it to see what dev tools were used for build the apps on your phone. You'll be surprised to see just how many were built with the NDK. All the fast and responsive games are at least.
Java tainted perception of Java on the server - all those Enterprise program's we're forced to use, they tole us all how good Java is.
The only thing Java has going for it is the salesmen for the shitty consultancies who sell such crap to the management.
so Reactive Programming is basically syntactic sugar making event handling a bit easier.
Fair enough... though I can't help thinking of Node.js and all those callbacks being heralded as a new revolution in programming when I hear about this stuff. As an old fart, I know there's nothing really new... just kids who think they need any new paradigm because they never had the balls to learn how the old stuff worked.
a load of bollocks. This "its only the plugin, everything else about Java is completely secure, don't worry" is just sticking your head in the sand.
There are loads of programs that are exploitable, and they get fixed - no-one says "its fine" with them, why would any part of Java be different. If there is an exploit, and you have a java app that connects to the internet or otherwise is accessible, then its a potential exploit waiting to happen.
That the plugin is a bad idea, and that it allows these exploits to be abused with almost trivial effort does not mean everything else is somehow magically 100% secure. Stop spreading that dangerous FUD. Someone might believe you, not bother patching and end up as part of a botnet.
Java is insecure, get it patched, keep it patched. (just like everything else).
as opposed to Java where even if you are the perfect programmer, your code is still insecure, which until Oracle decides to release some patches, can result in your company getting hacked and massive damage being inflicted.
Mind you, if you're running Java code at a company, you've already inflicted massive damage. I would welcome my new hacker overlords if they could rid me of the Enterprise Java code my company insists on using.
Anyway, you're thinking of C. No-one writing C++ uses scanf or any of the other C runtime calls, not for a decade or so.
Then you want to look at the Asus PG278Q 1440p monitor or imaginatively named PB287Q 4k monitor
so are the Dells. The 30Hz thing is down to the cabling required to get the data sent to the panel - HDMI 1.4a will only support 30Hz.
You'll need display port for 60hz.
Anyway, its not just Dells that are coming out - look at the Lenovo Pro2840m or the Asus's PB287Q which is touted as a "gaming monitor" with low latency and 60Hz refresh.
did I say fusion.. d'oh. Just being overly optimistic :)
I don't know, but there's a lot of solar energy in space that doesn't get reduced by an atmosphere. That said, why not fusion - Voyager was powered by a little plutonium, so its not like we can't send the required materials up there.
Chances are we'll be needing a moonbase before we get to the asteroids for anything other than science.
the point was that BSD licences aren't some sort of black hole into which companies will take and give nothing. Even if a company does do that, it doesn't mean that the project won't gain from it regardless.
But that's 100MB per million users, it all adds up.
FYI, twitter has 883 million users.. that's a lot of 100 bytes. 88 gigs worth of them.