The person who won does not matter to my post. There is evidence showing that regardless of who you were voting for, you were being targeted. Some of it was more obvious than others, but people on all sides of the political spectrum -- me included -- failed to filter out some of the spin coming their way.
Stop jumping to conclusions with divisive outrage. It's what they wanted. There's no room for pride here.
Our last election, and even current reporting, showed that a lot of people do not learn, and even the ones that do end up learning too late. If Google can do something to flag obviously false reports as what they are, then I say more power to them -- it'll be doing us a service.
Even if they take things that are merely probably false or highly spun and supply a few links to what reputable sources say about the issue, that'd help keep people more informed and outside of their bubble.
I don't like having one company be an arbiter of truth either, but... if people can't do it for themselves, who is going to do it? Traditional news agencies have been unable to counter this round of nonsense, and in some cases are contributing to it.
decoding those instructions takes time. you now have to run the clock at twice the speed of a RISC core in order to decode those "compact" instructions into the same equivalent RISC ones.
It used to work like this, but hasn't for a long time.
Desktop x86 CPUs have high maximum clock rates because they don't need to worry as much about heat, not because of complex instruction decode. CPUs are pipelined, and instruction decode is just one extra piece of that long pipeline. It definitely increases CPU size to need to dispatch and break down so many instructions, but really doesn't have any bearing on clock speed.
The last PC I had that wasn't capable of SSE2 was an Athlon T-Bird, which had a quite beefy for its time 768MB of RAM. I wouldn't want to even try running Windows 7 on that.
The mining causing prices to skyrocket also had the effect of making gamers not upgrade their GPUs, and now that the current lineup is old they will probably be waiting for the next version to come out.
You also have godlike 4K HDR10 144Hz monitors that are about to start shipping, and no current GPU can handle that even on a lot of simpler titles. So people may be waiting to upgrade to something that can handle that.
The altcoin mining craze seems to finally be dying down and prices are returning to normal, but it's too late. If gamers aren't crazy for these GPUs anymore, and miners aren't buying them either, it seems plausible that they'd have a lot of unsold inventory lying around.
H.264 was king. Now we've got H.265 and AV1 which have not entirely replaced H.264 due to compatibility purposes, but have still gained significant traction.
On the audio side, AAC replaced MP3, and Opus is set to replace AAC. Opus can generally reach the same quality as MP3 in less than half the bits!
So I don't see this stagnation they talk about. These algorithms are generally straightforward and codec devs, even if they don't have a hyper-efficient implementation yet, will be able to see the benefit -- it's just a matter of investing in their time to develop high quality code and hardware for it.
I don't think it's about nutrition, but about efficiency and sustainability. If we can get better nutrition into a package that is cheaper to produce or better for the environment, then there's a market for it.
Not having to care for cows, removing greenhouse gasses caused by cows, ability to create this milk in more varied environments leading to shorter transport routes, being more nutrition dense allowing fewer transports all together... there's a lot of potential to be explored.
I never said it was being done in the correct place, but you'd actually be surprised how difficult it actually is to do low-latency audio rendering in software.
When you render VR, the frame can take several milliseconds to render. It then, at the last moment before going to screen, performs a screen-space transform to account for any head rotation that happened in that short moment of rendering. So they have a way to hide the latency. There's no equivalent transform that can be done with audio, so you're stuck with just rendering it at the last possible moment.
So there's the rendering, which with 3D sound, environmental effects, and so on, can actually take a non-trivial amount of time. Then, you need to account for the PC's own latency -- audio drivers have a surprisingly high latency even when using ASIO or WASAPI's exclusive mode.
Having a device that is tightly controlled and bypasses the typical APIs would be a pain in the ass and probably not gain traction, but might actually be a benefit here if looking purely at VR-quality latency.
They were doing positional mixing inside the headphone, incorporating sensor data from a VR headset to allow for low-latency sound translation. Current VR mixes sound in software, which means for quick head movements, the sound can lag behind noticeably.
The headphones also had more than one driver per ear, with a custom HRTF to take advantage of them.
I hear that. I got my first glass-backed phone and also ended up getting my first case, because it was clearly going to get scratched up at best or, at worst, super prone to shattering on impacts. It also helped me realize why phone makers are so fixated on making slim phones: they're planning for a case to double its size.
The environmental cost of producing solar cells virtually negates the green benefits for many years.
The numbers I've seen show that over a 30 year lifetime, a solar panel (conservatively) results in about 10% the emission footprint when compared to coal and about 30% the footprint of natural gas. That doesn't seem terrible to me.
He's leaving because the intern program openly discriminates based on gender, sexual orientation, or ancestry. Basically, they won't hire a white American male as an intern.
You're pointing to a specific outreach program, not to LLVM's entire intern program.
8K broadcast standards use Rec 2020, which has a much wider gamut and can therefor show colors that most TVs these days can't. Rec 2020 is even wider than the DCI-P3 that many high-end monitors benchmark against these days.
Rec 2020 also defines a larger bit depth: 10 or 12 bits per component rather than 8. This is partly to support the wider gamut, but it'll also help everything else by allowing much better gradients.
Even if you don't have an 8K TV, ones that use HDR10 and Dolby Vision will benefit: both of these standards use the Rec 2020 gamut. So... bring on the 8K revolution. I want better browns.
The DNC definitely didn't help itself by putting forward such a boring, unpopular candidate and then doing seemingly everything they could to prevent Bernie from winning.
By actively preventing Bernie from getting the democratic nomination they made a Trump victory much more likely. Tons of people voted "not Hillary" with their Trump vote.
It's come out that Russia influenced this too. As soon as Bernie was out of the way, they doubled down stoking the fires to get Bernie supporters mad at Hillary. I doubt any significant amount of people who were voting on policy ended up switching, but those who were voting emotionally to begin with were probably pretty easy targets.
Agreed. Bandwidth is great but it's high enough now that it's not as important.
What I'd be interested in seeing is latency and "connectedness" if that makes sense.
How long does it take for me to load main page, and click a few levels deep, on the top 100 websites? What if I haven't been using my phone for an hour? How often do I open up an app and it just spins for 5 seconds while things get connected?
5-10 years ago when I heard "full stack", it meant that I could throw just about anything at you and you'd be well set to figure it out.
These days over half of the developers I interview call themselves "full stack", and upon further digging maybe 10% of them meet my prior definition. It's the new buzzword.
You can write Javascript and a stored procedure? It makes you full stack now - you don't even have to be very good at either of them. Most people draw a blank face when I ask what they've written that wasn't part of a website.
Ray tracing is an impressive technical feat, but the argument against it for gaming still stands:
However fast you get at ray tracing, you can instead use that power for rasterization and do far far more.
The day may come where that gap doesn't matter anymore, or where we find a way to overcome it... but for now, I think this technology will primarily be used to help accelerate very simple environments, and more complex for offline rendering.
I've heard a mixed bag coming out of Netflix re: developer experience, but one thing I admire is their effort toward a reliable user experience.
From testing everything down to minutiae, to designing things so that failure is simply another regular and expected state to move forward from... most companies do not commit the time/funds to do this sort of thing.
This practical engineering is much cooler to me than Facebook/Google's latest me-too Javascript libraries that iteratively steal the next good established idea from desktop coding and call it innovation.
"We segment the videos into shots, we analyze the video per shot," said the company's director of video algorithms Anne Aaron. Now, an action scene in a show may stream at a higher bit rate than a scene featuring a slow monologue
Video encoders have supported constant quality modes for quite a while that already do this very effectively. I'm guessing they don't do this out of some need for precise control or for hardware compatibility. It's obviously not a wasted effort, but it's unfortunate that Netflix is needing to reinvent the wheel here.
We're just taking a quick 4 year vacation to recharge ourselves. Well, technically a staycation -- wouldn't want to travel and risk visiting one of those shithole countries.
Slashdot Mirror
I've got plenty of Canadian buddies who're just outside of a major city and their only internet option is extremely slow and expensive wireless.
The person who won does not matter to my post. There is evidence showing that regardless of who you were voting for, you were being targeted. Some of it was more obvious than others, but people on all sides of the political spectrum -- me included -- failed to filter out some of the spin coming their way.
Stop jumping to conclusions with divisive outrage. It's what they wanted. There's no room for pride here.
Let people learn when they screw up
Our last election, and even current reporting, showed that a lot of people do not learn, and even the ones that do end up learning too late. If Google can do something to flag obviously false reports as what they are, then I say more power to them -- it'll be doing us a service.
Even if they take things that are merely probably false or highly spun and supply a few links to what reputable sources say about the issue, that'd help keep people more informed and outside of their bubble.
I don't like having one company be an arbiter of truth either, but... if people can't do it for themselves, who is going to do it? Traditional news agencies have been unable to counter this round of nonsense, and in some cases are contributing to it.
Intel CPUs only break down some of the more complex instructions into uops. Most of the common ones are executed directly.
decoding those instructions takes time. you now have to run the clock at twice the speed of a RISC core in order to decode those "compact" instructions into the same equivalent RISC ones.
It used to work like this, but hasn't for a long time.
Desktop x86 CPUs have high maximum clock rates because they don't need to worry as much about heat, not because of complex instruction decode. CPUs are pipelined, and instruction decode is just one extra piece of that long pipeline. It definitely increases CPU size to need to dispatch and break down so many instructions, but really doesn't have any bearing on clock speed.
The last PC I had that wasn't capable of SSE2 was an Athlon T-Bird, which had a quite beefy for its time 768MB of RAM. I wouldn't want to even try running Windows 7 on that.
I'd also really like to see some unified G-Sync/FreeSync standard come along, preferable without the 2-3x monitor markup.
VESA already did this, it's called Adaptive Sync and it's part of DisplayPort 1.2a.
NVIDIA refuses to implement it.
The mining causing prices to skyrocket also had the effect of making gamers not upgrade their GPUs, and now that the current lineup is old they will probably be waiting for the next version to come out.
You also have godlike 4K HDR10 144Hz monitors that are about to start shipping, and no current GPU can handle that even on a lot of simpler titles. So people may be waiting to upgrade to something that can handle that.
The altcoin mining craze seems to finally be dying down and prices are returning to normal, but it's too late. If gamers aren't crazy for these GPUs anymore, and miners aren't buying them either, it seems plausible that they'd have a lot of unsold inventory lying around.
H.264 was king. Now we've got H.265 and AV1 which have not entirely replaced H.264 due to compatibility purposes, but have still gained significant traction.
On the audio side, AAC replaced MP3, and Opus is set to replace AAC. Opus can generally reach the same quality as MP3 in less than half the bits!
So I don't see this stagnation they talk about. These algorithms are generally straightforward and codec devs, even if they don't have a hyper-efficient implementation yet, will be able to see the benefit -- it's just a matter of investing in their time to develop high quality code and hardware for it.
I don't think it's about nutrition, but about efficiency and sustainability. If we can get better nutrition into a package that is cheaper to produce or better for the environment, then there's a market for it.
Not having to care for cows, removing greenhouse gasses caused by cows, ability to create this milk in more varied environments leading to shorter transport routes, being more nutrition dense allowing fewer transports all together... there's a lot of potential to be explored.
I never said it was being done in the correct place, but you'd actually be surprised how difficult it actually is to do low-latency audio rendering in software.
When you render VR, the frame can take several milliseconds to render. It then, at the last moment before going to screen, performs a screen-space transform to account for any head rotation that happened in that short moment of rendering. So they have a way to hide the latency. There's no equivalent transform that can be done with audio, so you're stuck with just rendering it at the last possible moment.
So there's the rendering, which with 3D sound, environmental effects, and so on, can actually take a non-trivial amount of time. Then, you need to account for the PC's own latency -- audio drivers have a surprisingly high latency even when using ASIO or WASAPI's exclusive mode.
Having a device that is tightly controlled and bypasses the typical APIs would be a pain in the ass and probably not gain traction, but might actually be a benefit here if looking purely at VR-quality latency.
This is not your typical HRTF.
They were doing positional mixing inside the headphone, incorporating sensor data from a VR headset to allow for low-latency sound translation. Current VR mixes sound in software, which means for quick head movements, the sound can lag behind noticeably.
The headphones also had more than one driver per ear, with a custom HRTF to take advantage of them.
I hear that. I got my first glass-backed phone and also ended up getting my first case, because it was clearly going to get scratched up at best or, at worst, super prone to shattering on impacts. It also helped me realize why phone makers are so fixated on making slim phones: they're planning for a case to double its size.
The environmental cost of producing solar cells virtually negates the green benefits for many years.
The numbers I've seen show that over a 30 year lifetime, a solar panel (conservatively) results in about 10% the emission footprint when compared to coal and about 30% the footprint of natural gas. That doesn't seem terrible to me.
He's leaving because the intern program openly discriminates based on gender, sexual orientation, or ancestry. Basically, they won't hire a white American male as an intern.
You're pointing to a specific outreach program, not to LLVM's entire intern program.
8K broadcast standards use Rec 2020, which has a much wider gamut and can therefor show colors that most TVs these days can't. Rec 2020 is even wider than the DCI-P3 that many high-end monitors benchmark against these days.
Rec 2020 also defines a larger bit depth: 10 or 12 bits per component rather than 8. This is partly to support the wider gamut, but it'll also help everything else by allowing much better gradients.
Even if you don't have an 8K TV, ones that use HDR10 and Dolby Vision will benefit: both of these standards use the Rec 2020 gamut. So... bring on the 8K revolution. I want better browns.
The DNC definitely didn't help itself by putting forward such a boring, unpopular candidate and then doing seemingly everything they could to prevent Bernie from winning.
By actively preventing Bernie from getting the democratic nomination they made a Trump victory much more likely. Tons of people voted "not Hillary" with their Trump vote.
It's come out that Russia influenced this too. As soon as Bernie was out of the way, they doubled down stoking the fires to get Bernie supporters mad at Hillary. I doubt any significant amount of people who were voting on policy ended up switching, but those who were voting emotionally to begin with were probably pretty easy targets.
Agreed. Bandwidth is great but it's high enough now that it's not as important. What I'd be interested in seeing is latency and "connectedness" if that makes sense. How long does it take for me to load main page, and click a few levels deep, on the top 100 websites? What if I haven't been using my phone for an hour? How often do I open up an app and it just spins for 5 seconds while things get connected?
5-10 years ago when I heard "full stack", it meant that I could throw just about anything at you and you'd be well set to figure it out.
These days over half of the developers I interview call themselves "full stack", and upon further digging maybe 10% of them meet my prior definition. It's the new buzzword.
You can write Javascript and a stored procedure? It makes you full stack now - you don't even have to be very good at either of them. Most people draw a blank face when I ask what they've written that wasn't part of a website.
Lets just be glad there's no #metoo Leisure Suit Larry
Ray tracing is an impressive technical feat, but the argument against it for gaming still stands:
However fast you get at ray tracing, you can instead use that power for rasterization and do far far more.
The day may come where that gap doesn't matter anymore, or where we find a way to overcome it... but for now, I think this technology will primarily be used to help accelerate very simple environments, and more complex for offline rendering.
WTF is wrong with Microsoft that I can attempt to open a PDF in MS Server 2014
Their client OS supports PDF natively. I think the problem you're having is you're trying to use a server OS as a client OS.
The bottles themselves are made of PET, so it seems plausible to find that there. Why the rest of the plastics would be present are a mystery to me.
I've heard a mixed bag coming out of Netflix re: developer experience, but one thing I admire is their effort toward a reliable user experience.
From testing everything down to minutiae, to designing things so that failure is simply another regular and expected state to move forward from... most companies do not commit the time/funds to do this sort of thing.
This practical engineering is much cooler to me than Facebook/Google's latest me-too Javascript libraries that iteratively steal the next good established idea from desktop coding and call it innovation.
"We segment the videos into shots, we analyze the video per shot," said the company's director of video algorithms Anne Aaron. Now, an action scene in a show may stream at a higher bit rate than a scene featuring a slow monologue
Video encoders have supported constant quality modes for quite a while that already do this very effectively. I'm guessing they don't do this out of some need for precise control or for hardware compatibility. It's obviously not a wasted effort, but it's unfortunate that Netflix is needing to reinvent the wheel here.
We're just taking a quick 4 year vacation to recharge ourselves. Well, technically a staycation -- wouldn't want to travel and risk visiting one of those shithole countries.