From https://github.com/b3log/wide/blob/master/editor/editors.go : // 编辑器操作. (...) // TODO: 目前是调用 liteide_stub 工具来查找声明,后续需要重新实现 This is not an isolated example. People, please. For open source code stick to english in the code. Otherwise, you needlessly exclude anyone who doesn't speak your particular language. I was about to dive into the code thinking "this thing looks cool, maybe there's something to learn from it…
With the abundance of online translators this should not be a problem. This is what Google translate makes of it: // Editor operations (...) // TODO:. Is currently calling liteide_stub tool to find statement, the subsequent need to reimplement Baidu translate: / / editor operation. (...) / / TODO: is now calling the liteide_stub tool to find the following statement, the need to re implement Between the two of those i…
A Web IDE for Teams using Golang
31–40 of 53 posts
Re: A Web IDE for Teams using Golang
#32I don't want to sound arrogant, but can someone please try to explain to me what is the appeal of web-based IDEs for non-web development? The “feature” bullet points from their site do not really speak to me, and it overall still seems like a solution in search of a problem. I'd seriously like to hear some stories from people who use such solutions and environments. The only reason I can think of for the existence an…
For me it would be instant, remote collaboration. Unfortunately no web-based IDE offers that, as far as I know. Google docs for code anyone?
Re: A Web IDE for Teams using Golang
#33From https://github.com/b3log/wide/blob/master/editor/editors.go : // 编辑器操作. (...) // TODO: 目前是调用 liteide_stub 工具来查找声明,后续需要重新实现 This is not an isolated example. People, please. For open source code stick to english in the code. Otherwise, you needlessly exclude anyone who doesn't speak your particular language. I was about to dive into the code thinking "this thing looks cool, maybe there's something to learn from it…
I agree with you that projects using languages I don't understand is a major turn-off, I think they understand that as well, and live with the trade-off. As someone else said, many people are not comfortable using English (which is just a nice way of saying their English sucks). I wrote a small script [1] to translate this really cool Go blog [2] from Chinese using a free Bing API. 1: https://github.com/oyvindsk/Tore…
Ok, maybe their english sucks. Do you ever get better at something by not practising?
Re: A Web IDE for Teams using Golang
#34Earlier quoted context omitted.
I agree with you that projects using languages I don't understand is a major turn-off, I think they understand that as well, and live with the trade-off. As someone else said, many people are not comfortable using English (which is just a nice way of saying their English sucks). I wrote a small script [1] to translate this really cool Go blog [2] from Chinese using a free Bing API. 1: https://github.com/oyvindsk/Tore…
They have the freedom to do make that decision just as I have the freedom to voice my disagreement. Ok, maybe their english sucks. Do you ever get better at something by not practising?
I have to say, from this and your other comments ("Do not use any language other than english in public code"), you come off as extremely arrogant.
Re: A Web IDE for Teams using Golang
#35Earlier quoted context omitted.
I use Sublime Text 3 + GOSublime on my Mac and it has been a nice experience for developing golang apps. But I can see the appeal of web based IDE when combined with tools like nitrous.io, where your development tools are all in the cloud and you don't have to setup everything local just to start coding.
How do you find debugging? Debugging was one of the primary reasons of moving away from Sublime3 for me, though I didn't try Sublime with Go.
Most Go devs use logging/printing to debug. Mainly because of the prolific use of Goroutines, properly debugging an app can be very difficult.
Re: A Web IDE for Teams using Golang
#36Re: A Web IDE for Teams using Golang
#37From https://github.com/b3log/wide/blob/master/editor/editors.go : // 编辑器操作. (...) // TODO: 目前是调用 liteide_stub 工具来查找声明,后续需要重新实现 This is not an isolated example. People, please. For open source code stick to english in the code. Otherwise, you needlessly exclude anyone who doesn't speak your particular language. I was about to dive into the code thinking "this thing looks cool, maybe there's something to learn from it…
Re: A Web IDE for Teams using Golang
#38Earlier quoted context omitted.
While I do like English, the way you said 'your particular language' seemed a little off to me. I'm no expert but that sample you gave me looks like Simplified Chinese, which should be readable by about 1.2 billion people[0]. There is no solid data on how widespread English is yet but I think if 1/6th of the earth speaks a language which is also an official language of the United Nations, programmers should be able t…
You're missing the point comletely. There needs to be a common, agreed on ("standard") intercommunication language for exchange of knowledge to happen. For computer science related things, programming in particular, this is english. This happened historically because a lot of the development took place in the US and it is also a good choice, because english is easy to learn (I'm no native speaker btw.). Had computers…
OK, I guess your experience as a non-native speaker validates that claim?
I don't see how the claim "English is easy to learn" is obvious on an international level.
> I'm not advocating it because it is the easier choice for me,
But it also is an easier choice for me. Doesn't matter if you're a native speaker or not, since you're obviously comfortable with it.
(On this topic I also see a lot of "I wish everyone would just write in English/speak English in these contexts, and I'm not even a native speaker!", implying that they're an unbiased party. No, if you have a good command of the language, you're about as biased as any native speaker on this debate, really.)
Re: A Web IDE for Teams using Golang
#39/lazyweb
Re: A Web IDE for Teams using Golang
#40Earlier quoted context omitted.
You're missing the point comletely. There needs to be a common, agreed on ("standard") intercommunication language for exchange of knowledge to happen. For computer science related things, programming in particular, this is english. This happened historically because a lot of the development took place in the US and it is also a good choice, because english is easy to learn (I'm no native speaker btw.). Had computers…
> , because english is easy to learn (I'm no native speaker btw.). OK, I guess your experience as a non-native speaker validates that claim? I don't see how the claim "English is easy to learn" is obvious on an international level. > I'm not advocating it because it is the easier choice for me, But it also is an easier choice for me. Doesn't matter if you're a native speaker or not, since you're obviously comfortable…