I couldn't find it either. Neither on their project pages nor that specific blog article and not even the "Search" option (where I searched for inkscape) on the gitlab.com/ site.
Thanks TranquilMarmot for posting the link to the repo.
This whole naming of Skype app for linux is confusing. This announcement is just that they are retiring their older version of the app and they are asking users to switch to the newer beta version which is missing some features. Ultimately there's still going to be an official app for Linux.
What do they gain by retiring a working app in favour of an unreleased "upgrade"? Is there some problem with the old version that needs immediate upgrade and can't be (security) patched?
I like all the new things coming in iOS11, including this. I recently got my first iPhone and it's on iOS10. Do users like me get to upgrade just the OS on the same handset when they release iOS11? I haven't found the answer to this on some of the apple articles I have browsed.
It's worth mentioning though that there's often not a 100% feature parity between iOS versions on different devices, typically because of hardware changes. These even applies to devices of the same generation, e.g. iPhone 7 and iPhone 7 Plus have different camera features since the latter has two cameras and the former just has one.
The differences between feature sets on different generations is less and less it seems though. If I recall correctly, the differences between the iPhone 3G and iPhone 4 was bigger than for instance iPhone 6 and iPhone 7. If I weren't such a sucker for new and shiny things, I'd probably buy an iPhone SE today.
And my Galaxy Nexus stopped receiving updates 2-3 years ago despite it being a Google device (mine was also straight from the Google store, so it wasn't the carrier's fault).
Cyanogenmod supported the Galaxy Nexus until 13.0 which is Android 6.0.1. So Google just dropped support after 4.3 (coincidentally the last unsupported version) even though it was absolutely possible to update to newer versions of Android. As a result the Galaxy Nexus doesn't receive security updates from Google and is thus not usable as an online device.
While iOS upgrades are usually free these days, it hasn't always been like this. According to wikipedia, iOS 1.1.3 was a paid upgrade on iPod Touches (while being a free upgrade for iPhones).
No they are right. Due to some sort of accounting thing once upon a time on some of the first iPod touches there would be a small fee to upgrade the OS.
Killing 32-bit-only-applications sucks for those apps that haven't been updated in years, but it speeds up the OS and should give you a bit of disk space back as well.
The difference in disk space is basically nonexistent (I could gain significantly more by removing the 32b apps applications, especially since most are games), and the OS speedup/memory gain should be limited and mostly applicable to when you're actually launching 32b applications.
In order to support 32-bit apps the OS needs to include 32-bit versions of all the system frameworks. So dropping support for 32-bit apps means cutting the size of all the system frameworks in half.
As for speedup/memory gain, merely launching a 32-bit app will cause the OS to get a bit slower / use more memory until such time as the app is actually killed by the system. Merely going back to the home screen isn't good enough, since apps stay suspended in the background until the OS decides it needs that memory back. And if you have any 32-bit apps that actually do background processing, you'll end up with 32-bit apps in the background frequently.
> In order to support 32-bit apps the OS needs to include 32-bit versions of all the system frameworks. So dropping support for 32-bit apps means cutting the size of all the system frameworks in half.
Less than half as 32b code objects will be smaller than 64b ones, but even if it's half how much storage is that exactly? I mean I probably have games bigger than the frameworks on my device.
> As for speedup/memory gain, merely launching a 32-bit app will cause the OS to get a bit slower / use more memory until such time as the app is actually killed by the system.
Well yeah so it's just pay for what you use aka who gives a shit.
> And if you have any 32-bit apps that actually do background processing
Which is unlikely given the vast majority of applications being killed by this move are games.
I mean let's be honest for once, the gain from removing 32b frameworks is pretty much entirely on Apple's side, there's little gain to be found for end users when they're not just plain losing value in this move.
> I mean let's be honest for once, the gain from removing 32b frameworks is pretty much entirely on Apple's side
I've given you multiple concrete benefits to end users. You may not personally care about the code size difference, and you seem to be completely discounting the speed / memory usage issues, but just because you personally don't think those are a big deal doesn't mean they don't actually exist.
Think carefully before upgrade. You can't downgrade after you upgraded and new upgrades are known to significantly slow down old devices. My iPhone 4S became unusable after iOS 7 and it's almost bricked with iOS 9. This is Apple way to force users to buy new phones.
That said, they force developers to discontinue support for old iOS versions, so if you don't upgrade, you'll stuck with old apps and some might stop work if they rely on remote servers with changed protocols. So if you want to use iPhones, be prepared to buy new phone every 3-4 years.
Apple doesn't "force" developers to discontinue support for older OS's. Apple does require that you at least have a build that supports both 32 and 64 bit versions.
Apple also will allow you to download an older version of an app if the newest version doesn't support your hardware. I can confirm that this works back to devices that only support iOS 5 - like my first generation iPad from 2010.
Apple occasionally release upgrades which the hardware really isn't capable of supporting. I think the worst example was the iPhone 4, which was given the iOS 7 upgrade. iOS 7 was basically only suitable for multi-core capable devices, and the iPhone 4 was the only device it was released on (the same generation iPod and iPad didn't get the update).
Apple tries really damn hard to make their stuff run well on all devices and it's very impressive how well they support them.
But if your device is a few years old… You're right that you may want to wait and see what the reviews say. Sometimes the updates actually make the phone feel faster, but sometimes (like iOS 7 with all the new transparency effects) it definitely can be a worse experience.
>> Microsoft has been informed, but at the time of publication has not told us when or if the problem will be patched.
Doesn't a bug like this one deserve a responsible disclosure and wait for a patch to be available? The report doesn't state when Microsoft was informed about this, but given the severity of this issue and the fact that they haven't heard back, I would suspect it wasn't too long back.
It's a minor nuisance. It requires people to click on a local file. If a criminal can get a user to do that, he will not waste that opportunity on crashing the desktop.
>As was the case nearly 20 years ago, webpages that use the bad filename in, for example, an image source will provoke the bug and make the machine stop responding. Depending on what the machine is doing concurrently, it will sometimes blue screen. Either way, you're going to need to reboot it to recover. Some browsers will block attempts to access these local resources, but Internet Explorer, for example, will merrily try to access the bad file.
Have been using DuckDuckGo as primary search engine for more than a year. It's OK for many cases but the search results aren't yet there in terms of quality or relevance in many cases. Even searching for AMP shows the AMP spec page after some almost useless dictionary sites, in the search results.
What's going to be interesting is if browsers can at some point render a APM version of a page natively. What I mean is render the original page on the source website as APM content. That will stop the monopoly and hijacking (or rather the rationalization of it) of target websites in Google results.
A bit OT - does anyone know what tool was used to create those slides? They look very light and clean and something I might experiment with for technical presentations.
As mentioned it's the go present tool. It's ok, but kind of annoying. It runs it's own webserver (very easy in go), then does a decent job of slides. But it's kind of annoying to run, you can't run it as a user since it wants to bind to :80. You can't shared slides with people easily, nor host it statically by easily copying files.
Pandoc is pretty similar, just as powerful, and supports multiple output formats. That way you can statically host random files without depending on a go binary running 24/7.
Also be careful with present, it by default runs a sandbox to allow execution of code/examples that I wouldn't trust open to the internet... at least without good justification.
