The networks division branched off and joined with Siemens networks division to become Nokia-Siemens. The main Nokia at that point was phones and research, though it's a bit confusing since they had gone with a grid based org chart.
Oh yea, Nokian tires, but they branched off a long time ago.
Sometimes it's hard to use those sorts. Sometimes having your own is faster for your particular case, or involves less code to get it done, etc. Ie, I have a list, but the built in sort doesn't know how to sort lists, so I write a very brain dead insertion sort when adding elements and it's not efficient but efficiency in time isn't important for it. Which is why you see bubble sort so often, because you can do it in a very small amount of code and it's perfectly fine for sorting a small array.
Sometimes even for big arrays the built in sort is not very good. Sorting a million records for instance, quicksort or heapsort won't cut it if you can't keep it all in memory at the same time because the paging will destroy all your performance. Which is why having a better sort method for big iron mainframes in the past could make you a millionaire.
It depends upon how people think about it. Some try to have each class be a real "thing" instead of being something more abstract, it's the way a lot of textbooks try to teach OOP. A file is a thing and so gets a class; a semaphore is a thing; a window is a thing that you can actually see so definitely it's a class. But a behavior, yuck, it's not a thing, so it starts to trip people up. But if you think of classes as an abstraction to tie data and behavior together, then you can look at it differently. There have been abstractions around data and behavior since before we had electronic computers, so OOP is just a way to organize it. Every abstract data type is just rudimentary OOP. Functional programming is just a different way to organize data and behavior.
Bad programmers are bad programmers no matter what language or paradigm they use.
I think some of this arises from someone doing busy work and getting the feeling that they're making progress. Ie, create lots of classes, draw lots of lines between them, and it sort of looks like a design. Now you spend the next few months implementing the skeleton of all those classes, and then every time you go home it feels like you put in a good solid day at work, your boss looks at lines of code and you seem productive so you get a nice raise. If your fingers get sore from all that typing, then you just call a few meetings to start debating the merits of class naming, which patterns are missing that should be added, how to improve the whole process, and so on.
I have found many of those tests to actually be useless. Such as testing that the implementation is doing what the developer thinks the implementation should be doing, rather than testing that the behavior is correct. And then never documenting what those tests were really supposed to be testing (maybe testing that OS version must by 1.2.3 because they all break in 1.2.4).
Or the useless tests that don't really exercise anything important. Such as add 100 items to a list and then pull them all off and make sure they come out in the correct order. I modify it to insert then in a reverse order and it breaks. Didn't matter if they increased the test size to be one million as it would always succeed but I could make it break with a size of 2... The original test was ok, except that there were no other tests to go with it that would have caught any bugs.
C doesn't have portable exceptions. And it's problematic to get this done efficiently while C is used in many environments where efficiency is necessary (no room for extra stuff on the stack, or no room for exception tables in code space, etc).
In C++ I have seen that 99% of exception handling is all for error handling only, and throws to main() to do just print an error message then exit. Even many C++ books give examples where the arguments to throw are always error messages. In general, in most languages I see very few programmers who "handle" errors or exceptions in a more sophisticated way than just print an error and pop back to the main loop.
I've seen code that avoids this, or avoids multiple returns from a function, and the result was very difficult to understand. Either lots of misc state variables, or extreme indentation, etc.
Authoring tools? I'm not on Facebook so I'm confused here. You've got text, pictures, video, text with pictures, text with video, what else do you need? It's not a platform for bloggers. Post or share something without any delusions of being a journalist, then people comment on it, end of story.
Most things start as invite only and word of mouth only when they're new. Even Facebook did that in its infancy. This wasn't about exclusivity but about a slower and maintainable rollout. I've seen new products fail when they get inundated with too many users too soon then the word goes out that it's slow and down a lot.
I like it. I'm not on Facebook but I hear it's better in every way except popularity. And popularity has never proven to correlate with quality. Given all these things dropping off, I'm worried they're going to drop G+ altogether. Which should not affect any of the haters whether it lives or dies, but I'll be stuck without an alternative.
The nice thing about ARM is that it's simple. X86 today may be RISCy, but it's a very complex RISC. And ARM covers a lot of range. Ie, Cortex-M series are very nice for small devices, a very nice interrupt model, whereas Cortex-A is more for phones or other things that care about application speed, and so forth.
Apps are pointless. You don't need to keep getting more and more newer apps. The old ones work. And Android supports 4 year old phones. People keep them that long... Maybe not Windows Phones, but. I know someone running Windows Phone and he's disappointed at the lack of support.
When did Intel learn how to make low power chips? It's time for that x86 to finally die. And while the Windows phone looks nice, I wouldn't trust MS to ever create a decent OS, as their track record so far is at zero. A unified OS is a dumb idea anyway. Different tools for different purposes. Right now there is no one out there who wants Windows or x86 except for Windows developers, and their skills are so rusty from being in a monoculture for so long that they won't be leading any technology advances.
No, it's in the cloud, duh! The place where magic happens. Lackluster apps turn into lackluster apps in the cloud, and stocks go up. Like a miracle. Or magnets.
Everyone, left, right, up, or down, was switching to electronic voting after the hanging chad embarrasment. It's not a partisan issue, and if you think only the left is stealing votes then you're blind to the people on the other side stealing them too.
Slashdot Mirror
The networks division branched off and joined with Siemens networks division to become Nokia-Siemens. The main Nokia at that point was phones and research, though it's a bit confusing since they had gone with a grid based org chart.
Oh yea, Nokian tires, but they branched off a long time ago.
He caught a cold, so I had to shoot him.
Sometimes it's hard to use those sorts. Sometimes having your own is faster for your particular case, or involves less code to get it done, etc. Ie, I have a list, but the built in sort doesn't know how to sort lists, so I write a very brain dead insertion sort when adding elements and it's not efficient but efficiency in time isn't important for it. Which is why you see bubble sort so often, because you can do it in a very small amount of code and it's perfectly fine for sorting a small array.
Sometimes even for big arrays the built in sort is not very good. Sorting a million records for instance, quicksort or heapsort won't cut it if you can't keep it all in memory at the same time because the paging will destroy all your performance. Which is why having a better sort method for big iron mainframes in the past could make you a millionaire.
You code needs more FunctorFactoryGenerators.
It depends upon how people think about it. Some try to have each class be a real "thing" instead of being something more abstract, it's the way a lot of textbooks try to teach OOP. A file is a thing and so gets a class; a semaphore is a thing; a window is a thing that you can actually see so definitely it's a class. But a behavior, yuck, it's not a thing, so it starts to trip people up. But if you think of classes as an abstraction to tie data and behavior together, then you can look at it differently. There have been abstractions around data and behavior since before we had electronic computers, so OOP is just a way to organize it. Every abstract data type is just rudimentary OOP. Functional programming is just a different way to organize data and behavior.
Bad programmers are bad programmers no matter what language or paradigm they use.
I think some of this arises from someone doing busy work and getting the feeling that they're making progress. Ie, create lots of classes, draw lots of lines between them, and it sort of looks like a design. Now you spend the next few months implementing the skeleton of all those classes, and then every time you go home it feels like you put in a good solid day at work, your boss looks at lines of code and you seem productive so you get a nice raise. If your fingers get sore from all that typing, then you just call a few meetings to start debating the merits of class naming, which patterns are missing that should be added, how to improve the whole process, and so on.
I have found many of those tests to actually be useless. Such as testing that the implementation is doing what the developer thinks the implementation should be doing, rather than testing that the behavior is correct. And then never documenting what those tests were really supposed to be testing (maybe testing that OS version must by 1.2.3 because they all break in 1.2.4).
Or the useless tests that don't really exercise anything important. Such as add 100 items to a list and then pull them all off and make sure they come out in the correct order. I modify it to insert then in a reverse order and it breaks. Didn't matter if they increased the test size to be one million as it would always succeed but I could make it break with a size of 2... The original test was ok, except that there were no other tests to go with it that would have caught any bugs.
Unused cycles are wasted cycles!
C doesn't have portable exceptions. And it's problematic to get this done efficiently while C is used in many environments where efficiency is necessary (no room for extra stuff on the stack, or no room for exception tables in code space, etc).
In C++ I have seen that 99% of exception handling is all for error handling only, and throws to main() to do just print an error message then exit. Even many C++ books give examples where the arguments to throw are always error messages. In general, in most languages I see very few programmers who "handle" errors or exceptions in a more sophisticated way than just print an error and pop back to the main loop.
I've seen code that avoids this, or avoids multiple returns from a function, and the result was very difficult to understand. Either lots of misc state variables, or extreme indentation, etc.
Maybe, but we're still waiting for a suitable replacement.
Authoring tools? I'm not on Facebook so I'm confused here. You've got text, pictures, video, text with pictures, text with video, what else do you need? It's not a platform for bloggers. Post or share something without any delusions of being a journalist, then people comment on it, end of story.
If it doesn't bother you then why are you bashing it? Is Facebook sending out an army of astroturfers?
Why do you ACs hate it so much? If you don't like it, go somewhere else. Will Wheaton was actually using it, not just a paid promotion.
Most things start as invite only and word of mouth only when they're new. Even Facebook did that in its infancy. This wasn't about exclusivity but about a slower and maintainable rollout. I've seen new products fail when they get inundated with too many users too soon then the word goes out that it's slow and down a lot.
I like it. I'm not on Facebook but I hear it's better in every way except popularity. And popularity has never proven to correlate with quality. Given all these things dropping off, I'm worried they're going to drop G+ altogether. Which should not affect any of the haters whether it lives or dies, but I'll be stuck without an alternative.
The nice thing about ARM is that it's simple. X86 today may be RISCy, but it's a very complex RISC. And ARM covers a lot of range. Ie, Cortex-M series are very nice for small devices, a very nice interrupt model, whereas Cortex-A is more for phones or other things that care about application speed, and so forth.
The power usage of a laptop is immense relative to IoT devices. We are trying to build things that last 15 years on a single non-rechargeable battery.
There really is only one gargantuan thread on Slashdot. We just subdivide into topics for accounting purposes.
Apps are pointless. You don't need to keep getting more and more newer apps. The old ones work. And Android supports 4 year old phones. People keep them that long... Maybe not Windows Phones, but. I know someone running Windows Phone and he's disappointed at the lack of support.
When did Intel learn how to make low power chips? It's time for that x86 to finally die. And while the Windows phone looks nice, I wouldn't trust MS to ever create a decent OS, as their track record so far is at zero. A unified OS is a dumb idea anyway. Different tools for different purposes. Right now there is no one out there who wants Windows or x86 except for Windows developers, and their skills are so rusty from being in a monoculture for so long that they won't be leading any technology advances.
This means a new phone too.
No, it's in the cloud, duh! The place where magic happens. Lackluster apps turn into lackluster apps in the cloud, and stocks go up. Like a miracle. Or magnets.
And if you supported Microsoft by buying Windows Phone, then Microsoft's message to you regarding your loyalty is clear.
Everyone, left, right, up, or down, was switching to electronic voting after the hanging chad embarrasment. It's not a partisan issue, and if you think only the left is stealing votes then you're blind to the people on the other side stealing them too.