You're so stupid that you would rather believe celebrity halfwits and fringe health website over centuries of medical knowledge. If Jenny McCarthy or Rob Schneider says vaccines cause autism it must be true!
You like caring for your kids while they cough, hack and scratch in extreme distress. For days, or even weeks. And with a small real prospect of long term health consequences or even death.
Pregnant moms - deaf babies are so cute!
You think letting a kid acquire a preventable, potentially fatal, debilitating disease is "natural" as opposed to fucking stupid.
The hospital's kid ICU is awesome and has wifi, free coffee and everything!
The state endorses my child neglect for philosophical and religious reasons! Yay freedom!
You're antisocial and like the idea of making other people get sick. Even those who can least afford to get sick. Let's go to Disneyland or kerb crawl some old people's homes!
You're extremely paranoid and believe there is a vast conspiracy by government, the FDA and "big pharma" which involves vaccines somehow.
The likes of Python, Ruby and Node.js have eaten much of Perl's lunch and what they haven't eaten is already served by Perl 5. Unless migration is relatively simple (unlike some previous Perl upgrades), I could well see the world choosing to stay with 5.
This in itself is not enough either because you still have to shut down first. To do it properly the Pi would need a reset button and a standby state - pushing the button would signal the OS to halt and when it was halted, the kernel would send the command to cut the power. Better yet if it also had wake on LAN and wake from a timer.
I think this would be a useful function for other uses of the Pi where it sometimes needs to be on and sometimes needs to be off.
Search Banana Pi (for example) on Alibaba. This shameless name ripoff is a few bucks more, but gets you a device with a similar form factor as the Pi (including GPIO) but with a 1GHZ a dual core ARMv7 CPU and some extra things like a reset button, IR receiver, gigabit LAN, OTG usb port, eSATA port.
I think the Raspberry Pi's main strength is the community around it. That's what other boards including the Banana Pi would fail to supply. From a hardware perspective it is underpowered though.
It's not meant to be a set top multimedia box yet it is powered by a set top multimedia CPU, comes with an HDMI out, LAN, and has hardware codecs for audio and video... It's hardly surprising that people would want to use it in such a way.
I think a bigger issue from using the Pi as a multimedia player is that doesn't have a standby / low power mode. So either you leave the thing on continuously or you have to go over and physically pull the plug from it.
I expect a quad core CPU will improve things somewhat for media playing - the original Pi just about managed it assuming you had the codecs unlocked but it didn't have the juice to power the UI of something like MythTV so it could really chug at times. I wonder if sticking with Broadcom is something of a poisoned chalice given that there are so many affordable and more powerful SoCs they could use instead.
Well done to the team. The usability experience for Libre / OpenOffice has been traditionally bad so I'm glad some effort is going into fixing it. It's going to require constant effort and scrutiny to ensure the experience is good as it can be. A simple example of work still to do is the options dialog which is filled with a lot of advanced settings and clutter.
The payoff is an application which is more productive, forgiving, usable and attractive.
I would have thought that drilling some holes into the back, top or underside of the ATM would fix the problem. The ATM might need some steel plates on the inside of the holes to stop people poking wires through into the machine itself but it shouldn't be rocket science to solve. The underside would be better on the basis that these ATMs are likely to be heavy and fixed to the floor with bolts so the underside would be less accessible.
X is filled with APIs and functionality that no modern desktop has used in years. It requires numerous extensions to support a modern desktop experience but with serious caveats (e.g. compositor's extra latency and issues translating coordinate systems). Every app and widget set avoids X as much as possible by using middleware libraries to avoid this brain damage. Every app is pushing pixmaps around for the most part. Network performance is crippled by the amount of stuff being pushed and the amount of bidirectional messaging that goes into supporting. It has a woeful security model.
It may be in use but doesn't stop it being obsolete. Fortunately most dists will flip the switch and use wayland over the next year or two. And not before time.
Yes when it was flatline sales. It costs Steam very little to toss out free copies of its own game - cents perhaps. That's when digital can be an advantage. It doesn't excuse the MSRP prices for new titles.
"Good luck ever actually getting rid of it, considering it is what every *nix gui app runs on. Even if the switch to Wayland happens, most people will still be stuck with using XWayland constantly for a decade."
Virtually every *nix app runs over abstraction layers such as QT, GTK, Pango, Cairo etc. Assuming there are wayland backends for these layers then porting isn't as hard as you think. There may be vestigal bits of X to clean up and some edge cases that need more effort (screengrabbers, video players, browser plugins etc.) but porting the majority of apps will just port over. Aside from that, if you *did* have some ancient X app you could still fire up X over wayland just for that.
X will probably stick around as a core component for a few more years in most dists and then it'll be pushed off to the side as an optional package, available for those who want it but not installed otherwise because it won't be needed.
"the solution is to merely add an extra function call to the X11 API rather than rewriting the whole thing. Problem solved, if there is one."
X11 is an arcane and largely obsolete framework. The fact it needs so many damned extensions to be any way functional is precisely the reason that developers are keen to get rid of it. It's not secure, it's filled with arcane and obsolete code and it's terribly inefficient both locally and remotely. Fortunately it'll be moved aside and replaced by wayland over the next few years.
Yeah, well, EB games should be sued, if they don't have that warning printed in every store in large print. As well as Amazon and thousands of others.
EB games don't trade in digital games. They trade in physical media. And unless there is a registration code in the box then it's implicitly transferable.
That is not true: you are NOT "buying a license to a game", you're buying the game.
Sorry it is true and wishful thinking doesn't change it. Virtually all commercial software is covered by a EULA - end user licence agreement. You are buying a licence to use the software under the terms described by the EULA. If you run afoul of the terms then your right to use the software may be void or other penalties may apply.
In this particular case I suspect UPlay, Origin, Steam are reasoning that the licence is non transferrable, and since it WAS transferred from one person to another it has become void. That sucks but it's well known that they do this and if you want to avoid it, don't buy licences off some reseller.
They breached contract? They were given a code to redeem as a licence. If the code was associated with terms and conditions that said what kind of account, or region the licence could be used in then they're not breaching anything.
This is no different from what happens on Steam all the time. I remember buying Left 4 Dead in a store for less than it cost to buy it on steam. The retail copy contained a steam code so it was effectively the same game.
It just demonstrates the utterly obscene pricing models in these online stores. In the real world the MSRP / RRP is just a guideline - the store can sell a game for any margin they like and usually they reduce it below MSRP. In the online store, the price is always the MSRP. I occasionally read the (pathetic) excuse that it's the publishers who set the price and there is nothing the store can do about it. Wrong! Publishers should be required to sell their digital download licences at the same wholesale cost as the physical copy and then digital stores retail can compete on their margins.
Just recently Sony offered a 10% discount off of PSN by way of apology for being attacked on Christmas day. The irony is that even with 10% off the prices there were still more expensive than a physical copy with the cost of middleman and postage thrown in. It's not just them of course - XBL is the same. And Steam. And Origin. And UPlay. They only time these services offer value is for games so old that their retail sales have flatlined and where people might pay $10 for a game in digital form that they wouldn't even bother with in physical.
What Ubisoft are doing is no different from what EA did recently or what Steam did before them.
Personally I think they should let people use these keys but the keys should unlockversions of the game that are heavily localized, thus negating any "advantage" people think they got from buying them. e.g. I bet Far Cry 4 and AC 4 are a lot less fun if the audio, text and subtitles are hardcoded to Thai and multiplayer to Thai servers.
As it is, I wouldn't be surprised if the terms of service allow them to do precisely what they did but I think there are better ways to discourage code selling.
I think it's right to say vanilla Pascal was not a good language and so every implementation went off and implemented its own extensions, hacks, workarounds. Turbo Pascal, Free Pascal, Delphi etc. I was reading Gnu Pascal's features yesterday and it's amusing to read the "features" which are features cherry picked from other implementations. There wasn't any standard to maintain cohesion or enable portability and the entire platform suffered from that.
It's not like C/C++ is a perfect language - it's a horrible language in some ways but it's also very powerful and quite portable with discipline. It also has standards by which to measure implementations by and it has tended to keep compilers pretty close together aside from a few extensions.
The readability of C depends on who wrote the code. It's not hard to find code which uses abbreviated variables all on one line, no comments, bad formatting, monolithic, copious use of MACROS, pointer abuse and all the rest to make unreadable code. Indeed, the international obfuscated C contest shows how easy it is to write utterly meaningless code which somehow does something.
And C++ adds it's own layer of fun. Templates are the work of the devil - get an arg wrong e.g. miss a const or a (de)reference, and the compiler might throw a wall consisting of hundreds of errors back at you. Not intuitive at all and certain not easy to step debug.
Doesn't mean the answer is Pascal but C/C++ was never designed for readability and any that exists is by the grace of the person who wrote the code rather than inherent to the language. Other languages do try a lot harder to enforce readability in the file structure and in the code itself. Python would be most famous for it but even enforcing filename = classname, path = namespace as seen in Java / C# gives more structure than you get in C.
I envy you having to use Pascal at University. We had to use modula-2 which is even more anally retentive when it comes to boilerplate.
Anyway, Pascal lost the language war because it wasn't low level enough (at the time) to compete with C and didn't offer any other advantages. By the time franken-Pascals like Delphi appeared to gain those features it was too late because Java filled the application end and C/C++ was still there for the other stuff.
And if 100% of people wore seatbelts it wouldn't prevent some people dying in car crashes. Does that mean the exercise is worthless? After all, if a seatbelt isn't 100% effective what's the point? Except of course even if it were only 50% effective that still represents many thousands of lives saved every year, not to mention many tens of thousands more who suffered less traumatic injuries.
And in the case of a communicable disease, it needs pathways to spread. Block enough pathways and it cannot spread. This is what herd immunity is. Even if a few % of people cannot be vaccinated they are still surrounded by enough people who are. It is no coincidence at all that when these outbreaks occur it is ALWAYS in areas where the vaccinate uptake is lower than required for herd immunity to be effective.
Providing Disney pay for the shots then yes it's reasonable they require all customer facing staff to have shots for all common diseases like rubella, measles, chickenpox, flu etc. that vaccines are highly effective in preventing. It's not just for their benefit but the dozens if not hundreds of kids that performers and the like may come into close contact with during their work day.
And California and other states should start passing laws and prosecuting parents for child endangerment, harm or even manslaughter if their kid ends up contracting a disease because the parents wilfully failed to vaccinate them.
Ah right, so being the mouthpiece for hackers engaged in malicious attacks makes you a reporter and immune to prosecution does it? The courts appear to disagree with you on that point.
Slashdot Mirror
So see, there are reasons.
The likes of Python, Ruby and Node.js have eaten much of Perl's lunch and what they haven't eaten is already served by Perl 5. Unless migration is relatively simple (unlike some previous Perl upgrades), I could well see the world choosing to stay with 5.
I think this would be a useful function for other uses of the Pi where it sometimes needs to be on and sometimes needs to be off.
I think the Raspberry Pi's main strength is the community around it. That's what other boards including the Banana Pi would fail to supply. From a hardware perspective it is underpowered though.
It's not meant to be a set top multimedia box yet it is powered by a set top multimedia CPU, comes with an HDMI out, LAN, and has hardware codecs for audio and video... It's hardly surprising that people would want to use it in such a way.
I expect a quad core CPU will improve things somewhat for media playing - the original Pi just about managed it assuming you had the codecs unlocked but it didn't have the juice to power the UI of something like MythTV so it could really chug at times. I wonder if sticking with Broadcom is something of a poisoned chalice given that there are so many affordable and more powerful SoCs they could use instead.
The payoff is an application which is more productive, forgiving, usable and attractive.
I would have thought that drilling some holes into the back, top or underside of the ATM would fix the problem. The ATM might need some steel plates on the inside of the holes to stop people poking wires through into the machine itself but it shouldn't be rocket science to solve. The underside would be better on the basis that these ATMs are likely to be heavy and fixed to the floor with bolts so the underside would be less accessible.
I doubt many programmers would know what IoT means because it's an acronym for utterly meaningless umbrella term.
It may be in use but doesn't stop it being obsolete. Fortunately most dists will flip the switch and use wayland over the next year or two. And not before time.
Yes when it was flatline sales. It costs Steam very little to toss out free copies of its own game - cents perhaps. That's when digital can be an advantage. It doesn't excuse the MSRP prices for new titles.
Virtually every *nix app runs over abstraction layers such as QT, GTK, Pango, Cairo etc. Assuming there are wayland backends for these layers then porting isn't as hard as you think. There may be vestigal bits of X to clean up and some edge cases that need more effort (screengrabbers, video players, browser plugins etc.) but porting the majority of apps will just port over. Aside from that, if you *did* have some ancient X app you could still fire up X over wayland just for that.
X will probably stick around as a core component for a few more years in most dists and then it'll be pushed off to the side as an optional package, available for those who want it but not installed otherwise because it won't be needed.
X11 is an arcane and largely obsolete framework. The fact it needs so many damned extensions to be any way functional is precisely the reason that developers are keen to get rid of it. It's not secure, it's filled with arcane and obsolete code and it's terribly inefficient both locally and remotely. Fortunately it'll be moved aside and replaced by wayland over the next few years.
Yeah, well, EB games should be sued, if they don't have that warning printed in every store in large print. As well as Amazon and thousands of others.
EB games don't trade in digital games. They trade in physical media. And unless there is a registration code in the box then it's implicitly transferable.
That is not true: you are NOT "buying a license to a game", you're buying the game.
Sorry it is true and wishful thinking doesn't change it. Virtually all commercial software is covered by a EULA - end user licence agreement. You are buying a licence to use the software under the terms described by the EULA. If you run afoul of the terms then your right to use the software may be void or other penalties may apply.
In this particular case I suspect UPlay, Origin, Steam are reasoning that the licence is non transferrable, and since it WAS transferred from one person to another it has become void. That sucks but it's well known that they do this and if you want to avoid it, don't buy licences off some reseller.
The right of first sale doesn't apply to software licences. You're buying a licence to a game, not a physical thing that you can sell.
They breached contract? They were given a code to redeem as a licence. If the code was associated with terms and conditions that said what kind of account, or region the licence could be used in then they're not breaching anything.
It just demonstrates the utterly obscene pricing models in these online stores. In the real world the MSRP / RRP is just a guideline - the store can sell a game for any margin they like and usually they reduce it below MSRP. In the online store, the price is always the MSRP. I occasionally read the (pathetic) excuse that it's the publishers who set the price and there is nothing the store can do about it. Wrong! Publishers should be required to sell their digital download licences at the same wholesale cost as the physical copy and then digital stores retail can compete on their margins.
Just recently Sony offered a 10% discount off of PSN by way of apology for being attacked on Christmas day. The irony is that even with 10% off the prices there were still more expensive than a physical copy with the cost of middleman and postage thrown in. It's not just them of course - XBL is the same. And Steam. And Origin. And UPlay. They only time these services offer value is for games so old that their retail sales have flatlined and where people might pay $10 for a game in digital form that they wouldn't even bother with in physical.
Personally I think they should let people use these keys but the keys should unlockversions of the game that are heavily localized, thus negating any "advantage" people think they got from buying them. e.g. I bet Far Cry 4 and AC 4 are a lot less fun if the audio, text and subtitles are hardcoded to Thai and multiplayer to Thai servers.
As it is, I wouldn't be surprised if the terms of service allow them to do precisely what they did but I think there are better ways to discourage code selling.
It's not like C/C++ is a perfect language - it's a horrible language in some ways but it's also very powerful and quite portable with discipline. It also has standards by which to measure implementations by and it has tended to keep compilers pretty close together aside from a few extensions.
And C++ adds it's own layer of fun. Templates are the work of the devil - get an arg wrong e.g. miss a const or a (de)reference, and the compiler might throw a wall consisting of hundreds of errors back at you. Not intuitive at all and certain not easy to step debug.
Doesn't mean the answer is Pascal but C/C++ was never designed for readability and any that exists is by the grace of the person who wrote the code rather than inherent to the language. Other languages do try a lot harder to enforce readability in the file structure and in the code itself. Python would be most famous for it but even enforcing filename = classname, path = namespace as seen in Java / C# gives more structure than you get in C.
Anyway, Pascal lost the language war because it wasn't low level enough (at the time) to compete with C and didn't offer any other advantages. By the time franken-Pascals like Delphi appeared to gain those features it was too late because Java filled the application end and C/C++ was still there for the other stuff.
And in the case of a communicable disease, it needs pathways to spread. Block enough pathways and it cannot spread. This is what herd immunity is. Even if a few % of people cannot be vaccinated they are still surrounded by enough people who are. It is no coincidence at all that when these outbreaks occur it is ALWAYS in areas where the vaccinate uptake is lower than required for herd immunity to be effective.
And California and other states should start passing laws and prosecuting parents for child endangerment, harm or even manslaughter if their kid ends up contracting a disease because the parents wilfully failed to vaccinate them.
Ah right, so being the mouthpiece for hackers engaged in malicious attacks makes you a reporter and immune to prosecution does it? The courts appear to disagree with you on that point.