GPL doesn't restrict people from using the software any way they want.
Yes it does. I just downloaded a copy of Gnu Readline. I want to use it as in my new proprietary application that will make me $$$$$. Does the licence restrict me from using it in that way? Yes. That is by design and I do not criticise the developers for making that decision.
Which matters - let me know how trying to run Apple on non-apple hardware without paying for a license goes, in comparison to a GPL'd OS.
That is also by design and I do not criticise Apple for making that choice.
The idea that many eyes make all bugs shallow is a myth. Even most programmers don't bother auditing the open source code they download. I bet most of them don't really look beyond the API documentation.
Also, OpenSSL is one of the worst code bases you'll ever set eyes on. It's poorly documented and so complex, it'll make your eyes bleed.
I have a better idea: how about just keeping things how they are. People using mobile phones to take a photo of a stack trace + register dump mostly works reliably (barring wobbly hands).
^^ This.
Add a bit of OCR software and you have a system that can both be read by humans without the aid of special software and by computers to produce textual output with a bit of special software (you need a bit of special software anyway for QR codes, so you don't lose anything).
Bitcoin transactions will not be free in the long term. Once all the bit coins are mined, the people verifying the transactions will have to charge a fee unless they are using a bot net.
I keep hearing the "git is better than svn at handling conflicts" meme, but of course neither handles conflicts at all. A conflict is a file where the tool can't figure out how to merge two versions and therefore has to offload it to a human.
I've also heard on the Internet that git is better than svn at doing merges, but everybody I know who has used both git and svn in real production environments says the opposite.
In my company we use svn. I did consider moving us to git or - more likely - Mercurial (the hg user interface is more similar to svn so that would make the transition easier), but I found out that it is really easy to make a directory both an svn working copy and a git/hg repository just by using setting ignore properties so I can do local commits and still have a central svn repo.
I'm not an expert on any compiler code, but I thought that gcc was actually comparatively new, as it used to be called "egcs", and was different from what used to be "gcc", and was a newer project. At some point, the gcc team decided to simply adopt egcs as the new gcc and dump the original as it was too old and crufty.
If you call 1997 new, then yes it was new. Except that egcs was based on a gcc snapshot.
Re:3/14 is an idiotic way to write down a date.
on
Happy Pi Day
·
· Score: 1
Why is this a bad way? You're writing the month first, which doesn't change often, then your writing down the day which does change often. It makes perfect sense.
So you Americans put the year first then...... oh, wait, no you don't.
I find it surprising he was astonished since he was trying to emulate DEC Pathworks which was itself an attempt to provide DOS networking services to IBM PCs from VMS servers and was based on Lan Manager which is what SMB grew out of.
I don't understand the business model of renting hashing out to people. Either its profitable so you effectively lose money by renting it out,
Not true. It might be profitable for people elsewhere but not for you or for people who already have a data centre to put the mining rigs in, but not for you.
or its not profitable so noone in their right minds would rent it off you!
And you can't sell kit to people not in their right minds because.... ?
All 6502 opcodes are three characters long e.g. LDA (load accumulator), ASL (arithmetic shift left). So the opcodes you are thinking of are the AHL and FKU opcodes.
And good luck getting your dollars out of Mt Gox in a reasonable timeframe. The backlog on withdrawals of non trivial USD amounts is months at the moment
I worked as a contractor on an IBM project a year or two ago. I have to say that my experience backs your post up. All of the desktops were Windows based. The servers were Linux, but that was mandated by the customer.
Even worse, we were not allowed to use open source components unless they had been approved by IBM's legal department. We got into the ridiculous situation that we had to change our code coverage tool from one that was based on the GPL to one that wasn't even though the instrumented code it produced was never shipped to the customer.
murdering civilians based on shoddy intelligence, torturing people with new methods, social media puppetry, wholesale wiretapping etc is just things that have been avoided before but has been reintroduced when they could do it in new ways.
The technology is not the problem at all, its the people using it.
All of those things have always been a part of war, except the social media thing, but that is just an instance of propaganda.
Civilians have always found themselves being murdered in war. For example, in Wellington's Peninsular campaign, there were several instances of cities being taken by force and then the army doing a bit of rape pillage and murder. This was done by both sides even though the British were ostensibly trying to liberate the locals.
Then the invention of the bomber allowed civilian murder to be taken to new extremes in WW2. The British bombing campaign was particularly bad, based as it was on the premise that the smallest target that could reliably be hit by night bombers was a city.
Torture of captured opponents has always figured in warfare, if the opponent had information that you wanted.
Wiretapping or earlier means of intercepting of communications have always figured in warfare.
Slashdot Mirror
Not true.
GPL doesn't restrict people from using the software any way they want.
Yes it does. I just downloaded a copy of Gnu Readline. I want to use it as in my new proprietary application that will make me $$$$$. Does the licence restrict me from using it in that way? Yes. That is by design and I do not criticise the developers for making that decision.
Which matters - let me know how trying to run Apple on non-apple hardware without paying for a license goes, in comparison to a GPL'd OS.
That is also by design and I do not criticise Apple for making that choice.
Two reasons:
The idea that many eyes make all bugs shallow is a myth. Even most programmers don't bother auditing the open source code they download. I bet most of them don't really look beyond the API documentation.
Also, OpenSSL is one of the worst code bases you'll ever set eyes on. It's poorly documented and so complex, it'll make your eyes bleed.
I have a better idea: how about just keeping things how they are. People using mobile phones to take a photo of a stack trace + register dump mostly works reliably (barring wobbly hands).
^^ This.
Add a bit of OCR software and you have a system that can both be read by humans without the aid of special software and by computers to produce textual output with a bit of special software (you need a bit of special software anyway for QR codes, so you don't lose anything).
Bitcoin transactions will not be free in the long term. Once all the bit coins are mined, the people verifying the transactions will have to charge a fee unless they are using a bot net.
I keep hearing the "git is better than svn at handling conflicts" meme, but of course neither handles conflicts at all. A conflict is a file where the tool can't figure out how to merge two versions and therefore has to offload it to a human.
I've also heard on the Internet that git is better than svn at doing merges, but everybody I know who has used both git and svn in real production environments says the opposite.
In my company we use svn. I did consider moving us to git or - more likely - Mercurial (the hg user interface is more similar to svn so that would make the transition easier), but I found out that it is really easy to make a directory both an svn working copy and a git/hg repository just by using setting ignore properties so I can do local commits and still have a central svn repo.
I'm not an expert on any compiler code, but I thought that gcc was actually comparatively new, as it used to be called "egcs", and was different from what used to be "gcc", and was a newer project. At some point, the gcc team decided to simply adopt egcs as the new gcc and dump the original as it was too old and crufty.
If you call 1997 new, then yes it was new. Except that egcs was based on a gcc snapshot.
{ Bastard!
Why is this a bad way? You're writing the month first, which doesn't change often, then your writing down the day which does change often. It makes perfect sense.
So you Americans put the year first then... ... oh, wait, no you don't.
I find it surprising he was astonished since he was trying to emulate DEC Pathworks which was itself an attempt to provide DOS networking services to IBM PCs from VMS servers and was based on Lan Manager which is what SMB grew out of.
I don't understand the business model of renting hashing out to people. Either its profitable so you effectively lose money by renting it out,
Not true. It might be profitable for people elsewhere but not for you or for people who already have a data centre to put the mining rigs in, but not for you.
or its not profitable so noone in their right minds would rent it off you!
And you can't sell kit to people not in their right minds because.... ?
I'm Slashdot and so's my wife.
If the "new site" had been designed by competent programmers,
And you think the old one was?
Except it was. You know, given that Alan Turing kind of designed the thing.
No he didn't, it was designed by Tommy Flowers.
Colossus wasn't Turing complete either.
No. Colossus was programmable but it wasn't Turing complete.
Previews are adverts.
If the guy had been texting during the actual movie, it's pretty antisocial, but it's still not a reason to kill him.
It's more likely he would have backed down as soon as things started getting heated.
All 6502 opcodes are three characters long e.g. LDA (load accumulator), ASL (arithmetic shift left). So the opcodes you are thinking of are the AHL and FKU opcodes.
The second gen Macbook Pro is supported with Mavericks. In fact, the only Macbook Pros not supported seem to be the original 32 bit only ones.
There's no evidence that Apple has stopped providing security updates for older versions of OS X.
Lileth? The PDP-11 was a hardware Fortran machine
No it wasn't.
and C was its assembler!
No it wasn't, it's assembler was Macro 11 which doesn't look anything like Fortran or C.
And good luck getting your dollars out of Mt Gox in a reasonable timeframe. The backlog on withdrawals of non trivial USD amounts is months at the moment
And CUPS and Webkit.
I worked as a contractor on an IBM project a year or two ago. I have to say that my experience backs your post up. All of the desktops were Windows based. The servers were Linux, but that was mandated by the customer.
Even worse, we were not allowed to use open source components unless they had been approved by IBM's legal department. We got into the ridiculous situation that we had to change our code coverage tool from one that was based on the GPL to one that wasn't even though the instrumented code it produced was never shipped to the customer.
murdering civilians based on shoddy intelligence, torturing people with new methods, social media puppetry, wholesale wiretapping etc is just things that have been avoided before but has been reintroduced when they could do it in new ways.
The technology is not the problem at all, its the people using it.
All of those things have always been a part of war, except the social media thing, but that is just an instance of propaganda.
Civilians have always found themselves being murdered in war. For example, in Wellington's Peninsular campaign, there were several instances of cities being taken by force and then the army doing a bit of rape pillage and murder. This was done by both sides even though the British were ostensibly trying to liberate the locals.
Then the invention of the bomber allowed civilian murder to be taken to new extremes in WW2. The British bombing campaign was particularly bad, based as it was on the premise that the smallest target that could reliably be hit by night bombers was a city.
Torture of captured opponents has always figured in warfare, if the opponent had information that you wanted.
Wiretapping or earlier means of intercepting of communications have always figured in warfare.
The tech just alters the details.
He correctly predicted mobile phones, tablets and fibre optic cables. He got the World population about right.
And that was it. Everything else was a fail.