At the same time, a lot of these services have no issue with cancelling the subscription for a few months when it isn't needed... doesn't fit everyone's workflows, but can be used to cut costs. Might be a non-starter if you use their cloud hosting services though.
I will suggest that Visual Studio 2017 averts the newer != better notion, at least from my experience coming up from 2015. Slightly heavier, yes, but Intellisense seems to be massively more responsive, and the setup program seemed to suck a lot less. Also haven't had it blow up in my face when trying to resume execution during a debug session... yet.
It seems to have issues determining when it does or doesn't have to process every single row/column in the document; another advantage to using old MS Excel format, if you can deal with the 65536 row limitation.
While I do appreciate the sentiment, keeping Google's grubby little track-happy fingers out of an established open source project would be an entirely positive thing, in my book.
Also of note, I've been using staroffice derivatives (starting with a package distributed for SuSE 8.0) for many years, and the experience has always been much better on Linux. Unfortunately, I don't have the latitude to use it as my primary OS at work... next time I get a crap file, I'll see if I can replicate it on Linux.
I think part of my problem is that these documents are coming from my employer's business clients... many of them show signs of aging. People dragging 10+ year old templates through multiple format conversions, and then just deleting the contents of an existing document to use as a template... that sort of thing (e.g. an excel spreasheet that is several hundred kilobytes despite containing no actual entries in cells). I'm placing the blame on Microsoft for being unable to consistently turn out clean and bug-free files.
I've found it usually does alright, up until i need to search for something oddly specific. Frequently useless for highly technical issues, but it is what it is.
It just makes a redirect to google.com, making this a less-useful suggestion... useful if you don't feel like typing in google.com, i guess. Perhaps it was true at one time, but it does not appear to be the case now.
Which is why a holistic approach to tracking prevention is needed... DNS/IP blackholes, adblockers, noscript, etc. Those stupid little 1x1 px images they're so fond of are indeed a real hazard. At the same time, they're far less convenient, and only indicate that the page was loaded... no further behavior information can be directly obtained by that method.
I'd like to believe that, but the general degredation of the quality of search results (also the elimination of the + operator, and general crippling of allintext:) over the past decade say otherwise. Having a gameable algorithm leads to loads of pollution, also.
At the same time, it's like raising a giant red flag "HERE I AM! ABUSE ME BY WHATEVER MEANS YOU SEE FIT!"... I find passively dropping this type of traffic to be less noxious.
(recollection of the distant past) While slightly a hassle, it was not particularly difficult to install the filters for the older versions. Agree on all points though. I still retain o2000/XP for when I need it.
Matter of perspective, I guess... that seeming dedication (regardless of motive) to backwards compatibility is what has kept me from exiting their ecosystem entirely over the past 15 years. And yes, you can still install NTVDM on 32-bit Win 10, so win 3.x stuff can be made to work, as can many DOS applications.
I wonder when they'll extend their definition of "to misbehave" to include people who are critical of their services/policies...
Correct, we're in the process of cheapening it to the point that the general public is sick of hearing it. Be patient.
Worked for the original Xbox....
I think the issue was more with simply not telling anybody about the change, leading to frustration by a genuinely invisible foe.
Been using it since v. 4.0, have always liked their stuff quite a lot. Haven't used it much since X3, but it still holds a place in my heart.
At the same time, a lot of these services have no issue with cancelling the subscription for a few months when it isn't needed... doesn't fit everyone's workflows, but can be used to cut costs. Might be a non-starter if you use their cloud hosting services though.
I will suggest that Visual Studio 2017 averts the newer != better notion, at least from my experience coming up from 2015. Slightly heavier, yes, but Intellisense seems to be massively more responsive, and the setup program seemed to suck a lot less. Also haven't had it blow up in my face when trying to resume execution during a debug session... yet.
Software Assurance reads not unlike Comcast's recent "Service Protection Plan" nonsense...
"That's some nice softwares ya gots there... be a shame if something were to happen to it... ya know?"
(BigCorp): And they said we couldn't squeeze blood from a turnip...
It seems to have issues determining when it does or doesn't have to process every single row/column in the document; another advantage to using old MS Excel format, if you can deal with the 65536 row limitation.
While I do appreciate the sentiment, keeping Google's grubby little track-happy fingers out of an established open source project would be an entirely positive thing, in my book.
Also of note, I've been using staroffice derivatives (starting with a package distributed for SuSE 8.0) for many years, and the experience has always been much better on Linux. Unfortunately, I don't have the latitude to use it as my primary OS at work... next time I get a crap file, I'll see if I can replicate it on Linux.
I think part of my problem is that these documents are coming from my employer's business clients... many of them show signs of aging. People dragging 10+ year old templates through multiple format conversions, and then just deleting the contents of an existing document to use as a template... that sort of thing (e.g. an excel spreasheet that is several hundred kilobytes despite containing no actual entries in cells). I'm placing the blame on Microsoft for being unable to consistently turn out clean and bug-free files.
+1, that'd be rich xD
I've found it usually does alright, up until i need to search for something oddly specific. Frequently useless for highly technical issues, but it is what it is.
re: !* ... Would be nice if they did more than just cause the page to redirect to the relevant site.
It just makes a redirect to google.com, making this a less-useful suggestion... useful if you don't feel like typing in google.com, i guess. Perhaps it was true at one time, but it does not appear to be the case now.
There are search link fixers for all the major search engines out there, but I don't know of any general purpose tracking URL strippers.
Which is why a holistic approach to tracking prevention is needed... DNS/IP blackholes, adblockers, noscript, etc. Those stupid little 1x1 px images they're so fond of are indeed a real hazard. At the same time, they're far less convenient, and only indicate that the page was loaded... no further behavior information can be directly obtained by that method.
I'd like to believe that, but the general degredation of the quality of search results (also the elimination of the + operator, and general crippling of allintext:) over the past decade say otherwise. Having a gameable algorithm leads to loads of pollution, also.
At the same time, it's like raising a giant red flag "HERE I AM! ABUSE ME BY WHATEVER MEANS YOU SEE FIT!"... I find passively dropping this type of traffic to be less noxious.
(recollection of the distant past) While slightly a hassle, it was not particularly difficult to install the filters for the older versions. Agree on all points though. I still retain o2000/XP for when I need it.
De facto? I think it goes well beyond a general consensus...
Matter of perspective, I guess... that seeming dedication (regardless of motive) to backwards compatibility is what has kept me from exiting their ecosystem entirely over the past 15 years. And yes, you can still install NTVDM on 32-bit Win 10, so win 3.x stuff can be made to work, as can many DOS applications.
To that end, my main windows machine is 8.1; good until 2023... even more time to wrangle some good alternatives.