Re: I'm very sorry for them...
"With time, they invented marketing, a new way to exploit people...."
I thought they just renamed it crunch time...
1522 posts • joined 29 Oct 2009
"I was a total Microsoft Windows fan up until the announcement of the ".Not Initative" when Ballmer took the reigns. The 1997 PDC here in San Diego was the last conference I went to. I instinctively knew that Micro-shaft had made a sharp turn and was heading into the WRONG direction."
Trying new things is called "innovation". Sometimes it works, a lot of the time it doesn't (Microsoft seems especially good at this side of the equation), but without it, we wither and die.
Basically, you're saying they tried something new that you didn't like and you're bitter about it. Boo hoo. If your comment had read like a rational argument, then maybe it would have carried some weight. But no - here is the same old rant being trotted out again, complete with name-calling ("Micro-shaft", ".Not"), attempts to establish superiority ("those of us who actually know better"), and 90s AOL style use of caps, stars, underscores and deliberately incorrect spelling ("EVAR") in an attempt to draw emphasis.
We get that you do not like modern Microsoft. We get that you do not believe that their current UI style or initiatives are the right way to go. But, like it or not, this is the direction they have decided to go. If there is a specific issue that comes up in an article that you feel the need to comment on, then raise it and discuss it like an adult - these "it was better in the old days" rants and they way they are written are just plain boring now.
At least Eadon's explosions were mildly entertaining. Grow up.
"Okay, we're can't fine or tax them as their retaliation could do far more damage to us than anything we throw at them..."
"Christ, how did that happen?"
"Well, everybody bought into the free stuff and 'do not evil thing'... but that's not the point! C'mon, we need to be seen to be doing something here!"
"Wait a minute... how about we say we want to review what they do and set up a watchdog to keep an eye on them in future?"
"Hmmm... no threat of retaliation, looks like we're doing something and jobs for our mates - that's genius!"
"you throw away old cold, you throw away years and years of bug-fixes"
From my experiences (20 years commercial development), you're more likely to be throwing away years and years of horrible spaghetti code, full of patches, hacks and work-arounds that the business required in order to hit a deadline and that "we'll fix in the future" - but never did because of the next deadline and subsequent wave of patches, work-arounds etc...
A couple of roles back, the senior architects managed to convince the leadership team to do a from-scratch rebuild of one of the more major web-apps we offered (it's predecessor having 10+ year old code in it). Yes, there were weeks of analysis prior to anything happening, and it took over a year to bring it up to production-ready, but thanks to automated regression, when we went live with that rebuilt version, the only bugs we saw were real edge-cases.
A few years ago, Unity - and many other game engines - dropped their licence fees and became free, albeit with a number of limitations: in Unity's case, once your game reached a certain revenue, or if you wanted to remove the "made with Unity" splash screen, you had to pay.
Although this led to a huge flooding of the "indie" game dev markets, from a commercial point of view, it was a win for the game engines - those who were once put off by the price could now develop their games for free, while the engines got both a huge publicity boost and the revenue from those who wanted to buy advanced features or exceeded the revenue thresholds.
This feels like a comparable move by Microsoft: anyone can have a private repo, so those who - for whatever reason - want or need to keep their code private can now use Github, while the three-collaborator limit means that the projects that become successful and grow to the point where they require a bigger team will generate revenue.
"First question, how long does this last when when everything french vanishes from Google?"
As much as I believe that Google would threaten to do this, I don't believe they would.
Say that they did go and do this - any subsequent downturn in the French economy that could be pinned on such an action would undeniably prove that not only does Google have an effective monopoly on web search, but they are also capable of directly affecting major economies by their actions.
Google may be able to drag out anti-competition cases and lobby like nobody else, but doing something like this could only result in an immediate and massive legal response against them on an international level (apart perhaps from in America). And regardless of the outcome, public trust in Google would be utterly shattered forever - way beyond post-browser-wars stuff.
"But please explain why you're campaigning for the hard drive cause?"
You have to understand the thought process:
1) The HDD market is decreasing
2) About 10-15 years ago, HDDs were an essential component of the average PC
2a) "Things were better back then" (see comments about C++ vs ".Not", anything about old UI vs "ugly flatso", etc)
3) Therefore, if the HDD market is decreasing, the PC market must be decreasing
4) The vast majority of PCs are sold with Windows pre-installed...
5) The current version of Windows is Win10...
... and let the red mist descend.
A while back, I figured it would only be a matter of time before someone tried this... given how reluctant people seem to be to pay for anything these days - especially on mobile - having the game also use a bit of spare processing power to generate crypto seemed an obvious way to monetize.
Personally, I don't have a problem with it so long as the developer is up-front about the mining and doesn't take the piss ie: stuff in a whole load of paid DLC and/or ads on top, or hijack every single bit of remaining processing power for crypto-mining that's not being used to run their game/application.
And it might even help developers back onto the path of writing lean software again, as opposed to depending on the user having to have a hugely powerful PC...
(To be honest, I'm amazed that crypo-mining hasnt already been stuffed into Google search/Chrome, Windows, Facebook etc...)
@Marshaltown: careful there - reg forum rules say that direct accusations (in particular, the use of the "s-word") can get your post pulled and even result in a ban.
But yes, having actually taken a look at the post history under this handle, it looks like you're bang on the money...
"That bad boy would've had a wipe and reimage before it got more than 4 feet away from me."
Heck, I'd have gone full BOFH and wiped the entire thing right there in front of him, with a commentary along the lines of:
"No you can't take a backup, whatever's infected it will just get onto your USB stick... when did you first notice the noise? Ok, well you can't restore any backups from then until now, there's a risk that they're infected..."
That sort of user is just begging to be reduced to tears and having the fear of god put into them at the idea of trying it on again...
Said it before and I'll say it again:
The thing I've learned these days is that whoever writes the matching algorithms that recruiters use should be sacked.
My pet hate is that despite never having done contracting (and most roles on my CV being in the 3-5 year duration bracket), I still get scalper emails offering contract posts. Most of them get ignored. However, occasionally I get a complete howler - only a couple of my "secondary skills" matched at best, completely the wrong location, etc...
I now have a copy-paste template for such howlers, which gets emailed back, the appropriate replacement bits blatantly copy-pasted from the scalper's own email (ie: their font etc), stating how concerned I am at how bad a mismatch the role is, that as a professional software developer I feel I have a duty to point out how their crap algorithm is costing them time and money, and they should have an audit immediately with a view to fixing it.
This also gets CC'ed to their company's generic info email as well.
You had such an opportunity.
You could have tested Windows 10 to death, possibly even set up a "revert to Win7" theme (for the UGLY FLATSO haters), and above all, focused on security and privacy, and limited telemetry to crash reporting at the absolute most... with Google and Facebook increasingly coming into question about how they use the data they gather, you did have a shot at re-inventing yourselves to all but the like of those who are still stuck in the browser wars...
... but no. You had to try and do the same damn thing as Google and Facebook. And you had to do it badly. Is it that you just can't stand someone else being the villains or something???
"...could have been worse... Facebook was looking to buy DeepMind
The thing about Farcebook is that you don't have to create an account with them to do anything apart from use Facebook. Okay, so their tracking and "like" begging-buttons are all over the web, but judicious use of blocking software soon takes care of that.
Whereas when you fire up your brand new (non-Microsoft) browser for the first time, what's the default search engine?
And then there's Android, where you've got almost no hope of blocking Google's spyware unless you're willing to jump through numerous hoops...
"Google are good guys. They don't hide behind confusing privacy policies (Microsoft)"
I'll just leave this here:
"when these perpetual children physically age to the point of running the country"
But hey! At least when this happens, it'll finally be the year of Linux (albeit a very robot-y, Google-tied version) on the desktop!
"...and using the same code repositories that were facilitating student malpractice," Ofqual said."
So basically Ofqual, you want the means of gaining a certification in the subject of Computer Science to be completely at odds with how said subject is used out in the real world.
What he f*** planet are you on???
""Thank you for respecting my privacy,"
The irony of a Google employee saying this has blow my mind...
... or could it be that they are brainwashed with some Google-sanctioned definition of "privacy" upon signing the contract, hence they don't consider the recording of their making a public address a breach of privacy...
"you use that to WRITE the algorithm, and once done, you NEVER! HAVE! TO! TEST! IT! AGAIN!!!
... until your business requirements change and you have to modify said algorithm so that it returns a different results set under circumstances x, y and z, but otherwise must return exactly the same data as it has been doing until now.
That is the value of full and proper unit test coverage - it's not about making sure your code works right now, but ensuring that it continues to work as expected after modification. Otherwise, the chances are you're just playing whack-a-mole with bugs.
The idea that "just writing it right in the first place" is an archaic throw-back to the pre-internet era when systems were monolithic and updated once in a blue moon by a single big-bang operation. Businesses now expect new functionality to be delivered rapidly and seamlessly, and as developers, we have to adapt or die.
The irony is that until a few years ago, I used to think along the same lines - "what's the point of unit tests? I've manually tested my code and it works!" But now, when faced with modifying a chunk of code that was written a year ago by someone who is no longer with the company, finding a good suite of unit tests that document how it's supposed to work and catch what I might accidentally break is not only reassuring, but also vastly increases the speed I can work at.
"/me swings a clue-bat and a cat-5-o-nine-tails at ANYONE calling that so-called 'modern' 2D FLAT crap "modern" [and actually believing it]"
A couple of roles back, I once made the mistake of forgetting to lock my desktop before going to lunch... okay, I may have sent a couple of prank emails from similarly unlocked machines prior to this, and possibly have changed a couple of desktop wallpapers... you know, nothing malicious.
Oh, kharma... how sharp your teeth can be.
I got back and found that pretty much everything had been hit. Not just the things I had half expected on the way back from the sandwich shop when - in a moment of dawning horror - I realised what I had done, but everywhere.
I got the email signature switch before it could do any damage - but there are a few commits in that company's git repos that will forever immortalise that day before I spotted the vandalism...
I recall at one point that there was a trend (in my area at least) to have a tune from "The Good, the Bad and the Ugly". I can't remember the name of it - it wasn't the main theme - but it was someone whistling.
I had a second job in a pub at the time. Every now and then, it was entertaining to start whistling the aforementioned tune myself, and watch half the punters diving for their phones...
Biting the hand that feeds IT © 1998–2019