This is such a non-news. There wasn't even any controversy inside the project. Just a patch, short discussion, resolution, like many others that happen in many different projects each day. How is this newsworthy in any way?
"How do you describe a license that lets you run, modify, fork, and redistribute the code and do virtually anything other than offer a competing SaaS offering of the product? "
Definitely neither as "open source" nor "free software", which it simply isn't. If for some reason you don't want to just call it "proprietary", which it is, then invent your own new term.
The symbols on the cards were filled with ink and differentiated in size, so it wasn't the effect of gravitating towards less inky card, it was really counting.
Well, yes and no. While some managers, like Cargo, are strictly for build-time dependencies, others like npm, pip or RubyGems can also manage globally installed libraries and apps. This bug actually manifested itself in such global installation.
There's nothing "old" in tiles, they aren't just a fallback - they are still essential to the service they provide, so there's no reason to remove support for them. Maps offer two equally supported ways to get the map data: raster and vector. In some use cases you want raster, in others vector. That's it, not much to attribute to backwards compatibility, yet alone its "insane amount".
(sure, they do provide HTML-only frontend for instance and that's very good and could make some argument there, but that's not what the article was talking about)
Raster images are still used even by some of their Web frontends, and it seems completely reasonable to support both tiles and vectors for maps service API. You don't need to remove or "work hard to keep it working" old one when you add a new feature to your service, when the old one is still a core feature of your platform.
Even after the change, the headline is still garbage. And I'm not trolling, it's just plain wrong and misleading. Somebody read the Wired article, misunderstood it and wrote this headline.
Yale Privacy Lab and Exodus Privacy started to *collaborate* with F-Droid, a long-standing free software project endorsed by FSF.
iTunes is somewhat known for releasing stuff early due to mishap. Their management panel must have some poor UX, as it happens quite often with episodes of less known series.
A good CPU from 2015 (Haswell) is a pretty new CPU. High-end CPUs from 2012 (Ivy Bridge) are still perfectly capable, especially in laptops. If you don't need stuff like USB 3.0, you can easily end up today with a pretty beefy Ivy Bridge/Haswell laptop by just doing RAM and storage updates (and maybe WiFi). This is just a carefully designed PR piece to make the issue look less bad, nothing to see here.
Just from easily reproducible ones on my freshly reset iOS 11.2.1:
After a boot up, the first time you swipe left, the search bar overlaps other elements on the widget screen (however it's called) and weirdly jumps in when you finish swiping. When you very quickly swipe on the home screen to the left after moving it slightly to the right, the bottom bar (the one with brighter backgrounds) stops at some position until the swiping animation is finished, then jumps back where it should be. Can also be achieved in opposite way, but harder to notice, since most of the locking up bar is outside of the screen then. There's also a header in settings (on the development profile details) that's aligned right during the page switching animation, which jumps into being center aligned right after it ends.
Also, my whole activation process was basically me trying to skip logging in to iTunes (which resulted in consistent crashes and restarts), then trying to login to an old account I forgot my password to (which resulted in "unknown errors, try again"), and then, after finding out that I can't login to it from the Web either (apparently they blocked it after my many failed attempts), trying to create a new account (which didn't work two times and then magically worked for the third time). Also, each timethe activation process crashed, it resulted in a "Hello" screen overlapping with regular "Press Home to unlock" screen, which looked really bad.
There are more. Some of them I can't reproduce reliably, some of them are in the libraries instead of UI (like crash in WebCore after the app goes into background when there's a WebGL content inside WebView), but annoy me greatly as well.
And let's not even talk about that famous calculator bug - when I got my iPhone it was already fixed, but I'm absolutely not surprised that this bug has really existed.
I have recently bought an iPhone to port some of my games to iOS. Really, I haven't seen such a sloppy OS for a very long time - and I've been a user of various strange devices like Openmoko ones, mostly with community maintained software, so that speaks of something. The number of small weird glitches, animations that jump out or don't finish properly, errors solvable only by clicking "try again" for a few times, config options that take effect only after toggling them more than once... various kinds of little bugs, displaying the overall messiness and untidiness. A lot of them discovered during the first day with the device, and not even using it as a phone, just trying to get through menus to learn how to use it.
Rust doesn't do anything magical to the security of programs written in it. Rust simply won't allow you to compile quite a lot of vulnerable programs that would be happily compiled by a C compiler, because the language is a lot stricter in terms of memory and thread safety.
Also, "safety" of Rust actually requires you to be rather more than less competent. There's a rather steep learning curve, less competent coders will struggle (and learn a lot in the process) just by trying to come up with a code that will be finally accepted by the compiler. Rust doesn't provide safety by holding your hand and doing stuff for you - it's more like a strict parent that sets up boundaries of how you can play, so you won't hurt yourself, but otherwise leaves you alone.
Of course it doesn't mean that you can't write vulnerable code in Rust. It's just a bit harder to do it by accident for some class of potential issues.
Remember that there was a nasty bug in Intel drivers that caused some heavy Qt Quick users (like Plasma) to crash. A significant amount of bad reputation that Plasma 5 has earned should actually be attributed to Intel drivers.
Even ignoring the security aspect, using NoScript speeds up the web so much, it's definitely not worthless. Occasional annoyances like having to temporarily allow some scripts are nothing compared to performance boost.
That's why it wasn't considered when the protocol has been designed (and rightfully so), but it's great to see it as a later addition.
I have never used network transparency in X for any significant purpose, but it was great for quick hacks, especially when I had a smartphone running X.
Slashdot Mirror
This is such a non-news. There wasn't even any controversy inside the project. Just a patch, short discussion, resolution, like many others that happen in many different projects each day. How is this newsworthy in any way?
"How do you describe a license that lets you run, modify, fork, and redistribute the code and do virtually anything other than offer a competing SaaS offering of the product? "
Definitely neither as "open source" nor "free software", which it simply isn't. If for some reason you don't want to just call it "proprietary", which it is, then invent your own new term.
Exactly. "Hacker culture" means something completely different.
Forgot to paste the link: https://phys.org/news/2018-06-...
The symbols on the cards were filled with ink and differentiated in size, so it wasn't the effect of gravitating towards less inky card, it was really counting.
It's a matter of the client, not the protocol. Conversations, one of the best Android XMPP clients, encrypts by default now.
Welcome to the Tesla Motors computer-aided Enrichment Center.
Well, yes and no. While some managers, like Cargo, are strictly for build-time dependencies, others like npm, pip or RubyGems can also manage globally installed libraries and apps. This bug actually manifested itself in such global installation.
There's nothing "old" in tiles, they aren't just a fallback - they are still essential to the service they provide, so there's no reason to remove support for them. Maps offer two equally supported ways to get the map data: raster and vector. In some use cases you want raster, in others vector. That's it, not much to attribute to backwards compatibility, yet alone its "insane amount".
(sure, they do provide HTML-only frontend for instance and that's very good and could make some argument there, but that's not what the article was talking about)
Raster images are still used even by some of their Web frontends, and it seems completely reasonable to support both tiles and vectors for maps service API. You don't need to remove or "work hard to keep it working" old one when you add a new feature to your service, when the old one is still a core feature of your platform.
Maybe they just got a reasonable and stable API from the beginning, so they don't really need to have "insane" backward compatibility?
What was the expression? A drowning man will clutch at a straw?
"Higher than expected reboots"? What kind of newspeak is it?
Even after the change, the headline is still garbage. And I'm not trolling, it's just plain wrong and misleading. Somebody read the Wired article, misunderstood it and wrote this headline.
Yale Privacy Lab and Exodus Privacy started to *collaborate* with F-Droid, a long-standing free software project endorsed by FSF.
Check out the true source: https://www.f-droid.org/en/201...
iTunes is somewhat known for releasing stuff early due to mishap. Their management panel must have some poor UX, as it happens quite often with episodes of less known series.
The headline is garbage.
> going back to 2015
> older CPUs
A good CPU from 2015 (Haswell) is a pretty new CPU. High-end CPUs from 2012 (Ivy Bridge) are still perfectly capable, especially in laptops. If you don't need stuff like USB 3.0, you can easily end up today with a pretty beefy Ivy Bridge/Haswell laptop by just doing RAM and storage updates (and maybe WiFi). This is just a carefully designed PR piece to make the issue look less bad, nothing to see here.
It's 2017, it's not hard not to use Windows anymore.
Just from easily reproducible ones on my freshly reset iOS 11.2.1:
After a boot up, the first time you swipe left, the search bar overlaps other elements on the widget screen (however it's called) and weirdly jumps in when you finish swiping.
When you very quickly swipe on the home screen to the left after moving it slightly to the right, the bottom bar (the one with brighter backgrounds) stops at some position until the swiping animation is finished, then jumps back where it should be. Can also be achieved in opposite way, but harder to notice, since most of the locking up bar is outside of the screen then.
There's also a header in settings (on the development profile details) that's aligned right during the page switching animation, which jumps into being center aligned right after it ends.
Also, my whole activation process was basically me trying to skip logging in to iTunes (which resulted in consistent crashes and restarts), then trying to login to an old account I forgot my password to (which resulted in "unknown errors, try again"), and then, after finding out that I can't login to it from the Web either (apparently they blocked it after my many failed attempts), trying to create a new account (which didn't work two times and then magically worked for the third time). Also, each timethe activation process crashed, it resulted in a "Hello" screen overlapping with regular "Press Home to unlock" screen, which looked really bad.
There are more. Some of them I can't reproduce reliably, some of them are in the libraries instead of UI (like crash in WebCore after the app goes into background when there's a WebGL content inside WebView), but annoy me greatly as well.
And let's not even talk about that famous calculator bug - when I got my iPhone it was already fixed, but I'm absolutely not surprised that this bug has really existed.
I have recently bought an iPhone to port some of my games to iOS. Really, I haven't seen such a sloppy OS for a very long time - and I've been a user of various strange devices like Openmoko ones, mostly with community maintained software, so that speaks of something. The number of small weird glitches, animations that jump out or don't finish properly, errors solvable only by clicking "try again" for a few times, config options that take effect only after toggling them more than once... various kinds of little bugs, displaying the overall messiness and untidiness. A lot of them discovered during the first day with the device, and not even using it as a phone, just trying to get through menus to learn how to use it.
Rust doesn't do anything magical to the security of programs written in it. Rust simply won't allow you to compile quite a lot of vulnerable programs that would be happily compiled by a C compiler, because the language is a lot stricter in terms of memory and thread safety.
Also, "safety" of Rust actually requires you to be rather more than less competent. There's a rather steep learning curve, less competent coders will struggle (and learn a lot in the process) just by trying to come up with a code that will be finally accepted by the compiler. Rust doesn't provide safety by holding your hand and doing stuff for you - it's more like a strict parent that sets up boundaries of how you can play, so you won't hurt yourself, but otherwise leaves you alone.
Of course it doesn't mean that you can't write vulnerable code in Rust. It's just a bit harder to do it by accident for some class of potential issues.
Remember that there was a nasty bug in Intel drivers that caused some heavy Qt Quick users (like Plasma) to crash. A significant amount of bad reputation that Plasma 5 has earned should actually be attributed to Intel drivers.
Even ignoring the security aspect, using NoScript speeds up the web so much, it's definitely not worthless. Occasional annoyances like having to temporarily allow some scripts are nothing compared to performance boost.
That's why it wasn't considered when the protocol has been designed (and rightfully so), but it's great to see it as a later addition.
I have never used network transparency in X for any significant purpose, but it was great for quick hacks, especially when I had a smartphone running X.
Yes. This screen just looks like iPad's settings screen made uglier.