Try to code your ass off for 8h straight every day and you'll end up tired, burned out and making a huge number of mistakes where you haven't thought things through properly.
You can do it for a while after you first start working perhaps, I know I did and I was more productive for a while, but you can't keep it up forever and frankly if you can stay interested, inspired and creative for four hours a day your doing bloody well!
I know one or two people who are the exception to this. They seem to live for their work and revolve their lives around it much more than most. They are very highly valued but they are not always promoted first or given the best opportunities. They also seem to be the types with little to do when not at work.
It can't unless you assume that the ssh client is connecting without the help of stored signatures (i.e. first time with no pre-shared secret) and the client is content to store the (fake) sig provided by the proxy. Otherwise there's just no way.
Given the number of people on the internet that have photoshop without any sort of license at all, one has to wonder if it would make much difference...
And in doing so allow other people with 0 investment to sell the software they worked on...
Which is exactly what they would be doing with the hypothetical GPL component we're imagining them to have included. It swings both ways.
(BTW, no I don't think that GPL works everywhere, for everything. It suits some business models and not others)
And can we lose the 10 year old whining about the GPL being "viral" now please. If you don't like the license you don't have to use the code.
Without the GPL a lot of stuff would never have been opened. It still would have been written but the community would be poorer (look at linksys firmware, for instance). Maybe you would have a few less plugins, but at the cost of allowing your code to be used by commercial interests without them playing ball and releasing source back to their users.
There's a huge difference between GPL tools (which we at HUGE_CORP I work for use lots of) and GPL code/components.
We use binaries only, source could potentially lead to allegations of copying. And we make sure not to use any GPL code or components in our products so that we don't need to open them.
But all-out avoid GPL? No way. We use linux as a dev platform (amongst others) and we use all sorts of FOSS tools with a huge variety of licenses in addition to some commercial stuff.
You'd be a fool to make avoiding the GPL some sort of mandate.
I know I'm an old fashioned luddite (I code with nedit, gcc and Makefiles), but does anyone use MonoDevelop?
MS does free (but not open) versions of its dev tools already, and frankly if you're using Mono you're probably an MS guy who wants his stuff to work on linux rather than a *nix dev anyway. Aren't you?
I had been wondering about that. It seemed to me that it describes a system in which you don't have control of your system and couldn't poke around in the process to find out what it was doing.
These things are going to be built in batches, not in one-off weird configs. If I'm reading it right. There may be a bit of work every time the hardware changes, sure, it's not a trivial thing, but I didn't get the impression that every one was going to be a unique snowflake.
Debian (the basis of Ubuntu and by the sounds of TFA the basis of the cherrypal distro) has most applications compiled across very many architectures. It's already in place, drivers for a lot of stuff will be in the kernel. No problem!
The occasional cover can be good, usually when it's done in jest rather than seriously, IMHO. But I can't say I particularly like any of the artists you mentioned there, no.
My tastes generally tend towards goth/industrial, so I invite you to draw your own conclusions as to how useful it is to take my preferences into account:)
I was going to comment on that too. Android is a linux kernel with a custom userspace and display layer, AFAIK (and I've poked around the internals a bit).
I tend to find that the only way music sounds very good is when the "performer" has a personal stake in it. So your songwriter is out of luck in my case.
"I'm nearly certain that a PS3 costs much more than equivalent commodity x86 hardware would."
Then you're misinformed. Cheaper than $300? I don't think so. That said I don't know why you'd use the PS3 because you can't access the 3d chip from the guest OS. The only reason I can think of to do what he's proposing is for heavy scientific/mathematical programming. Or for console gaming with the occasional need to boot into linux, I guess.
Slashdot Mirror
Are you me?
If you're missing deadlines then that's bad, sure.
But most people seem to work about half the day as far as I can tell, inside and outside of programming.
This.
Try to code your ass off for 8h straight every day and you'll end up tired, burned out and making a huge number of mistakes where you haven't thought things through properly.
You can do it for a while after you first start working perhaps, I know I did and I was more productive for a while, but you can't keep it up forever and frankly if you can stay interested, inspired and creative for four hours a day your doing bloody well!
I know one or two people who are the exception to this. They seem to live for their work and revolve their lives around it much more than most. They are very highly valued but they are not always promoted first or given the best opportunities. They also seem to be the types with little to do when not at work.
Yes, because putting in a single point of failure is a GREAT way to ensure security from malicious outside entities.
THINK before you troll, idiot.
It can't unless you assume that the ssh client is connecting without the help of stored signatures (i.e. first time with no pre-shared secret) and the client is content to store the (fake) sig provided by the proxy. Otherwise there's just no way.
That seems like a nasty single point of failure just waiting to be hacked, to me.
Given the number of people on the internet that have photoshop without any sort of license at all, one has to wonder if it would make much difference...
And in doing so allow other people with 0 investment to sell the software they worked on...
Which is exactly what they would be doing with the hypothetical GPL component we're imagining them to have included. It swings both ways.
(BTW, no I don't think that GPL works everywhere, for everything. It suits some business models and not others)
What? Where did you see me whine about their decision?
Go on, point it out. I'm waiting.
*cough* *strawman argument* *cough*
Commercial interests can do the repackaging and selling thing with GPL software. They just have to play ball by opening their stuff up too.
And can we lose the 10 year old whining about the GPL being "viral" now please. If you don't like the license you don't have to use the code.
Without the GPL a lot of stuff would never have been opened. It still would have been written but the community would be poorer (look at linksys firmware, for instance). Maybe you would have a few less plugins, but at the cost of allowing your code to be used by commercial interests without them playing ball and releasing source back to their users.
There's a huge difference between GPL tools (which we at HUGE_CORP I work for use lots of) and GPL code/components.
We use binaries only, source could potentially lead to allegations of copying. And we make sure not to use any GPL code or components in our products so that we don't need to open them.
But all-out avoid GPL? No way. We use linux as a dev platform (amongst others) and we use all sorts of FOSS tools with a huge variety of licenses in addition to some commercial stuff.
You'd be a fool to make avoiding the GPL some sort of mandate.
I know I'm an old fashioned luddite (I code with nedit, gcc and Makefiles), but does anyone use MonoDevelop?
MS does free (but not open) versions of its dev tools already, and frankly if you're using Mono you're probably an MS guy who wants his stuff to work on linux rather than a *nix dev anyway. Aren't you?
I had been wondering about that. It seemed to me that it describes a system in which you don't have control of your system and couldn't poke around in the process to find out what it was doing.
I'll stick with the broken version, thanks.
Why would you do that?
These things are going to be built in batches, not in one-off weird configs. If I'm reading it right. There may be a bit of work every time the hardware changes, sure, it's not a trivial thing, but I didn't get the impression that every one was going to be a unique snowflake.
Have you ever heard of linux?
Debian (the basis of Ubuntu and by the sounds of TFA the basis of the cherrypal distro) has most applications compiled across very many architectures. It's already in place, drivers for a lot of stuff will be in the kernel. No problem!
(well, not quite, but it does help).
They are made with instruments. This is made by fourier series. Different.
"A show that clearly demonstrated that there's vanishingly little talent in the British population."
Or perhaps that people with genuine talent don't rely on reality tv to get noticed?
You've got me there. It's beautiful.
The occasional cover can be good, usually when it's done in jest rather than seriously, IMHO. But I can't say I particularly like any of the artists you mentioned there, no.
My tastes generally tend towards goth/industrial, so I invite you to draw your own conclusions as to how useful it is to take my preferences into account :)
I was going to comment on that too. Android is a linux kernel with a custom userspace and display layer, AFAIK (and I've poked around the internals a bit).
I tend to find that the only way music sounds very good is when the "performer" has a personal stake in it. So your songwriter is out of luck in my case.
"I'm nearly certain that a PS3 costs much more than equivalent commodity x86 hardware would."
Then you're misinformed. Cheaper than $300? I don't think so. That said I don't know why you'd use the PS3 because you can't access the 3d chip from the guest OS. The only reason I can think of to do what he's proposing is for heavy scientific/mathematical programming. Or for console gaming with the occasional need to boot into linux, I guess.
1. You already subsidise everyone else through your insurance. Not least you subsidise the insurance industry
2. Those people you mentioned, they die young, it's the healthy ones you need to watch out for, they'll drag on costing you money forever
3. WTF are you talking about policies for? You don't need any policy when you have a proper universal health system.
Seems to be some folks attitude to universal healthcare too.
It's a good job that these people usually get overridden in the end.
Thanks for that, it was very informative. +1 would read again.