relation between solo learn and the new boston

Question

solo learn has copied content from new boston (bucky ) . Whats your opinion

Answer 1

bucky has much more courses

Answer 2

Can you explain how Sololearn copied content from thenewboston? I won't believe you otherwise

Answer 3

if you have watched the c++ course of bucky the. you will know . specially the class topics. same example , same thing , same variables , same function , ....moreover , previously when solo learn released , it had option for both theory and video for a topic ... at that time I used to study c++ , I used to see videos , then the corresponding theory was similar like notes made from the video itself . later on , videos option was removed and only theory was allowed. Later on I came to know of this new Boston channel and saw there videos , and guess what , these were the same videos which solo learn had ,and thus ,they would have removed it due to copy right issues . But I guess no one checked the theory part 😏

Answer 4

Now that you mentioned, I remember that I noticed some similarities in variable names too. But I don't know about the videos as I never saw any on sololearn. Anyways, it's not very tragical if variable or function names are the same, they are only small examples. But if they remade bucky's videos and posted on sololearn, that's pretty stupid thing to do

Answer 5

Yeah , Take a look at the examples of polymorphism on c++.. They are as same as what bucky done in his videos

Answer 6

i agree , you can check Bucky's SQL tutorials , SoloLearn are using the exact same tables and the exact same order of lessons and content !
It would be a shame and a disgrace if they truly did steal his content

Answer 7

Solo Learn still the best....challenges,Discuss,code playground....

Answer 8

at first i thought they were using the same textbook but printCrap() gave it away. lol

Answer 9

I dont know, I watched buckys's c++ tutorial which was from 2011 and sololearn was launched in 2013 so its true that the soloelearn guys copied him...