the concept of the bracket placement there is to emphasise indentation over bracketing. Once you "get" the view of it, it becomes a nice thing to look at, similar to python code.
I don't use it nowadays (too many coding standards that are written for the bracketing-style) but I appreciated it when I did. There's nothing wrong with the style, so I hope that you pass any code you review written in this style and focus on the important parts like readability of the code, good naming, commenting and the like rather than subjective opinions.
There is a reason developers fled C++ to Java back in the 1990s
yes, coolness. Java was "cool" and so everyone wanted to stop supporting their crappy C++ apps and wanted to do a big rewrite in the cool new system, and so wrote crappy Java apps instead.
I would hope the industry has grown up enough that they could go back to C++ and write boring, but good, apps.. but I imagine they'll just write crappy C# (or worse) apps.
If you port it to C++ and you have vulnerabilities, they will at least be *your* vulnerabilities and you can fix them.
With Java you're effectively hamstrung until Oracle pulls their finger out and fixes them.
Now, which situation would you rather be in? Noting that C++ isn't insecure by default, and isn't as difficult as its made out to be once you know what you're doing.
consumer costs are never in line with the full manufacturing costs. the additional cost of something new is because the factory lines havn't been set up yet - production capability makes things cheaper. Then there's the 'new design' aspect, if it can use less of a very expensive raw material in favour of a cheaper one, then it will get cheaper.
Of course, adding touch to a screen doesn't require that much more stuff.
but the OP has it right - I didn't mind at all when flatscreen displays were cheap enough to replace CRTs, and no-one minded when they were replaced throughout the entire portable PC range.
In this case, touch-screens will simply be a cheaper option than the standard flatscreen, so manufacturers will install them.
Now... the problem comes when silly old Julie Larson-Green (of Ribbon and Metro infamy) comes along and says "hey, changing all that old working stuff with anything new will make me look good" and puts a table interface on all PCs. Nor if Shuttleworth sees this and thinks that the mobile interface is taking over the world and so all desktops need roughly the same interface too (to be fair to Ubuntu, their desktop interface isn't designed to be touch-only unlike Metro).
Just don't blame the hardware manufacturers for software 'designers' mistakes.
I have java 7u10 plugin installed, and its now disabled (ok, good). So I check the latest version from Oracle so I can install the fixed, safe version.... which is Java 7u10.
tell you what, I'll unblock it for you... oh wait, you're not running it anymore as its disabled.. damn! I'll have to find a different vector to "assist" you with your computers.
But if your team has such little concern for teamwork and code tidying as they go, then your problems run a little deeper than leaving comments present.
then the only sensible approach is to release your own hardware too - eg a Steambox where everything is fully supported by Steam as they know exactly what is installed and have tested it out to make sure it works.
Its true, Linux is great, but too many distros with too many options is a nightmare for commercial software. Kernel ABIs would help massively, but the linux community still seems stuck in a "just recompile the source" mentality, which works great for open source stuff, but is a fail for closed-source commercial stuff.
you want to check the distance you stand from the whiteboard next time you use one, and compare it to the distance you are from your monitor when you sit at your desk. You'll find that you stand a lot closer to the board than you think, your arm doesn't reach out much at all.
but we are talking about software that is explicitly designed for touch - those large buttons, the full-screen-only interface, the swipe-from-the-side stuff that is all mouse un-friendly. Maybe Microsoft doesn't want us to use touch on desktop monitors, but then why id they foist this touch-focussed interface on us?
I have a feeling Microsoft thinks that we'll all get surface PCs or touchscreen laptops to replace the old desktop, but they just haven't thought it through to reality. Even if I have a touchscreen laptop to replace the normal laptop, I still slap it in a dock when I'm at my desk.
How does data showing the rates of use for various features winds up with the conclusion that you should less commonly used features even harder to access I will never know.
I agree - to show how useless the statistics are, consider the huge paste button, and the smaller cut and copy ones. Why is Paste so much bigger? Its because the statistics show that paste is used twice as often as copy, and twice as often as cut. Therefore its twice as important.....
I also hate that the Print button is hidden away off the ribbon, its a poorly designed interface. However, consider the bright spot in all this - Microsoft can change it, and then sell you another new version of Office! Another win for Microsoft...
the protected software was never protected in the first place - its the hardware that gets protected, so someone else cannot just make a different piece of kit that works the same way, as its patented.
They can make a different piece of hardware that works in a different way though, and then (fortunately) we can change the software so things still work with it.
I understand how a software keyboard can emulate a physical keyboard, but how about a webcam, or a graphics card, or a mobile phone. In all cases, you can patent the hardware device and let copyright laws handle copying of your software whilst still allowing someone else to still use the concept you came up with in your hardware+software combo.
The new mobile OS will presently only work on the Google Nexus Phone, (the one which was released by Samsung). Ubuntu will release an open-source code as a file and users can install it on their Nexus phone. The OS will replace Android once you install it.
in a way USB mass storage is the wrong thing - it exposes the underlying device in block mode, meaning both device and client cannot access it at the same time (they should get a cluster filesystem on these things, but I guess they never thought you could plug a USB device into 2 'ports' at once).
MTP does expose the underlying files in the filesystem of the client's choice (as I understand it), so it might have quirks, but at least its trying to be the right thing.
it'll be cheaper than Android probable, and possibly more profitable for Samsung too (they won't have to pay the Microsoft tax on each android handset)
As for HTML5, its almost certainly crap for high-performance stuff like games, but perfectly capable for the most low-perf stuff like displaying screens and buttons. But then you can say the same for dalvik - all the high-perf apps I have turn out to be written with the NDK. Mozilla's firefox OS would disagree with you though.
one thing you're missing is the difference between 20 seconds and 1 minute - when you're sat there watching it, that difference is nothing. Its meaningless as you have to sit, bored, like watching paint dry, for the system to start for you. So most people turn it on, and then do something else, like tidy their desk, go for a coffee, say hello to their colleagues. By the time they've done those tasks, the system is fully booted and has been sat waiting for the login prompt to be filled...
and then you have to wait for the system to connect to the network, start up outlook, and download all your emails.... you can get another coffee in that time.
So super-fast boot up times, unless they're of the 5 seconds or so time, is meaningless.
it quite probably will, people buy a Windows 8 tablet and then find they cannot run Windows apps on it (as they bought the ARM version, 99% of consumers won't know the difference beyond the price, battery life, and the considerable weight of the Pro version).
BBC Click did a review of Win8, and you can expect them to be as impartial as you're going to get - certainly compared to the other reviews on sites that also have "sponsored by Microsoft" articles. They weren't too complimentary whilst still being polite (its at the start of the programme, first 7 minutes).
They also did a review of Surface - they did not like it, basically. (14 minutes in, 4 minutes long, just past the nice bit with the raspberry pi and Mike Powell at 9:30). they really showed how useless the keyboard is too - see 15:20 in for the demo....
I guess the article editor doesn't support reading what he's just posted to see if he got it right!
Where do they get these guys from? Couldn't we have a random selection of/. readers on a rotating basis instead, I'm sure we couldn't do a worse job if we tried (as the peer condemnation would act as some deterrent, even if the/. "editors" don't give a fig)
Slashdot Mirror
the concept of the bracket placement there is to emphasise indentation over bracketing. Once you "get" the view of it, it becomes a nice thing to look at, similar to python code.
I don't use it nowadays (too many coding standards that are written for the bracketing-style) but I appreciated it when I did. There's nothing wrong with the style, so I hope that you pass any code you review written in this style and focus on the important parts like readability of the code, good naming, commenting and the like rather than subjective opinions.
yeah, I should think they'll be fine... for a week or two.
I was going to say "do you have a link for those", but then I realized what I was asking for :)
On the other hand, it wouldn't make a difference - I doubt Mozilla or Apple will whitelist the new version.
There is a reason developers fled C++ to Java back in the 1990s
yes, coolness. Java was "cool" and so everyone wanted to stop supporting their crappy C++ apps and wanted to do a big rewrite in the cool new system, and so wrote crappy Java apps instead.
I would hope the industry has grown up enough that they could go back to C++ and write boring, but good, apps.. but I imagine they'll just write crappy C# (or worse) apps.
If you port it to C++ and you have vulnerabilities, they will at least be *your* vulnerabilities and you can fix them.
With Java you're effectively hamstrung until Oracle pulls their finger out and fixes them.
Now, which situation would you rather be in? Noting that C++ isn't insecure by default, and isn't as difficult as its made out to be once you know what you're doing.
consumer costs are never in line with the full manufacturing costs. the additional cost of something new is because the factory lines havn't been set up yet - production capability makes things cheaper. Then there's the 'new design' aspect, if it can use less of a very expensive raw material in favour of a cheaper one, then it will get cheaper.
Of course, adding touch to a screen doesn't require that much more stuff.
now that is *the* killer app for all monitors, bring on touch-enabled screens!
but the OP has it right - I didn't mind at all when flatscreen displays were cheap enough to replace CRTs, and no-one minded when they were replaced throughout the entire portable PC range.
In this case, touch-screens will simply be a cheaper option than the standard flatscreen, so manufacturers will install them.
Now... the problem comes when silly old Julie Larson-Green (of Ribbon and Metro infamy) comes along and says "hey, changing all that old working stuff with anything new will make me look good" and puts a table interface on all PCs. Nor if Shuttleworth sees this and thinks that the mobile interface is taking over the world and so all desktops need roughly the same interface too (to be fair to Ubuntu, their desktop interface isn't designed to be touch-only unlike Metro).
Just don't blame the hardware manufacturers for software 'designers' mistakes.
I have java 7u10 plugin installed, and its now disabled (ok, good). So I check the latest version from Oracle so I can install the fixed, safe version.... which is Java 7u10.
ho hum.
tell you what, I'll unblock it for you... oh wait, you're not running it anymore as its disabled.. damn! I'll have to find a different vector to "assist" you with your computers.
deleting comments is hardly an onerous task.
But if your team has such little concern for teamwork and code tidying as they go, then your problems run a little deeper than leaving comments present.
then the only sensible approach is to release your own hardware too - eg a Steambox where everything is fully supported by Steam as they know exactly what is installed and have tested it out to make sure it works.
Its true, Linux is great, but too many distros with too many options is a nightmare for commercial software. Kernel ABIs would help massively, but the linux community still seems stuck in a "just recompile the source" mentality, which works great for open source stuff, but is a fail for closed-source commercial stuff.
you want to check the distance you stand from the whiteboard next time you use one, and compare it to the distance you are from your monitor when you sit at your desk. You'll find that you stand a lot closer to the board than you think, your arm doesn't reach out much at all.
but we are talking about software that is explicitly designed for touch - those large buttons, the full-screen-only interface, the swipe-from-the-side stuff that is all mouse un-friendly. Maybe Microsoft doesn't want us to use touch on desktop monitors, but then why id they foist this touch-focussed interface on us?
I have a feeling Microsoft thinks that we'll all get surface PCs or touchscreen laptops to replace the old desktop, but they just haven't thought it through to reality. Even if I have a touchscreen laptop to replace the normal laptop, I still slap it in a dock when I'm at my desk.
How does data showing the rates of use for various features winds up with the conclusion that you should less commonly used features even harder to access I will never know.
I agree - to show how useless the statistics are, consider the huge paste button, and the smaller cut and copy ones. Why is Paste so much bigger? Its because the statistics show that paste is used twice as often as copy, and twice as often as cut. Therefore its twice as important.....
I also hate that the Print button is hidden away off the ribbon, its a poorly designed interface. However, consider the bright spot in all this - Microsoft can change it, and then sell you another new version of Office! Another win for Microsoft...
the protected software was never protected in the first place - its the hardware that gets protected, so someone else cannot just make a different piece of kit that works the same way, as its patented.
They can make a different piece of hardware that works in a different way though, and then (fortunately) we can change the software so things still work with it.
Hardware can be emulated in software
I understand how a software keyboard can emulate a physical keyboard, but how about a webcam, or a graphics card, or a mobile phone. In all cases, you can patent the hardware device and let copyright laws handle copying of your software whilst still allowing someone else to still use the concept you came up with in your hardware+software combo.
I think this is the current plan:
The new mobile OS will presently only work on the Google Nexus Phone, (the one which was released by Samsung). Ubuntu will release an open-source code as a file and users can install it on their Nexus phone. The OS will replace Android once you install it.
in a way USB mass storage is the wrong thing - it exposes the underlying device in block mode, meaning both device and client cannot access it at the same time (they should get a cluster filesystem on these things, but I guess they never thought you could plug a USB device into 2 'ports' at once).
MTP does expose the underlying files in the filesystem of the client's choice (as I understand it), so it might have quirks, but at least its trying to be the right thing.
it'll be cheaper than Android probable, and possibly more profitable for Samsung too (they won't have to pay the Microsoft tax on each android handset)
As for HTML5, its almost certainly crap for high-performance stuff like games, but perfectly capable for the most low-perf stuff like displaying screens and buttons. But then you can say the same for dalvik - all the high-perf apps I have turn out to be written with the NDK. Mozilla's firefox OS would disagree with you though.
And these people will return them and buy a Surface, running Windows RT :)
after that review ( which was recent, not some pre-release stuff) I'd have to see and use it to believe it.
one thing you're missing is the difference between 20 seconds and 1 minute - when you're sat there watching it, that difference is nothing. Its meaningless as you have to sit, bored, like watching paint dry, for the system to start for you. So most people turn it on, and then do something else, like tidy their desk, go for a coffee, say hello to their colleagues. By the time they've done those tasks, the system is fully booted and has been sat waiting for the login prompt to be filled...
and then you have to wait for the system to connect to the network, start up outlook, and download all your emails.... you can get another coffee in that time.
So super-fast boot up times, unless they're of the 5 seconds or so time, is meaningless.
it quite probably will, people buy a Windows 8 tablet and then find they cannot run Windows apps on it (as they bought the ARM version, 99% of consumers won't know the difference beyond the price, battery life, and the considerable weight of the Pro version).
BBC Click did a review of Win8, and you can expect them to be as impartial as you're going to get - certainly compared to the other reviews on sites that also have "sponsored by Microsoft" articles. They weren't too complimentary whilst still being polite (its at the start of the programme, first 7 minutes).
They also did a review of Surface - they did not like it, basically. (14 minutes in, 4 minutes long, just past the nice bit with the raspberry pi and Mike Powell at 9:30). they really showed how useless the keyboard is too - see 15:20 in for the demo....
I guess the article editor doesn't support reading what he's just posted to see if he got it right!
Where do they get these guys from? Couldn't we have a random selection of /. readers on a rotating basis instead, I'm sure we couldn't do a worse job if we tried (as the peer condemnation would act as some deterrent, even if the /. "editors" don't give a fig)