I recently needed a free software operating system that could replace Solaris on a couple of Sun UltraSparc machines. After testing out the relatively small number of alternatives I found that OpenBSD had by far much better hardware support than the others. I know that a lot of this is the result from the effort your group spent a couple of years ago to get docoumentation from what used to be Sun. How would you describe collaboration with Oracle now when they run the remains of Sun, in particular around supporting modern Sparc64 based systems?
I'll need to use it, since I have a decent library of XP-era software that won't work, even in compatibility mode. Turns out that compatibility mode won't actually let you ignore all the new security policies that XP didn't have.
And how long do you think that will last? Will you continue to use XP in 10, 20, 30 years from now? If not then your should really start looking for alternatives, preferably free software alternatives that don't hide their source code. That way you're more likely to not get into the same situation again.
It is more like a traditional GNU/Linux distribution. Just to take an example; if you want to install an app then nothing stops you from ssh:ing into the phone and install the rpm directly or through a frontend like yum or zypper.
The lack of appeal in doing such things just highlights some bad points that Linux developers don't get if they want to have it used more. Yum? Zypper? The names make zero sense as to the function of the service, plus they are odd/wanting to sound l33t as well. Intuitive it is not.
You can always do the same thing by clicking the install thingie in the store app. But what do I know, some people want choice.
While few people run raw AOSP a lot of people run Cyanogen, which is a popular AOSP distro.
That is true.
AOSP also allows other operating systems to have full application API level compatibility, meaning they can run Android apps, with minimal hassle or compatibility issues.
Unless your app requires Google Play Services of course.
It is more like a traditional GNU/Linux distribution. Just to take an example; if you want to install an app then nothing stops you from ssh:ing into the phone and install the rpm directly or through a frontend like yum or zypper.
No. When handled correctly a bank or other type of financial institution should _never_ mix their own funds with their customers. They are completely separate entities.
Maybe there are other ways to make prisoners less violent. I guess they are violent for a reason, and if you remove that reason then maybe they won't be violent anymore. Sometimes you just need to treat people well and they will change.
It's not just the phone itself, it's the radio that is usually running its own firmware. It can technically spy on you even if the computer part of the phone is turned off.
Debian moved all their non-free firmware out of main a couple of years ago, but because they are still present in non-free despite that is not part of Debian itself the FSF won't recommend it. They are fairly strict about their definition of free.
I believe that you're wrong there. The law doesn't specify an organization at all, only that organizations representing large a number of Swedish authors have the right to demand compensation. You could create a competitor to Copyswede if you wanted.
They don't own it but they have most likely licensed it for your region. That's unfortunately how the music business work. Content is created somewhere, then licensed to other companies around the world and they in turn handle local distribution.
I would say that's true in particular for UI builders that produce code. I find UI builders that produce non-code tend to be better. Glade for GTK+ produces XML for example, just as if you had written it yourself. You can edit it if you want to, or write the XML from scratch and open it up in Glade if you want to fix something visually.
Xcode/Gnustep has an interesting approach which is worth mentioning. The UI builder does not work like a traditional UI builder, instead you work directly with the actual objects. Back in the days the way you saved was litterally as an binary object serialization.
That wasn't a programming class, it was brainwashing by CS people. There's nothing wrong with goto itself.
It makes perfect sense to use if you have a function that does initialization, a number of processing steps and ends with cleanup. If any of the steps fail you can jump directly to the cleanup code. This is particularly useful in C where you lack exceptions. If you don't use goto's you tend to get much more heavily indented code riddled with conditionals and code duplication. When handled properly a goto can make such code much more readable.
What happened in this case was not a problem with the goto statement, but with pure programmer carelessness and failed code auditing.
That's even more alarming. This is not just "Widget A", this is the main TLS implementation in the operating system. You just don't do automatic code merges without looking at the result. Seriously.
Doesn't that assume that Apple is bound to unlock any device at all? I don't know if that's the case.
I recently needed a free software operating system that could replace Solaris on a couple of Sun UltraSparc machines. After testing out the relatively small number of alternatives I found that OpenBSD had by far much better hardware support than the others. I know that a lot of this is the result from the effort your group spent a couple of years ago to get docoumentation from what used to be Sun. How would you describe collaboration with Oracle now when they run the remains of Sun, in particular around supporting modern Sparc64 based systems?
I'll need to use it, since I have a decent library of XP-era software that won't work, even in compatibility mode. Turns out that compatibility mode won't actually let you ignore all the new security policies that XP didn't have.
And how long do you think that will last? Will you continue to use XP in 10, 20, 30 years from now? If not then your should really start looking for alternatives, preferably free software alternatives that don't hide their source code. That way you're more likely to not get into the same situation again.
GnuTLS is actually under the lesser GPL.
It is more like a traditional GNU/Linux distribution. Just to take an example; if you want to install an app then nothing stops you from ssh:ing into the phone and install the rpm directly or through a frontend like yum or zypper.
The lack of appeal in doing such things just highlights some bad points that Linux developers don't get if they want to have it used more. Yum? Zypper? The names make zero sense as to the function of the service, plus they are odd/wanting to sound l33t as well. Intuitive it is not.
You can always do the same thing by clicking the install thingie in the store app. But what do I know, some people want choice.
While few people run raw AOSP a lot of people run Cyanogen, which is a popular AOSP distro.
That is true.
AOSP also allows other operating systems to have full application API level compatibility, meaning they can run Android apps, with minimal hassle or compatibility issues.
Unless your app requires Google Play Services of course.
Maemo was pretty close to that. Pretty much Debian with a custom desktop environment. Sailfish is kind of in the same realm too.
Too bad almost no one uses AOSP, but relies on the Google Play services which are non-free. Almost like saying that OS X is open because Darwin is.
It is more like a traditional GNU/Linux distribution. Just to take an example; if you want to install an app then nothing stops you from ssh:ing into the phone and install the rpm directly or through a frontend like yum or zypper.
Patches are welcome. =)
No. When handled correctly a bank or other type of financial institution should _never_ mix their own funds with their customers. They are completely separate entities.
Maybe there are other ways to make prisoners less violent. I guess they are violent for a reason, and if you remove that reason then maybe they won't be violent anymore. Sometimes you just need to treat people well and they will change.
those who have attacked others or have shown to have colluded in harming people outside the prison system?
a lot of these people are bad people and deserve what they get and will never be normal
And somehow making them less normal is a good thing?
Which programs do you use on a daily basis?
What's your opinion about GitHub and that more and more free software development is moving there?
It's not just the phone itself, it's the radio that is usually running its own firmware. It can technically spy on you even if the computer part of the phone is turned off.
Debian moved all their non-free firmware out of main a couple of years ago, but because they are still present in non-free despite that is not part of Debian itself the FSF won't recommend it. They are fairly strict about their definition of free.
I believe that you're wrong there. The law doesn't specify an organization at all, only that organizations representing large a number of Swedish authors have the right to demand compensation. You could create a competitor to Copyswede if you wanted.
They don't own it but they have most likely licensed it for your region. That's unfortunately how the music business work. Content is created somewhere, then licensed to other companies around the world and they in turn handle local distribution.
We don't know because Apple never comments on things. It's a black box.
I would say that given how much functionality is in Emacs that's pretty much an IDE.
I would say that's true in particular for UI builders that produce code. I find UI builders that produce non-code tend to be better. Glade for GTK+ produces XML for example, just as if you had written it yourself. You can edit it if you want to, or write the XML from scratch and open it up in Glade if you want to fix something visually.
Xcode/Gnustep has an interesting approach which is worth mentioning. The UI builder does not work like a traditional UI builder, instead you work directly with the actual objects. Back in the days the way you saved was litterally as an binary object serialization.
That wasn't a programming class, it was brainwashing by CS people. There's nothing wrong with goto itself.
It makes perfect sense to use if you have a function that does initialization, a number of processing steps and ends with cleanup. If any of the steps fail you can jump directly to the cleanup code. This is particularly useful in C where you lack exceptions. If you don't use goto's you tend to get much more heavily indented code riddled with conditionals and code duplication. When handled properly a goto can make such code much more readable.
What happened in this case was not a problem with the goto statement, but with pure programmer carelessness and failed code auditing.
Yes.
That's even more alarming. This is not just "Widget A", this is the main TLS implementation in the operating system. You just don't do automatic code merges without looking at the result. Seriously.