Windows releases used to be good for **10 YEARS** (mainstream plus extended). IMO, this was one their few big advantages in the server market over linux options, where even LTS linux distros only tend to be good for 3 or 4 without forced updates.
Now, even in the best case, you only get two years, and that's after they extended Fall (H2) releases up from just 18 months.
"Still in support" is the key line, but they don't have to change any other policies to make this hurt. This was already changed a while back so the Spring (H1) feature updates only have 18 months of support and Fall (H2) feature updates only have 24 months of support.
So the best you can do is update to the latest in Fall, where you won't be bugged again for two years... and at that point, if you skip the intervening updates and go straight to latest, you get two more years. If you don't want the current Fall update, you'll be bugged again much sooner.
They should have named it "Java 10", to signify a greater jump, and to avoid breaking changes with all of code out in the wild that looks for "Java 98" to indicate the old version.
Not exactly. Some people are better **software engineers** than others. That's why they were promoted to Level 4. But the idea is, within a given level, the difference should be close enough that a big company doesn't have to negotiate salary with 10,000 different employees individually. Here's what "Level 4 Software Engineer" makes. If you want more, do better work to get promoted to Level 5 (or whatever is next up the chain).
But even putting that aside, why two completely different systems? That's not substantially different than just carrying two devices. Why not just select a different boot drive? If you're really paranoid this could be a hardware switch that completely changes which disk is at the end of a single sata connection, so there is absolutely no possibility of the system installed on disk having online content with the system installed on the other.
Historically, disruptive economic shifts such as the Industrial Revolution **DO** create widespread job loss and suffering during the transition.
But.
On the other side of the transition, populations have always emerged **much** better off for their trouble.
History will likely repeat itself here. If we have a similar Computer and Information Revolution creating similar economic disruption, we should expect a lot of lost jobs to result. We should also expect new, better jobs to be created. But there will lag from one to the other, and it's really gonna suck for the generation caught in the middle.
Back then there wasn't as much opportunity from organizations like Arena Football or the Canadian Football League. Those organizations existed, but with lower numbers of teams and roster sizes, and there were fewer private club leagues. Most of the replacements were recent NFL cuts (and this group was counted as a regular NFL player vs simple replacement player) or had played in college, but otherwise were not directly involved with football.
I'm really curious to see some sample documents, and side-by-side renderings for how they look in MS Office, LibreOffice 5, and LibreOffice 6. Additionally, I'd like to see if the bug list for remaining known discrepancies... what features should I avoid if I want to make sure a document will render consistently across applications.
Agreed. This "pause to work on quality" approach leads to a "Mission Accomplished" attitude when developers go back to "real" feature work, where attitudes and approaches never changed. And with new features right on deck and waiting, they'll be right back where they were inside of two years. If they want success, they need to adopt something like *gasp* Microsoft's trustworthy computing initiative from a number of years ago, where the attitude permeates everything they do.
I worry more about this in combination with the Russian government's influence over any certificate authorities located in the country that may be trusted by default by major operating systems and browsers.
OS X doesn't *really* do AD. It just does the central account/login system, and that's just one small part of of AD. The group policy and software deployment pieces are completely AWOL.
I give it two months following the first widespread implementations before an open source library accurately duplicates the mandatory closed-source portion. Maybe three if they did an especially good job on the algorithm.
I give it two months following the first widespread implementations before there's a open source library the accurately duplicates the mandatory closed-source portion. Maybe three if they did an especially good job on the algorithm.
> For Python, I always use spaces since whitespace is part of the syntax. For other languages, I am not even sure. I would need to look at my.emacs file.
I think you've hit the crux of it. Emacs, Visual Studio, and Eclipse (at least) all use tabs by default. What we may be seeing is a selection for people who know enough about their environment to configure it to work for them.
If you think that's bad, look carefully at the installer for MS Office 2016/365. If you do nothing, it still installs the 32-bit version by default.
You can see Microsoft's own 32 vs 64 guide for Office here: https://support.office.com/en-us/article/Choose-between-the-64-bit-or-32-bit-version-of-Office-2dee7807-8f95-4d0c-b5fe-6c6f49b8d261
The 2013 version of that guide still recommends 32-bit for most people, and I believe until recently the 2016 version did the same.
Latency is a fundamental physical limitation. We'll never have technology that can fully beat it. But we can design competitions that account for and offset the problem. Eventually, some combination of three things will happen as eSports leagues develop:
1. eSports teams will travel for competitions, just like regular sports teams, so that playing fields are always more even (and sub-millisecond LAN latency to boot). 2. Teams will host their own servers, and every match will have a home team, with the home team having a massive latency advantage that's cancelled out by each team playing an equal number of home and away games. I don't see this sticking because it would confer too much advantage during any post-season play. 3. Teams will host their own servers, and each match will always have two halves, with each team hosting a local server for half of the competition.
I could see some combination of #2 and #3, where regular season events have a designated home team, but post-season play has two halves, or perhaps teams will travel only for post-season or tournament play, with either of option 2 or 3 used during a regular season.
Low-latency games typically don't need much bandwidth. They use lots of very small packets to frequently update minimal position and state info. The total throughput is normally fairly small. However, the *delay* it takes for the average packet to reach the server and vice versa matters a great deal.
Slashdot Mirror
> To initiate the exploit, a user simply needs to open an attachment received by email, messenger, or other file transfer service.
When you can convince a user to open a malicious attachment, there are many many options open to you. This is nothing new.
This is after they shortened it.
Windows releases used to be good for **10 YEARS** (mainstream plus extended). IMO, this was one their few big advantages in the server market over linux options, where even LTS linux distros only tend to be good for 3 or 4 without forced updates.
Now, even in the best case, you only get two years, and that's after they extended Fall (H2) releases up from just 18 months.
"Still in support" is the key line, but they don't have to change any other policies to make this hurt. This was already changed a while back so the Spring (H1) feature updates only have 18 months of support and Fall (H2) feature updates only have 24 months of support.
So the best you can do is update to the latest in Fall, where you won't be bugged again for two years... and at that point, if you skip the intervening updates and go straight to latest, you get two more years. If you don't want the current Fall update, you'll be bugged again much sooner.
They should have named it "Java 10", to signify a greater jump, and to avoid breaking changes with all of code out in the wild that looks for "Java 98" to indicate the old version.
Not exactly. Some people are better **software engineers** than others. That's why they were promoted to Level 4. But the idea is, within a given level, the difference should be close enough that a big company doesn't have to negotiate salary with 10,000 different employees individually. Here's what "Level 4 Software Engineer" makes. If you want more, do better work to get promoted to Level 5 (or whatever is next up the chain).
MS has their "Windows To Go" product now that will even let you run a special Windows install from a flash drive.
This is what VMs are for.
But even putting that aside, why two completely different systems? That's not substantially different than just carrying two devices. Why not just select a different boot drive? If you're really paranoid this could be a hardware switch that completely changes which disk is at the end of a single sata connection, so there is absolutely no possibility of the system installed on disk having online content with the system installed on the other.
Historically, disruptive economic shifts such as the Industrial Revolution **DO** create widespread job loss and suffering during the transition.
But.
On the other side of the transition, populations have always emerged **much** better off for their trouble.
History will likely repeat itself here. If we have a similar Computer and Information Revolution creating similar economic disruption, we should expect a lot of lost jobs to result. We should also expect new, better jobs to be created. But there will lag from one to the other, and it's really gonna suck for the generation caught in the middle.
Back then there wasn't as much opportunity from organizations like Arena Football or the Canadian Football League. Those organizations existed, but with lower numbers of teams and roster sizes, and there were fewer private club leagues. Most of the replacements were recent NFL cuts (and this group was counted as a regular NFL player vs simple replacement player) or had played in college, but otherwise were not directly involved with football.
I'm really curious to see some sample documents, and side-by-side renderings for how they look in MS Office, LibreOffice 5, and LibreOffice 6. Additionally, I'd like to see if the bug list for remaining known discrepancies... what features should I avoid if I want to make sure a document will render consistently across applications.
Agreed. This "pause to work on quality" approach leads to a "Mission Accomplished" attitude when developers go back to "real" feature work, where attitudes and approaches never changed. And with new features right on deck and waiting, they'll be right back where they were inside of two years. If they want success, they need to adopt something like *gasp* Microsoft's trustworthy computing initiative from a number of years ago, where the attitude permeates everything they do.
Walmart needs to become Amazon before Amazon can become Walmart.
I don't believe it would. The network would still be "Open" in the sense that anyone can connect and use it without authorization.
You can turn it back on with a registry key.
What makes this patch especially interesting is they also released it for Word 2007, which otherwise would be end of life and excluded from updates.
There's hacking, and then there's hacking. Current law treats any piddly little violation as if you're some l33t mastermind expert criminal.
I worry more about this in combination with the Russian government's influence over any certificate authorities located in the country that may be trusted by default by major operating systems and browsers.
OS X doesn't *really* do AD. It just does the central account/login system, and that's just one small part of of AD. The group policy and software deployment pieces are completely AWOL.
I give it two months following the first widespread implementations before an open source library accurately duplicates the mandatory closed-source portion. Maybe three if they did an especially good job on the algorithm.
Okay, somehow this comment is appearing on a different post than the one I was reading when it was submitted.
I give it two months following the first widespread implementations before there's a open source library the accurately duplicates the mandatory closed-source portion. Maybe three if they did an especially good job on the algorithm.
> For Python, I always use spaces since whitespace is part of the syntax. For other languages, I am not even sure. I would need to look at my .emacs file.
I think you've hit the crux of it. Emacs, Visual Studio, and Eclipse (at least) all use tabs by default. What we may be seeing is a selection for people who know enough about their environment to configure it to work for them.
If you think that's bad, look carefully at the installer for MS Office 2016/365. If you do nothing, it still installs the 32-bit version by default.
You can see Microsoft's own 32 vs 64 guide for Office here:
https://support.office.com/en-us/article/Choose-between-the-64-bit-or-32-bit-version-of-Office-2dee7807-8f95-4d0c-b5fe-6c6f49b8d261
The 2013 version of that guide still recommends 32-bit for most people, and I believe until recently the 2016 version did the same.
Latency is a fundamental physical limitation. We'll never have technology that can fully beat it. But we can design competitions that account for and offset the problem. Eventually, some combination of three things will happen as eSports leagues develop:
1. eSports teams will travel for competitions, just like regular sports teams, so that playing fields are always more even (and sub-millisecond LAN latency to boot).
2. Teams will host their own servers, and every match will have a home team, with the home team having a massive latency advantage that's cancelled out by each team playing an equal number of home and away games. I don't see this sticking because it would confer too much advantage during any post-season play.
3. Teams will host their own servers, and each match will always have two halves, with each team hosting a local server for half of the competition.
I could see some combination of #2 and #3, where regular season events have a designated home team, but post-season play has two halves, or perhaps teams will travel only for post-season or tournament play, with either of option 2 or 3 used during a regular season.
It's not speed; it's latency.
Low-latency games typically don't need much bandwidth. They use lots of very small packets to frequently update minimal position and state info. The total throughput is normally fairly small. However, the *delay* it takes for the average packet to reach the server and vice versa matters a great deal.