|
What the whole operating-system-as-a-service thing tells me is that Windows 7 is the last version of Windows.
Learn from history:
- Many machines that ran win 3.1 could not run Win 97.
- Many machines that ran Win 97 could not run XP.
- Many machines that ran XP could not run Vista.
- etc.
The point of an operating system is to give access to the hardware of the machine.
If a new operating system is required to handle new technology, then it's good that new operating systems are being developed to handle it.
However, have a think about what would have happened to, for example, people with XP machines if the OS had been a service.
Their machines would have been bricked by being "updated" to an operating system that would not give them access to the hardware, because it was consuming it all for itself -- an operating system that was almost universally hated, anyway.
The "Hey! What we do is more important than you or your machine! If what we've made won't run on your machine, buy a new one!" attitude of Windows developers has been clear since XP; they seem to truly believe that their code is more important than their users' property.
Already, Weven and W8 machines are being overladen with "updates" that have nothing to do with giving access to the hardware. In some cases, the hardware that the updates are good for do not even exist on the machines that the updates are being forced on, so all they do is cause latency and/or other problems.
And that's just with the version-specific updates. What will happen when their are no more versions?
I foresee a new blue-screen message:
"Sorry, but we've decided that your machine has to be junked, because it doesn't meet the requirements of our latest updates. Go shopping."
Although it probably won't blue-screen machines at all. The screens will just remain black.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
The real reason: MS employees who actually got stuff done are becoming tired of the *@~!ing ribbon interface. They have decided to move on to greener pastures, which will leave only those who cannot wrap their head around version control. MS will then be left with nobody capable of incrementing, much less improving, the Windows core.
|
|
|
|
|
Nikola Labs, based out of Columbus, Ohio, says it’s about to debut a new iPhone case that can convert radio frequencies into power to help keep your phone charged throughout the day. "She's a witch! Burn her!"
I suspect reality will be underwhelming
|
|
|
|
|
For a quick charge, simply put it into the next microwave oven. "Group-charging" during lunch breaks possible to save energy.
|
|
|
|
|
When Microsoft turns a customer into a subscriber, it gets 1.2 to 1.8 times the revenue compared to old-school licensing. "When you ask 'em, 'How much should we give?' Ooh, they only answer 'More! More! More!'"
Shocking news, I know.
|
|
|
|
|
A look at JavaScript's evolution around an expanding ecosystem of superset languages, libraries and frameworks and the coming impact of ECMAScript 6underlying the browser-centric shift in Web development.
JavaScript today. JavaScript tomorrow. JavaScript forever.
|
|
|
|
|
Use jQuery!
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
The hackopalypse is upon us.
|
|
|
|
|
Duncan Edwards Jones wrote: The hackopalypse is upon us.
So true! mega-upvotes!!
|
|
|
|
|
Io.js 2.0 makes accommodations for ECMAScript 6 and Google's V8 JavaScript engine
It's a V8 world; we're just living in it.
|
|
|
|
|
Let's go behind the specs and find out everything you need to know about getting Windows 10 running on a PC, but were too afraid (or confused) to ask. The fine-print edition
|
|
|
|
|
How amusing. It says Windows 8 purchase is not available in the country that I'm in. Checked my region settings, and it says "United States". I guess I should have voted Republican last election.
Marc
|
|
|
|
|
Wouldn't it be better simply to let the public version come out and then try installing it? We will definitely know whether our machine supports it or not!
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
One of the differences between a great programmer and a bad programmer is that a great programmer adds logging and tools that make it easy to debug the program when things fail. Measure twice, code once
|
|
|
|
|
If you’re 40 or older, you’ve probably seen cases where younger developers were picked over older ones. "Age is strictly a case of mind over matter. If you don't mind, it doesn't matter."
|
|
|
|
|
Yep, I left my previous organization because the top managers were running their mouths that they weren't going to promote anyone over 40. They will learn that these kids that know how to copy and paste all of the JQuery tools don't know how to implement a solid solution and it will cost the organization in the long run.
I will say in their defense, there are a lot of "legacy" IT personnel that don't pull their weight. Their problems seems to be a lack of education and resistance to learn new technologies.
|
|
|
|
|
It's not just IT, if your over 40 you are more of a liability in terms of medical issues / insurance everywhere. Also everyone that is clawing their way up the career ladder gets to they're personal top rung and realizes that journey sucked and there is nothing really up here. So it's really hard to buffalo the over 40 crowd into working really long hours and being abused like the younger who haven't found out it may not be worth it.
Don't believe me? just wait till you get here.
Party on.
|
|
|
|
|
Ron Anders wrote: Also everyone that is clawing their way up the career ladder gets to they're personal top rung and realizes that journey sucked and there is nothing really up here. So it's really hard to buffalo the over 40 crowd into working really long hours and being abused like the younger who haven't found out it may not be worth it.
Well said!
Marc
|
|
|
|
|
Ron Anders wrote: Don't believe me? just wait till you get here. I believe you, and, yes, I'm there age-wise; I have not had a personal experience of "rejection because of age" that I am aware of, and it has been many years since I have "worked" for anyone but myself.
I have, however, fired myself frequently for various causes: usually, laziness, or not showing up.
cheers, Bill
«To kill an error's as good a service, sometimes better than, establishing new truth or fact.» Charles Darwin in "Prospero's Precepts"
|
|
|
|
|
jgakenhe wrote: because the top managers were running their mouths that they weren't going to promote anyone over 40.
Except themselves.
Marc
|
|
|
|
|
Oh no!
It has over 4000 improvements, dropped support to old (IE only) technologies, like ActiveX and VBScript, no more document modes to support older IE anomalies...
So what?!
For those are looking from the developers point of view:
Microsoft Edge has the exact same support for HTML5/CSS3 as IE11 (390 out of 555/45%)...
(So no support for new, but dropping support for old - what we have left?)
I think renaming a product line is just not enough - you should change the brains!!!
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Wrong forum? BTW if you're referring to HTML5test[^], the latest version of IE 11 (11.0.18) only scores 348, not 390.
|
|
|
|
|
Maybe wrong forum...I'm not always sure...
My version of IE11 is 11.0.10011.0 - it suns on Windows 10 , build 10074 and scores 390...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I'm far from being a HTML/CSS expert, but along the few months I faced some web programming, I realized the Htlm5Test site (and others similar) are kinda crappy stuffs. Most of the claimed features aren't officially standardized yet, but for some (censored) reason Chrome put them inside itself.
That's a very bad practice, IMHO, from the programming perspective. However, from the browser-war perspective, is the perfect way to kill the enemies...
Happy to hear from who's more involved than me!
|
|
|
|
|
It is true that most test sites are checking for features that are still in pre-recommendation state at W3C, but I do not see it as a problem - W#C works way too slow, and implementing proposed features gives the community a great tool to provide feedback...
As for IE11/Edge, you should look for the unsupported features that ARE in recommendation state!
Or for the open-source video/audio formats that Microsoft refuses to support!
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|