If valid criticism is rude, we're all doomed here on HN. The parents point is valid. If you don't like it, that's fine, but rude it was not. Google doesn't know anything more than DDG, so you're just plain old wrong on that argument.
This made me chuckle, since modern Python and Java styles are very, very similar, if not identical in places, to those of 10 years ago. Some of the libraries have changed, but many are the same as well. Shoot, I can still run Python code I wrote 10 years ago on the latest version (yep, that means something originally written for Python 2.3 can run fine on Python 3.6).
And no, that doesn't make Python and Java old hat or redundant.
You can run 10 year old JavaScript as well, no problem. But Java written today is pretty different from Java written 10 years ago and the Java frameworks are very different.
My point is that you can write code in the style from 10 years ago in any stack but for some reason people seem to take pride in it in the JavaScript world just because they cannot be bothered the actually learn modern development. Not to mention they tend to exaggerate the difficulty of getting started. Compare the tooling, build chain and language features of a JavaScript stack with for example Java. It is not like the JavaScript one is more complicated.
You don't need something like React if you are doing a simple web page but a lot of people ARE building more advanced web applications these days and then it is probably best to just suck it up and learn a modern stack because the old ways of development is not really suited for it.
Bitrise seem to deal with a niche market (mobile development), so claiming their study shows a general trend in the self hosted git market is a stretch at best. I'd imagine boring old git itself and non-website backed things like gitosis are still a massive part of the overall install base. In any case, the claim that gitlab's on 2/3 market share just screams disingenuous marketing fluff to me and cheapens gitlab as a whole.
You are correct, Google trends is pretty much irrelevant here. You would be surprised by Gitosis (and many others you've dismissed). It's pretty much in every company I've worked in over the last 7 years. It's never well liked, but it works just fine. Most companies don't need bells and whistles that come with GUI based git installs, so they don't waste the money switching away to them.
They've been promising to fix performance and the UI for years now, so I wouldn't hold out much hope. It's a shame, but there are better open source products so it's not like there are no other options for self hosted.
For what it's worth, in the last year (since January 23, 2017) we've merged ~440 merge requests labeled "performance"[0]. It's not perfect right now and there's still plenty of work to do, but compared to when I started at GitLab almost two years ago it's night-and-day.
We've also got an entire team dedicated to porting our Git layer to Go with Gitaly[1], which has been a major bottleneck that we've started resolving over the last year or so.
Looks like replacing the money isn't the issue, it's whether or not D-Cal have screwed over the agency. Over half of the KS pledges were made fraudulently by D-Cal themselves, meaning the money doesn't actually exist and their campaign was a failure. This puts the agency on the hook for any and all refunds if the people who actually put their money into pledges ask for a refund (the agency account is tied to the campaign now). D-Cal have apparently not come up with a proper solution to repay the money if this happens, so Woodshed are not happy about releasing the funds until this is resolved (on their accountants advice). I'd suggest that all D-Cal have to do is finish setting up an account that can be used on KS and the account could be switched and funds deposited. Either that or put enough cash to cover the agencies costs into some sort of escrow.
This really isn't true and I really wish this myth would stop. Sure, if you go into the financial sector or find a startup where they don't know their arse from their elbow about software workers, you can dupe them into giving you more money. But 55k in London is a good wage for a software developer and you're definitely not looking at that if you're mid-level and working for a regular company.
Source: I've lived and worked (and continue to do so) as a software developer, technical lead and CTO in London and have been in several different sectors.
Oh, 55k GBP is a nice salary by absolute standards, but not for software developers in London.
Yes, you can see people working for so little. But why leave money on the table?
> Sure, if you go into the financial sector or find a startup where they don't know their arse from their elbow about software workers, you can dupe them into giving you more money.
Yes, obviously. Why wouldn't you? If some sectors have more money than sense, that's an opportunity--not a problem.
(I can see that there are reasons to take a lower salary in return for a job you really like; but then you don't get to complain about low pay.)
Source: I've lived and worked in Cambridge (Cambridgeshire), Singapore, Sydney, London in various roles. Mostly in big tech and finance.
And, yes, if you look at Glassdoor you can find the numbers you cited. In my experience Glassdoor seems to be systematically lower than the numbers I get from my own experience and asking friends and coworkers.
(But I might just be living the charmed life that people live who have enough sense to negotiate salaries on job offers?)
Care to explain how 55k GBP (60k EUR) can be a good wage, when the average new grad software developer in Germany makes like 50k EUR? And the cost of living is what, half or less than what it is in London?
Less taxes in the UK means higher take home from the 55k than you would have in germany. And you have to factor in that the 55 figure is probably from a time where GBP to EUR was still 1.4:1. Consider that 55k GBP might have been ~4.5k EUR/mo take home not too long ago vs ~2.5k EUR/mo take home from 50k EUR in germany. Still shitty, but not as shitty as it seems now.
EDIT: Also, using current exchange rates, the cost of living in one of the larger cities (Berlin, Munich, etc) in germany isnt that much lower compared to London anymore.
Calling the argument contrived is really rather immature. It's not contrived, it's very real and important. Please stop being so quick to dismiss those that you disagree with as it's childish at best.
You speak of cargo cult, but your entire comment reeks of it. Ok, we understand, you like being able to isolate yourself. That's nice, and I'm glad you found a niche, but it's not the same for the vast majority of jobs and people. You call other people lazy, but I think perhaps that's just you. Social interaction and moving above an intermediate level where you can isolate yourself is hard work. Don't be so dismissive of others that strive for more.
Working remotely is great for the unambitious and the antisocial. Please stop trying to put those who do more down though.
Working remotely doesn't mean someone is unambitious or antisocial. The ability to focus without interruptions while still communicating/documenting clearly is easier done with remote work (in my experience).
I think you touched on a sad aspect of tech. For anyone to be "ambitious" or to "move above an intermediate level" they essentially have to become managers, which means less technical work. The likelihood of you joining the VP/higher ranks and still working on low level issues, as a respected technical fellow, are low to nill (Google, FB, MS have some positions but otherwise you're filtered into a manager to "move up.").
Your comment about "striving for more" is disrespectful to most developers/engineers.
How are people who spend their entire work days talking to others, but not actually working, "doing more?" I've seen more talkative/social people not getting work done than
"antisocial" workers being "unambitious" or stagnant.
Don't see why you were voted down on this, since it's true. Slack working to get things running again doesn't mean they're prioritising your companies particular instance or region. They're likely to be making sure their own region and their own stuff is up and fixed first, so anyone away from the east coast of America is likely to get seen to after that. It would be stupid to do it any other way, since slack employees are likely affected as well and they're the ones trying to fix it. Down voting someone pointing that out is pretty fanboi-esk or really naieve.
Pretty much, if you don't own the service, you don't get to decide where in the queue you are for a fix.
I'm guessing from your posts here that you're either very naive and/or too young to have been in a hiring role.
Yes, it does indeed work both ways. Just because you don't understand this doesn't make you in any way correct.
I'm not really sure what your second paragraph means. Are you saying you job hunt while at work? That's not a professional thing to be doing. In any case, writing a cover letter is very easy, so being unable to do that probably means you need to work on your communication skills. Heck, with the amount of posts you've stuck onto HN today alone, you could have knocked up a short cover letter that would suit 90% of technical job applications, so this can't be a time problem for you.
