Does Jailbreaking void your warranty? Oh? darn. I guess you're argument is just fallacious. If I HAVE to void my warranty in order to use alternative applications on my phone then the market concept is NOT OPEN no matter how much of a bow you wrap around it. Time to take the fanboy cool aid and sit it out for a round.
read the book, but ANY text that enforces a mandatory set of principles to program probably has a healthy amount of: 1.overly dogmatic approaches to solving a problem. The zealots will eat it up and constantly espouse the belief to all within ear shot, but unless institutionally mandated will probably be ignored for a variety of perfectly viable solutions. Eg. Web Session Persistence: Thou shalt never store state within a web session context and you will perform all backend processing with either cookie or DB looked up data. The idea is sound and it makes a lot of scaling problems go away, but there are times/places/situations where web session contexts on web servers are perfectly valid solutions to a given problem. I find books of similar ilk will tackle problems by shoving one solution down the reader's throat and completely eschew the exception or the philosophically diverging opinions.
2. too many pedantic problems/solutions in that everything stated is either terribly obvious to any programmer of a certain benchmark quality or so trivial that static analysis could identify the problem. There are definitely patterns that should be avoided like the plague, and the earlier a developer identifies them the better. Assuming your language of choice can be statically analysed, this is a non-issue, but I suppose -someone- needs to cook up these best of breed solutions to trivial problems, but I'd envision a web page that took in these types of problems as a collection as a better approach. A single book seems to be too dated and too ridged in its recommendations. Adding a rev to a programming language or library could vastly change what is recommended / disdained causing someone to publish a brand new book, etc...
There is a good reason to have documentation on why solution X or Y is the best of class for a given set of problems, but the zealottry and scope of said solutions always seems lacking. A good book will given concrete solutions and properly scope the solutions for targeted purposes. Of course a very narrowly focused book won't sell nearly as well, so they tend to not get made.
I'd say that #2 rules of thumb are best presented in a web focus so that they can breath and evolve as the communities that use them evolve. Having books on the subject just solidify rules of thumb that shouldn't be fixed in stone.
Woah, that's way too much pragmatism for a slashdot programming discussion. I mean I don't think there's a single piece of mud you've slung there... very disappointing...
"1024 bytes to make a kilobyte and 1024 kilobytes to make a megabyte much less why."
Well, technically we're talking kibibyte's and and mebibyte's if we're going by standards here... but your sentiments aren't far from a lot of people's reality.
It all comes down to scale. If you have millions of programmers of varying scale of 0 - 1, you're going to deal with a lot of 0.1's in your job. The closer to systems development and hopefully academic programming the closer to 1 you get.
Don't forget HTC's been in bed with MS for a very long time, so having a good business relationship with your partners can be seen, you know as a good thing.
Welcome to the way all creative expression works. You find something you like and you make it a little better. Do you think Beethoven could have existed in his time if it wasn't for the countless innovators who's creative works inspired him to write in the way he did?
If you want to go down the road of supporting UI design in the same way one pays for sheet music then fine, but frankly, if you have to worry about the knock off's substantially impacting your business, then you're probably not executing very well to begin with.
Self-answering my own question, I tried the distro in VirtualBox, so immediate impressions:
1. It crashed doing somewhat simple tasks (VM acceleration conflicts between NV driver, VBOX, Gnome3? I dunno, but it was annoying) 2. The title bars are retarded wastes of space, and I hate the monochromatic ways that title bars no longer stand out. 3. The navigation really does look geared toward tablets and not desktop computers... where is my Linux DESKTOP.... *sigh* 4. I really really hate the IOS check box style.. Was the classical check box SO inferior? I mean its things like that which really erk me. 'Lets change things for no good reason' Its somehow subjectively better for me (or the 3 of us) and we should all jump on it. 5. Everything was scaled way too large, so probably related to DPI issues (once again, may be because of Vbox). If the system would stop crashing, I may have found the menu setting to fix it.
To be completely honest, the best thing I liked about Gnome 3 was when it was in fail-safe fallback mode. At least then it looked like Gnome that I've loved over the years.
To me anyways, It looks like half the gnome team are in love with MAC/IOS based UI concepts. I just don't understand. If you love them so much, why not just use a mac? I love gnome for what it is, not for it to look exactly like -desktop environment of the month-.
I really really love the UI of the Fedora 14 GUI and of Windows 2000(much of XP), I really really hate Windows Vista/7, and I'm mostly ambivalent when it comes to the OSX philosophy. The question is, am I going to hate the new Gnome 3 look and feel, or what?
One would hope that having ebooks reduce the costs of Libraries would allow for the libraries to better serve their patrons through diversified services beyond just providing access to materials.
BSD: Pretty much super niche. Gnome is probably too bloated for their lean and mean servers anyways Solaris: Only got support because Sun dumped a pile of money to replace CDE? Maybe not but none the less, the dream of thin client computing in the form of remote desktops seems a distant dream that is thankfully dead. Linux: The duopoly of desktop environments means that Gnome needs to be very competitive here Windows: On windows, the gnome support helps port over many familiar Linux based apps to a windows world which is great for Linux people who are forced to work in a windows world, but the apps have little to zero adoption from 'Windows users' themselves, or so I've noticed OSX: I can't really say much about it. Are OSX Gnome apps considered first class citizens or are they marginalized much the same way it is in windows? Embedded: Well, as long as its embedded Linux, I guess it wouldn't be a problem
I don't think I've ever met really good programmers that have had little interest in programming. In fact, I'd almost say that one's lust for good programming is what elevates most dev's into really talented individuals. Are you working in a company with real programmers? Something violates the stink test with anonymous here.
Wouldn't any OS API exploit allow said -now deleted- program from installing a real root kit within something that apple can't just wave a magic wand to clean up? One of the hardest entry vectors for virus writers is to run binaries on hardware. Since Apple's platform is one universal hardware platform, its a lot easier to exploit a single weakness for large impact effects.
That's just retarded, really? Why is Slashdot so full of trolling anti-Sony's? Have you ever been a systems administrator? It takes time and effort to actually detect and then judge the severity of a given attack. One week does not seem like a big deal from -woops we have a big problem- to sending out a formal acknowledgement of the issue. Hell, it would take at LEAST 1 day for a Sony rep to officially write up the disclosure in legally tin foil jargon and probably another for the notice to be translated into every language that Sony officially supports.
Sure, why decline when you can accept their offer and flip them on eBay legally and make money on the deal?
For a better deal, say that they can have their required materials sold in electronic format for half the cost, but they're only tied to the registered account of the device? (Skipping for a moment the whole thought of broken hardware). At least then, the students would actually have to use the devices.
"both compilable to native code and a good target for a JIT" == fail. I always find that going against the grain and trying to force deep native/managed integration to be a big fail. Most companies will do 100% one way or the other, and anyone else left straddling the fence never end up satisfied with the implementation anyways.
Tablet/Controller is too small to play with friends (unless everyone involved had their own and they just link up together for any/all games) and too large and bulky to play on the go. What's the absent niche that they hope to fill with this?
Seriously? Python's dependence on strict and unwavering structural significance to character placement just harkens me back to COBOL which I'd inflict on nobody. The love you have for implicit statement and loop characteristics is the single reason why you'll never see python spread beyond niche crowds.
Which is a good reason that C/Python have almost no adoption outside of the OSS world. I've worked in enterprise for long enough to know that there's no way that I'd let half the developers I've worked with use C as their standard language. Does that mean that C#/Java are better languages because of it? Yes. If I can cut out the ugly overly open languages that make some much more effective but most of the others incompetent or highly ineffective, then I choose no.
When is C appropriate? We all know systems development will remain solidly C based for quite a while. If Google (or the like) could get a language like go to do 100% conversion of the Linux kernel, I think that would persuade a large number of forces to take a serious look at the language. I haven't more because I don't care about program for bits, bytes or pointers anymore. Better yet, if you could compile the Linux kernel using a statically linked language and have it optimized it to levels within deviation of the GCC's efficiency, we'd be looking at the death of C. Oh, and of course we'd need to have the compiler compile itself as a minimum =) Of course I don't see either scenario happening for quite a while, so no need to worry.
Java works fine on Dalvik, but there are performance regressions that deeply separate Dalvik from Hotspot. Sun's long and hard work over the years has produced a very well performing system that Dalvik is quite a leap from atm. The fact that they recommend avoiding virtual methods in a language with the concept deeply seeded philosophy of abstraction is disconcerting and frankly worrying. I hope that the virtual machine gets to the point where that facet and the many other performance penalizing pieces become irrelevant.
As a developer, this was a big one for me, but I can't say that I'm the OP's wife, so who knows what their requirements are. If all things being equal, go with the higher res for sure though =)
Slashdot Mirror
Thank you, you moronic fucks that give governments and corporations just cause to hunt down and destroy anonymity on the internet.
Does Jailbreaking void your warranty? Oh? darn. I guess you're argument is just fallacious. If I HAVE to void my warranty in order to use alternative applications on my phone then the market concept is NOT OPEN no matter how much of a bow you wrap around it. Time to take the fanboy cool aid and sit it out for a round.
read the book, but ANY text that enforces a mandatory set of principles to program probably has a healthy amount of:
1.overly dogmatic approaches to solving a problem. The zealots will eat it up and constantly espouse the belief to all within ear shot, but unless institutionally mandated will probably be ignored for a variety of perfectly viable solutions. Eg. Web Session Persistence: Thou shalt never store state within a web session context and you will perform all backend processing with either cookie or DB looked up data. The idea is sound and it makes a lot of scaling problems go away, but there are times/places/situations where web session contexts on web servers are perfectly valid solutions to a given problem. I find books of similar ilk will tackle problems by shoving one solution down the reader's throat and completely eschew the exception or the philosophically diverging opinions.
2. too many pedantic problems/solutions in that everything stated is either terribly obvious to any programmer of a certain benchmark quality or so trivial that static analysis could identify the problem. There are definitely patterns that should be avoided like the plague, and the earlier a developer identifies them the better. Assuming your language of choice can be statically analysed, this is a non-issue, but I suppose -someone- needs to cook up these best of breed solutions to trivial problems, but I'd envision a web page that took in these types of problems as a collection as a better approach. A single book seems to be too dated and too ridged in its recommendations. Adding a rev to a programming language or library could vastly change what is recommended / disdained causing someone to publish a brand new book, etc...
There is a good reason to have documentation on why solution X or Y is the best of class for a given set of problems, but the zealottry and scope of said solutions always seems lacking. A good book will given concrete solutions and properly scope the solutions for targeted purposes. Of course a very narrowly focused book won't sell nearly as well, so they tend to not get made.
I'd say that #2 rules of thumb are best presented in a web focus so that they can breath and evolve as the communities that use them evolve. Having books on the subject just solidify rules of thumb that shouldn't be fixed in stone.
Woah, that's way too much pragmatism for a slashdot programming discussion. I mean I don't think there's a single piece of mud you've slung there... very disappointing...
"1024 bytes to make a kilobyte and 1024 kilobytes to make a megabyte much less why."
Well, technically we're talking kibibyte's and and mebibyte's if we're going by standards here... but your sentiments aren't far from a lot of people's reality.
It all comes down to scale. If you have millions of programmers of varying scale of 0 - 1, you're going to deal with a lot of 0.1's in your job. The closer to systems development and hopefully academic programming the closer to 1 you get.
Don't forget HTC's been in bed with MS for a very long time, so having a good business relationship with your partners can be seen, you know as a good thing.
Welcome to the way all creative expression works. You find something you like and you make it a little better. Do you think Beethoven could have existed in his time if it wasn't for the countless innovators who's creative works inspired him to write in the way he did?
If you want to go down the road of supporting UI design in the same way one pays for sheet music then fine, but frankly, if you have to worry about the knock off's substantially impacting your business, then you're probably not executing very well to begin with.
Self-answering my own question, I tried the distro in VirtualBox, so immediate impressions:
1. It crashed doing somewhat simple tasks (VM acceleration conflicts between NV driver, VBOX, Gnome3? I dunno, but it was annoying)
2. The title bars are retarded wastes of space, and I hate the monochromatic ways that title bars no longer stand out.
3. The navigation really does look geared toward tablets and not desktop computers... where is my Linux DESKTOP.... *sigh*
4. I really really hate the IOS check box style.. Was the classical check box SO inferior? I mean its things like that which really erk me. 'Lets change things for no good reason' Its somehow subjectively better for me (or the 3 of us) and we should all jump on it.
5. Everything was scaled way too large, so probably related to DPI issues (once again, may be because of Vbox). If the system would stop crashing, I may have found the menu setting to fix it.
To be completely honest, the best thing I liked about Gnome 3 was when it was in fail-safe fallback mode. At least then it looked like Gnome that I've loved over the years.
To me anyways, It looks like half the gnome team are in love with MAC/IOS based UI concepts. I just don't understand. If you love them so much, why not just use a mac? I love gnome for what it is, not for it to look exactly like -desktop environment of the month-.
I really really love the UI of the Fedora 14 GUI and of Windows 2000(much of XP), I really really hate Windows Vista/7, and I'm mostly ambivalent when it comes to the OSX philosophy. The question is, am I going to hate the new Gnome 3 look and feel, or what?
One would hope that having ebooks reduce the costs of Libraries would allow for the libraries to better serve their patrons through diversified services beyond just providing access to materials.
BSD: Pretty much super niche. Gnome is probably too bloated for their lean and mean servers anyways
Solaris: Only got support because Sun dumped a pile of money to replace CDE? Maybe not but none the less, the dream of thin client computing in the form of remote desktops seems a distant dream that is thankfully dead.
Linux: The duopoly of desktop environments means that Gnome needs to be very competitive here
Windows: On windows, the gnome support helps port over many familiar Linux based apps to a windows world which is great for Linux people who are forced to work in a windows world, but the apps have little to zero adoption from 'Windows users' themselves, or so I've noticed
OSX: I can't really say much about it. Are OSX Gnome apps considered first class citizens or are they marginalized much the same way it is in windows?
Embedded: Well, as long as its embedded Linux, I guess it wouldn't be a problem
Other OS? Opinions?
I don't think I've ever met really good programmers that have had little interest in programming. In fact, I'd almost say that one's lust for good programming is what elevates most dev's into really talented individuals. Are you working in a company with real programmers? Something violates the stink test with anonymous here.
Wouldn't any OS API exploit allow said -now deleted- program from installing a real root kit within something that apple can't just wave a magic wand to clean up? One of the hardest entry vectors for virus writers is to run binaries on hardware. Since Apple's platform is one universal hardware platform, its a lot easier to exploit a single weakness for large impact effects.
That's just retarded, really? Why is Slashdot so full of trolling anti-Sony's? Have you ever been a systems administrator? It takes time and effort to actually detect and then judge the severity of a given attack. One week does not seem like a big deal from -woops we have a big problem- to sending out a formal acknowledgement of the issue. Hell, it would take at LEAST 1 day for a Sony rep to officially write up the disclosure in legally tin foil jargon and probably another for the notice to be translated into every language that Sony officially supports.
Sure, why decline when you can accept their offer and flip them on eBay legally and make money on the deal?
For a better deal, say that they can have their required materials sold in electronic format for half the cost, but they're only tied to the registered account of the device? (Skipping for a moment the whole thought of broken hardware). At least then, the students would actually have to use the devices.
"both compilable to native code and a good target for a JIT" == fail. I always find that going against the grain and trying to force deep native/managed integration to be a big fail. Most companies will do 100% one way or the other, and anyone else left straddling the fence never end up satisfied with the implementation anyways.
70% gross on sales - Opportunity cost of writing the game = ($100,000)
Does anyone here think this will make it?
Tablet/Controller is too small to play with friends (unless everyone involved had their own and they just link up together for any/all games) and too large and bulky to play on the go. What's the absent niche that they hope to fill with this?
Seriously? Python's dependence on strict and unwavering structural significance to character placement just harkens me back to COBOL which I'd inflict on nobody. The love you have for implicit statement and loop characteristics is the single reason why you'll never see python spread beyond niche crowds.
Win/IOS/Android all support core C libraries as well, so there needs to be compelling reasons to use .NET over C if portability is the top concern.
Which is a good reason that C/Python have almost no adoption outside of the OSS world. I've worked in enterprise for long enough to know that there's no way that I'd let half the developers I've worked with use C as their standard language. Does that mean that C#/Java are better languages because of it? Yes. If I can cut out the ugly overly open languages that make some much more effective but most of the others incompetent or highly ineffective, then I choose no.
When is C appropriate? We all know systems development will remain solidly C based for quite a while. If Google (or the like) could get a language like go to do 100% conversion of the Linux kernel, I think that would persuade a large number of forces to take a serious look at the language. I haven't more because I don't care about program for bits, bytes or pointers anymore. Better yet, if you could compile the Linux kernel using a statically linked language and have it optimized it to levels within deviation of the GCC's efficiency, we'd be looking at the death of C. Oh, and of course we'd need to have the compiler compile itself as a minimum =) Of course I don't see either scenario happening for quite a while, so no need to worry.
Java works fine on Dalvik, but there are performance regressions that deeply separate Dalvik from Hotspot. Sun's long and hard work over the years has produced a very well performing system that Dalvik is quite a leap from atm. The fact that they recommend avoiding virtual methods in a language with the concept deeply seeded philosophy of abstraction is disconcerting and frankly worrying. I hope that the virtual machine gets to the point where that facet and the many other performance penalizing pieces become irrelevant.
PS: Serialization is REALLLLLLLLLLLLLLLLLLY slow.
Apple has netbooks, the difference was that they're still priced at $1000+ so nobody equates them to 'cheap laptop' category devices.
As a developer, this was a big one for me, but I can't say that I'm the OP's wife, so who knows what their requirements are. If all things being equal, go with the higher res for sure though =)
*correction... Java 1.5 was 2004 so that's 7 years ago that concurrency made it into Java.. damn I'm getting old.