I've read the propaganda, but still I don't see how it departs from simple common sense
That would be the 'trusting automated testing enough to push potentially catastrophic updates straight to production' part. Not assigning blame to the dev's fixing the resulting mess might be a necessary concession to getting the job done, no one accepting responsibility for such a testing failure, not acceptable.
For many organisations giving the end user faster updates most of the time is a small benefit compared to the risks involved.
1: this infection defaults to enabled in the optional update list, it's trying to get installed 'by accident'. Trying very hard.
2: it's burning 3Gb of my deliberately small C: partition and every time I deleted the installer it just downloaded it again.
That's not looking like any sort of choice to me unless I revert the entire OS to an unsafe state without security updates. Given I don't have a clean ISO for Win8 with Bing that's going to be a challenge.
I don't understand why the GUI would even be difficult. There are a finite number of calls. All they have to do is be slavishly followed
There may be a finite number of them (vast but still finite), they're sitting in a sea of asynchronous execution while maintaining internal state. If MS don't just clone Android source, manually reproducing all the subtle interactions adds a huge level of complexity to the task.
Get that all working and you still have to replace the rendering layer or accept the graphics won't render identically, shim the hardware drivers and fake up an interface to hide lots of timing and formatting issues with the hardware.
Then remember, Microsoft has spent years telling people how much more efficiently Windows uses hardware than Android. That's suddenly not true.
Our 'planning task' took a dozen programmers 4 months staring at and experimenting with the codebase before we even knew enough to start splitting the work into tasks. Even then we had things that obviously couldn't be guesstimated with any sort of accuracy or split into small parallel workflows with any hope of measuring progress.
Some projects are just so fscked the only method that works is hitting them with the sharpest sticks you can find till they give up.
Its not useful feedback if you cherry pick only the things you want to see or worse, use it to work out how to discourage use of the things you want to kill.
Left it on for the insider programme and they still went ahead with all that shit i never used but never fixed the stuff i did use. If telemetry was being used to improve win10 they'd have bought Classic Shell and built it into the os.
More than a decade ago a bunch of economists with no obvious bias ran the math and said prey much the same thing. With one huge difference, back then the result came out firmly in favour of action because more time was left to spread the investment over. All that happened is the fossil fuel industries threw more money at denial and we posed away the chance to start early and save money.
And worst of all that investment brings worthwhile results whether there's a climate problem or not. Old news that powerful vested interests continue to want buried.
Properly calculated kWh has the voltage drop baked into the calculation, amp hours don't (and what would it even mean?). More simply though, kWh is a measure of energy stored, amp hours isn't without doing that time volts calculation. So kWh is a lot easier to compare different technologies with. We still regularly compare an online for like comparisons like phone batteries, where the voltage curves are similar.
I have 32Gb because Visual C++ on an 8 core CPU is currently gobbling 24Gb and 99% CPU to compile my project. The remaining 8Gb is caching the source or it would be much slower. Because of that caching adding an SSD made no detectable difference!
The data build just barely runs 6 parallel processes in 32Gb. Just. And still takes 4-5 hours.
More important, iOS and Android established that users are completely happy using different UIs on different types of devices, Windows or Chrome on the laptop, iOS or Android on their phone, some hideous barely usable travesty on their smartTV... and so on.
Methinks the value of the Win10 on everything is massively less than Microsoft needs.
And that's their other mistake. The people that want a FB like service are already on Facebook. Google never stopped to consider why us holdouts aren't on FB, they just assumed we were waiting for something different/better and could be grabbed before FB wore us down.
Offering even more intrusive creepy tracking was never going to convert any of us.
Meanwhile... the truth is Microsoft are fscking useless at policing Update. If I don't block the specific updates it will quite happily update my DVBT card drivers to ones that at best don't work but usually cause a kernel crash. Same with the WiFi stick I used to use to work in the garden, except that always crashes Win8.
Microsoft can't be bothered testing hardware drivers in their system, blocking it begins to sound less stupid. The correct thing would be leaning hard on MS to cleanup the update repository but no-one (governments included) has enough influence to do that. Samsung probably didn't even try.
My memory of Nvidia before I dumped them was of terrible drivers and broken and removed features. CCC is indeed a clusterfuck but Nvidia have rarely been far behind them.
I dropped Nvidia thanks to their eagerness to just drop features in new drivers (like usable PAL TV support years ago) and a really shitty attitude to fixing user reported problems, you really have to be an AAA developer before they care. Don't have this years new card and you can forget getting support.
In the comments he accidentally stumbles on the real problem, without really understanding.
Pixel art as a more expressive form, sure, it's easier than trying to bend 3D or vector art to your vision.
Pixels as a statement, no problem there. It completely misunderstands what artists were trying to achieve back in the day when all game art was pixel art and the work went into making it not look like a bunch of pixels. But I can go with a deliberate style.
The screenshot of his game just looks like they drew the graphics at too low a resolution then badly scaled them, not an explicit statement about pixels as an artform. Either go big on pixels or go HD, anything in between is a rendering error and users will see the error not the intent.
Bi-modal or not, the less skilled you are as a programmer the more frustrating some parts of programming become. For the more skilled it's fighting boredom on easy work, but they stay productive and looking skilled.
That could be pushing average programmers to find something more rewarding to do, rather than facing frustration regularly. Some of the merely above average ones are mostly above average in being more prepared to fight through that frustration - I'm one of them, the rest probably just quit.
Most websites work better on my (secondary) 1920x1080 desktop than they do on my 1080x1920 mobile. They always work better than my 1920x1080 mobile with half the screen covered by a touch keyboard.
And I swear my fingers are 100x less precise hitting the mobile touchscreen than my mouse on the desktop.
mobile friendly != mobile sites. Till they borked it Dolphin on Android was good at reflowing pages to readable font sizes without horizontal scrolling, if this encourages 'desktop' sites to format themselves better and/or adaptively I'm for it.
The article quotes "all artists are fairly compensated".
Why would the publishers and music companies ever support something like that? Their business is based on making sure artists collect as little as possible of their royalties, assisted by collecting organisations siphoning off their share.
Something smells fishy, unless this is actually a strike against middlemen like the BMI? Probably with the end goal of handing collection over to the music biz further guaranteeing artists don't in fact get "fairly compensated".
I'll be watching the politicians that spend so much time trying to shut down the BBC's funding scramble to explain why sacking a bigoted thug who went too far was wrong, without looking like a bumbling bunch of Clarksons.
They'll fail of course because they are a bumbling bunch of Clarksons.
The direct disc write should also manages to overlap write to the stream object with flushes from it to the underlying drive. Except of course it doesn't because they aren't writing enough data for the disc write to actually start before they're done. I'm also a little confused about why they think flush+close is synchronous, it's going to return instantly and flush data in the background. So they aren't even timing what they think they are.
Back in the world of programmers with a clue, I did fix an in-memory piece of insanity like this not long ago. Making buffer expansion allocations more aggressive got a 10,000x speed improvement.
Dumb concatenation is for lazy or dumb programmers. Programmers that lazy probably could benefit from using more efficient append ops in the streaming libs, even if they don't understand why it works.
No, she's saying she doesn't use pubs or understand drinking. Mostly UK parents don't expect to see their children drinking under age in the same pub they're in. They're meant to find their own pubs and be discreet about it!
Anyway, most UK pubs have child licences even if some choose not to allow children in even with their parents. This woman is clearly clueless.
When I upgrade to 4K it will be to show more content on the screen, not showing the same stuff with more pixels. Scaling is irrelevant.
My current setup is a QVGA 27" primary flanked by 2x 23" 1920x1080 monitors. The pixel densities are close enough that dragging windows between displays doesn't jar badly and it feels acceptably close to a single wide surface (albeit not rectangular). Again scaling is not just irrelevant, it would be bad.
Even my phones offer differing size icon grids for each screen size.
In any sane implementation any scalable elements would be rendered scaled then cached, no need at all to make the initial render efficient. Scaling is a BS excuse for this crap.
These are just piss poor graphics. If they insist on rendering them with vectors then they need to spend more time getting them right, instead of blaming
The key thing is older styles properly emphasise the boundaries between UI elements and the active surfaces of control areas. Something vanilla Modern look if fscking awful at and consequently harder to use.
I predict that about 1hour after installing Win10 (a job requirement sadly), mine will have classic WinXP theming like my 8.1 build does. And if MS try to block the UxStyle theming hack, I'm pretty confident whatever pitiful hack they used to kill it will be broken within hours.
In reality the majority of owners of todays cheap cameras aren't using them to entertain you or anyone else. We are actually just snapshotting our own memories and the raw unedited result will be good enough for it's job - triggering our memory. The mainstream you think need targeting don't care, aren't sharing tedious slide shows or very much of what they take.
Good editing solutions solve a problem almost none of us has. 3D in casual photography similarly offers something few care about. To succeed it needs to have zero cost over just taking a crappy 2D snapshot.
Slashdot Mirror
I've read the propaganda, but still I don't see how it departs from simple common sense
That would be the 'trusting automated testing enough to push potentially catastrophic updates straight to production' part. Not assigning blame to the dev's fixing the resulting mess might be a necessary concession to getting the job done, no one accepting responsibility for such a testing failure, not acceptable.
For many organisations giving the end user faster updates most of the time is a small benefit compared to the risks involved.
...which will include the GWX, Win Update and telemetry I want rid of.
1: this infection defaults to enabled in the optional update list, it's trying to get installed 'by accident'. Trying very hard.
2: it's burning 3Gb of my deliberately small C: partition and every time I deleted the installer it just downloaded it again.
That's not looking like any sort of choice to me unless I revert the entire OS to an unsafe state without security updates. Given I don't have a clean ISO for Win8 with Bing that's going to be a challenge.
They truly are scum.
I don't understand why the GUI would even be difficult. There are a finite number of calls. All they have to do is be slavishly followed
There may be a finite number of them (vast but still finite), they're sitting in a sea of asynchronous execution while maintaining internal state. If MS don't just clone Android source, manually reproducing all the subtle interactions adds a huge level of complexity to the task.
Get that all working and you still have to replace the rendering layer or accept the graphics won't render identically, shim the hardware drivers and fake up an interface to hide lots of timing and formatting issues with the hardware.
Then remember, Microsoft has spent years telling people how much more efficiently Windows uses hardware than Android. That's suddenly not true.
It's not easy.
Our 'planning task' took a dozen programmers 4 months staring at and experimenting with the codebase before we even knew enough to start splitting the work into tasks. Even then we had things that obviously couldn't be guesstimated with any sort of accuracy or split into small parallel workflows with any hope of measuring progress.
Some projects are just so fscked the only method that works is hitting them with the sharpest sticks you can find till they give up.
Its not useful feedback if you cherry pick only the things you want to see or worse, use it to work out how to discourage use of the things you want to kill.
Left it on for the insider programme and they still went ahead with all that shit i never used but never fixed the stuff i did use. If telemetry was being used to improve win10 they'd have bought Classic Shell and built it into the os.
Except my copy was not free, I sacrificed years of prepaid Win8.x support to install this steaming POS.
(No, I don't have any choice in running it, damn job)
More than a decade ago a bunch of economists with no obvious bias ran the math and said prey much the same thing. With one huge difference, back then the result came out firmly in favour of action because more time was left to spread the investment over. All that happened is the fossil fuel industries threw more money at denial and we posed away the chance to start early and save money.
And worst of all that investment brings worthwhile results whether there's a climate problem or not. Old news that powerful vested interests continue to want buried.
Properly calculated kWh has the voltage drop baked into the calculation, amp hours don't (and what would it even mean?). More simply though, kWh is a measure of energy stored, amp hours isn't without doing that time volts calculation. So kWh is a lot easier to compare different technologies with. We still regularly compare an online for like comparisons like phone batteries, where the voltage curves are similar.
I have 32Gb because Visual C++ on an 8 core CPU is currently gobbling 24Gb and 99% CPU to compile my project. The remaining 8Gb is caching the source or it would be much slower. Because of that caching adding an SSD made no detectable difference!
The data build just barely runs 6 parallel processes in 32Gb. Just. And still takes 4-5 hours.
For normal tasks though it's complete overkill ;)
More important, iOS and Android established that users are completely happy using different UIs on different types of devices, Windows or Chrome on the laptop, iOS or Android on their phone, some hideous barely usable travesty on their smartTV... and so on.
Methinks the value of the Win10 on everything is massively less than Microsoft needs.
And that's their other mistake. The people that want a FB like service are already on Facebook. Google never stopped to consider why us holdouts aren't on FB, they just assumed we were waiting for something different/better and could be grabbed before FB wore us down.
Offering even more intrusive creepy tracking was never going to convert any of us.
Meanwhile... the truth is Microsoft are fscking useless at policing Update. If I don't block the specific updates it will quite happily update my DVBT card drivers to ones that at best don't work but usually cause a kernel crash. Same with the WiFi stick I used to use to work in the garden, except that always crashes Win8.
Microsoft can't be bothered testing hardware drivers in their system, blocking it begins to sound less stupid. The correct thing would be leaning hard on MS to cleanup the update repository but no-one (governments included) has enough influence to do that. Samsung probably didn't even try.
My memory of Nvidia before I dumped them was of terrible drivers and broken and removed features. CCC is indeed a clusterfuck but Nvidia have rarely been far behind them.
I dropped Nvidia thanks to their eagerness to just drop features in new drivers (like usable PAL TV support years ago) and a really shitty attitude to fixing user reported problems, you really have to be an AAA developer before they care. Don't have this years new card and you can forget getting support.
In the comments he accidentally stumbles on the real problem, without really understanding.
Pixel art as a more expressive form, sure, it's easier than trying to bend 3D or vector art to your vision.
Pixels as a statement, no problem there. It completely misunderstands what artists were trying to achieve back in the day when all game art was pixel art and the work went into making it not look like a bunch of pixels. But I can go with a deliberate style.
The screenshot of his game just looks like they drew the graphics at too low a resolution then badly scaled them, not an explicit statement about pixels as an artform. Either go big on pixels or go HD, anything in between is a rendering error and users will see the error not the intent.
Bi-modal or not, the less skilled you are as a programmer the more frustrating some parts of programming become. For the more skilled it's fighting boredom on easy work, but they stay productive and looking skilled.
That could be pushing average programmers to find something more rewarding to do, rather than facing frustration regularly. Some of the merely above average ones are mostly above average in being more prepared to fight through that frustration - I'm one of them, the rest probably just quit.
Most websites work better on my (secondary) 1920x1080 desktop than they do on my 1080x1920 mobile. They always work better than my 1920x1080 mobile with half the screen covered by a touch keyboard.
And I swear my fingers are 100x less precise hitting the mobile touchscreen than my mouse on the desktop.
mobile friendly != mobile sites. Till they borked it Dolphin on Android was good at reflowing pages to readable font sizes without horizontal scrolling, if this encourages 'desktop' sites to format themselves better and/or adaptively I'm for it.
The article quotes "all artists are fairly compensated".
Why would the publishers and music companies ever support something like that? Their business is based on making sure artists collect as little as possible of their royalties, assisted by collecting organisations siphoning off their share.
Something smells fishy, unless this is actually a strike against middlemen like the BMI? Probably with the end goal of handing collection over to the music biz further guaranteeing artists don't in fact get "fairly compensated".
I'll be watching the politicians that spend so much time trying to shut down the BBC's funding scramble to explain why sacking a bigoted thug who went too far was wrong, without looking like a bumbling bunch of Clarksons.
They'll fail of course because they are a bumbling bunch of Clarksons.
The direct disc write should also manages to overlap write to the stream object with flushes from it to the underlying drive. Except of course it doesn't because they aren't writing enough data for the disc write to actually start before they're done. I'm also a little confused about why they think flush+close is synchronous, it's going to return instantly and flush data in the background. So they aren't even timing what they think they are.
Back in the world of programmers with a clue, I did fix an in-memory piece of insanity like this not long ago. Making buffer expansion allocations more aggressive got a 10,000x speed improvement.
Dumb concatenation is for lazy or dumb programmers. Programmers that lazy probably could benefit from using more efficient append ops in the streaming libs, even if they don't understand why it works.
No, she's saying she doesn't use pubs or understand drinking. Mostly UK parents don't expect to see their children drinking under age in the same pub they're in. They're meant to find their own pubs and be discreet about it!
Anyway, most UK pubs have child licences even if some choose not to allow children in even with their parents. This woman is clearly clueless.
When I upgrade to 4K it will be to show more content on the screen, not showing the same stuff with more pixels. Scaling is irrelevant.
My current setup is a QVGA 27" primary flanked by 2x 23" 1920x1080 monitors. The pixel densities are close enough that dragging windows between displays doesn't jar badly and it feels acceptably close to a single wide surface (albeit not rectangular). Again scaling is not just irrelevant, it would be bad.
Even my phones offer differing size icon grids for each screen size.
In any sane implementation any scalable elements would be rendered scaled then cached, no need at all to make the initial render efficient. Scaling is a BS excuse for this crap.
These are just piss poor graphics. If they insist on rendering them with vectors then they need to spend more time getting them right, instead of blaming
UxStyle can do other styles if you don't like XP.
The key thing is older styles properly emphasise the boundaries between UI elements and the active surfaces of control areas. Something vanilla Modern look if fscking awful at and consequently harder to use.
I predict that about 1hour after installing Win10 (a job requirement sadly), mine will have classic WinXP theming like my 8.1 build does. And if MS try to block the UxStyle theming hack, I'm pretty confident whatever pitiful hack they used to kill it will be broken within hours.
UxStyle already supports Win10 technical preview :)
In reality the majority of owners of todays cheap cameras aren't using them to entertain you or anyone else. We are actually just snapshotting our own memories and the raw unedited result will be good enough for it's job - triggering our memory. The mainstream you think need targeting don't care, aren't sharing tedious slide shows or very much of what they take.
Good editing solutions solve a problem almost none of us has. 3D in casual photography similarly offers something few care about. To succeed it needs to have zero cost over just taking a crappy 2D snapshot.