291–300 of 369 posts
This whole "build in the open" stuff has gone too far.
Some intentionally publish sources for audit and compatibility purpose, still proprietary though.
You get 90% of the kudos for being opensource-friendly, while no serious sized company can just clone your code and steal all your business.
That's huge. What takes up most of that 40Gb+?
Earlier quoted context omitted.
> What? Why? Isn't this what software developers do — they read a lot of code; they find ideas they like; they mix them together with their own ideas while building something. Not normally. https://en.wikipedia.org/wiki/Not_invented_here#In_computing More to the point: an organisation will usually use cleanroom techniques to clone something like this, if they choose to do so. Anyone who's been in contact with the ori…
You aren't allowed to use cleanroom techniques to clone something that's been stolen. You're still guilty of copyright violation for even downloading the code in the first place, and who knows, maybe also laws against receipt of stolen goods. Cleanroom reverse engineering is usually applied to a product that you've actually bought and paid for. You'd have to be really crazy to try and use this code for anything.
How do companies prevent their employees from leaking code?
Earlier quoted context omitted.
Probably Yandex will start watching their infrastructure very closely, and go through all known attack vectors that haven't been prioritized before to fix them ASAP. Won't be a boon for OSS, any author would be idiotic to read stolen source code and then decide to create a OSS library/project based on what they learn from it.
> any author would be idiotic to read stolen source code and then decide to create a OSS library/project based on what they learn from it. What? Why? Isn't this what software developers do — they read a lot of code; they find ideas they like; they mix them together with their own ideas while building something. Isn't this how learning works in general?
Earlier quoted context omitted.
> People avoid using BSD-licensed code in GPL code base Huh? I don't believe they do that. It's completely fine to use BSD in GPL code, but not the other way around.
It is fine to do either but the result is always a GPL license.
Binaries, yes -- either more or less restricted depending on which side of the ideological fence you're sitting on.
Earlier quoted context omitted.
Someone could still get the uncopyrightable ideas out of it though.
Sort of. There may also be pantents involved. It'll be specially hard to defend against it when your inspiration came from the patented code itself.
Interesting that most of the code comments are in English.
It's inconvenient to switch the keyboard layout each time you write a comment.
Earlier quoted context omitted.
At first I wanted to give a serious reply, but then I saw your (very aptly chosen, given the context) username and found myself wondering if HN rules allow parody accounts... However, I'll give one for those who've missed the irony: It's considered gauche to have ubiquitous non-english comments. Pretty much the only kosher use case is when you have to warn people not to modify otherwise bizarre looking code because o…
In many places I worked at in Brazil people will just write everything, even variable names, in Portuguese. That came down to the developers not speaking English at all. Who considers it gauche to have software written in non-English? The Russians you mean? I certainly find it perfectly acceptable and even desirable depending on the contributor's English fluency.
2x BigCo's I've worked at, with 1-5K IT staff. Yandex is xbig though, with 5K+.
>That came down to the developers not speaking English at all.
That sounds implausible and not very sane, unless of course you're working for something very static like the government, and the tech stack you're using is set in stone.
Imagine that you're using a popular library and decide to update your dependencies, who's going to read the change logs & the documentation? Sr. Architect?
If you have a security issue and the only writeups are in English, who's going to be trusted to implement a fix correctly if the people can't understand what the problem is in the first place?
Earlier quoted context omitted.
I think you're reading to much into this. It's easier to not switch languages in one task. If you're using an English-based programming language and English libraries/frameworks, you're not going to name your own variables in a different language. Comments most often follow that too. Any time I see someone attempt that, it's extremely distracting.
Not really. I've attended a meeting on the subject where people decided to use English "not to be loosers" and I've heard similar stories from other teams and departments.