For free? This January, the very OpenBSD project almost had to halt operations as they didn't have the money to pay for the power bill for the build servers. Thankfully they did get a donation package to get over it.
Yes. This is why you should cut out unnecessary portability for legacy platforms (for example old HP/SPARC/SGI UNIX machines which should be in a computer history museum anyway).
It's good that they are ripping out some of the portability. For most people, x86-64 and Linux/BSD/Windows support should be enough in modern days. Many OSS projects are overly portable and they unnecessarily brag how they support all the crusty HP-UX and SGI workstations with ages-old libraries and special legacy implementations. By cutting that support out, problems are avoided and the code is made more clean.
As he said, they also spent 14 weeks planning and setting up the perfect test environment, waiting for environments to be built and going patiently through all the required paperwork. That sounds pretty responsible to me.
Newflash: The vast majority of 0-days are known in the underground long before they are disclosed publicly. In fact, quite a few exploits are found because - drumroll - they are actively being exploited in the wild and someone's honeypot is hit or a forensic analysis turns it up.
It's not that black and white. You expose the vulnerability to even more crackers if you go shouting it around like was done here.
Open source only has the advantage that they will be found and published. In closed source, usually NDAs keep you from publishing anything you might come across, ensuring that knowledge about these bugs stays within certain groups that have a special interest in not only knowing about it but abusing them.
That doesn't still automatically mean that closed source fares worse in found bugs. Companies often have quite bad-ass internal quality assurance measures. They have money to put in it and, it actually produces them value. There is an incentive to do it properly. Of course the tools and methodologies vary from company to company. But let's take Microsoft: they have very rigorous code quality standards and very thorough code audits, before anything gets out from the house.
Sure, we can have lots of eyeballs scanning open source code, but there is no guarantee that a quantified amount of review ever happens. That's really, really bad.
There have been situations where a seed company was collecting seeds of traditional crops, selecting the ones with the most marketable potential, patenting and reselling them again
That is allowed with Public Domain material.
PD license basically means that you throw the product to the wilderness and dogs might shred it into pieces.:)
One big reason is that they never turned on the D2 discussion system. So right now Soylent News is even more clunky to use than the Slashdot Beta. You get directed to another page every time you want to reply or moderate.
Now do the same to all the other important components of the OSS server software stack.
For free? This January, the very OpenBSD project almost had to halt operations as they didn't have the money to pay for the power bill for the build servers. Thankfully they did get a donation package to get over it.
Yes. This is why you should cut out unnecessary portability for legacy platforms (for example old HP/SPARC/SGI UNIX machines which should be in a computer history museum anyway).
It's good that they are ripping out some of the portability. For most people, x86-64 and Linux/BSD/Windows support should be enough in modern days. Many OSS projects are overly portable and they unnecessarily brag how they support all the crusty HP-UX and SGI workstations with ages-old libraries and special legacy implementations. By cutting that support out, problems are avoided and the code is made more clean.
Everything should be fine in Windows 9.1 Update 1 Refresh 1 Patchouli 1.
As he said, they also spent 14 weeks planning and setting up the perfect test environment, waiting for environments to be built and going patiently through all the required paperwork. That sounds pretty responsible to me.
Because the vulnerability was in the server side.
Exactly this.
Newflash: The vast majority of 0-days are known in the underground long before they are disclosed publicly. In fact, quite a few exploits are found because - drumroll - they are actively being exploited in the wild and someone's honeypot is hit or a forensic analysis turns it up.
It's not that black and white. You expose the vulnerability to even more crackers if you go shouting it around like was done here.
Open source only has the advantage that they will be found and published. In closed source, usually NDAs keep you from publishing anything you might come across, ensuring that knowledge about these bugs stays within certain groups that have a special interest in not only knowing about it but abusing them.
That doesn't still automatically mean that closed source fares worse in found bugs. Companies often have quite bad-ass internal quality assurance measures. They have money to put in it and, it actually produces them value. There is an incentive to do it properly. Of course the tools and methodologies vary from company to company. But let's take Microsoft: they have very rigorous code quality standards and very thorough code audits, before anything gets out from the house.
Sure, we can have lots of eyeballs scanning open source code, but there is no guarantee that a quantified amount of review ever happens. That's really, really bad.
There have been situations where a seed company was collecting seeds of traditional crops, selecting the ones with the most marketable potential, patenting and reselling them again
That is allowed with Public Domain material.
PD license basically means that you throw the product to the wilderness and dogs might shred it into pieces. :)
Yep. Seeds in general have a Public Domain (PD) license.
It does not suck that bad anymore. For anyone still having a grudge against Unity, I recommend trying it again at this point.
It's quite cringe-worthy view if you look at all the stuff that is tweeted with the hashtag #HeartbleedVirus. :)
But how many actually use it on a daily basis?
Hehheh, you're modded down by open source fanboys so that the grimy truth would not come to light.
But exactly. How many of those downloads is just "Hey, free Office! Oh, this is trash, uninstalling..."
Games are typically 10GB. You could easily have 10 games installed simultaneously.
It would cost $500.
So the backup disk is online in the same system? Sounds dangerous.
Well, 256GB SSD ought to be enough for anybody, and is relatively affordable.
Today we can have an SSD for the price of $0.50 / GB. It is already good enough.
Hey, you're trying to find a reasonable and truthful middle ground. That prevents all the juicy flame wars. Someone call the guards!
One big reason is that they never turned on the D2 discussion system. So right now Soylent News is even more clunky to use than the Slashdot Beta. You get directed to another page every time you want to reply or moderate.
I would guess that's a pretty rare thing to do, still. So it shouldn't skew the metrics too much.
Why is capacitive touch so important? Multi-touch is cool but I use my Android phone all the time and for just about everything.
It's not only about multitouch. Capacitive touchscreens are more accurate to use with a bare finger than resistive ones, which call for a stylus.
I thought Office 2013 RT shipped with all Windows RT devices.