We don't want systemd. Just like we didn't want pulseaudio. Those systems which still vaguely resemble unix (just openbsd and netbsd at this point isn't it?) are not interested in linux bloatware, they want to continue resembling unix.
This is precisely it. Linux is not unix. It only vaguely and superficially resembles unix. Those of us who like unix aren't using linux anyways. If you want to use unix, do so. But suggesting linux distros need to be a certain way because unix is that way makes no sense.
You are confusing a sense of accomplishment for happiness. That suggests that you may not have felt happiness enough (or recently enough) to recognize it.
Why 10 years? Given that we've known what a mess the software development world is for 50 years and nothing has improved, what makes you think anything will be better 10 years from now?
Why do you think responding to "you are making a bunch of uninformed assumptions" with more uninformed assumptions is productive? Protip: some of us saw this site when it was made 2 years ago. Some of us are even aware of the context of 37signals founders being abusive on twitter that the site was created in response to. That does not mean we are all the people who made the site.
I'd be extremely surprised if they can. Just because there are a lot of options, doesn't mean there's any good ones. Tons of nearly identical, virtually featureless products does not make it easier to find one that actually does the job.
>Judging from the fact that their service has good reviews in major media and millions of users
They have no reviews in major media. They have both good and bad reviews in minor media. The "millions of users" claim is not supported at all.
>Any examples? Surely those mythical people know how to save a screenshot, right?
Yes, I happen to collect screenshots of things that are well known every time anyone talks to me about anything just in case some random redditard wants proof that the sky is blue.
>That's not funny or educational or even interesting.
Two of those are subjective and I'll ignore. But it is educational, it links to alternatives to 37 signals products.
>I can't really think of anything 37signals has done to warrant this
The company and its reputation was built on aggressively bad-mouthing and trash-talking anyone and everyone they could. Remember when rails started out? Anyone who dared to like something other than their framework was an idiot (at best).
Why are you bragging about making a bunch of uninformed, knee-jerk assumptions about someone you know nothing about? And why is this trash the top comment? Whether or not $20/month is too much does not depend on whether you have $20 to spend or not, it depends on the value you get from that $20. Products with very little value, and which have $0 alternatives that provide more value are not worth $20.
>I think it's because there are lots of PHP programmers who don't have the first clue about setting up an actual server on the internet (and keeping it up).
Well PHP programmers are going to want to use PHP anyways. But as far as users not knowing how to setup a server, that's true. But it is also irrelevant. Tons of people provide tons of different VM images for all sorts of things, node included. At that point it is no harder than PHP, with the added benefit of not needing to upgrade PHP every 2 weeks for the latest round of security holes.
That's an arbitrary and useless guideline, using made up numbers. If losing 1% of your potential users costs $100k in lost sales a year, and 20% of my time costs $20k, then spending that 20% time seems like a pretty good idea.
>Walter is saying you can't have good error messages without semicolons
That is what he said though. I understand it is one example for a larger point, but it is an example that doesn't support that point at all. It is pretty hard to judge the overall point when the example is nonsense.
I think this shows that Walter has lots of compiler experience, not so much lots of language design experience. You can't get good error messages without semicolons? How can anyone say something that absurd in a serious article? Have you tried a language without them? It works just fine.
Minimizing keywords is important not because of a word shortage, but because of an overlap with words the programmer wants to use. It is obvious that if you make "i" a keyword, someone will likely murder you. But there's tons of grey area where you might be stepping on toes and getting in the way, so minimizing the amount of toe stepping is good. Especially since there is absolutely no reason to have lots of keywords.
Well one other difference is that D is a systems language, and Go is nothing even remotely close to a systems language but initially claimed to be one. There is not much demand for a new systems language, most people are happy to use higher level languages for what they do these days. Most go converts are coming from python and ruby, not C++.
Your own examples contradict your hypothesis. Ruby is a generic scripting language, it is not better or worse than python or perl at anything. Rails made ruby popular due to evangelism, not solving a problem others do not (notice how rails was literally just a crappier django?).
"Being portable assembler" is not solving one problem at all, it is one of the most general things you could cite. That literally is being a better language.
Java took millions of dollars of marketing to make it popular, people didn't just suddenly flock to it because it was C with garbage collection (which was already a solved problem: see C).
Perhaps lisp "never took off" (seems like it took off pretty well to me) because it isn't the greatest language ever? Lisp barely is a language, it is more of a toolkit to build a language with.
Useful tab completion, more useful commands, catching Ctrl+C like a shell is supposed to do instead of exiting like an asshole, etc. Can you give an example of your opposite experience? I've literally never met someone who has used both and not preferred psql before.
>As JavaScript is basically a required feature on the web these days, who cares?
People who don't live in a fantasy bubble world where that is true? "Hey, just throw away 1% of your potential user base for no reason" isn't a very compelling sales pitch.
The problem with that is confusing users. When you have a "login with firefox" option you will get "but I don't use firefox anymore, I switched to chrome".
We don't want systemd. Just like we didn't want pulseaudio. Those systems which still vaguely resemble unix (just openbsd and netbsd at this point isn't it?) are not interested in linux bloatware, they want to continue resembling unix.