Pretty much. With C, you usually handle resources by using goto (cleanup_step_n).. which Java does not have. With C++, of course, you have several good options, which all are more or less RAII in some form.
The problem with Java re GUIs is that Java does not have a reasonable way to handle resources. Try writing a snippet that copies a file to another, and remembers to close them both:) Then recall that in a GUI, you'll have dozens of resources to manage all the time. That makes it harder.
IF I was going to do GUI in Java, I'd look at QtJambi, even though it is no longer officially supported. But that is because I know Qt/C++, which is rather pleasant to work with, even if it sometimes takes a bit of exploring to find out how something is done.
Eclipse uses SWT, another toolkit not part of the standard lib. It sucks. I have never used AWT, but that was the predecessor to Swing...
The language itself is partly at fault, since it GUI programming means handling a lot of resources (window handles e.g.), but Java is notoriously bad at handling resources bar memory.
Ok, but to be fair at least Eclipse and netbeans feels like a beached whale. Then, most IDEs do.
Admittedly, the Java straightjacket has never been my cup of tea in any case. Nothing personally, I think every programming language I have tried just sucks for no good reason. For Java it would be: no operators except the build in ones, no static asserts/polymorphism, no proper resource management, no closures and general uglyness of a lot of constructs like "switch" and "if".
Postgresql is superior to mysql in nearly every way imaginable, so that would make sense in any case. It can also distinguish between null and the empty string;)
Depends on what you need. If you want a crossreferenced, searchable desktop environment with all your files and links in... RDBMS sounds like just the find you need.
There are plenty of solutions in this space which do not require something anywhere near as heavy as MySQL. Which is, after all, the entirely the basis for my rant. Even then, chances are extremely high, even sqlite is needlessly over the top.
Really? Could you name a system where you could say ask for all emails by a GooberToo that have an attachment which is somewhere in my filesystem? Or perhaps give me all chats with people that have sent me patches? Whether you need this is hardly the point, it is not like it is mandatory. Depending on how your distribution packages it. As for sqlite being over the top: You clearly do not know just how lightweight that is. You propose xml for this? Even plain expat has a comparable footprint to sqlite (154K vs. 553K), and then you need to add the code to write an appropriate schema, debug it, performance tune it.. it's not worth it. Do you know how firefox stores its bookmarks?
We're talking application, not desktop environment.
Interesting, given that the desktop environment runs fine without mysql or any other rdbm.
If the desktop environment is now mandating application core functionality, again we have absolutely confirmation that someone making important decisions have absolutely not idea what they are doing.
Take a breath a *think*. How would the environment even dictate something like that?
Collaboration has absolutely nothing to do with relational requisites.
I just gave you an example of just that. Unless you want every app to code specifically to integrate with every other app? That just does not scale. It should (ideally) be email and versioning system that collaborates, not (just) kmail and git.
When you desktop environment requires a RDBMS, you know something is broken.
Depends on what you need. If you want a crossreferenced, searchable desktop environment with all your files and links in... RDBMS sounds like just the find you need.
For what possible reason do they require a true RDBMS rather than something like bdb or even sqlite if you want to get crazy?
You know, I did write above that sqlite is offered as an option?
But frankly, why wouldn't you simply use xml (bottom of the list), flat files, csvs, or some such thing behind a configuration server?
Is that even simpler? It's not configuration that is stored, it is mail and stuff like that. Configuration is still in.kde/share/config in a bunch of text files + the places mandated by freedesktop.org.
Also, for what reason does one application and/or desktop need to relate to another application and/or desktop? This smells of a classic example of what happens when developers have absolutely no clue what the hell they are doing and needlessly complicate things.
Seriously, why do they need a relational anything?
I am not a developer on these things. But I can find plenty of reasons for apps to collaborate. E.g, my mail client could submit the patches I just got to my git repository. Then, when I looked at the change set, I could click a link and get the email back. But I do not want my email client needlessly complicated by having to know about git (or git to grow a nice GUI to view emails). Thus, collaboration would be nice in at least 1 case.
I'd think gold would be impractically soft. You want something stiff, so that you can form a near-perfect sphere of the stuff, and measure the diameter.
As I saw it, she went to speak to the little dragon thinking it was Scales, and the mother reacted by trying to kill Sintel. From that point on till she is flat on her back (and being sniffed by Scales) she is simply fighting for her life. Apparently, she has no idea that a baby dragon would be a full grown dragon at the time; but perhaps dragon lore is exoteric lore in her world.
Perhaps dragons produce something of value? Dragon scales? Egg shells? Such might provide the basis for a small economy.
The real question is (as always with something involving dragons) is: how can something that big fly? Perhaps it's a world with lower gravity, which also explains the big jumps she was capable off.
DHCP is unlikely to get much used in IPv6. It works otherwise...
Then how does the new-out of the box computer bought by my grandparents get it's IPv6 address? What about the fridge/toaster they keep proposing to network?
I'll fully admit that I haven't thouroughly studied the issue.
I'm not *totally* straight on this either, but I have IPv6 (tunnel) set up here. It works by the router advertising over ICMP (I think it's called) what *prefix* devices on this network should use. The devices then decide on some suitable postfix (the MAC address is a popular choice; an random one is also). The device the asks something (possibly the router) if this assembled address is a-ok. If it is, this is the address it gets. So no more setting up DHCP and manually assigning IP numbers. Any experts are more than welcome to fix any glaring error; I am not an expert on this.
Learn copy and paste.
Which I tend to do now, except for the tendency to use four fields to store the address so I can't just paste it in.
Yeah, that IS fucked up, isn't it? Whoever came up with that idea should be tickled. Severely. I'm talking goose feathers here.
DHCP is unlikely to get much used in IPv6. It works otherwise...
As for remembering or typing them... just don't. Learn copy and paste. It's not something you should have to do often anyway, unless you are a poor network administrator.
How about Pluto and Charon? That's a double system, albeit not planets but dwarf-ditto. Besides, 8 planets are not a HUGE number of cases to base a probability calculation on:)
Well, that depends on how strict you are. The chances of getting an integer when picking a random (real) number is almost never, or in fact, 0%. Yes, that is the terms I was taught, freely translated. The same is true for picking rational numbers from reals...
Slashdot Mirror
Pretty much. With C, you usually handle resources by using goto (cleanup_step_n).. which Java does not have. With C++, of course, you have several good options, which all are more or less RAII in some form.
The problem with Java re GUIs is that Java does not have a reasonable way to handle resources. Try writing a snippet that copies a file to another, and remembers to close them both :) Then recall that in a GUI, you'll have dozens of resources to manage all the time. That makes it harder.
IF I was going to do GUI in Java, I'd look at QtJambi, even though it is no longer officially supported. But that is because I know Qt/C++, which is rather pleasant to work with, even if it sometimes takes a bit of exploring to find out how something is done.
Eclipse uses SWT, another toolkit not part of the standard lib. It sucks. I have never used AWT, but that was the predecessor to Swing...
The language itself is partly at fault, since it GUI programming means handling a lot of resources (window handles e.g.), but Java is notoriously bad at handling resources bar memory.
Ok, but to be fair at least Eclipse and netbeans feels like a beached whale. Then, most IDEs do.
Admittedly, the Java straightjacket has never been my cup of tea in any case. Nothing personally, I think every programming language I have tried just sucks for no good reason. For Java it would be: no operators except the build in ones, no static asserts/polymorphism, no proper resource management, no closures and general uglyness of a lot of constructs like "switch" and "if".
Postgresql is superior to mysql in nearly every way imaginable, so that would make sense in any case. It can also distinguish between null and the empty string ;)
Hopefully, noone is using ruby because of the speed ;) If you want speed, there is C++ and friends.
Depends on what you need. If you want a crossreferenced, searchable desktop environment with all your files and links in... RDBMS sounds like just the find you need.
There are plenty of solutions in this space which do not require something anywhere near as heavy as MySQL. Which is, after all, the entirely the basis for my rant. Even then, chances are extremely high, even sqlite is needlessly over the top.
Really? Could you name a system where you could say ask for all emails by a GooberToo that have an attachment which is somewhere in my filesystem? Or perhaps give me all chats with people that have sent me patches? Whether you need this is hardly the point, it is not like it is mandatory. Depending on how your distribution packages it. As for sqlite being over the top: You clearly do not know just how lightweight that is. You propose xml for this? Even plain expat has a comparable footprint to sqlite (154K vs. 553K), and then you need to add the code to write an appropriate schema, debug it, performance tune it.. it's not worth it. Do you know how firefox stores its bookmarks?
We're talking application, not desktop environment.
Interesting, given that the desktop environment runs fine without mysql or any other rdbm.
If the desktop environment is now mandating application core functionality, again we have absolutely confirmation that someone making important decisions have absolutely not idea what they are doing.
Take a breath a *think*. How would the environment even dictate something like that?
Collaboration has absolutely nothing to do with relational requisites.
I just gave you an example of just that. Unless you want every app to code specifically to integrate with every other app? That just does not scale. It should (ideally) be email and versioning system that collaborates, not (just) kmail and git.
When you desktop environment requires a RDBMS, you know something is broken.
Depends on what you need. If you want a crossreferenced, searchable desktop environment with all your files and links in... RDBMS sounds like just the find you need.
For what possible reason do they require a true RDBMS rather than something like bdb or even sqlite if you want to get crazy?
You know, I did write above that sqlite is offered as an option?
But frankly, why wouldn't you simply use xml (bottom of the list), flat files, csvs, or some such thing behind a configuration server?
Is that even simpler? It's not configuration that is stored, it is mail and stuff like that. Configuration is still in .kde/share/config in a bunch of text files + the places mandated by freedesktop.org.
Also, for what reason does one application and/or desktop need to relate to another application and/or desktop? This smells of a classic example of what happens when developers have absolutely no clue what the hell they are doing and needlessly complicate things.
Seriously, why do they need a relational anything?
I am not a developer on these things. But I can find plenty of reasons for apps to collaborate. E.g, my mail client could submit the patches I just got to my git repository. Then, when I looked at the change set, I could click a link and get the email back. But I do not want my email client needlessly complicated by having to know about git (or git to grow a nice GUI to view emails). Thus, collaboration would be nice in at least 1 case.
It doesn't, actually. I've run it with postgresql underneath instead :) sqlite is also offered.
Only if you never need to buy a house, or insurance.
Sure you mean that each bag take 1.05 decaseconds to fill?
60 would have the same divisors except 120 itself....
Actually, cooking water is a common method to reduce the calcium content around here (we have very "hard" water).
I'd think gold would be impractically soft. You want something stiff, so that you can form a near-perfect sphere of the stuff, and measure the diameter.
As I saw it, she went to speak to the little dragon thinking it was Scales, and the mother reacted by trying to kill Sintel. From that point on till she is flat on her back (and being sniffed by Scales) she is simply fighting for her life. Apparently, she has no idea that a baby dragon would be a full grown dragon at the time; but perhaps dragon lore is exoteric lore in her world.
Perhaps dragons produce something of value? Dragon scales? Egg shells? Such might provide the basis for a small economy.
The real question is (as always with something involving dragons) is: how can something that big fly? Perhaps it's a world with lower gravity, which also explains the big jumps she was capable off.
similar to using an NAT router that doesn't have any protocol mangling stuff like we generally expect these days
Not just the unemphasized part.
DHCP is probably not going to be used by most people using IPv6.
DHCP is unlikely to get much used in IPv6. It works otherwise...
Then how does the new-out of the box computer bought by my grandparents get it's IPv6 address? What about the fridge/toaster they keep proposing to network?
I'll fully admit that I haven't thouroughly studied the issue.
I'm not *totally* straight on this either, but I have IPv6 (tunnel) set up here. It works by the router advertising over ICMP (I think it's called) what *prefix* devices on this network should use. The devices then decide on some suitable postfix (the MAC address is a popular choice; an random one is also). The device the asks something (possibly the router) if this assembled address is a-ok. If it is, this is the address it gets. So no more setting up DHCP and manually assigning IP numbers. Any experts are more than welcome to fix any glaring error; I am not an expert on this.
Learn copy and paste.
Which I tend to do now, except for the tendency to use four fields to store the address so I can't just paste it in.
Yeah, that IS fucked up, isn't it? Whoever came up with that idea should be tickled. Severely. I'm talking goose feathers here.
DHCP is unlikely to get much used in IPv6. It works otherwise...
As for remembering or typing them... just don't. Learn copy and paste. It's not something you should have to do often anyway, unless you are a poor network administrator.
There is only one planet in the solar system that supports life, so your sample size is now just 1 :P
Vi brugte "næsten aldrig" og "næsten altid". Begivenheder der "næsten aldrig" indtræffer sker aldrig.
So AmigaMMC is actually incorrect, with this definition. Almost sure(ly) is in fact 100%. So there!
How about Pluto and Charon? That's a double system, albeit not planets but dwarf-ditto. Besides, 8 planets are not a HUGE number of cases to base a probability calculation on :)
Well, that depends on how strict you are. The chances of getting an integer when picking a random (real) number is almost never, or in fact, 0%. Yes, that is the terms I was taught, freely translated. The same is true for picking rational numbers from reals...