Why would they? It's basic privacy no? Just because I want to pay money to carrier to provide me with data and phone service, I shouldn't have to give up my location from my device. I expect them to know my approximate location from cell tower data.
Generally I'd not expect them actively triangulate my exact location, but I'd realise that's at least possible - but GPS data, wake my phone up, switch on the GPS radio, drain it's battery, send that data back... no. That wouldn't be legal where I live either, let alone expected.
> but GPS data, wake my phone up, switch on the GPS radio, drain it's battery, send that data back... no. That wouldn't be legal where I live either, let alone expected.
Where does the article claim this turns on the GPS if off?
Yes - but perpetual purchases have an interesting gotcha that Microsoft didn't realise at first. To encourage subscription over perpetual, ongoing or evergreen updates are limited to subscription version.
Office 2024 has every feature that was added since Office 2021 to the subscription version - while a chunk of loyal customers are unaware of them.
Back when Google was competing hard with Google Suite, a big perception problem formed with the perpetual customers believing and convincing others that Google were far ahead, with collab editing and other features - after Office had added equivalent.
So for me, If there's a subscription and one-time option - I wonder if the one-time gets all updates going forward. If it doesn't, I realise that they'll regret that if competition picks up, and try to fix it later.
If it does include updates... I worry it will be like many other lifetime updates one-time purchases - when competition is low they'll renege on that promise.
You would definitely not get free upgrades for Office. You would get minor point release updates. You also had to upgrade the Mac version often for:
- the System 7 transition
- the 040 Macs and to get a “32 bit clean version”
- to get the full speed of running natively on PPC Macs
- to get a native OS X version instead of one that ran in the OS 9 sandbox
- the Intel transition to get native performance.
I would much rather pay $150 (?) a year for a five user license where each user gets 1TB of storage and each user can use Office across Macs, Windows, iPhones and iPads.
It’s the same price as Dropbox’s 2TB plan and all you get for that is storage.
On a related note: Steve Jobs was right - Dropbox is a feature not a product.
Yes. That sentence is setup for the speculation in the third paragraph. Folks in this sub-thread are wondering how the one-time price option plays out with Apple Creator Studio.
If you look at Office 365, OneDrive, Teams, SharePoint and Exchange Online as well as AI services and coauthoring are not included in the one time purchase price, as these require ongoing infrastructure supplied by Microsoft.
If you look at Adobe Creative Cloud, you see cloud storage and cloud libraries for maintaining files and assets and sharing them for collaboration, Behance, asset licensing such as Adobe Fonts, and generative AI tooling, as well as a pile of additional apps which were never sold separately. There's also tutorials to help you learn that smattering of apps and plugins.
Apple Creator Studio is a service, so there will likely be at least some product development going to create exclusive functionality - likely in the form of new apps which cannot be bought separately, content packs, AI integrations, additional collaboration features relying on hosted infrastructure, and so on. Since a lot of the storage features and base collaboration are instead part of the iCloud infrastructure, that last point may be a tricky line to walk though.
So far from what I can tell, Final Cut Pro has gotten perpetual updates. Since you can only buy it via the Mac App Store, ther can’t do upgrade pricing.
They could - and some of the 3rd party vendors did: There is a 1Password 7 and a 1Password 8. There was also a Things 1/2, which is now a Things 3. it usually works by creating a new app, and not updating the old one anymore.
Can't comment on quality - but I think it's more nuanced than adjusted too high.
Was getting a lift from a friend in a less than 1 year old Yaris cross. Noticed many cars flashing us on a short flat drive home - assumed it was headlights adjusted wrong.
But no - headlight were in the lowest position. Driver had asked the garage twice to check the headlight adjustment.
Went out the front and headlight looked normal - but squatted and as soon I hit the sweet spot got blinded worse than high beams on my own car.
This Yaris cross, which is going to be a very common car, has dips more powerful than my full beams - it will only take a small bump in the road to shine those adjustment or not - that's a problem all by itself.
I've seen some theories or maybe more like guesses as to how the paywall bypass works - I don't think anyone (or at least no one posting places like here) seems to know.
One I saw suggested they've a set of subscriptions to the paywalled sites and some minimal custom work to hide the signed in account used - which seems plausible. That makes the defense most likely used to catch the account used and ban them - which would be a right pain.
This seems the most likely way it works. Which makes me unsympathetic to publishers who complain about it. Digital distribution will always have this issue. Substack goes from strength to strength because they don't give an inch on the paywall.
I'm thinking they considered this strongly, since that's what they did with the steam deck.
We don't know price yet, but if it's like the deck they'll be trying to keep it as cheap as possible. The deck supposedly was so off-the-shelf that it re-used a design for another AMD customer, leftover elements and all - https://boilingsteam.com/an-in-depth-look-at-the-steam-deck-...
Unless Valve took a big risky bet, the Steam deck is going to be again re-using existing hardware and excess hardware. I'm presuming there are leftover unsold Zen 4 and RDNA 3 dies - and nothing competitive that AMD could offer from Valves perspective, at least when they locked the design some months ago.
The public outcry was to ban cars - literally. They blocked streets, and did what they needed to to block drivers and vehicles. It's long enough ago that maybe the abrasiveness and confrontational nature of it is forgotten now - lots of big changes start out that way, but if successful the success almost drives the way the history is remembered more postively.
It looks to me like it was 100% a "think of the children" moment that often gets ridiculed. I can see the same inflection point in my country around the same time, when street and road design shifted to car orientated and car priority - Amsterdam being one of the notable exceptions but with a well documented fight.
Yes - I'm running a LM Studio on windows on a 6800xt, and everything works more-or-less out of the box using always using Vulkan llama.cpp on the gpu I believe.
There's also ROCm. That's not working for me in LM Studio at the moment. I used that early last year to get some LLMs and stable diffusion running. As far as I can tell, it was faster before, but Vulkan implementations have caught up or something - so much the mucking about isn't often worth it. I believe ROCm is hit or miss for a lot of people, especially on windows.
Microsoft.com and Office.com used to be entirely built upon SharePoint, as SharePoint solutions. It was to prove it out as possible, eat your own dogfood.
I think the shift away started in 2013 or 2014, but you can imagine the throw away effort spent on it.
Not sure about microsoft.com, but office.com frontend "rendering" SharePoint instances were read-only, not plain SharePoint exposed as-is.
Something not touched on by others. The standard Microsoft contract outlawed any moonlighting for years, any code you created was potentially going to be claimed by Microsoft - so you didn't feel safe working on side projects or contributing to open source.
Open source code was a pariah - you were warned unless you had an exception to never look at any open source code even vaguely related to your projects, including in personal time, for fear of opening up Microsoft to legal trouble.
In the context of this, when and why would the average dev get time to properly use git - no just get a shallow understanding, but use it at the complexity level needed for an large internal mono-repo ported to it.
I've used git Microsoft for years, but using git with Office client is totally different. I believe it's used differently, with very different expecations in Windows.
Generally I'd not expect them actively triangulate my exact location, but I'd realise that's at least possible - but GPS data, wake my phone up, switch on the GPS radio, drain it's battery, send that data back... no. That wouldn't be legal where I live either, let alone expected.
reply