I still run the Zune software and have a Zune Subscription. I don't know what you're talking about, because I'm still enjoying my 10 free songs per month!

No it's written in WinRT which is to say it's sandboxed from the rest of the operating system using the WinRT app model. One of the annoying things about developing for WinRT is just how low privileged an application in WinRT is without any means to escalate except by explicit user permission. Shell access is impossible. COM is nearly non-existent. The only way to get data to and from the application in the WinRT framework is through a specific API contract that makes Soviet Russia look like a libertarian paradise by comparison.

In short, by writing Edge in WinRT they automatically picked up a lot of security features automatically. I would be really surprised if in its current state it could be used to modify system files.

Oops I mean "over a hundred million instanced trees" obviously haha.

Don't forget that when new technology is announced they always list the upper limits of a technology. So it has 1,000 times the potential of current best-case-scenario NAND but you won't see that 1,000 performance boost for 3 decades when they tap out the technology's maximum potential.

I'm rendering a project right now that has over a hundred instanced trees in a forest. So the forest is pretty much instanced, but each tree instance is around 1GB of memory and there are about 12 individual models. Then once I get into terrain geometry and villages and trains and that isn't even getting into the volumetric sparse oct-trees for like smoke from chimneys... etc.. anyway long story short 32GB is already gone *with* massive scale instancing.

Obviously this would follow regular air traffic regulations where there are staggered altitude exclusion zones around airports, national security sites etc.

http://nevhgc.net/images/Airsp...

If I can buy a TB of RAM that's maybe DDR4 speeds but not DDR5 speeds but at say somewhere between NAND and DRAM pricing that would be huge.

Also incredibly useful for something like a phone where you might want to shoot 4k video. The CPU would have a hard time processing that but if you buffered to say a 64GB cache and then processed you could shoot highspeed for a minute instead of 2-3 seconds.

One of the articles says the initial products will be PCIe and NVMe.

The Toms Hardware Article is much better:
http://www.tomshardware.com/ne...

Clearly this memory will necessitate new motherboards. But I would also love to see this on Nvidia cards.

MPEG-LA claims to have full H265 patent coverage, so it'll be decided in the courts if MPEG-LA can defend their H265 claims against HEVC Advance. My guess is that MPEG-LA knows what they've got and HEVC Advance is making a big show for shareholders. Technicolor already put it in their last quarterly earnings report that they had massive profit potential from their HEVC patents. To me this looks like a fake out by companies like Technicolor to trump up the value of their patents while MPEG-LA continues to do real business with reasonable terms. By the time Technicolor et-all's stock holders realize that they aren't making anything off of their ludicrous terms they'll have moved on to the next scam.

Not to mention bandwidth. How are you going to move 500TB to the cloud and back in a reasonable time frame? You're looking at several months even over a gigabit connection.

What are your performance requirements. If you just need a giant dump of semi-offline storage then look into building a backblaze Storage Pod.
https://www.backblaze.com/blog...

For about $30,000 you could build four storage pods. Speed would not be terrific. Backups are handled through RAID. If you want faster, more redundant or fully serviced your next step up in price is probably a $300,000 NAS solution. Which might serve you better anyway.

That's unfair, I use a lot of software that I pay for but want to make peripheral changes to. For instance I use a compute job scheduler that costs about $180 per compute node + maintenance. It's worth the price for the existing features, but I also want to implement esoteric features that maybe nobody else needs but will help it work better with our workflow so I have forked a number of the built in options. The company even has a github repository of the latest release so that you can get performance and reliability bug fixes from the developer while still keeping your one-off tweaks or even share with other companies who need similar fixes.

This same company eventually even bought a substantial addition I made to make it a core feature. This model works well for everybody, if you need a custom feature you just need to add that one small feature without starting from scratch and I don't have to worry about maintaining the code and add big core features like moving to a new database or extending the SDK or writing a web interface or creating a native Python library.

As the author stated, this sort of situation doesn't lend itself well to a support model since most of the users have the same needs so it's only fair that everybody pay a share of the updates and many of the studios that use the software *could* write it themselves if they were just going to develop it indirectly.

No we have two different statistics competing. I can say that 20% of the population died this year, oh my god end of days tragedy! But I can also encourage 50% of the population to procreate this year and have a child. Yay! Population growth everything is fine no need for doom and gloom!

There are more hives. But bees are still dying in record numbers. Both can be true simultaneously. If 50% of every hive died you would have 50% less bees even if the number of hives increased slightly.

>"Non-experts are less likely to use password managers: some find them difficult to use, some don't realize how helpful they can be, and others are simply reluctant to (as they see it) "write" passwords down."

Yeah, because only non-experts would worry about a closed-source, unknown, third party having access to all their extremely sensitive passwords, stored on a server outside their control, stored with unknown methodology, connected to the Internet, with who-knows what access to the data.

Yeah, only non-experts should be worried.

I was just going to say that I am using a cpu raster renderer from 1993 on my latest project. Why? Because for simple data passes it's the fastest renderer available and it's single threaded! I can run 14 concurrent instances on one machine and render in near real-time on the CPU but with proper shading and filtering unlike GPU rendering.

It's pretty much all phong and blinn shading but that goes back to 1977 and the birth of computer graphics.