MS buys Github. It's time to move on.
Heater.
Posts: 21,230
Microsoft is to buy Github https://www.bbc.com/news/technology-44351214
It makes me very sad to have to abandon github and move on. Whatever junk I have on github will be making its way to Bitbucket and or gitlab ASAP.
Suggest Parallax do likewise.
It makes me very sad to have to abandon github and move on. Whatever junk I have on github will be making its way to Bitbucket and or gitlab ASAP.
Suggest Parallax do likewise.
Comments
-Phil
Really! Let me just take three engineers off their current work and alert them of this emergency so they can spend the next week moving our content.
We're not making any rash decisions around here. As soon as we get familiar with one platform it is changed, retired, bought, made "not popular" or something else that renders it the wrong tool. I guarantee you that if we made decisions based on emotion we'd be long gone by now (and there would be no Propeller 2 either).
Sit tight, let's not get excited and just see what happens.
Yup, time to wait and see... and as always, cherry-pick pick the best bits of open source ...
Note the largest project on github is apparently Microsoft's Visual Studio Code, which one Heater. made this earlier comment about
I would prefer it if this were done with Microsoft's Visual Studio Code. VS Code is open source and cross-platform. Visual Studio is not.]
There are already some looking at P1/P2 support using Microsoft's Visual Studio Code, given that Visual Studio Code is getting mature.
Addit: inside VS code I see support for PlatformIO, which looks to already cover much of the MCU space.
https://github.com/platformio/platformio-examples
and drilling into that, looking for smallest PCBs with Debug support finds a few close to $10
https://os.mbed.com/platforms/FRDM-KL05Z/?utm_source=platformio&utm_medium=docs
https://www.pjrc.com/store/teensylc.html
None of the 8b Ardunio boards seem to include Debug=Yes, but the newest Ardunios have larger flash USB bridge parts, so that might come.. ?
Feel free to put on your tin foil hats and flee from anything MS buys, but that's your loss in most cases.
All this talk of "it is still a thrill when it happens", "tin hats", "heads in the sand", whatever, is just a put down for your opponent in a discussion without saying anything substantive.
Those interested in a somewhat rational summary of the different perspectives of this issue one might find this short video by Bryan Lunduke of interest.
He puts my point of view better than I can.
By the way, I love Visual Studio Code. It works brilliantly well, has good performance, is open source and cross-platform. Wonderful.
So moving over there is a solution for a only while.
We need a P2P VCS!
Yea... that's fun. He's absolutely right. I haven't seen anything that would imply they're tipping back toward that direction and I really hope they're not.... but he's right. If they were tipping back that direction, this is exactly the right way to do it. Scary.
Gr.... I hope they don't. They haven't renamed Skype yet. Oh wait... yes they did! Lync! So maybe the public-facing GitHub.com will remain GitHub long-term, but their internally hosted product (as in, you host it on your own server) will be branded differently? I could see that. In any case, if that's the worst that comes from this, I call it a win.
Only time will tell. Personally, I'm taking the optimistic path and holding my hopes high. I think they'll do right by the community.
Migrate from GitHub to SourceForge with this tool. A lot has changed for the better at SourceForge recently.
Mike
...so it will take only one tock or so...
\\o o// \o/
Ok... will that migrate issues and other uncloneable stuff too?
IBM was no different with OS/2. I always suspected IBM had a case of mad brain syndrome going on and found out later that there was (rumored to be) an internal group actively working against it to retain special pricing for the resale of Windows on their pcs. Surprised, but not really, seemed to explain IBM's behavior though. So that's my prism, or not so rosy colored glasses.
As long as they don't turn into SourceForge I'll be happy. Tired of being over-run with ads and BS that feels more like scamware.
The thing to watch going forward is the T&Cs. Realizing they will have direct access to ALL code on that site, what is to protect the developers from M $ from going back to the "Halloween Papers" days, of them identifying a potential product or competitor and out spending or otherwise burying the project they want to grab. I doubt they will change much of what is github's function though. They by now may realize that a new github-like site can be created and movement to it would be swift if M $ github fails the smell test at anytime, even a rumour of such given their history would cause a big hit if there is an alternative.
Then of course, when does the pricing structure change..... by how much and other little things, like say cloning a project is free....... for now........
Exactly. Especially if it's as easy to migrate as people indicate. From a business perspective, theres's little reason to incur an expense when you can't realize any obvious return on investment.
Ken Gracey
Others may like to think it will be trivial to move (only an hour, yeah right), but the reality is likely not as easy as they think. You have many people from all over contributing to your projects on github, so first of all it's not as simple as getting your own staff to switch (which could be done in a reasonable time frame). Everyone working in Parallax's github would need to migrate also, and what of their forks with changes that aren't merged back yet? What about all the history and linkage that would likely be lost?
If Microsoft changes things at github that causes a problem, then sure move on to something else, but until then it's just the "anti-MS" crowd crying wolf again.
Let's say the "master" upstream repo is in Github. And you have a ton of developers cloning that, hacking their own clones and branches and so on. Like you do with git.
Then that "master" repo disappears from Github and is cloned to somewhere else, say Bitbucket. The history is not lost. All clones of git repos are peers.
All the developers need to do is change their git config to point to the new "master" repo. And continue as if nothing had happened.
My company did this twice already. Moving from our in house git repos, to Github, to Bitbucket.
I agree there is a little problem with other github features, like issue tracking and such. As far as I can tell Parallax does not pay much attention to those.
Or more currently, is github going to ask me if they can give my account details to someone else? I guess not. Time to move. Indeed. This is git we are talking about. Created by Linus Torvalds to be resilient to this kind of problem.
My beef is not with MS here. My beef is with the coagulation of everything into the hands of the few. Whoever they are.
Yes. moving anything needs real care, and you also bang into the classic issue of
"The man with one watch always knows what time it is, the man with two, is never sure"
I'd certainly wait to see if something else does emerge as the next defacto Github, otherwise there is the additional risk of backing the wrong horse, (and moving camp yet again)
I had a quick glance at that, and it seems to have Microcontroller ecosystem support, and some debug capability. I don't have any of the Eval boards they list here, but they go down to $10+,
Parallax should put some staff onto checking into the usage aspects of that.
The issue is not git itself, it is all the links already in peoples posts/blogs/docs.
Then, with two copies in place, which one is the most recent / most active ?
Easy to create a shambles, purely to avoid an imagined problem...
I do see what you mean.
Such is the magic of the Open Source world. Just because you put up a project does not mean that you own it. If you don't pay attention and cooperate with the developers attracted to your project, it can up sticks and move on without you. A simple command, "git log", will tell you. I see no shambles in cloning a thing from one place to another. Sure it needs some links updating perhaps. No worse than the billion links broken everyday on the net.
Why do you say "imagined problem" ?