This. Actual stamps is mostly a consumer thing, I just checked our commercial postal service and they recommend a "stamping" machine if you send more than 40 letters/week where you charge it up like a prepaid cell phone, same thing for packages except there they normally print to labels they slap on the package. And for the big companies you get bulk pre-printed envelopes with logo that are collected at your place of business and charged to your corporate account, we have those at work. The potential for abuse is small since you can't drop them off at a regular mailbox and it'd be obvious who you're using to pay for your postage. A lot of the consumer-to-business mail is prepaid and rolled into the cost of business too, the few times I use stamps is to other people but most of that is replaced by email since you don't need a formal signature on anything. I guess there's the odd package, but if it's too big to fit a mail box you're going to the post office anyway.
Nokia has more brand name recognition, so of course we won't use that.
Of the "let's frame it and put it on a wall" more than "I want one in my pocket" variety. I'll always have fond memories of Nokia 3210 and the state of the art in 1999, but it's not selling a new phone and it's not quite up to collectible/antique standards either. And Elop's little stunt sure didn't help Nokia's reputation as a has-been either. Not to mention that Nokia running Windows Phone might have some of the same hardware but there's very little in common between "old Nokia" and "new Nokia" anyway. I think this was a pretty easy call of Microsoft and would have happened regardless, if they'd ponied up a little more they could have gotten the Nokia name for good as it matters more to consumers than the commercial market the remains of Nokia serves.
Because Facebook is really interested in their stock value and not kicking the DEA in the teeth? They're not going to win any favors with anybody for actively sabotaging a criminal investigation, even an illegally conducted one. They want to have the public on their side which is why we're hearing about this in the news, Facebook couldn't win an escalating conflict with proxies and whatnot. If this becomes a big enough PR problem for the police though, the practice might go away.
3) Contractual obligations/customer relations, in the enterprise world people build systems they expect to last many, many years and not have the parts disappear on a whim. Which is is why Intel has launched Itaniums as late as 2012, whoever they suckered into buying it will get time to bail out. Don't underestimate the value of grudges in the enterprise, any executive who gets burned by IBM ditching it fast and dirty will be their enemy when the next big consulting/outsourcing contract rolls around.
Re:Unity is rubbish. Systemd is rubbish
on
Ubuntu Turns 10
·
· Score: 3, Interesting
Except they're not chasing the mainstream, they're chasing the hype wave of Apple/Google/Microsoft trying to be the "big next thing" instead of what is actually mainstream today with Win7/OS X. Instead of picking a market and staying on target to finish the job they still haven't finished on the office desktop from 1999 or the laptop from 2004 or smartphone from 2009 or tablet from 2014. And at this rate I don't think Ubuntu will stay in one place long enough to be relevant to anyone outside the ~1% of the desktop market Linux owns today.
While there'll always be exceptions I imagine it's usually a very short list of persons who want any one article removed, blowing the whistle saying "someone is trying to bury this article" should have the intended effect anyway.
Games only started using D3D 10/11 *very* recently -- the back catalog this could enable is huge, and D3D 9 games are still coming out today. It'd say it's very important to support.
Bullshit. Almost all games have had an D3D 9 rendering path since XP has been so massively popular, but a whole lot of games has taken advantage of D3D 10/11 where it's been available. It's very important to the number of games you can run on Linux, but it does not represent the state of the art. Speaking of which, WINE's support of D3D 9 through an OpenGL has been pretty good. Or rather my impression has been that if they can figure out what DirectX is doing, there's usually a fairly efficient way of doing in OpenGL. The summary tries to paint it as if OpenGL has been a blocker to DirectX support, my impression is quite the opposite. A gallium3d implementation is closer to the hardware and "more native" than a DirectX-to-OpenGL translation layer, but while it might boost performance a little it won't fundamentally support anything new.
Does he mean a transient reaction in the test set-up that produces the byproducts of fusion, but not long enough to generate useful power?
A transient reaction that can't be reliably reproduced despite recreating the same conditions to the best of our ability. Which might be because the conditions necessary are so extremely specific that they only got them right once by accident or because of some contamination or malfunction that somehow produced the necessary conditions yet attempts to recreate them fail. Or the results of the initial experiment were wrong, but here they've clearly put their desire to believe it was real over their good judgement.
Except authentication is usually not username+password or digital signature, it's identification+official paper saying you're that person. Everywhere your use your passport, driver's license or any other photo ID you're relying on three things:
1) The difficulty of acquiring the information to be on the card 2) The difficulty of forging the card 3) The difficulty of fooling the issuers into producing a fake card
The last one is often a sneaky one, enough ID info and you might trick one of them into believing you've lost your ID and issue a new one. But there's enough direct fakes too, if they have the necessary information that's half the way.
Except that's pretty much what all AJAX web apps do, they "export the UI through some generic mechanism" to the browser so I'd say it's very common. No need for roll-outs and patches, if the server now says there should be a new button there is a new button for everyone. The issue is that I find most web apps really suck compared to native applications so locally I usually want a native, non-web application.
What I'm talking about is a native toolkit that'd make the applications you normally use locally network transparent at the application level, not the display server level. Essentially a toolkit where the UI is always living in its own thread, asynchronously to the actual application. Network transparency just means that thread happens to be living on a different machine, drawing to a different display. And you could tweak it to handle that better, but you wouldn't have to it'd sort of run remotely without modification.
For example, I made a basic calculator just as a proof of concept. Connected locally (I still used a TCP connection just to localhost, better options are available) it looked and acted entirely as a native app you could use every day. It recorded buttons pushed, sent the push events to the back-end and sent updated display text back. I hadn't made it better, but I hadn't made it worse either. The cool thing though was that now I could connect to it remotely. Same calculator popped up, my button clicks go over the network, display text came back over the network. It's a working local native app and a working network transparent remote app. At once. Without any application logic in the client, just drawing tools.
People would like a magic box that make them anonymous and secure on the internet while they log into Facebook, just like they want a magic diet pill while they continue to stuff their faces with sugar and fat. Or for a more relevant tech example they'd like a magic oracle to tell them if a website belongs to who they think it belongs to which is why we have CAs as the best approximation. It's never going to work that way, but there's a lot of money in selling snake oil...
The layer in the system between the user applications and the hardware interface is the place where QT, GTK, Windows graphics api, and all the other graphics toolkits go. Those toolkits shouldn't care too much about the hardware details, just the published capabilities of the GPUs.
It's kinda hard not to care, because a lot of it depends on where you have the data, where the processing capability is and what the link capability is. Sending a video stream is heavy. Even sending an event stream like applications do all by themselves is too heavy during say a resize or scrolling action. Some time ago I experimented with turning Qt into a remote application toolkit, basically taking all signals and slots and serializing them over SSL. It was actually surprisingly successful, basically it was puppeteering a client to draw the interface and using signals and slots to synchronize information on demand. Only the bits you connected sent events across the link.
There were plenty little gotcha's though, like the scrolling I found a way to make a trigger that'd only fire after a custom delay, like for example 50ms after you were done resizing. And I needed to add a system to say "When this button is called, include the check state of this radio button and text of that textbox", but the nice thing was that on the client side it was acting like a client window. It was resizing, the menus were popping up, the buttons responded (though the actions might take time due to latency) and I could do client-client signal/slots like "when the user checks this box, enable these extra fields" too without a server round-trip.
I could do neat things like send a jpg and have the client draw it and even if the client moved the window around, covered it with other dialogs, scrolled it in and out of sight it was zero overhead. Yeah I know kind of like a browser, but not like any RDP/VNC solution. Often I needed the same resources over and over and didn't want to transfer them every time, so I needed a caching system. Kind of like HTML5 persistent objects I guess but before that. And I could populate list/tree/grid objects up front or on demand, a bit like DOM manipulation in HTML.
It wasn't transparent but it was somewhat API transparent, you'd get a "RemotePushButton" instead of a "QPushButton" which acted the same, but instead of actually drawing anything just sent commands to the client which drew the real QPushButton. You didn't really see that though, you just called the functions and connected the RemotePushButton's onClick() signal as if it were a QPushButton. Kind of like HTML+AJAX on steroids but looking and feeling like a native application. That I feel would have been rather next-gen to see it finished.
If you're wondering why I didn't then mainly because the product I was thinking to use it for kinda died on the drawing board. And because to really become user friendly it'd have to integrate on a much deeper level, so you could use all the Q* classes without rewriting everything, the Remote* classes were a hack (QObjects) working with the standard library. And you'd want to put more work in persistence, the idea was that you could yank out the plug on one machine, log back in on another and it'd redraw everything but initially it passed all though and didn't shadow the client state on the server. It could have though, the rewrite was just too much.
which still imposes a significant overhead in terms of transistor count
They did it on the Pentium Pro which had ~1/1000th of the transistors modern processors have today. Even though the instruction set has grown a few times in size, it's certainly entirely irrelevant when it comes to total transistor count today. But keep on spouting nonsense.
*digs up the carcass you can flog the dead horse again*
No x86 chip from the last 20 years runs CISC instructions internally, it's split into micro-ops and AMD/Intel has spent the last 20 years optimizing their decoder and internal instruction set for this one task. If you think using the ARM instruction set is more optimized than that you've drunk way too much of the kool-aid.
I'm really waiting for an x86 phone that can be bought in the USA. These have been available for years in India (!!!!), its really appalling that you cannot yet buy one in the US of all places.
Well, are the current x86 phones Google Android or AOSP Android? In India the latter might sell fine as a smartphone, I think here in the western world we expect all the Google services (and tie-ins...)
IF they will give me episodes... 1) On their TV release date. 2) Of quality at least as good as cable feeds 3) In a usable non-DRM container which doesn't require a web browser 4) Charge no more than $5 per episode (even that is steep).
If it's anything like HBO Nordic: 1) Within 24 hours, often <6 hours 2) Less bandwidth than H.264 cable rips, no 5.1 sound but also not terrible 3) When hell freezes over 4) Here in Norway it's 79 NOK/month, subtracting VAT = $115/year for access to all HBO series
I'm a subscriber but still prefer downloading due to 2), then again I think HBO Nordic is their own company that bought to rights from HBO centrally so whether or not any of this applies is uncertain. I think the delay is because they don't get access to the episode until it's aired in the US, for example.
On the other hand, all the persons infected so far were people with known risk factors for ebola like travelling to ebola country or treating an ebola patient. Assume for a moment that one of these people managed to infect someone random. Are the symptoms going to get bad enough quickly enough that you get flagged as an ebola patient before you've had the chance to infect other people? My usual expectation would be like:
1. You're feeling a bit under the weather, but go to work away. 2. You feel rather crap with feber and a headache, the doctor says to stay in bed. 3. You're really not getting better, doctor runs tests and schedules you for a trip to the hospital. 4. You finally get into the hospital in the "normal" ward, they find out what you got. 5. Shit hits the fan and they try finding everyone you've been in contact with in steps 1-4.
If your average patient manages to infect >1.1 new patients before you can put a stop to it, you have a problem.
One can dump on the Germans as much as one wants but both during WWI and WWII they matched and in some fields outdid the allies in technology and scientific research despite these boycotts, despite the isolation and despite the stultifying effect that the Nazi regime had on parts of the German tech sector which says something about the caliber of German science, scientists and engineers.
Germany lost WWII mainly through their own mistakes, their war machine was strong enough to break Europe's back. Major WTFs being:
- Battle of Dunkirk, could have been a slaughter - No real plan for the Blitz - Opening the eastern front before Britain capitulated - Pearl Harbor, not really Germany's fault tho
Sure, but why? If you start out on a long haul drive it's been charged overnight, if you end a long haul drive it'll charge the coming night. The only reason you'd need a really quick charge at home is if you're just doing a pit stop between one long drive and the next. In that particular case I'd just plan on using superchargers as if my own home was just a diner, it's so rare it'd never pay off.
With closed source you have companies that will spend the minimal amount they can on security, and sweep issues under the rug as long as no one is complaining
If security holes didn't have economic consequences, that'd be true. And I don't mean incident-related costs because the EULA got the almost watertight covered there, but no doubt bad press about zero day bugs hurt their sales and bottom line. If it becomes common and grave enough it also becomes a brand and reputation problem which costs a lot for marketing to tackle. When Blaster and Slammer was all over the news they implemented the firewall. When malware exploited that everyone runs as admin they implemented UAC. When malware corrupted the boot process they came up with Secure Boot, of course throwing a wrench in easy Linux booting was bonus.
They'll put as much effort into it as it pays off rather than dealing with the fallout. Of course they'll cover up and downplay all that they can as damage control regardless, but they're still interested in avoiding it altogether. As long as it doesn't clash with other money making attributes like convenience, in early UAC they dialed it up too high. Now a watered down version is in Windows 7 and few complain anymore. Patch Tuesday is such a convenience, not for security but for IT staff managing Microsoft machines. The downside of 24x7 patching is that all Linux admin must keep up and having them just roll out automatically without testing could get nasty.
Basically, Microsoft takes take blame for whatever happens before patch Tuesday. IT staff can plan for a monthly test and patching session, in between they have it easy unless there's an emergency patch and then everyone knows you "must" do it because it's an emergency. Microsoft is big enough to just absorb the blame because if 0,001% of their customers is mad at them it doesn't really matter. The CIO can point to the company following best practices regarding Microsoft products. All the blame gets neatly passed around and defused, unlike the CIO having to defend their home grown solution where bits and pieces were cobbled together with open source and the only support was themselves so all the blame stays in-house. It might not work better for the system, but it works better for the people in the system.
Actually if you "stick to the story" there's only 50 dollar bills to choose from and once chosen it's eliminated from the set so 50*49*48*.... = 3*10^64 combinations. Less if any of the bills have identical last digits, which is likely due to the birthday paradox. And if they were just counted and put in an evidence bag most the bills are in the right order. If they count the ones, either in order or reverse order and the only thing you need to figure out is where a few fivers or tens go that's cryptologically pathetically weak. And if it did disappear down some pocket, well there goes your evidence that there actually was a pile of cash making up your password. Worst, the police will probably take this as gloating on your part by showing off your perfect yet obviously constructed get-out-of-jail free card. I think the good old "I don't recall" works better.
Since SDXC cards go up to 2TB and record 4K at consumer bitrates I don't see any reason for a new standard for years and even if one was needed it doesn't matter one bit to Google's data mining and most likely all it'd do is make phones with SD cards $2 cheaper so there's no money in it either. Sure denying Microsoft revenue would be nice but Microsoft already has a fat wallet, Google mainly wants to keep them out of their product space.
and two, who the hell sends naked pictures of themselves and actually thinks other people won't see them? 1999 called and it wants it's noobs back.
Teens who want to get laid. Like it or not, cell phones and social media has taken over a lot of the real-world interaction we used to have as teens. Mainly because I didn't have a cell phone until my late teens, much less a camera phone and nothing like social media. A lot of the flirting and teasing that used to happen in dark corners at parties is now happening through texting and sexting online. Not to mention the upkeep of an ongoing relationship, if you wanted to get more graphical than you'd say over a fixed phone line in the hallway you had to hook up in person. Today you're more expected to keep it up all the time, even if you're apart which means sending naughties on Snapchat and such. Yes, sometimes it backfires badly but people in love won't believe their love will stab them in the back. And while I'm pulling this statistic out of my ass, I think most personal photos most of the time aren't shared with anyone but the intended recipient and aren't abused. And I think that still holds true even though these 200k pics leaked.
Not to mention that it was a lot more obvious who was copying and who was not. Ever hear the expression "yesterday's news"? Well that was whatever they read in a competitor's paper yesterday and printed as news today. Today I'm sure they all have watcher services on each other, for every article posted they have someone evaluate whether they can run a copycat article. And I don't mean that in terms of copyright infringement, but just knowing that some event happened and is newsworthy they can write their own, non-infringing article using much the same sources. Today that might mean that one online site is 5-10 minutes behind the original source instead of a day, most people don't even notice who broke the news. Like today pretty much all our services covered the hit-n-run of a cyclist that died. I'm sure someone was first but it's not exclusive and they can all use the same source so they don't have to cite anyone. I suppose investigative journalism is still valuable, but "discovering" journalism has lost a lot of value.
That makes as much sense as saying Intel should provide a magic generic driver so it can run ARM software. nVidia, AMD and Intel all have different hardware implementations, the only thing most people care about is high level DirectX/OpenGL support which is the equivalent of Java on the CPU side. You have an expected functionality but how it's actually implemented in assembler differs from hardware to hardware. To be fair, there is a "thinnest possible overlay" created with Gallium3D which is something like what you ask for. Basically it's something like C for graphics card, one unified interface for shaders. As I understand it in theory the community could create support for OpenGL 4.5 and hardware accelerate it on AMD and Intel chips given the information that's available now. But the open source drivers are ~4 years behind the state of the art at OpenGL 3.3. And that's just for support, the closed source drivers go through tons of optimization for popular games so in practice they're way further behind on performance parity. Why don't they give it away? Competition mainly, just like AMD with Catalyst. Why give Intel a free optimized driver way more advanced than their current one?
Slashdot Mirror
This. Actual stamps is mostly a consumer thing, I just checked our commercial postal service and they recommend a "stamping" machine if you send more than 40 letters/week where you charge it up like a prepaid cell phone, same thing for packages except there they normally print to labels they slap on the package. And for the big companies you get bulk pre-printed envelopes with logo that are collected at your place of business and charged to your corporate account, we have those at work. The potential for abuse is small since you can't drop them off at a regular mailbox and it'd be obvious who you're using to pay for your postage. A lot of the consumer-to-business mail is prepaid and rolled into the cost of business too, the few times I use stamps is to other people but most of that is replaced by email since you don't need a formal signature on anything. I guess there's the odd package, but if it's too big to fit a mail box you're going to the post office anyway.
Nokia has more brand name recognition, so of course we won't use that.
Of the "let's frame it and put it on a wall" more than "I want one in my pocket" variety. I'll always have fond memories of Nokia 3210 and the state of the art in 1999, but it's not selling a new phone and it's not quite up to collectible/antique standards either. And Elop's little stunt sure didn't help Nokia's reputation as a has-been either. Not to mention that Nokia running Windows Phone might have some of the same hardware but there's very little in common between "old Nokia" and "new Nokia" anyway. I think this was a pretty easy call of Microsoft and would have happened regardless, if they'd ponied up a little more they could have gotten the Nokia name for good as it matters more to consumers than the commercial market the remains of Nokia serves.
Because Facebook is really interested in their stock value and not kicking the DEA in the teeth? They're not going to win any favors with anybody for actively sabotaging a criminal investigation, even an illegally conducted one. They want to have the public on their side which is why we're hearing about this in the news, Facebook couldn't win an escalating conflict with proxies and whatnot. If this becomes a big enough PR problem for the police though, the practice might go away.
3) Contractual obligations/customer relations, in the enterprise world people build systems they expect to last many, many years and not have the parts disappear on a whim. Which is is why Intel has launched Itaniums as late as 2012, whoever they suckered into buying it will get time to bail out. Don't underestimate the value of grudges in the enterprise, any executive who gets burned by IBM ditching it fast and dirty will be their enemy when the next big consulting/outsourcing contract rolls around.
Except they're not chasing the mainstream, they're chasing the hype wave of Apple/Google/Microsoft trying to be the "big next thing" instead of what is actually mainstream today with Win7/OS X. Instead of picking a market and staying on target to finish the job they still haven't finished on the office desktop from 1999 or the laptop from 2004 or smartphone from 2009 or tablet from 2014. And at this rate I don't think Ubuntu will stay in one place long enough to be relevant to anyone outside the ~1% of the desktop market Linux owns today.
While there'll always be exceptions I imagine it's usually a very short list of persons who want any one article removed, blowing the whistle saying "someone is trying to bury this article" should have the intended effect anyway.
Games only started using D3D 10/11 *very* recently -- the back catalog this could enable is huge, and D3D 9 games are still coming out today. It'd say it's very important to support.
Bullshit. Almost all games have had an D3D 9 rendering path since XP has been so massively popular, but a whole lot of games has taken advantage of D3D 10/11 where it's been available. It's very important to the number of games you can run on Linux, but it does not represent the state of the art. Speaking of which, WINE's support of D3D 9 through an OpenGL has been pretty good. Or rather my impression has been that if they can figure out what DirectX is doing, there's usually a fairly efficient way of doing in OpenGL. The summary tries to paint it as if OpenGL has been a blocker to DirectX support, my impression is quite the opposite. A gallium3d implementation is closer to the hardware and "more native" than a DirectX-to-OpenGL translation layer, but while it might boost performance a little it won't fundamentally support anything new.
Does he mean a transient reaction in the test set-up that produces the byproducts of fusion, but not long enough to generate useful power?
A transient reaction that can't be reliably reproduced despite recreating the same conditions to the best of our ability. Which might be because the conditions necessary are so extremely specific that they only got them right once by accident or because of some contamination or malfunction that somehow produced the necessary conditions yet attempts to recreate them fail. Or the results of the initial experiment were wrong, but here they've clearly put their desire to believe it was real over their good judgement.
Except authentication is usually not username+password or digital signature, it's identification+official paper saying you're that person. Everywhere your use your passport, driver's license or any other photo ID you're relying on three things:
1) The difficulty of acquiring the information to be on the card
2) The difficulty of forging the card
3) The difficulty of fooling the issuers into producing a fake card
The last one is often a sneaky one, enough ID info and you might trick one of them into believing you've lost your ID and issue a new one. But there's enough direct fakes too, if they have the necessary information that's half the way.
Except that's pretty much what all AJAX web apps do, they "export the UI through some generic mechanism" to the browser so I'd say it's very common. No need for roll-outs and patches, if the server now says there should be a new button there is a new button for everyone. The issue is that I find most web apps really suck compared to native applications so locally I usually want a native, non-web application.
What I'm talking about is a native toolkit that'd make the applications you normally use locally network transparent at the application level, not the display server level. Essentially a toolkit where the UI is always living in its own thread, asynchronously to the actual application. Network transparency just means that thread happens to be living on a different machine, drawing to a different display. And you could tweak it to handle that better, but you wouldn't have to it'd sort of run remotely without modification.
For example, I made a basic calculator just as a proof of concept. Connected locally (I still used a TCP connection just to localhost, better options are available) it looked and acted entirely as a native app you could use every day. It recorded buttons pushed, sent the push events to the back-end and sent updated display text back. I hadn't made it better, but I hadn't made it worse either. The cool thing though was that now I could connect to it remotely. Same calculator popped up, my button clicks go over the network, display text came back over the network. It's a working local native app and a working network transparent remote app. At once. Without any application logic in the client, just drawing tools.
People would like a magic box that make them anonymous and secure on the internet while they log into Facebook, just like they want a magic diet pill while they continue to stuff their faces with sugar and fat. Or for a more relevant tech example they'd like a magic oracle to tell them if a website belongs to who they think it belongs to which is why we have CAs as the best approximation. It's never going to work that way, but there's a lot of money in selling snake oil...
The layer in the system between the user applications and the hardware interface is the place where QT, GTK, Windows graphics api, and all the other graphics toolkits go. Those toolkits shouldn't care too much about the hardware details, just the published capabilities of the GPUs.
It's kinda hard not to care, because a lot of it depends on where you have the data, where the processing capability is and what the link capability is. Sending a video stream is heavy. Even sending an event stream like applications do all by themselves is too heavy during say a resize or scrolling action. Some time ago I experimented with turning Qt into a remote application toolkit, basically taking all signals and slots and serializing them over SSL. It was actually surprisingly successful, basically it was puppeteering a client to draw the interface and using signals and slots to synchronize information on demand. Only the bits you connected sent events across the link.
There were plenty little gotcha's though, like the scrolling I found a way to make a trigger that'd only fire after a custom delay, like for example 50ms after you were done resizing. And I needed to add a system to say "When this button is called, include the check state of this radio button and text of that textbox", but the nice thing was that on the client side it was acting like a client window. It was resizing, the menus were popping up, the buttons responded (though the actions might take time due to latency) and I could do client-client signal/slots like "when the user checks this box, enable these extra fields" too without a server round-trip.
I could do neat things like send a jpg and have the client draw it and even if the client moved the window around, covered it with other dialogs, scrolled it in and out of sight it was zero overhead. Yeah I know kind of like a browser, but not like any RDP/VNC solution. Often I needed the same resources over and over and didn't want to transfer them every time, so I needed a caching system. Kind of like HTML5 persistent objects I guess but before that. And I could populate list/tree/grid objects up front or on demand, a bit like DOM manipulation in HTML.
It wasn't transparent but it was somewhat API transparent, you'd get a "RemotePushButton" instead of a "QPushButton" which acted the same, but instead of actually drawing anything just sent commands to the client which drew the real QPushButton. You didn't really see that though, you just called the functions and connected the RemotePushButton's onClick() signal as if it were a QPushButton. Kind of like HTML+AJAX on steroids but looking and feeling like a native application. That I feel would have been rather next-gen to see it finished.
If you're wondering why I didn't then mainly because the product I was thinking to use it for kinda died on the drawing board. And because to really become user friendly it'd have to integrate on a much deeper level, so you could use all the Q* classes without rewriting everything, the Remote* classes were a hack (QObjects) working with the standard library. And you'd want to put more work in persistence, the idea was that you could yank out the plug on one machine, log back in on another and it'd redraw everything but initially it passed all though and didn't shadow the client state on the server. It could have though, the rewrite was just too much.
which still imposes a significant overhead in terms of transistor count
They did it on the Pentium Pro which had ~1/1000th of the transistors modern processors have today. Even though the instruction set has grown a few times in size, it's certainly entirely irrelevant when it comes to total transistor count today. But keep on spouting nonsense.
*digs up the carcass you can flog the dead horse again*
No x86 chip from the last 20 years runs CISC instructions internally, it's split into micro-ops and AMD/Intel has spent the last 20 years optimizing their decoder and internal instruction set for this one task. If you think using the ARM instruction set is more optimized than that you've drunk way too much of the kool-aid.
I'm really waiting for an x86 phone that can be bought in the USA. These have been available for years in India (!!!!), its really appalling that you cannot yet buy one in the US of all places.
Well, are the current x86 phones Google Android or AOSP Android? In India the latter might sell fine as a smartphone, I think here in the western world we expect all the Google services (and tie-ins...)
IF they will give me episodes...
1) On their TV release date.
2) Of quality at least as good as cable feeds
3) In a usable non-DRM container which doesn't require a web browser
4) Charge no more than $5 per episode (even that is steep).
If it's anything like HBO Nordic:
1) Within 24 hours, often <6 hours
2) Less bandwidth than H.264 cable rips, no 5.1 sound but also not terrible
3) When hell freezes over
4) Here in Norway it's 79 NOK/month, subtracting VAT = $115/year for access to all HBO series
I'm a subscriber but still prefer downloading due to 2), then again I think HBO Nordic is their own company that bought to rights from HBO centrally so whether or not any of this applies is uncertain. I think the delay is because they don't get access to the episode until it's aired in the US, for example.
On the other hand, all the persons infected so far were people with known risk factors for ebola like travelling to ebola country or treating an ebola patient. Assume for a moment that one of these people managed to infect someone random. Are the symptoms going to get bad enough quickly enough that you get flagged as an ebola patient before you've had the chance to infect other people? My usual expectation would be like:
1. You're feeling a bit under the weather, but go to work away.
2. You feel rather crap with feber and a headache, the doctor says to stay in bed.
3. You're really not getting better, doctor runs tests and schedules you for a trip to the hospital.
4. You finally get into the hospital in the "normal" ward, they find out what you got.
5. Shit hits the fan and they try finding everyone you've been in contact with in steps 1-4.
If your average patient manages to infect >1.1 new patients before you can put a stop to it, you have a problem.
One can dump on the Germans as much as one wants but both during WWI and WWII they matched and in some fields outdid the allies in technology and scientific research despite these boycotts, despite the isolation and despite the stultifying effect that the Nazi regime had on parts of the German tech sector which says something about the caliber of German science, scientists and engineers.
Germany lost WWII mainly through their own mistakes, their war machine was strong enough to break Europe's back. Major WTFs being:
- Battle of Dunkirk, could have been a slaughter
- No real plan for the Blitz
- Opening the eastern front before Britain capitulated
- Pearl Harbor, not really Germany's fault tho
Sure, but why? If you start out on a long haul drive it's been charged overnight, if you end a long haul drive it'll charge the coming night. The only reason you'd need a really quick charge at home is if you're just doing a pit stop between one long drive and the next. In that particular case I'd just plan on using superchargers as if my own home was just a diner, it's so rare it'd never pay off.
With closed source you have companies that will spend the minimal amount they can on security, and sweep issues under the rug as long as no one is complaining
If security holes didn't have economic consequences, that'd be true. And I don't mean incident-related costs because the EULA got the almost watertight covered there, but no doubt bad press about zero day bugs hurt their sales and bottom line. If it becomes common and grave enough it also becomes a brand and reputation problem which costs a lot for marketing to tackle. When Blaster and Slammer was all over the news they implemented the firewall. When malware exploited that everyone runs as admin they implemented UAC. When malware corrupted the boot process they came up with Secure Boot, of course throwing a wrench in easy Linux booting was bonus.
They'll put as much effort into it as it pays off rather than dealing with the fallout. Of course they'll cover up and downplay all that they can as damage control regardless, but they're still interested in avoiding it altogether. As long as it doesn't clash with other money making attributes like convenience, in early UAC they dialed it up too high. Now a watered down version is in Windows 7 and few complain anymore. Patch Tuesday is such a convenience, not for security but for IT staff managing Microsoft machines. The downside of 24x7 patching is that all Linux admin must keep up and having them just roll out automatically without testing could get nasty.
Basically, Microsoft takes take blame for whatever happens before patch Tuesday. IT staff can plan for a monthly test and patching session, in between they have it easy unless there's an emergency patch and then everyone knows you "must" do it because it's an emergency. Microsoft is big enough to just absorb the blame because if 0,001% of their customers is mad at them it doesn't really matter. The CIO can point to the company following best practices regarding Microsoft products. All the blame gets neatly passed around and defused, unlike the CIO having to defend their home grown solution where bits and pieces were cobbled together with open source and the only support was themselves so all the blame stays in-house. It might not work better for the system, but it works better for the people in the system.
Actually if you "stick to the story" there's only 50 dollar bills to choose from and once chosen it's eliminated from the set so 50*49*48*.... = 3*10^64 combinations. Less if any of the bills have identical last digits, which is likely due to the birthday paradox. And if they were just counted and put in an evidence bag most the bills are in the right order. If they count the ones, either in order or reverse order and the only thing you need to figure out is where a few fivers or tens go that's cryptologically pathetically weak. And if it did disappear down some pocket, well there goes your evidence that there actually was a pile of cash making up your password. Worst, the police will probably take this as gloating on your part by showing off your perfect yet obviously constructed get-out-of-jail free card. I think the good old "I don't recall" works better.
Since SDXC cards go up to 2TB and record 4K at consumer bitrates I don't see any reason for a new standard for years and even if one was needed it doesn't matter one bit to Google's data mining and most likely all it'd do is make phones with SD cards $2 cheaper so there's no money in it either. Sure denying Microsoft revenue would be nice but Microsoft already has a fat wallet, Google mainly wants to keep them out of their product space.
and two, who the hell sends naked pictures of themselves and actually thinks other people won't see them? 1999 called and it wants it's noobs back.
Teens who want to get laid. Like it or not, cell phones and social media has taken over a lot of the real-world interaction we used to have as teens. Mainly because I didn't have a cell phone until my late teens, much less a camera phone and nothing like social media. A lot of the flirting and teasing that used to happen in dark corners at parties is now happening through texting and sexting online. Not to mention the upkeep of an ongoing relationship, if you wanted to get more graphical than you'd say over a fixed phone line in the hallway you had to hook up in person. Today you're more expected to keep it up all the time, even if you're apart which means sending naughties on Snapchat and such. Yes, sometimes it backfires badly but people in love won't believe their love will stab them in the back. And while I'm pulling this statistic out of my ass, I think most personal photos most of the time aren't shared with anyone but the intended recipient and aren't abused. And I think that still holds true even though these 200k pics leaked.
Not to mention that it was a lot more obvious who was copying and who was not. Ever hear the expression "yesterday's news"? Well that was whatever they read in a competitor's paper yesterday and printed as news today. Today I'm sure they all have watcher services on each other, for every article posted they have someone evaluate whether they can run a copycat article. And I don't mean that in terms of copyright infringement, but just knowing that some event happened and is newsworthy they can write their own, non-infringing article using much the same sources. Today that might mean that one online site is 5-10 minutes behind the original source instead of a day, most people don't even notice who broke the news. Like today pretty much all our services covered the hit-n-run of a cyclist that died. I'm sure someone was first but it's not exclusive and they can all use the same source so they don't have to cite anyone. I suppose investigative journalism is still valuable, but "discovering" journalism has lost a lot of value.
That makes as much sense as saying Intel should provide a magic generic driver so it can run ARM software. nVidia, AMD and Intel all have different hardware implementations, the only thing most people care about is high level DirectX/OpenGL support which is the equivalent of Java on the CPU side. You have an expected functionality but how it's actually implemented in assembler differs from hardware to hardware. To be fair, there is a "thinnest possible overlay" created with Gallium3D which is something like what you ask for. Basically it's something like C for graphics card, one unified interface for shaders. As I understand it in theory the community could create support for OpenGL 4.5 and hardware accelerate it on AMD and Intel chips given the information that's available now. But the open source drivers are ~4 years behind the state of the art at OpenGL 3.3. And that's just for support, the closed source drivers go through tons of optimization for popular games so in practice they're way further behind on performance parity. Why don't they give it away? Competition mainly, just like AMD with Catalyst. Why give Intel a free optimized driver way more advanced than their current one?