and IMHO that is it's unique selling point. You can run programs written 20 years ago unchanged without the programs looking like garbage.
Yeah. I interpreti it like that, and you obviously too. You would be amazed at the level of ignorance among the general population and the funny implications by badly made laws.
e.g. in Germany there is a law which says that you should not help in circumventing access restrictions. Even if the access restriction is not useful at all.
ext2/3/4 has owners of files. It's a pain in the ass. eitehr you support it correctly (whihc is impossible if you dont manage the uid database for a single organization) or you make ugly patches which try to magically detect on which drives (removable) the os is supposed to drop uid infromation.
The first approach is useless, and i see big legal issues with the second approach (if somebody indeed would rely on protecting infromation by uid)
so better just stop it completely
Moreover, that missing quotation marks in scripted languages are a problem is basic knowledge.
Yes. Usually the deal is this:
-To the outside it looks like there is a great idea in your project, which will be attributed to
-To the inside everybody knows it would not work that smoothly without your understanding.
-You know that you kept back the little vital idea for which you *really* did that system (hey, it's practical even without that idea)
Wise bosses stick to the deal that they will recommend you highly. Stupid bosses dont. I always stop irrevocably working with stupid bosses at the next suitable painless occasion. And yes, you seen the drop in the projects/groups output of stupid bosses when people leave like that (i know a project, where the 3 most competent people - me included - all left within 6 months to "better jobs").
thats my thought. Conferences up to 50 people havign a workshop are good, 200 are ok, 1000 or more are a waste of everybodies money.
I for my part digest talks in written form faster than anybody could listen, and my comprehension goes down if somebody talks.
in the self-ironic naming of open source software.
Yes, but in the times when i needed it, it was really helpful.
Side remark: my mobile storage in my andoid devices is 16Gb since quite some time (beginning of 2011), although i use sd card to expand it (mainly backup).
maybe 16Gb is enough for the real current use cases for the average iphone user?
Apple has been pretty good in identifying the users needs and limiting what they put in the phones.
Which was the case for the iphone 1, where everybody wondered about UMTS. As a matter of fact, iphones are not meant to be "general puprose computers", and they suck ehen used as such. They are perfectly balanced media players.
Better: use the Iceberg tactics for deeply embedding your ideas in other peoples projects without them noticing.
You did not understand what i meant.
If something is inside the universe we can interact with it. If we cant interact with something, then it is outside our space-time.
I dont waste my time thinking about untestable things.
So in KDEs terms that would be 1 year?
we have no idea what is outside our universe. we can only test theories inside the universe.
making testable predictions is the realm of science.
making untestable predictions is the realm of religion.
the hypothesis that there is no god/higher force outside the universe is as untestable as the hypothesis that ther is any kind of god outside the universe.
as a physicist I therefore am agnostic, buy I expect religions not to make any conclusions which affect my life by conclusions from unproven fairytales
-Possibility to access the "parent" scope
-Distinction between "workspace scope" and "global variables"
-Really weird stateful behaviour when using/declaring global variables
-Impossibility to redirect the output of commands under special circumstances
-Lazy copy in combination with slices (yeah, awfully practical, but run a profiler to see what happens)
-At least two different ways of associating data with "handle objects"
-"handle objects" (feels like the early 80s)
-weird scopes for function declarations
-absence of a decent "map" operator
-half-assed "function handles"