It's also been horribly unstable for me since the 57 update. Not a crash for years before. Practically a daily occurrence when 57 first came out.
Works fine for me. Hasn't crashed once yet on me (and hasn't in years before that) and it's considerably faster than previous versions. I've run it on Windows, Macs and Linux on somewhere north of 20 machines. Color me dubious.
You must be a Gnome developer. "It works for me therefore it's definitely you, not the software".
Anyway, why is this even surprising, it's clearly a major change for 57, there's going to be problems along the line. Problems can be fixed, but denying that anyone has them is not going to help.
Despite so many claims to the opposite from its supporters, the fact remains that the GPL family of licenses is very restrictive, and they do deprived users of many critical rights, including the right to modify and to distribute software without releasing the source code changes.
As is also mentioned by those supporters, this is the exact point. It restricts the rights of the immediate developers, to protect the rights of all developers down the line, who would not be able to further develop the code if it was closed.
The GPL restricts your rights in a similar way to laws preventing you from murdering people. It restricts your freedom to stab me, but it is rather a good thing for me and everybody around you that you aren't allowed to do that.
Google has always suffered from NIH syndrome. They will develop and abandon their own kernel rather than use the Linux kernel with billions of development hours because Google engineers didn't write linux.
It really is that simple.
What? They have been using a modified Linux kernel in Android and ChromeOS for nearly a decade now. They use a modified version of the kernel in their server farms. Clearly they are using Linux. Or is that not enough? They have to use it forevermore - Linux is the be-all-and-end-all of kernels, and can never be improved upon.
Add to that: there's almost no point in recycling aluminum. It's extremely plentiful on earth and landfills aren't actually a problem
What a shitty way to look at the world....
Yeah, let's not do one of the easiest forms of recycling, and instead mine it out of the ground... from underneath forests generally. We don't need to breathe, right? And more landfill is always a fun things to have around.
Personally I say it's like building imaginary machines... They can't be seen but they exist inside the machine, and inside my imagination. There's cogs and movement and whatever, but those things aren't really there they are constructs of the computer logic and how I manipulate it.
Alternatively, you could just wait a bit, and there will be posts on fan sites and eventually Wikipedia that explore all the nuances of the plot twists. You read those, and you are up to date. It's a more efficient use of your time and economic resources.
Wow, you sound like a riot to be with. Experiencing culture is not the same as reading the synopsis of it.
Soo what about Kylo Ren, described in TFS as "the most magnetic and unpredictable antagonist since Heath Ledger's Dark Knight Joke". Because I thought Ren was a terrible (as in lame) villain in The Force Awakens. Almost as bad as young Anakin in eps 1-3
Agreed, and he's much more interesting here. We get no backstory in TFA, and there frankly he's a bit-player, but he's a main character here undoubtedly. You might not like him still, but there's much more to his character in this film than the previous.
The credit card charge is a bullshit argument. Patreon bills you monthly so they only get hit with the fee once. They were going to add a fee to EVERY pledge. So if someone makes 10 videos in a month Patreon would have taken the fee 10 times. Had that been $1 pledges they would have pocketed $3.70 on top of the $10 they charged you.
No, its exactly what happened. They were *changing* the system to make lots of small charges to you every month. Which is dumb, and not well thought through, but why the costs changed. Patreon wasn't taking more of your money for themselves.
They didn’t ASK. Instead, they simply said “All your wallets are belong to us.”
They forgot that trust, once broken, is damn near impossible to repair. I am reminded of an exchange in the British Parliament after Dunkirk, when an admiral was being upbraided for risking the fleet. The admiral replied, “We can rebuild the fleet in thirty years. We can rebuild the tradition in three hundred.”
I may check in on Patreon in 2317.
Alright calm down, they weren't raiding your wallet, this is not a trust issue. They changed the system in a stupid way that lead to charges (to Paypal, not Patreon) to increase, and you can debate the decision to change the system but it's not like they were personally taking your money to enrich themselves. They changed the system to make more, inefficient, charges.
Jesus, do we really have to have this conversation here, where cynicism reigns? Where the default tone is "I'm so much cooler and more intelligent than everyone else"? Where most of the comments are going to be by people who haven't seen it (but they don't need to, because they're so much more intelligent and already can judge based on their massive predictive brain)? Cultural debate is not a./ strong point.
For my part, I loved it. I might even say it's the best Star Wars film... though that might come down a bit on rewatching... It's funny, serious, genuinely moving when it needs to be, and says very much different things than the other films have. After the feature-length trailer that was The Force Awakens (which I still liked, but was a bit frustrating), we're going new places now.
On the one hand it's eminently sensible to slow the device if that will eek out enough battery for the expected usage - a dead phone has zero performance. And batteries degrade as they get older, that we know... but if the user has no visibility of this, if they have no idea that it's happening or how to fix it then their device is being hobbled without an obvious fix.
Everybody knows that if battery doesn't last, you should replace the battery. But if the phone gets slower... the fix isn't visible. And we know Apple employees aren't the most honest when you ask for diagnosis...
Sensible thing to do, but as all closed-source bundles, if the user isn't informed then it's still pretty anti-consumer.
See Pixel 2 phones that are able to constantly monitor and recognise songs to an on-device hash list.
Surely they do that by reading the ID4 or MP3 or something records of metadata in the file being played. Never had a need to use such tags myself, but I remember being prompted for them when trying to make MP3 audio files. Nothing to do with reading the audio data, unless it happens to reside in the same sector of the hard drive as the Artist/ Album/ Track name of the sound file.
No, literally they listen to the audio in the room. It's not what's playing on the phone, it's what's playing that it can hear.
In reality though, nobody can live like this. You have to trust something and someone at some point. Even if you can see the source you have to trust those that vetted it, and that the compile matches the code, or do that all yourself. And even then, what about firmware, what about hardware, you don't know what that does without the circuit diagrams. So its about picking your level, and trying to do the best you can.
Yes, but you'd have to actually enable "OK Google". Who does that besides my parents because they think it's "nifty"?
While it's certainly true that any system with a mic, be it a home device or a smartphone, could be hacked; I'm definitely not going to intentionally enable such a device to listen to and record my conversations.
My point is that if the device is capable of it, and you can't tell, you have to then trust the company to have implemented it non-maliciously and correctly. We've already had the situation where the Home Minis have been recording when they shouldn't because of a faulty touch sensor on the top.
The Pixel 2 phones can now listen and recognise songs in the background with no noticeable battery effect. They also can recognise the "OK Google" wake phrase. They're not actively transmitting this, though. But if they wanted to be nefarious and record this, and only transmit certain sections of audio, perhaps based on "bad keyword" recognition, I really don't think you'd notice.
Not really, if they were doing that then I don't think battery is an issue anymore. See Pixel 2 phones that are able to constantly monitor and recognise songs to an on-device hash list. I think we have to assume it's possible now.
Having said that, given the size of Google and Amazon etc, I think there would be leaks, someone would let slip that bad stuff was being done. That this has not happened at all, is encouraging. There is trouble ahead though, for sure.
And if anyone has ever been into a Domino's, you can see them doing the work - they don't hit a button advancing the order between each stage, so we can see it must be mostly made-up. It's obvious from just looking at the process, eg there's no scanner when they put the pizza in the oven after it's made, infact it doesn't even have a label at that stage.
If the guy had gone through the proper legal process to register a DNR, then presumably there wouldn't be a debate about it - but he didn't, he got a tattoo. Which is not a legal document last time I checked.
The patient in this case is a moron. Tattoo removal or infill is something they should look into prior to them ending up in an ER unconscious and not able to clarify the "joke" status.
Also - who the hell honours a bet to get a tattoo? Or even makes that bet?
Google's Pixel 2: The plastic section starts at the same place as the volume button making it mechanically weak
*looks at own Pixel 2*. *doesn't see any 'plastic' section*.
The back is metal covered in a plastic coating, so I don't really know what you're talking about. I definitely don't feel you should be so confident about what you're saying, though...
Or material design man, the radio button and checkbox that are both circles and you only know its action by pressing it to see what happens....
My guess is that a "cornerstone" feature like this isn't so much artificially restricted as it is just disabled because Apple isn't testing iPhone 7s. That's not to say they won't backport, but their hands are probably pretty full just fixing iOS 11's messes.
I mean we've been lobbing pretty much exactly the same criticism at Android for all of it's existence, but without the lovely benefit-of-the-doubt tone. If they aren't porting it then they aren't porting it, and all that "old iPhones get all the new functionality they're capable of" rhetoric is not exactly true, is it?
Right. I have zero doubt or cynicism as to the sincerity of this post. But all of the complaints are merely bug reports, more or less. That is to say, the goals and approach of the technology is sound, and once the rough edges are worked out, it will be a game changer. The current state of the audio filtering technology is not up snuff. So be it. These real-world tests will only make it stronger. The poster uses strong language (sucks), but the frustrations are helpful and will only improve the tech.
Do we really care if it's a fundamental problem or a bug, as consumers? I care about what it does now, if I'm going to pay for it now... and I would hope that reviews do the same. It may get improved, but there's no guarantee, and indeed Google's habit of dropping products means I really need to be happy with it now. If it gets improved in the future then I'll reconsider, but for now these seem to be dud products.
And I say this while posting from a new Pixelbook... I've been generally pretty positive about Googles slew of new products, but this one seems not ready.
Slashdot Mirror
It's also been horribly unstable for me since the 57 update. Not a crash for years before. Practically a daily occurrence when 57 first came out.
Works fine for me. Hasn't crashed once yet on me (and hasn't in years before that) and it's considerably faster than previous versions. I've run it on Windows, Macs and Linux on somewhere north of 20 machines. Color me dubious.
You must be a Gnome developer. "It works for me therefore it's definitely you, not the software".
Anyway, why is this even surprising, it's clearly a major change for 57, there's going to be problems along the line. Problems can be fixed, but denying that anyone has them is not going to help.
Despite so many claims to the opposite from its supporters, the fact remains that the GPL family of licenses is very restrictive, and they do deprived users of many critical rights, including the right to modify and to distribute software without releasing the source code changes.
As is also mentioned by those supporters, this is the exact point. It restricts the rights of the immediate developers, to protect the rights of all developers down the line, who would not be able to further develop the code if it was closed.
The GPL restricts your rights in a similar way to laws preventing you from murdering people. It restricts your freedom to stab me, but it is rather a good thing for me and everybody around you that you aren't allowed to do that.
Google has always suffered from NIH syndrome. They will develop and abandon their own kernel rather than use the Linux kernel with billions of development hours because Google engineers didn't write linux.
It really is that simple.
What? They have been using a modified Linux kernel in Android and ChromeOS for nearly a decade now. They use a modified version of the kernel in their server farms. Clearly they are using Linux. Or is that not enough? They have to use it forevermore - Linux is the be-all-and-end-all of kernels, and can never be improved upon.
I thought this was a tech site?
Add to that: there's almost no point in recycling aluminum. It's extremely plentiful on earth and landfills aren't actually a problem
What a shitty way to look at the world....
Yeah, let's not do one of the easiest forms of recycling, and instead mine it out of the ground... from underneath forests generally. We don't need to breathe, right? And more landfill is always a fun things to have around.
it's OK, we've got this sort of news covered...
https://www.xkcd.com/1930/
Personally I say it's like building imaginary machines... They can't be seen but they exist inside the machine, and inside my imagination. There's cogs and movement and whatever, but those things aren't really there they are constructs of the computer logic and how I manipulate it.
Alternatively, you could just wait a bit, and there will be posts on fan sites and eventually Wikipedia that explore all the nuances of the plot twists. You read those, and you are up to date. It's a more efficient use of your time and economic resources.
Wow, you sound like a riot to be with. Experiencing culture is not the same as reading the synopsis of it.
Soo what about Kylo Ren, described in TFS as "the most magnetic and unpredictable antagonist since Heath Ledger's Dark Knight Joke". Because I thought Ren was a terrible (as in lame) villain in The Force Awakens. Almost as bad as young Anakin in eps 1-3
Agreed, and he's much more interesting here. We get no backstory in TFA, and there frankly he's a bit-player, but he's a main character here undoubtedly. You might not like him still, but there's much more to his character in this film than the previous.
The credit card charge is a bullshit argument. Patreon bills you monthly so they only get hit with the fee once. They were going to add a fee to EVERY pledge. So if someone makes 10 videos in a month Patreon would have taken the fee 10 times. Had that been $1 pledges they would have pocketed $3.70 on top of the $10 they charged you.
No, its exactly what happened. They were *changing* the system to make lots of small charges to you every month. Which is dumb, and not well thought through, but why the costs changed. Patreon wasn't taking more of your money for themselves.
They didn’t ASK. Instead, they simply said “All your wallets are belong to us.”
They forgot that trust, once broken, is damn near impossible to repair. I am reminded of an exchange in the British Parliament after Dunkirk, when an admiral was being upbraided for risking the fleet. The admiral replied, “We can rebuild the fleet in thirty years. We can rebuild the tradition in three hundred.”
I may check in on Patreon in 2317.
Alright calm down, they weren't raiding your wallet, this is not a trust issue. They changed the system in a stupid way that lead to charges (to Paypal, not Patreon) to increase, and you can debate the decision to change the system but it's not like they were personally taking your money to enrich themselves. They changed the system to make more, inefficient, charges.
Jesus, do we really have to have this conversation here, where cynicism reigns? Where the default tone is "I'm so much cooler and more intelligent than everyone else"? Where most of the comments are going to be by people who haven't seen it (but they don't need to, because they're so much more intelligent and already can judge based on their massive predictive brain)? Cultural debate is not a ./ strong point.
For my part, I loved it. I might even say it's the best Star Wars film... though that might come down a bit on rewatching... It's funny, serious, genuinely moving when it needs to be, and says very much different things than the other films have. After the feature-length trailer that was The Force Awakens (which I still liked, but was a bit frustrating), we're going new places now.
"eke". Not "eek". That's the sound a mouse makes.
Actually, the original spelling was correct. I use a hamster-wheel generator to charge my phone.
On the one hand it's eminently sensible to slow the device if that will eek out enough battery for the expected usage - a dead phone has zero performance. And batteries degrade as they get older, that we know... but if the user has no visibility of this, if they have no idea that it's happening or how to fix it then their device is being hobbled without an obvious fix.
Everybody knows that if battery doesn't last, you should replace the battery. But if the phone gets slower... the fix isn't visible. And we know Apple employees aren't the most honest when you ask for diagnosis...
Sensible thing to do, but as all closed-source bundles, if the user isn't informed then it's still pretty anti-consumer.
The device listens to the room. For identifying music from other sources. Like shazam.
Surely they do that by reading the ID4 or MP3 or something records of metadata in the file being played. Never had a need to use such tags myself, but I remember being prompted for them when trying to make MP3 audio files. Nothing to do with reading the audio data, unless it happens to reside in the same sector of the hard drive as the Artist/ Album/ Track name of the sound file.
No, literally they listen to the audio in the room. It's not what's playing on the phone, it's what's playing that it can hear.
In reality though, nobody can live like this. You have to trust something and someone at some point. Even if you can see the source you have to trust those that vetted it, and that the compile matches the code, or do that all yourself. And even then, what about firmware, what about hardware, you don't know what that does without the circuit diagrams. So its about picking your level, and trying to do the best you can.
Yes, but you'd have to actually enable "OK Google". Who does that besides my parents because they think it's "nifty"?
While it's certainly true that any system with a mic, be it a home device or a smartphone, could be hacked; I'm definitely not going to intentionally enable such a device to listen to and record my conversations.
My point is that if the device is capable of it, and you can't tell, you have to then trust the company to have implemented it non-maliciously and correctly. We've already had the situation where the Home Minis have been recording when they shouldn't because of a faulty touch sensor on the top.
The Pixel 2 phones can now listen and recognise songs in the background with no noticeable battery effect. They also can recognise the "OK Google" wake phrase. They're not actively transmitting this, though. But if they wanted to be nefarious and record this, and only transmit certain sections of audio, perhaps based on "bad keyword" recognition, I really don't think you'd notice.
Not really, if they were doing that then I don't think battery is an issue anymore. See Pixel 2 phones that are able to constantly monitor and recognise songs to an on-device hash list. I think we have to assume it's possible now.
Having said that, given the size of Google and Amazon etc, I think there would be leaks, someone would let slip that bad stuff was being done. That this has not happened at all, is encouraging. There is trouble ahead though, for sure.
And if anyone has ever been into a Domino's, you can see them doing the work - they don't hit a button advancing the order between each stage, so we can see it must be mostly made-up. It's obvious from just looking at the process, eg there's no scanner when they put the pizza in the oven after it's made, infact it doesn't even have a label at that stage.
If the guy had gone through the proper legal process to register a DNR, then presumably there wouldn't be a debate about it - but he didn't, he got a tattoo. Which is not a legal document last time I checked.
The patient in this case is a moron. Tattoo removal or infill is something they should look into prior to them ending up in an ER unconscious and not able to clarify the "joke" status.
Also - who the hell honours a bet to get a tattoo? Or even makes that bet?
Google's Pixel 2: The plastic section starts at the same place as the volume button making it mechanically weak
*looks at own Pixel 2*. *doesn't see any 'plastic' section*.
The back is metal covered in a plastic coating, so I don't really know what you're talking about. I definitely don't feel you should be so confident about what you're saying, though...
Or material design man, the radio button and checkbox that are both circles and you only know its action by pressing it to see what happens....
Again, no, the Material Design checkbox square. https://material.io/guidelines...
My guess is that a "cornerstone" feature like this isn't so much artificially restricted as it is just disabled because Apple isn't testing iPhone 7s. That's not to say they won't backport, but their hands are probably pretty full just fixing iOS 11's messes.
I mean we've been lobbing pretty much exactly the same criticism at Android for all of it's existence, but without the lovely benefit-of-the-doubt tone. If they aren't porting it then they aren't porting it, and all that "old iPhones get all the new functionality they're capable of" rhetoric is not exactly true, is it?
Right. I have zero doubt or cynicism as to the sincerity of this post. But all of the complaints are merely bug reports, more or less. That is to say, the goals and approach of the technology is sound, and once the rough edges are worked out, it will be a game changer. The current state of the audio filtering technology is not up snuff. So be it. These real-world tests will only make it stronger. The poster uses strong language (sucks), but the frustrations are helpful and will only improve the tech.
Do we really care if it's a fundamental problem or a bug, as consumers? I care about what it does now, if I'm going to pay for it now... and I would hope that reviews do the same. It may get improved, but there's no guarantee, and indeed Google's habit of dropping products means I really need to be happy with it now. If it gets improved in the future then I'll reconsider, but for now these seem to be dud products.
And I say this while posting from a new Pixelbook... I've been generally pretty positive about Googles slew of new products, but this one seems not ready.