Really appreciate Matz stepping up to take on this difficult situation.
As a Japanese developer, I’ve been worried about the direction things were going, so it’s reassuring to see this.
Stepping up how? It was always clear that Hiroshi Shibata didn't act solo without approval. I am not saying he knew the outcome before that, but WHEN was the decision made to take over gems + bundler? I have a slight suspicion that this may have been decided upon months ago already.
> As a Japanese developer, I’ve been worried about the direction things were going, so it’s reassuring to see this.
I am actually much more worried now. I don't live in the USA; I don't live in Japan. To me it seems as if Japan and the USA are totally over-dominating in the ruby ecosystem. While this is understandable that it is Japan (local community, I get it, this is different to english-speaking ones), I am absolutely upset that the USA has so much proxy-influence here. But I guess there is nothing that can be done. I guess in Python the USA also over-dominates. I just think this sucks really.
Yes. At least Ruby was always strongly Japanese though. In Python European and Asian developers are overtly exploited, with U.S. corporations and their employed stooges holding the reins of power.
I'm considering switching to Erlang, which was developed at a corporation from the start and appears to be drama and cancel free.
American salaries are typically wildly higher, both on the low end and on the high end. It's often remote work. There are more jobs and more variety of jobs, on an absolute scale, than any particular locality. There may be more of a job ladder, and less stigma to wanting to climb it. There are some other cultural aspects as well.
I would love to see such options become available in Europe (insofar as additional options existing, not taking away the ones that already exist). But that would require some extremely successful European companies working to change it.
My comment was unclear. I am American. I think I am familiar with these differences. You seem to agree with me that in light of these aspects, referring then to American company employees as stooges is exaggerated. Regarding Asia of course it's a different topic, and I am unfamiliar with it. Obviously some American companies are bad but I just question the comment I responded to, that's all. And I don't understand "stigma to climbing it." Depending on the country, of course, but I didn't think there was stigma. Europeans compete for prestige like the rest of us. Don't they? Some do, some don't, of course.
Different money and different attitudes.
Trying to get paid more than your peers if you're appropriately skilled isn't social kryptonite here in the states.
I think game is art. Art is made for publish thought of creater, which has power that solves real-world problems. Writing game code (art) is equals to solving problems.
You're telling me there are cases where a company has so many projects in it's gitlab instance that employees routinely have to search for things? That seems odd to me. I'd expect there to be a naming scheme for most things, and even if there's some oddball project, I'd think somebody else you work with knows about it and where it is. My company has maybe 20-30 projects, and I can find any of them easily if I know the client's name.
Ever worked in a company with micro services or a company that has a bunch of employees? You'll have hundreds of projects easily if it's a bunch of teams. If someone tells me "it's in our SRE libs package" I'll go ahead and search that. (Usually I can't find it because it's in a separate namespace on our Gitlab instance. Doing that is an Enterprise only feature on Gitlab right now: https://docs.gitlab.com/ee/user/search/advanced_global_searc...)
The point is that search is important and not a social network gimmick.
Yep, same here. We architected our services so that a common layer could be used which reduces service duplication but still we have over 700 projects for just one company doing end-to-end ecommerce and fulfillment. At some point you even start running out of names so you end up with people using acronyms from their specific fields which quickly ends up being unfindable. Not because of search but because you no longer know what to search for.
Actually, it doesn't even have to be microservices. At my current workplace we have over 1000 projects in our Gitlab. And many of those projects are a collection of up to 20 libraries.
I work for a university that has a centralized IT, but each of the schools may also have an IT group. When they setup a local Gitlab instance I moved our team's (web development) projects over.
We have over 60 projects alone within our group (our own school was decentralized, and only in the last 5 or so years have I been able to get things centralized within our team), and there's a ton that the centralized IT group has on the instance, plus all of those that other schools share. We currently have three people in our team (two designers/front-end, one full stack), but at one point were at six plus a consultant.
I've got a good idea of what most of the 60+ repos contain, and where things are, but a good search for the various open repos, and those that I'm semi-associated with, would be fantastic.
reply