I'm pretty sure, at a bare minimum, Vista and 7 could do this out-of-the-box. They removed it in Windows 8, requiring the "Windows Media Center" upgrade to re-add the codecs as Microsoft didn't like paying the licensing fees for a feature few people used.
C++ is one of the toughest languages for tools to handle - it's crazy complicated even just to parse right.
You're not wrong, and I don't disagree with anything you said. I was just merely pointing out that, for a large C++ project, the value of the refactoring tools in an IDE is of little concern, so a smart editor is often sufficient.
Nitpick - technically, we're talking about Java, where there are no header files. The interface is defined in the same source files as the implementation.
Even so, I don't think an API should be copyrightable, but if it is, it should be considered fair use to actually use it. Otherwise, the software industry just wouldn't work.
You can still seed at a ratio of 200 and not seed the whole file, if you're constantly uploading a single block multiple times. I don't think you'd be able to get away with claiming that you didn't seed the whole file in that case to avoid copyright infringement. Once you start breaking it up like that, the opposition lawyers will claim that you uploaded, say, 1 small segment of the file to 500 separate users, which is 500 instances of copyright infringement, even if the seed ratio is less than 1.
You're forgetting the series of points near the south pole, where walking 1 mile west does 1 or more complete laps around the pole, bringing you back to where you started.
Using Visual Studio 2013 here. The refactoring tools are near useless in our large C++ project. For example, using "Rename" on a member field called m_size will often rename m_size instances from other classes too. They intentionally dumbed down the "Find all references" feature as users complained it was too slow, and by default it now uses a text search based approach which isn't really any better than a dumb text editor. I find it's easier to just rename the m_size field in the class to m_size2, find all the build errors, then do a text replacement on m_size2, than it is to deal with the unreliable tools in Visual Studio.
People would trade their old cars in for one equipped with an Apple iCarStereo if it solved those problems.
When the nav/infotainment system is a small fraction of the cost of a car, it's not likely to shorten the expensive replacement cycles by much, if at all. And most of the proceeds of the new car doesn't go to Apple, so they won't even see much benefit.
Urschel acknowledges that he has faced questions from NFL officials, journalists, fans and fellow mathematicians about why he runs the risk of potential brain injury from playing football when he has "a bright career ahead of me in mathematics"
Funny how the NFL officials only care about potential brain injury on players who are good at math. If the risk of brain injury was truly that high, nobody should be playing it.
The basic UI may feel smoother, but the moment you run some software that needs to crunch numbers, no amount of OS magic will negate the limited SoC performance.
I used Visual Studio every day at work. It has a good feature set, but it is notoriously unreliable, and every new release comes with more bugs than fixes. Visual Studio 2013 for example forgets to perform the post-build registration step in 64bit projects, requiring a manual post-build step. It's the year 2015, and the IDE still regularly hangs for seconds at a time when I simply type in the text editor. The debugging engine regularly gets confused, and I have to close all instances of devenv and kill mspdbsrv to get it to respect breakpoints again. I get an average of one day between IDE crashes (even though VS is written in.NET, it still suffers from frequent access violation [0xC0000005] crashes). When 2010 and 2013 are installed side by side, 2010 misbehaves and believes the project needs a full rebuild every time it is run when the project uses IDL files.
I've used Eclipse, and while I don't like the UI or feature set, it has at least been more stable during the times I've used it.
Considering that this build was not supposed to make its way out of Redmond and that the company is not releasing any new builds this year, this may be the best look we get until the Consumer Preview arrives.
If they're not releasing new builds, why did they recently introduce the fast/slow opt-in mode for how quickly you get access to the new builds?
They've stopped shrinking the process (they're actually going bigger again) and are just layering NAND vertically for extra density. We've still got some way to go with reliable high density flash memory.
Slashdot Mirror
I'm pretty sure, at a bare minimum, Vista and 7 could do this out-of-the-box. They removed it in Windows 8, requiring the "Windows Media Center" upgrade to re-add the codecs as Microsoft didn't like paying the licensing fees for a feature few people used.
C++ is one of the toughest languages for tools to handle - it's crazy complicated even just to parse right.
You're not wrong, and I don't disagree with anything you said. I was just merely pointing out that, for a large C++ project, the value of the refactoring tools in an IDE is of little concern, so a smart editor is often sufficient.
At this rate, it'll be easier (and perhaps more useful to consumers) to list the routers without known unpatched vulnerabilities.
It has everything to do with SOHO.
Nitpick - technically, we're talking about Java, where there are no header files. The interface is defined in the same source files as the implementation.
Even so, I don't think an API should be copyrightable, but if it is, it should be considered fair use to actually use it. Otherwise, the software industry just wouldn't work.
The Laws we have in place are the same as we had back then.
The DMCA most definitely wasn't in place back then.
You can still seed at a ratio of 200 and not seed the whole file, if you're constantly uploading a single block multiple times. I don't think you'd be able to get away with claiming that you didn't seed the whole file in that case to avoid copyright infringement. Once you start breaking it up like that, the opposition lawyers will claim that you uploaded, say, 1 small segment of the file to 500 separate users, which is 500 instances of copyright infringement, even if the seed ratio is less than 1.
Plus the mass of the mountain above you will be pulling you upwards to a small degree.
Except Earth has moved relative to the Sun, so you're not in the same position relative to space.
You're forgetting the series of points near the south pole, where walking 1 mile west does 1 or more complete laps around the pole, bringing you back to where you started.
That violates the definition of "walk".
The cycle is repeating
Using Visual Studio 2013 here. The refactoring tools are near useless in our large C++ project. For example, using "Rename" on a member field called m_size will often rename m_size instances from other classes too. They intentionally dumbed down the "Find all references" feature as users complained it was too slow, and by default it now uses a text search based approach which isn't really any better than a dumb text editor. I find it's easier to just rename the m_size field in the class to m_size2, find all the build errors, then do a text replacement on m_size2, than it is to deal with the unreliable tools in Visual Studio.
People would trade their old cars in for one equipped with an Apple iCarStereo if it solved those problems.
When the nav/infotainment system is a small fraction of the cost of a car, it's not likely to shorten the expensive replacement cycles by much, if at all. And most of the proceeds of the new car doesn't go to Apple, so they won't even see much benefit.
Urschel acknowledges that he has faced questions from NFL officials, journalists, fans and fellow mathematicians about why he runs the risk of potential brain injury from playing football when he has "a bright career ahead of me in mathematics"
Funny how the NFL officials only care about potential brain injury on players who are good at math. If the risk of brain injury was truly that high, nobody should be playing it.
The basic UI may feel smoother, but the moment you run some software that needs to crunch numbers, no amount of OS magic will negate the limited SoC performance.
I used Visual Studio every day at work. It has a good feature set, but it is notoriously unreliable, and every new release comes with more bugs than fixes. Visual Studio 2013 for example forgets to perform the post-build registration step in 64bit projects, requiring a manual post-build step. It's the year 2015, and the IDE still regularly hangs for seconds at a time when I simply type in the text editor. The debugging engine regularly gets confused, and I have to close all instances of devenv and kill mspdbsrv to get it to respect breakpoints again. I get an average of one day between IDE crashes (even though VS is written in .NET, it still suffers from frequent access violation [0xC0000005] crashes). When 2010 and 2013 are installed side by side, 2010 misbehaves and believes the project needs a full rebuild every time it is run when the project uses IDL files.
I've used Eclipse, and while I don't like the UI or feature set, it has at least been more stable during the times I've used it.
Sure. I'll just abandon my home country and never visit my family again. Thanks for the tip.
Even then it could still be faked pretty easily, just make some cloned RFID tags.
I'd take those odds.
Even for a shitty movie from Sony?
Considering that this build was not supposed to make its way out of Redmond and that the company is not releasing any new builds this year, this may be the best look we get until the Consumer Preview arrives.
If they're not releasing new builds, why did they recently introduce the fast/slow opt-in mode for how quickly you get access to the new builds?
Storage Spaces and Hyper-V are in the client versions of Windows too.
More likely the US would detain him and trade him for Snowden.
All those words are correctly spelt. A spell checker won't help.
They've stopped shrinking the process (they're actually going bigger again) and are just layering NAND vertically for extra density. We've still got some way to go with reliable high density flash memory.