What a spit in the face of whistleblowers, especially Snowden. Those who sacrifice themselfs for whom they love, will end hating who they sacrificed for.
Why no scenario from an alien invasion? Did they omit this possibility to make the center for terminator studies look more serious? Is it more likely that we will be wiped out by skynet than by ET? I have no preference whatsoever.
To post something more meaningful. I think RiscOS, missed a great opportunity here years ago. They should have moved to a Linux kernel/riscos userland approach when it could have still made a difference.
The most powerful corporations are banks. If you want to unpower them, you have to remove the right for them to create money at will. This is a political decision.
Little is known to date about a RiscOS (open) port to the Pi, but this I find fascinating. The dated OS could be a reasonable match to the limited hardware.
That's what I did, one and a half year ago, when I found myself in nearly the same position as you are now. I literally felt a burnout syndrome creeping up slowly and that was for me the sign to change. Before you say you can't do that because of your family and so on: I have a 3 year old daughter and my university is 250km away and I don't get any financial support from the public hand. When I first got the idea, I didn't believe it was possible at all, but after some time and more thinking about it, more and more possibilities turned up for realization.
Most important, don't give up easily. What first seems impossible might turn out as a lovely new experience.
Empirical Research (I followed it closely after I became a father myself) shows, that TV does hinder brain development in young children. To put it simple: The medium is the problem not the shows (for example synchronization is skewed between audio and video signals). The younger the kids and the more they watch the worse it gets. Dr. Manfred Spitzer and Dr. Gerald Huether from Germany doing the most work here. The conclusion for me was to throw out the TV! The best decision I did in a long time.;-) And my daughter? She is now 3 and a half year old. She outperforms 5-6 year olds in our environment in almost all regards (talking, reading glyphs and numbers, simple calculus, motorical skills, singing and most noticeable social skills. Is it because she didn't watch any TV so far? Judge yourself.
> don't go running after new stuff simply because it's there.
Like introducing a source code revision system in 2008!!!, as I once had to. Not aiming at you here though, just an example...
There was this senior developer who always did the "hard" stuff on 8051 based embedded applications and thus was highly respected by managers who hadn't any clue. He used to assembler optimize things on a daily basis of course without documentation to make him unfireable. I took over the lead for rewriting the firmware as a switch to a FPGA based soft CPU was due anyway. On my team were: this old guy (around 55 years or something), his fellow coworker (heavily influenced by him) and a freshmen (6 month out of college).
You can't imagine what I went through to introduce SVN and a more modular instead of the former monolithic approach to this team. Not to speak of that crazy idea to look at C++ for a possible successor to C.
At the end the youngster did 2/3 of all the code and was paid 1/2 of what the seniors each got. For me it was an interesting experience stopping them from killing each other in the weekly meetings.
Some large projects are organized and run in ways that require branching and merging. Some are organized and run in ways that don't. Generally these decisions are mandated by factors that have nothing to with any developers preference about source control or anything else, but are based on the external nature of the project at hand or management decisions or whatever.
i can't agree more. in the company i'm in we have switch the development process from a monolitic sourcetree with lots of braches (some of them proved themselfs unmergable, so they have to be maintained seperatly) to a modular aproach. this switch was only possible because we started a complete rewrite of the old code (besides switching from windows to linux at the same time) though. the old windows code is still maintained by a 10 members team, while the rewrite is done by 8 people. constantly branching and merging proved to be a big headache but was unavoidable. now we make heavy use of tags and a sophisticated modul versioning system and we didn't have to branch once 'til now.
This slotted mode does not make sense to me. The gsm receiver chip just has to stay powered and will wake up the main cpu when it receives a call. So most of the phone can be sleeping all the time without constantly waking up every now and then. exept maybe the gsm chip itself will be powered down too to save even more battery, what i find hard to believe.
windowless codepath is completly broken (unusable slow), videos are not rendered properly half the time and the sound device is not released ever (have to restart firefox). so for me it did not work at all that well - switched back to latest stable after a few days.
> I think that at one point, there was an effort to make it compile
> with the Intel compiler (which, performance-wise, it much superior to GCC),
> but I haven't heard about it since; I'm sure that it failed.
here is an interesting read from the FFdecsa documentation:
icc is currently unusable. In the initial phases of development of
FFdecsa icc was able to compile the code and gave interesting speed
results when using the 8charA grouping mode (array of 8 characters are
automatically manipulated through MMX instructions). At some point the
code began to work incorrectly because of a compiler bug (but I found a
workaround). Then, the performance dropped with no reason; I found a
workaround by adding an unused variable (alignment problem, grep for icc
in the code to see where it happens). Then, with the introduction of
group modes based on intrinsics, gcc was finally able to go beyond the
speed record originally set by icc. Additional code tweaks added more
speed to gcc, while icc started to segfault on compilation (both version
7 and 8). In conclusion, icc is bugged and this code is too hard for it.
gcc on the other hand is great. I tried to inspect generated assembler
to find weak spots, and the generated code is very good indeed.
i just tried to write down the OPs axiom in a/. compatible way. if it was me to define the underlaying logic operation i would clearly have written something like:
Re:My only suggestion for X
on
X Power Tools
·
· Score: 1
I have no doubt, that X will be there the day monitor and panel vendors fill in their EDID roms with sane data instead of shipping cdroms with their hardware.
Slashdot Mirror
What a spit in the face of whistleblowers, especially Snowden. Those who sacrifice themselfs for whom they love, will end hating who they sacrificed for.
Why no scenario from an alien invasion? Did they omit this possibility to make the center for terminator studies look more serious? Is it more likely that we will be wiped out by skynet than by ET? I have no preference whatsoever.
Connect to the fiber, and use it up for yourself.
I want RiscOs on that!
To post something more meaningful. I think RiscOS, missed a great opportunity here years ago. They should have moved to a Linux kernel/riscos userland approach when it could have still made a difference.
The most powerful corporations are banks. If you want to unpower them, you have to remove the right for them to create money at will. This is a political decision.
Little is known to date about a RiscOS (open) port to the Pi, but this I find fascinating. The dated OS could be a reasonable match to the limited hardware.
http://www.riscosopen.org/forum/forums/5/topics/783?page=12#posts-11917
C'mon, all this buzz about a 4 line post on G+ ? It's not even silly season yet.
That's what I did, one and a half year ago, when I found myself in nearly the same position as you are now. I literally felt a burnout syndrome creeping up slowly and that was for me the sign to change. Before you say you can't do that because of your family and so on: I have a 3 year old daughter and my university is 250km away and I don't get any financial support from the public hand. When I first got the idea, I didn't believe it was possible at all, but after some time and more thinking about it, more and more possibilities turned up for realization.
Most important, don't give up easily. What first seems impossible might turn out as a lovely new experience.
So what if it were a choice?
Reminds me on Reggie Watts saying something along the line: " Lately I became gay... Because being gay is a choice!".
will not work, because you can simple read with one account and mod with another. it's just too easy to circumvent.
Empirical Research (I followed it closely after I became a father myself) shows, that TV does hinder brain development in young children. To put it simple: The medium is the problem not the shows (for example synchronization is skewed between audio and video signals). The younger the kids and the more they watch the worse it gets. Dr. Manfred Spitzer and Dr. Gerald Huether from Germany doing the most work here. The conclusion for me was to throw out the TV! The best decision I did in a long time. ;-) And my daughter? She is now 3 and a half year old. She outperforms 5-6 year olds in our environment in almost all regards (talking, reading glyphs and numbers, simple calculus, motorical skills, singing and most noticeable social skills. Is it because she didn't watch any TV so far? Judge yourself.
> don't go running after new stuff simply because it's there.
Like introducing a source code revision system in 2008!!!, as I once had to. Not aiming at you here though, just an example...
There was this senior developer who always did the "hard" stuff on 8051 based embedded applications and thus was highly respected by managers who hadn't any clue. He used to assembler optimize things on a daily basis of course without documentation to make him unfireable. I took over the lead for rewriting the firmware as a switch to a FPGA based soft CPU was due anyway. On my team were: this old guy (around 55 years or something), his fellow coworker (heavily influenced by him) and a freshmen (6 month out of college).
You can't imagine what I went through to introduce SVN and a more modular instead of the former monolithic approach to this team. Not to speak of that crazy idea to look at C++ for a possible successor to C.
At the end the youngster did 2/3 of all the code and was paid 1/2 of what the seniors each got. For me it was an interesting experience stopping them from killing each other in the weekly meetings.
Some large projects are organized and run in ways that require branching and merging. Some are organized and run in ways that don't. Generally these decisions are mandated by factors that have nothing to with any developers preference about source control or anything else, but are based on the external nature of the project at hand or management decisions or whatever.
i can't agree more. in the company i'm in we have switch the development process from a monolitic sourcetree with lots of braches (some of them proved themselfs unmergable, so they have to be maintained seperatly) to a modular aproach. this switch was only possible because we started a complete rewrite of the old code (besides switching from windows to linux at the same time) though. the old windows code is still maintained by a 10 members team, while the rewrite is done by 8 people. constantly branching and merging proved to be a big headache but was unavoidable. now we make heavy use of tags and a sophisticated modul versioning system and we didn't have to branch once 'til now.
This slotted mode does not make sense to me. The gsm receiver chip just has to stay powered and will wake up the main cpu when it receives a call. So most of the phone can be sleeping all the time without constantly waking up every now and then. exept maybe the gsm chip itself will be powered down too to save even more battery, what i find hard to believe.
windowless codepath is completly broken (unusable slow), videos are not rendered properly half the time and the sound device is not released ever (have to restart firefox). so for me it did not work at all that well - switched back to latest stable after a few days.
politicans. not so sure about the "better" anymore, though.
> I think that at one point, there was an effort to make it compile
> with the Intel compiler (which, performance-wise, it much superior to GCC),
> but I haven't heard about it since; I'm sure that it failed.
here is an interesting read from the FFdecsa documentation:
icc is currently unusable. In the initial phases of development of FFdecsa icc was able to compile the code and gave interesting speed results when using the 8charA grouping mode (array of 8 characters are automatically manipulated through MMX instructions). At some point the code began to work incorrectly because of a compiler bug (but I found a workaround). Then, the performance dropped with no reason; I found a workaround by adding an unused variable (alignment problem, grep for icc in the code to see where it happens). Then, with the introduction of group modes based on intrinsics, gcc was finally able to go beyond the speed record originally set by icc. Additional code tweaks added more speed to gcc, while icc started to segfault on compilation (both version 7 and 8). In conclusion, icc is bugged and this code is too hard for it. gcc on the other hand is great. I tried to inspect generated assembler to find weak spots, and the generated code is very good indeed.
i just tried to write down the OPs axiom in a /. compatible way. if it was me to
define the underlaying logic operation i would clearly have written something like:
p w s
X X 1
I put it in a more readable form:
p w s
1 1 1
0 1 0
0 0 0
1 0 X
p=pretty, w=witty, s=sex
I have no doubt, that X will be there the day monitor and panel vendors fill in their EDID roms with sane data instead of shipping cdroms with their hardware.