a lot of what the GNOME hackers do, goes into the base for many other projects as well.
I think a lot of the hostility comes from seeing GNOME developers take an actively hostile attitude to non-GNOME projects using components like GTK+ that we used to think of as vital infrastructure everybody used.
The Mozilla Suite (codenamed "SeaMonkey") was discontinued. A new project, outside of (but not on bad terms with) the Mozilla Foundation, was started to continue development under the name "SeaMonkey" (now as a brand, not just as a codename). As far as I know, they use recent upstream versions of Gecko and thus automatically support HTML5 and so on.
This is only confusing to people who followed Mozilla development closely enough to have seen "SeaMonkey" used to refer to the Suite. I'd guess that it was somewhat inspired by the origins of the Mozilla project - "Mozilla" was the old codename for Netscape Navigator.
True, but Switzerland takes it up a level. Permanent tank traps in farmers fields, hidden military installations all over the country, bomb shelters, and a huge military reserve with regular training.
It seems to work for them, though. How many countries have had nearly 200 years of peace?
Canonical decided to write their own Mir display server instead of adopting the existing Wayland. They stated their reasons for doing so, but I'm not convinced they really had to start their own project instead of modifying Wayland.
The nice thing about Wayland is that, because all the real work is being done by things like evdev, KMS and widget toolkit the actual display server is *much* simpler than Xorg. Weston is only a reference implementation of a Wayland compositor, and it's expected that desktop environments will implement their own that work the way they want them to (for example, work is underway to let KWin function as a Wayland compositor).
So it's not even a question of having to do some hackish modification of upstream to get their own way - they could have just implemented Wayland in Unity's WM, like other major DEs have done. The concerns about running on Android drivers are weird - the Wayland protocol doesn't care how you actually do your compositing and display the finished screen (there is already a modified version of Weston for the Raspberry Pi, which uses the device's video scaling hardware to do the actual composition work), so a seperate client protocol (as opposed to rendering backend) makes no sense.
(Apologies if the linked video is edited and does not include the quote - I'm on mobile right now and haven't watched that copy. Search for Patrick Clawson to find the rest.)
But they aren't using the other compiler properly - their results effectively rely on the lie that they can do SIMD and ARM can not.
And even without the actual dishonesty, it's a synthetic benchmark selected specially to show off their compiler/processor's strong points.
Flash drives seem to be characterized by very high failure rates. Changing the drive? Unclear this is a user operation. All real drives -- the ones you use for your data -- would have to be external bricks.
Hard drives are also prone to high failure rates. If your "real data" lives only on a single magnetic disk (in a portable device, FFS) you're already asking to lose it.
And the gunsmiths of the Khyber Pass have been making real, metal firearms on a completely amateur basis since before CNC mills existed. Not single-shot proofs-of-concept either, working copies of Lee Enfields and the like. No high-tech of any sort required.
On a modern network, it is.... at least at the consumer level where nobody knows how to configure a subnet manually, but if you're managing any kind of large scale network it becomes very difficult to work with static configurations on every workstation even when you know how.
My point is that it is *incredibly* trivial to connect to a wireless router that has DHCP enabled and just use an IP address of your choosing. It's a perfectly normal thing to do if you want to be able to predictably SSH a machine or something, and even MS Windows has a GUI way of doing it. Somebody who is sniffing network traffic and cracking encryption keys can easily determine which addresses are already in use, and in practice, if you take an address at the high end of the range (e.g. 192.168.1.250), you won't run in to any trouble with other clients.
And the bots are REALLY stupid. I have more than one internet-connected machine with a key-only sshd open to the internet, and, infuriatingly, they try to brute-force it anyway. That is, even though they don't even get a chance to offer a password, they still make multiple attempts to connect...
It allows for a certain amount of changes over time, e.g. changing disk. It contacts the activation servers during activation, but after that it *never* phones home.
Slashdot Mirror
http://appleplugs.com/
Bruce Dickinson also really, really likes aviation.
a lot of what the GNOME hackers do, goes into the base for many other projects as well.
I think a lot of the hostility comes from seeing GNOME developers take an actively hostile attitude to non-GNOME projects using components like GTK+ that we used to think of as vital infrastructure everybody used.
This is beside the point, unless Valves wants to indemnify users of the code they released (hint: they won't).
Do real-time video processing server-side? Seriously?
It's not like Satoshi is controlling the system from the shadows or something - Bitcoin is open-source. You don't need to trust its creators.
The Mozilla Suite (codenamed "SeaMonkey") was discontinued. A new project, outside of (but not on bad terms with) the Mozilla Foundation, was started to continue development under the name "SeaMonkey" (now as a brand, not just as a codename). As far as I know, they use recent upstream versions of Gecko and thus automatically support HTML5 and so on.
This is only confusing to people who followed Mozilla development closely enough to have seen "SeaMonkey" used to refer to the Suite. I'd guess that it was somewhat inspired by the origins of the Mozilla project - "Mozilla" was the old codename for Netscape Navigator.
I don't think you know how one gets mod points.
True, but Switzerland takes it up a level. Permanent tank traps in farmers fields, hidden military installations all over the country, bomb shelters, and a huge military reserve with regular training.
It seems to work for them, though. How many countries have had nearly 200 years of peace?
Canonical decided to write their own Mir display server instead of adopting the existing Wayland. They stated their reasons for doing so, but I'm not convinced they really had to start their own project instead of modifying Wayland.
The nice thing about Wayland is that, because all the real work is being done by things like evdev, KMS and widget toolkit the actual display server is *much* simpler than Xorg. Weston is only a reference implementation of a Wayland compositor, and it's expected that desktop environments will implement their own that work the way they want them to (for example, work is underway to let KWin function as a Wayland compositor).
So it's not even a question of having to do some hackish modification of upstream to get their own way - they could have just implemented Wayland in Unity's WM, like other major DEs have done. The concerns about running on Android drivers are weird - the Wayland protocol doesn't care how you actually do your compositing and display the finished screen (there is already a modified version of Weston for the Raspberry Pi, which uses the device's video scaling hardware to do the actual composition work), so a seperate client protocol (as opposed to rendering backend) makes no sense.
(Apologies if the linked video is edited and does not include the quote - I'm on mobile right now and haven't watched that copy. Search for Patrick Clawson to find the rest.)
We're "truthers" if we don't think Saddam attacked the towers? Nobody outside of the United States believed that.
But they aren't using the other compiler properly - their results effectively rely on the lie that they can do SIMD and ARM can not. And even without the actual dishonesty, it's a synthetic benchmark selected specially to show off their compiler/processor's strong points.
Hard drives are also prone to high failure rates. If your "real data" lives only on a single magnetic disk (in a portable device, FFS) you're already asking to lose it.
What about retroreflectors? Presumably, it would require only a miniscule fraction of a missile-killing laser beam to screw up the tracking optics.
And the gunsmiths of the Khyber Pass have been making real, metal firearms on a completely amateur basis since before CNC mills existed. Not single-shot proofs-of-concept either, working copies of Lee Enfields and the like. No high-tech of any sort required.
Ammo was already relatively easy to make.
I feel compelled to point out that pigeons are dinosaurs.
its hobbies most likely consist of "feeding on geothermal heat" and "being adapted to an extremely stable, homogeneous environment
As a stable, homogenous environment, and a source of heat, I find this worrying.
(Yes, I know that, jokes aside, it wouldn't last an hour against a modern immune system.)
Bash 3 can pretend TCP sockets are files.
On a modern network, it is.... at least at the consumer level where nobody knows how to configure a subnet manually, but if you're managing any kind of large scale network it becomes very difficult to work with static configurations on every workstation even when you know how.
My point is that it is *incredibly* trivial to connect to a wireless router that has DHCP enabled and just use an IP address of your choosing. It's a perfectly normal thing to do if you want to be able to predictably SSH a machine or something, and even MS Windows has a GUI way of doing it. Somebody who is sniffing network traffic and cracking encryption keys can easily determine which addresses are already in use, and in practice, if you take an address at the high end of the range (e.g. 192.168.1.250), you won't run in to any trouble with other clients.
Why would he even send a DHCP request?
(Several posts here are talking as if DHCP is a vital stage in setting up a network connection.)
And the bots are REALLY stupid. I have more than one internet-connected machine with a key-only sshd open to the internet, and, infuriatingly, they try to brute-force it anyway. That is, even though they don't even get a chance to offer a password, they still make multiple attempts to connect...
A single motherboard swap can trip it.
If we're going to be working around the bullshit restrictions anyway, there's going to be a decent pirate edition almost immediately.