MS is deploying agents to give you a Mountain Dew enema and throw Doritos dust in your face until you repent, blasphemer!
They also closed-sourced all the things they had open-sourced. I got one JUST before they did that and I've been not-so-happy with it ever since.
They betrayed "makers", open source, and their customers. They deserve a worse fate.
I only paid one-way shipping on the RMA, which wasn't so much. You had to pay to get yours fixed/replaced?
While your genaralization of GoPro users is probably over 90% accurate they are actually amazingly good action cameras. I use one myself for a variety of motorsports. Eg:
Carting requires you to find the fastest line around a course. I use the GoPro video and check my lap times with different lines. What's great about it is the video is very clean - the GoPro has extra processing hardware that cleans up jitters and keeps the colors clean whereas a normal video camera you'll get a blurry mess.
I'm really not sure how secure you need to keep these things either. The WiFi is really only to control the camera or grab files off of it over the air so I really could care less if someone got the auth credentials to mine.
I wonder if they have improved. I got a Hero 3+ Black which had issues in very cold weather - I sent one e-mail, they sent me an RMA form, I sent it out and a week later had a brand new unit. This was maybe 5 months ago - so fairly recent; and it was with support in east Asia so it could be a difference between support teams as well.
BTW don't discredit accusations of a bad SD card - I've had a few SD cards go bad on me that caused some crazy issues including me bricking a Zaurus during a firmware update.
Until you framed the context here I actually hadn't realized what the motivation for designing systemd like that could have been. As you've pointed out; while that mentality of hard-coding all these modules into pretty-little uniformly shaped candy shells will be super convient to deploy a few thousand disposable server instances it's going to make any hand-tuning a big pain in the ass.
The fact that one of the "sale points" of systemd is to have these localized initialization modules included in packages just re-inforces your point - and it makes me worry systemd is going to replace any customized modules each time a package is updated. Ugh.
This is the most insightful comment in this entire discussion. It's nested pretty deep though - maybe you should copy this and paste it as a new post. People need to see this.
Again, I don't hate him. I'm just curious as to why you defend him so much. And by "relationship" I mean do you know him? Have you worked with him? Have you been involved in the technical discussions his negative image arose from? I wasn't implying anything else... So why are you so bent on defending him?
> and using that hate in place of technical considerations
I think the problem here is a lot of the "hate" he's getting is from *him* ignoring technical criticism. At least that's what a lot of people have pointed out. He kind of projects this attitude of "I'm right because I know I'm right and my way is better" which is an extermely frightening considering how much of an integral and low level component of the system systemd is.
As developers we need to take criticism seriously. When someone says "I think this is wrong" or "I'm worried about this in this situation" or "Do you think this is really a good idea?" it is quite possible they may have noticed something we've overlooked or failed to consider.
SysV is significantly simpler in design and functionality than systemd and that is exactly why so many people want to stick to it rather than jump on the systemd bandwagon. systemd tries to do way too much and in turn gets itself tangled into parts of the system that SysV would never be involved in. That means that in cases where SysV has done its simple job and gotten out of the way systemd could have some failure in some unrelated part of the system that could have a residual effect on something else. What's damning is that there are quite a few recorded instances of this happening.
The fact of the matter is as much as SysV can be inflexible and occasionally difficult to deal with, it works and it rarely breaks. You need to consider the install base we're talking about and how much of a massive loss of time and money even a 1% increase in down time could cause. This is an issue we need to be certain on, we need more testing on, and as much as it would be great to just love new and shiny things we need to act like grumpy old men a little bit so we don't break parts of the world.
First off I don't hate him - I just don't trust him and I find the way he deals with people to be a bit childish.
As for the rest of your post:
> He's a famous, successful programmer.
He's kind of famous for not being liked by some other high profile programmers more than he's famous for delivering a stellar project. We can only hope systemd will turn out to be as fantastic as is promsied and everyone can just drop the issue and give praise [when and] where it is due. Mind you, that day has not yet come.
> none of whom are qualified for his job
He's not some sort of genius. There are many many incredible coders out there who would certainly be as qualified for his job - just few of them are so motivated or have been offered the incentive or opportunity to do it.
> All your hate
Criticism and/or lack of trust are quite different than hate. Again, I don't hate him. And I really, really want systemd to be good. I want to just transition into using it regularly and think "This is great! I'm so happy it turned out so good." And that possibility certainly exists as I regularly have deployment issues that hinge on sysv being a little too old and crusty to deal with newer things elegantly. Some of the things promised by systemd look like they will gracefully solve these problems but I have yet to see an actual build of it that did.
Seriously though, what kind of relationship do you have with him? It's obvious you have some sort of emotional or empathetic attachment to him and I'm curious as to what warrants that.
The terminal in OS X is OK if you install iterm2 - and in fact when I use OS X it's usually just a full screen terminal. The probelm lies in using the GUI. Aside from the fact that I'm not used to it and honestly don't really like it (and can't switch window managers like I can in Linux) there is a lot of functionality which has been strangely obscured. Case in point is showing hidden files in the finder. Maybe this has been improved since I last did it, but I actually had to modify some setting and restart finder. It seems to me a lot of the mentality in the design is "Grandma could accidentally do something if we let her see/access this. We should hide it.".
> in order to boost support revenue
I don't want to believe that's the reason systemd was pushed through, but if that statement has even a fragment of truth to it then someone at RedHat needs to have their skull busted.
I actually completely agree with you on most parts here. The "not very *nix like" thing is more referring to how the core of systemd is trying to do a lot more than it should and then is wrapping that in several layers. Then to make matters worse many of those processes are hard coded and not configurable without actually recompiling the module for that. As cluttered and dated as SysV is at least you don't have to take pieces of it apart to change what flags are being used to call some secondary command at boot time.
Of course I say this but you are correct in that the design states it should not be this way but it is. Or, to put it another way, let me just quote the last line of your comment:
> The basic concepts of what systemd does is good, this does not mean the execution has been particularly great.
I don't think you are familiar with the controversy surrounding him, but a quick google search dug up a rather good summary of the situation:
The people involved are always important because the people involved will:
1. Shape how the project evolves.
2. The life of the project is usually dependent on those primarily interested in it staying interested in it.
3. A project needs to take criticism into account and look for opporunities to improve. Completely ignoring all critcisim could be ignoring fixes you could make now that could make things a lot smoother and avoid problems in the future.
Also I'm not defending SysV
Every time I've played with it I had things like weird locking issues - but this was maybe a year ago when I last tried it.
What bothers/worries me about it are the devs behind it. Poettering was bitching about how hostile the community was before but he completely deserved every bit of criticism. All the major devs on that project are known to have abandoned other projects. Several times they made mainline commits which completely broke things. They constantly pushed barely tested and poor quality code (which is why Linus got angry at one of them and banned them from making pull requests till they got their sh*t together). On top of that the design of systemd is not very *nix like so it does seem an odd fit. All this makes me uneasy, and I don't think I'm the only one, because from this I am expecting a big lump of poorly tested experimental play code that the lead devs will just abandon once they get interested in another project.