Had a friend ask me this once. I honestly couldn't come up with an answer. You look at the nuts and bolts of O/S's both realtime and non realtime, and it's basically all the same stuff, with more emphasis given to lower transaction times. Is it just a buzzword? Not trying to troll, but if someone has a definitive answer I'd love to hear it.
Realtime simply means that certain operations are guaranteed to complete in a given timeframe. This is harder than it appears.
No need to get so upset. Surely not upset enough to defend Apple and only eat two lunches today! If you read my post closely, you'll notice I'm not attacking Apple. All I'm saying is that 1) it isn't factually impossible like GP stated; and 2) The fact that Apple had to stop using gcc without copylefting Xcode is considered a feature, not a bug, according to FSF holy scriptures. That's just a fact; I'm not stating whether it's right or wrong. I certainly understant Apple's point of view which you defended, but I also understand FSF's pov which needed to be reminded.
And no, I'm not going to repeat FSF's goals and Apple's stance on closed systems for the umpteenth time on slashdot. It really is left as an exercise to the reader if anyone needs it. Sorry about that.
TL;DR: Chill, dude.
LLVM/Clang has existed for a while now, and one of the primary motivations behind it was the license, particularly w/ GCC going GPLv3. Suddenly, RMS one day wakes up and realizes that it's not copyleft? That's the very idea!
Actually RMS didn't just wake up and realized that. He was indirectly replying to a flame started by the usual open source master troll, Eric S. Raymond. A pity the summary doesn't mention ESR at all and phoronix misses the real start of the discussion.
They want a compiler that's good for their platform and lets them package it into Xcode. GCC would make this impossible.
Surely not impossible. Apple could simply copyleft Xcode. Why Apple doesn't want to do that and rather prefers to fund a non-free alternative, and how this relates to FSF's goals, are left as an exercise to the reader.
I must disagree with this. The hacker did a very useful service, and not because he hacked a public network, but because he proved that members of the Parliament were not taking the necessary precautions in dealing with very sensitive information, such as emails and their own passwords. The real story is not a guy setting up a fake access point, anyone can do that; it's government data being trivially snooped because of weak security policy. I see this all the time in eduroam (an international wireless roaming service for students), which despite being WPA2-Enterprise (802.1x), most people don't bother setting up the security certificate and/or prefer connecting to hassle-free open wifi networks. It's bad enough that students do this, but utterly unacceptable for politicians.
The fact that the hacker exposed this to IT services (and it was the IT services who went public) instead of selling intelligence to foreign powers, makes him a whitehat.
There's a difference between doing it and telling the world which is attention whoring, and just letting their IT team know, and if they don't fix it, escalating it to parliamentarians themselves.
I think you have misunderstood the summary. The second link implies the whitehat didn't go public because it was the IT services who made it public.
Am sure this new model is an "Android Metoo" phone.
Far fom it! Sailfish has a very distinct feel and it actually goes back a few years, being from the same lineage of Meego and Maemo before it. Check out the main interface features in this short video. And it's a proper GNU/Linux system (as opposed to Android/Linux), if you're into that sort of thing.
More expensive than a Raspberry PI, with a slower processor.
I'm sick and tired of seeing the Raspberry Pi, which is essentially a black box run by a binary blob both fully controlled by Broadcom, being compared to proper open source and open hardware platforms, such as Arduino, OLinuXino, Beagleboard and others. Yes they are more expensive for what they do, but that is the cost of not being locked down to proprietary hardware. I'm glad 86Duino and in particular its Vortex86EX SoC is truly open.
Add in the community that has grown up around the Raspberry and I know where my money will be going.
I know where my money goes: to platforms that unreservedly foster education, both civic and technical.
Good news: it *is* out of beta!Sadly, it'll be years, if ever, before we see dart VM in browsers outside of google (I'm sure it'll come to chrome soon, now that they declared dart is production-ready.)
Regarding dynamic typing, don't forget it has static type annotations, too. I was a bit suspicious at first but now it's one of my favorite features of dart. On the one hand, the annotations give a peace of mind because everything is checked at compile-time. On the other, sometimes it's useful to be able do just declare a dynamic var to speed up prototyping, or because it's a minor thing and its type is completely irrelevant, and it just works. Best of both worlds, in my opinion.
There have been enough of these headlines inferring that other countries want to fork the internet. That has never been said anywhere. The real plan is actually in the TFA, surrounded by the author's unsubstantiated FUD:
All of these are perfectly sensible if you can wrap your head around the concept that US isn't a belevolent dictator, it's more like an abusive stepfather. Would you like it if all your data was stored in China? How about if most of your international traffic was routed through Russia? No? So maybe now you're getting a hint where Brazil's attitude is coming from. They have the power to become more self-reliant, and that doesn't mean creating a different internet, it means having more control over its own resources while being connected to the plain old internet.
TL;DR: Stop the FUD.
IPV6 does not help, because the issue is network topology: If all traffic in the US passes through a very limited set of nodes, then you can still snoop all the traffic
IPv6 makes topology less important because it enables opportunistic p2p encryption such as ipsec. The same applies for running our own services with our own CAs. The current public CA system is fundamentally flawed, and third-party services are never secure regardless of encryption or topology because they're legally snooped from within. Snowden leaks made clear that the math behind encryption is still sound; it's everything around it that has been broken.
core error - bus dumped