Every single one of those is a trojan or malware that requires user interaction to install. No viruses per se. Nothing like the many Windows variants in the past. No situation where merely connecting your machine to the internet caused your machine to be infected with any number of worms, viruses, malware, etc via the standard OS installation.
To me, it seems such a level of complexity for such a miniscule problem points far more at a desire to enforce user lock-in and freeze out aftermarket parts.....both of which I put in the category of "Screwing your own customers".
I guess that's why USB-C exists and Apple supports it?
OSX has been out since 2001. I was running Slackware v2.1 back in 1994. So there's a significant difference there, but yes, Apple is leaps and bounds beyond all Linux versions combined on the desktop, and for good reason. Apple is also estimated to be near 10% in desktops, which is a huge number considering the size of the market and that they were less than 2% 10 years ago.
You have to go back a bit further, with PGP in 91, or even further back with InfoZip's encryption, IIRC. I'm sure I haven't gone to the beginning.
Just curious about the apple hate: lightning connectors finally addressed one of the biggest annoyances - keyed connectors. USB-C's connector is a direct reflection of that, as I understand that it was not directionless in its early phases. Walled gardens? Yeah, but you don't have to play there if you don't want to. Let's also not forget that Apple was instrumental in getting DRM removed from music. I'd hoped they'd do the same for video, but it doesn't look likely. It's not like they put rootlets on their CDs after all.
Make it this simple - any US citizen with the requirements can apply for the job at the stated 100% pay. All H1Bs must be posted. If that makes an H1B position unpleasant for the H1B folks, maybe they won't take those jobs either.
As far as I'm concerned, you'd use whatever works for the language in question. I generally prefer readability and for me, at least, GT equates to something that could be a variable, whereas '>' is unambiguous. But again, whatever the language calls for.
Actually, a project using commons is questionable right off the bat. The commons libraries have so many problems it's almost always better to avoid them. Commons logging is a travesty that should have been wholesale replaced long ago, yet it is still "current" and even had a relatively recent nonsensical updates that appear not to address some of its core issues. For a nice read while old, appears to still be the core of commons-loggings problems. You'll note that Craig McClanahan was involved in this, as with Digester, another pile of pain if you want to do anything dynamic. In fact, I'd go out on a limb and state that everything Craig did works statically only, if you're doing any long-running systems with mutations, you'll be debugging and altering anything he wrote (I've been through Tomcat, JBoss's adaptation of Tomcat's core, Struts, Commons-Digester and Commons-Logging among other libraries, so yes, I do indeed know what smells under the covers regarding his work)
Considering the bugs in those libraries, I'm pretty sure proprietary code is not any worse given my own history.
This is not a Java security vulnerability, this is (yet another) commons vulnerability. Every project I've been on since 2006 has banned all use of all commons components across the board. That library set is a virtual shit-pile of crappy ugly hacks and bugs waiting to bite you. There's no reason to import a library to do an empty string check for example. Either cut and paste that function/class into your codebase or write your own and own it.
You can always record it and store it locally. This works with hulu, netflix, or anything else. Personally, I prefer something higher quality than any of those sources (no idea what iPlayer quality is like since I don't have it) The same goes for all those supposedly CD like quality music streams.
If you think that Win7 on up doesn't suffer from the same issues
I am very positive that Win7 does not have the same issues as WinXP. It's got different ones. Even the one that you describe does not technically exist in WinXP because it does not even have an elevation of privileges mechanism - the privileges are simply all granted at the start.
XP did have elevation of privileges mechanism, the Win32 token manipulation APIs date back to at least NT 4, but IIRC were based on modified NT 3.1 code. That no one used them because everyone and everything ran system high, because generally the software forced you to, is an entirely different issue.
I do not smoke, but I do enjoy a glass of wine from time to time - I'd recommend an aromatic white from New Zealand - and stay away from the Malborough ones, they are hopelessly overpriced. Try something from Gisbourne or Napier...
While Microsoft is definitely a candidate for anti-customer activities, even they don't come close to Sony (FYI - I also avoid MS products, but more for my sanity than any other reason at this point). I'm familiar with Nintendo, and Volkswagen I'm not convinced yet qualifies in the anti-consumer area. Sure, they gamed the testing, but apparently they're not the only ones.
I'll add to that - I negatively speak about Sony all the time. I merely mention the CD root kit as the start of a long list of bad behavior that caused me to boycott all Sony products. What's funny is that over time, the reaction I get now is "oh yeah, that's right" instead of "wow, you really believe that?".
Sony is a company full of narcissists who thought they were always right and could do no wrong and thought of their customers as chattel. They still are, and now Sony the company is imitating the Titanic. The only question is "will Sony sink?" I can't think of a more deserving major company.
Hey, the 40's were dangerous, sure, but a good chunk of the jobs were shooting other people with guns. Or hurriedly making more planes and bombs.
My opinion is that it was exactly that labor shortage that allowed the workers to band together and demand better working conditions and allowed for the passage of regulations.
Running your stuff on Win XP is just not feasible - not because of the superficial UI differences, but the deeply engrained unsecure mechanisms it employs.
If you think that Win7 on up doesn't suffer from the same issues, I'd like some of what you're smoking. Windows was designed with a fatal core security flaw, and it has been made worse over time. Check out security tokens and "elevating" privileges, and you'll find that all processes that need an elevated security levels must be started with all elevated security features, and then reduce them on a sub-process/thread basis. There is no means to elevate a security token temporarily. That is the core of 99% of windows flaws, because as soon as you've escaped your process' bounds via an overflow, you are almost always system high. MS has been feverishly bandaiding this via ever more restrictions, but, as long as you can do DLL injection, windows security remains swiss cheese.
Wish you'd written this as a non AC. That covers a whole lot of valid territory.
A couple of points I'd like to add - young people refuse to work with "legacy" apps, rather wanting to rewrite that finely honed cluster as a bunch of web services using some scripting language. (I've actually seen this done, horribly, more than once).
I've see old people that just cannot seem to get their heads around anything that deviates from the narrow slice they've specialized in. That's sad, because they're definitely the first to go when that slice is retired.
But my biggest peeve is with the young, and those who taught them, because they do not learn the basics of programming anymore. Data Structures? Memory management? Algorithm optimizations for CPUs? Nope, none of those, because that's boring and the [language of the day] will take care of it or just buy more memory/servers. That is false for anything interesting you might want to do if you want it to be successful. That lack of knowledge will doom them to poor careers overall.
Actually, we're getting closer to that wonderful time before we had the government looking out for the workers which started in the 40s. Just take a skim at how many incidents occurred in the past and how they diminished and changed past the 60s. Looking at that, I think we've based our entire quality of life on some tenuous regulation by the government of business, and that is being whittled away, causing more and more companies thinking they can go back to the earlier higher short term profit models pre-regulation.
Note that as automation takes over more and more low-skilled jobs, that the labor market will continue to contract. There's going to be some seriously interesting things happening over the next 30-40 years, and it won't look like anything we have today.
Slashdot Mirror
Every single one of those is a trojan or malware that requires user interaction to install. No viruses per se. Nothing like the many Windows variants in the past. No situation where merely connecting your machine to the internet caused your machine to be infected with any number of worms, viruses, malware, etc via the standard OS installation.
To me, it seems such a level of complexity for such a miniscule problem points far more at a desire to enforce user lock-in and freeze out aftermarket parts.....both of which I put in the category of "Screwing your own customers".
I guess that's why USB-C exists and Apple supports it?
OSX has been out since 2001. I was running Slackware v2.1 back in 1994. So there's a significant difference there, but yes, Apple is leaps and bounds beyond all Linux versions combined on the desktop, and for good reason. Apple is also estimated to be near 10% in desktops, which is a huge number considering the size of the market and that they were less than 2% 10 years ago.
You have to go back a bit further, with PGP in 91, or even further back with InfoZip's encryption, IIRC. I'm sure I haven't gone to the beginning.
Just curious about the apple hate: lightning connectors finally addressed one of the biggest annoyances - keyed connectors. USB-C's connector is a direct reflection of that, as I understand that it was not directionless in its early phases. Walled gardens? Yeah, but you don't have to play there if you don't want to. Let's also not forget that Apple was instrumental in getting DRM removed from music. I'd hoped they'd do the same for video, but it doesn't look likely. It's not like they put rootlets on their CDs after all.
And yet Linux just got it's first malware target also. And how big is that desktop market compared to OS X?
Make it this simple - any US citizen with the requirements can apply for the job at the stated 100% pay. All H1Bs must be posted. If that makes an H1B position unpleasant for the H1B folks, maybe they won't take those jobs either.
As far as I'm concerned, you'd use whatever works for the language in question. I generally prefer readability and for me, at least, GT equates to something that could be a variable, whereas '>' is unambiguous. But again, whatever the language calls for.
Actually, a project using commons is questionable right off the bat. The commons libraries have so many problems it's almost always better to avoid them. Commons logging is a travesty that should have been wholesale replaced long ago, yet it is still "current" and even had a relatively recent nonsensical updates that appear not to address some of its core issues. For a nice read while old, appears to still be the core of commons-loggings problems. You'll note that Craig McClanahan was involved in this, as with Digester, another pile of pain if you want to do anything dynamic. In fact, I'd go out on a limb and state that everything Craig did works statically only, if you're doing any long-running systems with mutations, you'll be debugging and altering anything he wrote (I've been through Tomcat, JBoss's adaptation of Tomcat's core, Struts, Commons-Digester and Commons-Logging among other libraries, so yes, I do indeed know what smells under the covers regarding his work)
Considering the bugs in those libraries, I'm pretty sure proprietary code is not any worse given my own history.
And there are a lot more reasons to avoid including them.
This is not a Java security vulnerability, this is (yet another) commons vulnerability. Every project I've been on since 2006 has banned all use of all commons components across the board. That library set is a virtual shit-pile of crappy ugly hacks and bugs waiting to bite you. There's no reason to import a library to do an empty string check for example. Either cut and paste that function/class into your codebase or write your own and own it.
Programmers are not software engineers.
Software Engineers are, generally, programmers also.
You can always record it and store it locally. This works with hulu, netflix, or anything else. Personally, I prefer something higher quality than any of those sources (no idea what iPlayer quality is like since I don't have it) The same goes for all those supposedly CD like quality music streams.
It took me 5 minutes to get over the cringe factor of reading your post: They made a third starship troopers? How much pain can one person take?
GPG started life as PGPs lesser cousin. And PGP has at least one OSS version available as well. So you're actually using PGP.
Definitely a difference, but it was one of the only times Comcast didn't screw me. That is an event worth noting.
So Comcast screwing up by not screwing you is an event worth noting?
If you think that Win7 on up doesn't suffer from the same issues
I am very positive that Win7 does not have the same issues as WinXP. It's got different ones. Even the one that you describe does not technically exist in WinXP because it does not even have an elevation of privileges mechanism - the privileges are simply all granted at the start.
XP did have elevation of privileges mechanism, the Win32 token manipulation APIs date back to at least NT 4, but IIRC were based on modified NT 3.1 code. That no one used them because everyone and everything ran system high, because generally the software forced you to, is an entirely different issue.
I do not smoke, but I do enjoy a glass of wine from time to time - I'd recommend an aromatic white from New Zealand - and stay away from the Malborough ones, they are hopelessly overpriced. Try something from Gisbourne or Napier...
I'm always game for a new vintage.
While Microsoft is definitely a candidate for anti-customer activities, even they don't come close to Sony (FYI - I also avoid MS products, but more for my sanity than any other reason at this point). I'm familiar with Nintendo, and Volkswagen I'm not convinced yet qualifies in the anti-consumer area. Sure, they gamed the testing, but apparently they're not the only ones.
I'll add to that - I negatively speak about Sony all the time. I merely mention the CD root kit as the start of a long list of bad behavior that caused me to boycott all Sony products. What's funny is that over time, the reaction I get now is "oh yeah, that's right" instead of "wow, you really believe that?".
Sony is a company full of narcissists who thought they were always right and could do no wrong and thought of their customers as chattel. They still are, and now Sony the company is imitating the Titanic. The only question is "will Sony sink?" I can't think of a more deserving major company.
If you listen to those asking to increase the H1B limits, I'd say there's a shortage of potential employees.
Hey, the 40's were dangerous, sure, but a good chunk of the jobs were shooting other people with guns. Or hurriedly making more planes and bombs.
My opinion is that it was exactly that labor shortage that allowed the workers to band together and demand better working conditions and allowed for the passage of regulations.
Definitely not the fault of the CIO. It must be the fault of one of the techs. You just cannot find good techs.
Better ask for 1000 more H1Bs!
Running your stuff on Win XP is just not feasible - not because of the superficial UI differences, but the deeply engrained unsecure mechanisms it employs.
If you think that Win7 on up doesn't suffer from the same issues, I'd like some of what you're smoking. Windows was designed with a fatal core security flaw, and it has been made worse over time. Check out security tokens and "elevating" privileges, and you'll find that all processes that need an elevated security levels must be started with all elevated security features, and then reduce them on a sub-process/thread basis. There is no means to elevate a security token temporarily. That is the core of 99% of windows flaws, because as soon as you've escaped your process' bounds via an overflow, you are almost always system high. MS has been feverishly bandaiding this via ever more restrictions, but, as long as you can do DLL injection, windows security remains swiss cheese.
Wish you'd written this as a non AC. That covers a whole lot of valid territory.
A couple of points I'd like to add - young people refuse to work with "legacy" apps, rather wanting to rewrite that finely honed cluster as a bunch of web services using some scripting language. (I've actually seen this done, horribly, more than once).
I've see old people that just cannot seem to get their heads around anything that deviates from the narrow slice they've specialized in. That's sad, because they're definitely the first to go when that slice is retired.
But my biggest peeve is with the young, and those who taught them, because they do not learn the basics of programming anymore. Data Structures? Memory management? Algorithm optimizations for CPUs? Nope, none of those, because that's boring and the [language of the day] will take care of it or just buy more memory/servers. That is false for anything interesting you might want to do if you want it to be successful. That lack of knowledge will doom them to poor careers overall.
It was actually about 4 numbers that I'm aware of before I attempted to contact them and wound up reporting them. Haven't heard a peep since then.
Actually, we're getting closer to that wonderful time before we had the government looking out for the workers which started in the 40s. Just take a skim at how many incidents occurred in the past and how they diminished and changed past the 60s. Looking at that, I think we've based our entire quality of life on some tenuous regulation by the government of business, and that is being whittled away, causing more and more companies thinking they can go back to the earlier higher short term profit models pre-regulation.
Note that as automation takes over more and more low-skilled jobs, that the labor market will continue to contract. There's going to be some seriously interesting things happening over the next 30-40 years, and it won't look like anything we have today.