While I do agree that the post was essentially decently-disguised flamebait, there's one point he really does make: "Whether you love, hate, or are ambivalent about systemd, I think you have to accept it at this point."
I see nobody working on an alternative init system. openlaunchd is both dead and limited to FreeBSD, upstart is likely to die with the march of systemd (Which, as you'll need to understand, is not an init system anymore, but literally a system daemon. It owns, controls and plays with your machine at its own volition and there's nothing you can do to stop it.), OpenRC isn't taken seriously because the gentoo folks propose it and now that both Debian and Red Hat, the two major players on the market, have both decided to play along with the systemd game (one of them was more or less forced into it, but no matter), systemd is omnipresent and impossible to stop.
We would've needed to have a concrete, working answer that made systemd pale in performance, code quality AND documentation back in 2012. If Apple had released launchd as open source back when Ubuntu started writing upstart, things might have ended differently. If upstart wasn't pushed too early, things might have ended differently. However, at this point of time, the UNIX way on Linux is dead. Irrecoverably. I wish I didn't have to paint such a black picture, but it's too tightly-coupled with the rest of the Linux ecosystem to ever remove it again.
Another argument frequently used is portability; you just port the browser and all the web apps run, at least somewhat. Your examples, however, aren't all that convincing in that direction. While C# works somewhat with Mono on Linux and OS X (though the (Free)BSD port isn't actually officially part of Mono) when using WinForms, WPF is not supported and Mono has no plans to support it. C++ with Qt and/or Boost is reasonable, though there are some pitfalls here and there to watch out for. As for Delphi, I'm not sure how mature Kylix is and if it runs on the BSDs.
Generally, if you say portability is more than just x86 with Windows/OS X/Linux, you'll hit a brick wall really fast, and browsers are surprisingly frequently ported.
It's only straightforward if it's documented somewhere in a sane, complete and concise manner. Is it in a manpage? If not, is it installed by default at least?
Well, women are frequently deeply confused. The difference between "shut up and make me a sandwich" and "talk at me for hours upon hours despite your judgment hopefully telling you that I couldn't care less" has stumped women for centuries with no hope of improvement in sight.
"Anope can be interacted with via RPC"... Yes, Anope 1.9. That's the development release, though. As much as I'd like to share your idealized view of IRC becoming a better place (except for the fact that I definitely wouldn't want to create an IRCd from scratch these days -- linking protocol and especially these goddamn CAP negotiations are just as bad as doing SSL from scratch. Who had the idea of message intents anyway?), fact is that the majority of networks that use Anope (and there are, due to the fact that quite a number of admins believe that levels are easier/better in some way or that Atheme is too much work to set up) use the stable 1.8 version.
Unlike the 1.7 dev version, 1.9 has not been widely adopted. This is mainly due to the fact that Anope 1.8 does just nearly enough out of the box to be still considered modern services, it's more hackable due to being coded in C (writing a module in 1.8 is definitely easier than in the C++ using 1.9 version. It's also easier to make it a complete fucking hackjob in 1.8) and has a bigger modding community (see http://modules.anope.org/ for pretty simple proof of that).
Additionally, it's still a mystery to me how IRCv3 works as an organization. It's described as a "meritocracy", but who is calling the shots in the end? You, nenolod? If so, then I'm not sure if the description shouldn't be rather "oligocracy" but that's pretty bad for the image of anything these days.
Furthermore, I would like to point out that, while four major IRCds are part of IRCv3/implement it, a big part of the implementations (especially so in UnrealIRCd) have actually come from people in the working group (namely you). While that in and of itself can hardly be considered a bad thing, it does lower the bus factor for future changes to the protocol to... precisely 1.
I do, however, agree with your belief that IRC needs a change, but I believe this is heading in the wrong direction. This is just cleaning the protocol up a bit. What we actually need are radical changes, which you'd need to discard all the old diehard IRC brigade for. Analyze what is currently popular: Xat, Facebook, IMs. Observe how two of those are web-based. Does IRC have a web-based client? Yes, it does. Mibbit, qwebirc and KiwiIRC (as well as IRCCloud, but they are absolutely uncooperative with any network). Mibbit sucks downright and is missing the oh-so-important colors to today's generation for the most part. qwebirc is tied to a network each. While that might simplify the handing on the user's part (one website for one network), it still sucks as a client (same color issue as Mibbit, even) and the entire concept of a network just rapes the minds of users. Users today don't know and they do not WANT to know that there are multiple IRC networks. They just want a chat room. Centralization is key. You can't talk of "a Xat chat" or "the Facebook chat" or "ICQ" or "MSN (Messenger)" in the same way you talk about IRC because the decentralized nature is included in none of them (though, if Jabber had found broader adoption amongst non-techies, which will not happen because of this precise very same argument, that would be a basis to work off). KiwiIRC looks promising, but no network has webirc blocks for them yet. Facebook wins because everybody else is already there, not because their chat technology (or anything else for that matter) is particularly innovative or good. Speaking of centralization, having multiple clients and networks is just even more confusion for new users. There is no "the IRC client" and there is no "the IRC network". That is not what users want. Janus links are a step in the right direction (as ugly as they may be), but not a solution.
On the topic of webirc blocks, banning people on IRC is an ordeal. It is a brutal pain in the neck. Other systems may require and enforce registration, so banning is very easy: Right click -> Ban. Or at least they abstract the banning itself away in some manner. You can't do that on IRC. You'll first spend
Is anything major using Python 3 already? Most distributions still use Python 2 as their default Python interpreter, the big libs (twisted and Django come to mind) aren't ported yet. Is there any reason to use it?
In a press conference this morning, 600 KB/s stated that "after months of being abused and hit, it's finally time to stop. We won't cooperate anymore until the ISPs stop hitting us." Soon afterwards, higher speeds also agreed with 600 KB/s and followed his example.
No company does anything out of the goodness of their own hearts. They're in business to make a profit, and you, the consumer, have shown them what you're willing to pay.
I'll admit, I've never ever read the entire GPL (or one of its variations), simply because they're so incredibly massive that I just know there's some paragraphs just to screw people over. I refuse to use any license I cannot understand within two minutes, including reading time. Everything else is just plain ridiculous and will never be done by any kind of end-user anyway.
Because of that, I try to avoid using any GPL code, no matter what variation it might be, as much as possible in my code. Just the sound of GPL makes me run in circles, then crying myself to sleep in a lonely corner.
"The release also brings the latest KDE and XFCE versions, improved Btrfs support, amd a switch from OpenOffice.org to LibreOffice." I'm pretty sure it should read "and a switch."
This could actually really prove to be useful, since that could open the possibility of a "counter-trojan" infecting all vulnerable computers and getting rid of other Zeus installations, while then proceeding to purge itself.
There's quite an amount of people who do get moderator points but don't have the time to actually use them, not to mention it's usually such a small amount that proven good moderators can only take minuscle action while karma whores can mess things up big time, meta-moderation only has a limited amount of influence, too.
1984 and Animal Farm would most likely not become mandatory, simply because they might teach people to be wary of what's going on so that the government can't screw them up bit by bit. That's not what a good, fair, nice government wants, since that would mean people wouldn't be able to be controlled 24/7, just think of the children!
Firefox is the only "mainstream" one. If we define mainstream as what most people use, there's barely Firefox. Normal people who don't code and don't administrate a server use neither BIND nor Apache nor PHP nor Peopl.
Slashdot Mirror
The Internet of Things just found my lost wallet. So did the NSA, which is why it's empty now.
Weird shit.
While I do agree that the post was essentially decently-disguised flamebait, there's one point he really does make: "Whether you love, hate, or are ambivalent about systemd, I think you have to accept it at this point."
I see nobody working on an alternative init system. openlaunchd is both dead and limited to FreeBSD, upstart is likely to die with the march of systemd (Which, as you'll need to understand, is not an init system anymore, but literally a system daemon. It owns, controls and plays with your machine at its own volition and there's nothing you can do to stop it.), OpenRC isn't taken seriously because the gentoo folks propose it and now that both Debian and Red Hat, the two major players on the market, have both decided to play along with the systemd game (one of them was more or less forced into it, but no matter), systemd is omnipresent and impossible to stop.
We would've needed to have a concrete, working answer that made systemd pale in performance, code quality AND documentation back in 2012. If Apple had released launchd as open source back when Ubuntu started writing upstart, things might have ended differently. If upstart wasn't pushed too early, things might have ended differently. However, at this point of time, the UNIX way on Linux is dead. Irrecoverably. I wish I didn't have to paint such a black picture, but it's too tightly-coupled with the rest of the Linux ecosystem to ever remove it again.
I do have to wonder: Which platforms does your software target?
The systemd guys clearly don't understand unix and they're not even close to reimplementing it, though.
Another argument frequently used is portability; you just port the browser and all the web apps run, at least somewhat. Your examples, however, aren't all that convincing in that direction. While C# works somewhat with Mono on Linux and OS X (though the (Free)BSD port isn't actually officially part of Mono) when using WinForms, WPF is not supported and Mono has no plans to support it. C++ with Qt and/or Boost is reasonable, though there are some pitfalls here and there to watch out for. As for Delphi, I'm not sure how mature Kylix is and if it runs on the BSDs.
Generally, if you say portability is more than just x86 with Windows/OS X/Linux, you'll hit a brick wall really fast, and browsers are surprisingly frequently ported.
I think the important part is that GlassFish is the reference implementation of all Java EE features.
It's only straightforward if it's documented somewhere in a sane, complete and concise manner. Is it in a manpage? If not, is it installed by default at least?
You're ignoring the Rankine and Roemer scales.
If anyone wants to follow up and mention Kelvin, then you're wrong because Kelvin doesn't use degrees.
Well, women are frequently deeply confused. The difference between "shut up and make me a sandwich" and "talk at me for hours upon hours despite your judgment hopefully telling you that I couldn't care less" has stumped women for centuries with no hope of improvement in sight.
You forgot to press the foot pedals and playing Beethoven's Moonlight Sonata with the secondary keyboard. ...At least you tried.
"Anope can be interacted with via RPC"... Yes, Anope 1.9. That's the development release, though. As much as I'd like to share your idealized view of IRC becoming a better place (except for the fact that I definitely wouldn't want to create an IRCd from scratch these days -- linking protocol and especially these goddamn CAP negotiations are just as bad as doing SSL from scratch. Who had the idea of message intents anyway?), fact is that the majority of networks that use Anope (and there are, due to the fact that quite a number of admins believe that levels are easier/better in some way or that Atheme is too much work to set up) use the stable 1.8 version.
Unlike the 1.7 dev version, 1.9 has not been widely adopted. This is mainly due to the fact that Anope 1.8 does just nearly enough out of the box to be still considered modern services, it's more hackable due to being coded in C (writing a module in 1.8 is definitely easier than in the C++ using 1.9 version. It's also easier to make it a complete fucking hackjob in 1.8) and has a bigger modding community (see http://modules.anope.org/ for pretty simple proof of that).
Additionally, it's still a mystery to me how IRCv3 works as an organization. It's described as a "meritocracy", but who is calling the shots in the end? You, nenolod? If so, then I'm not sure if the description shouldn't be rather "oligocracy" but that's pretty bad for the image of anything these days.
Furthermore, I would like to point out that, while four major IRCds are part of IRCv3/implement it, a big part of the implementations (especially so in UnrealIRCd) have actually come from people in the working group (namely you). While that in and of itself can hardly be considered a bad thing, it does lower the bus factor for future changes to the protocol to... precisely 1.
I do, however, agree with your belief that IRC needs a change, but I believe this is heading in the wrong direction. This is just cleaning the protocol up a bit. What we actually need are radical changes, which you'd need to discard all the old diehard IRC brigade for. Analyze what is currently popular: Xat, Facebook, IMs. Observe how two of those are web-based. Does IRC have a web-based client? Yes, it does. Mibbit, qwebirc and KiwiIRC (as well as IRCCloud, but they are absolutely uncooperative with any network). Mibbit sucks downright and is missing the oh-so-important colors to today's generation for the most part. qwebirc is tied to a network each. While that might simplify the handing on the user's part (one website for one network), it still sucks as a client (same color issue as Mibbit, even) and the entire concept of a network just rapes the minds of users. Users today don't know and they do not WANT to know that there are multiple IRC networks. They just want a chat room. Centralization is key. You can't talk of "a Xat chat" or "the Facebook chat" or "ICQ" or "MSN (Messenger)" in the same way you talk about IRC because the decentralized nature is included in none of them (though, if Jabber had found broader adoption amongst non-techies, which will not happen because of this precise very same argument, that would be a basis to work off). KiwiIRC looks promising, but no network has webirc blocks for them yet. Facebook wins because everybody else is already there, not because their chat technology (or anything else for that matter) is particularly innovative or good. Speaking of centralization, having multiple clients and networks is just even more confusion for new users. There is no "the IRC client" and there is no "the IRC network". That is not what users want. Janus links are a step in the right direction (as ugly as they may be), but not a solution.
On the topic of webirc blocks, banning people on IRC is an ordeal. It is a brutal pain in the neck. Other systems may require and enforce registration, so banning is very easy: Right click -> Ban. Or at least they abstract the banning itself away in some manner. You can't do that on IRC. You'll first spend
Is anything major using Python 3 already? Most distributions still use Python 2 as their default Python interpreter, the big libs (twisted and Django come to mind) aren't ported yet. Is there any reason to use it?
So, essentially, wouldn't that say "Look guys, we finally caught up to 19 year old technology and we're pretty fucking proud of it?"
In a press conference this morning, 600 KB/s stated that "after months of being abused and hit, it's finally time to stop. We won't cooperate anymore until the ISPs stop hitting us." Soon afterwards, higher speeds also agreed with 600 KB/s and followed his example.
News at eleven.
A bag of rice fell over in China. Please put this up as a story!
No company does anything out of the goodness of their own hearts. They're in business to make a profit, and you, the consumer, have shown them what you're willing to pay.
Rest in peace, Sun Microsystems.
I'll admit, I've never ever read the entire GPL (or one of its variations), simply because they're so incredibly massive that I just know there's some paragraphs just to screw people over. I refuse to use any license I cannot understand within two minutes, including reading time. Everything else is just plain ridiculous and will never be done by any kind of end-user anyway.
Because of that, I try to avoid using any GPL code, no matter what variation it might be, as much as possible in my code. Just the sound of GPL makes me run in circles, then crying myself to sleep in a lonely corner.
"The release also brings the latest KDE and XFCE versions, improved Btrfs support, amd a switch from OpenOffice.org to LibreOffice."
I'm pretty sure it should read "and a switch."
This could actually really prove to be useful, since that could open the possibility of a "counter-trojan" infecting all vulnerable computers and getting rid of other Zeus installations, while then proceeding to purge itself.
There's quite an amount of people who do get moderator points but don't have the time to actually use them, not to mention it's usually such a small amount that proven good moderators can only take minuscle action while karma whores can mess things up big time, meta-moderation only has a limited amount of influence, too.
1984 and Animal Farm would most likely not become mandatory, simply because they might teach people to be wary of what's going on so that the government can't screw them up bit by bit. That's not what a good, fair, nice government wants, since that would mean people wouldn't be able to be controlled 24/7, just think of the children!
Why bother with funny?
It won't raise your karma, even if +5 Insightful never made anyone snort coffee out of their nose.
Firefox is the only "mainstream" one. If we define mainstream as what most people use, there's barely Firefox. Normal people who don't code and don't administrate a server use neither BIND nor Apache nor PHP nor Peopl.
WikiLeakss's
Last time I checked it was WikiLeaks with one s, not WikiLeakss.