131–140 of 148 posts
Earlier quoted context omitted.
I've been consistently unimpressed with the offerings in that space.
Curious what's missing, iirc you can set figshare to automatically pull from GitHub on a release. Seems pretty low requirements for free long term archiving and fitting into the common workflows with DOIs
Earlier quoted context omitted.
I really don't get the hate MS gets for Skype. I used it before the acquisition and it was usually ok, and I've used it since and it's usually ok. I dont' like how I can't find some menu items because they keep moving, but this happened a lot before, too. Is it just that they didn't progress the platform? What - specifically - have they done wrong with it?
If you and I were in a group meeting, you would get an alert stating _you_ would not be able to use the good features on this call because _I_ needed to update my skype client. Of course, only client available to me is the same exact version they bought years before as they never updated with features just bug fixes. You would have been used an unwitting tool as you helpfully mansplained how to overcome my version de…
If that is the limit of the problems people have with that acquisition then I really fail to understand what the problem is.
Earlier quoted context omitted.
See I hope that "expert" coders understand that 'git push' works even on non-MS controlled endpoints, and how to setup a damned wiki if need be... GitHub is stupid valuable for MS, and will make their dev tools offerings much stronger (TFS is a dog, bringing GitHub Enterprise into MS Enterprise support & sales cycle is gonna make a loooot of scratch). But the value of the GitHub community persists only so long as the…
You can already use GitHub in visual studio. MS didn't have to buy GitHub to integrate with it. Pretty much the best that can happen is GitHub will now get worse as MS puts in functionality to do with their tools. The worst is they really fuck it up like they did with Skype.
What there is not is a comprehensive end-to-end support for github based workflows (issues, projects, hooks, wiki-branches, releases), as first class citizens across the entire MS platform. Github Enterprise, sufficiently tailored for MS shops, presents some huge opportunities for scaling dev teams and integrating with other languages and tool chains. I believe there are also significant opportunities in academics: something like VS Code + Jupyter notebooks + deep Github integration, aligned with K-to-PHD and classroom support, strikes right at a core MS's market and would provide significant capture of key users and key metadata.
These are not hurdles of a technically challenging nature, just product design, and will improve their offerings markedly. I see them as givens for their next product updates.
The best that can happen here is a new breed of pre-shared, DCVS based, open source projects and learning tools. MS can't do a lot to stop that, as the tools are already available for GitLab or Atlissan or a monied interest, but MS can do a lot to enable it.
Earlier quoted context omitted.
If you and I were in a group meeting, you would get an alert stating _you_ would not be able to use the good features on this call because _I_ needed to update my skype client. Of course, only client available to me is the same exact version they bought years before as they never updated with features just bug fixes. You would have been used an unwitting tool as you helpfully mansplained how to overcome my version de…
That seems reasonably understandable from the technical point of view. I'd prefer to know that than the alternative of not knowing why I couldn't use some feature. If that is the limit of the problems people have with that acquisition then I really fail to understand what the problem is.
I have long since deleted it, too many semi-competent users telling me that all you have to do is go to this site and click on this link ...
Earlier quoted context omitted.
There is not much to be gained by defending Microsoft. But from my view, my appreciation for their tooling is highly correlated with my own technical maturity. I spent about a decade primarily Mac, ran several Linux servers and developed from my Mac environment. But in the last few years I have switched to surface book and a windows development environment. It does not totally suck. Especially, now that I’ve got an U…
With a few exceptions, the problem with MS has never been their technical chops. True, they've moved from a malignant stance to a more benign one recently, but their disregard for privacy and partnership with government should still make folks pause to consider. And pause we do.
I generally much prefer GUIs over command lines as I'm lazy and have a bad memory, so anything off the beaten path involves loads of unnecessary googling to remind me of the right invocation to the CLI gods.
I'd avoided using it for so long because of bad memories of using TFS, but I must admit it's pretty good for generally using git, with only a few minor UI gripes. I must admit I haven't had to do a merge yet because I'm flying solo on my newest project, which is usually the big test.
Earlier quoted context omitted.
You're going to have to go in depth about what makes the Microsoft stack so beautiful. From the outside it looks likes it grown without a benevolent dictator to keep it in line, and there's way too many wrapper layers
It's a copypasta https://www.reddit.com/r/copypasta/comments/6qhyr3/rick_and_...
Earlier quoted context omitted.
That seems reasonably understandable from the technical point of view. I'd prefer to know that than the alternative of not knowing why I couldn't use some feature. If that is the limit of the problems people have with that acquisition then I really fail to understand what the problem is.
It is not reasonable to trick your users into harassing someone who uses a platform for which there is no newer version because MS abandoned it. A more honest technical note would own up for their choice to discontinue adding features. I have long since deleted it, too many semi-competent users telling me that all you have to do is go to this site and click on this link ...
But is that really the worst thing about it? Or have you heard other things?
I’m a desktop Linux users but even I don’t try using Skype on Linux.
Earlier quoted context omitted.
So what I'm hearing is the solution to this migration problem is to also store the entire issue tracker as a git repo alongside the real repo and wiki repo? Git repos for all the things! (Seriously, I think this solution would fit right in along with the way Wikis are handled)
How hard is it for some ont to use the GitHub api and port all of that over to a new system?
Earlier quoted context omitted.
I think it's blindingly naive to think that, on any meaningful timeline, a company like GitHub wouldn't be mining their userbase for trends and capitalising on them by selling it to third parties... There's nothing shady about using corporate information and user metadata to provide value to others, but you have to imagine that MS owning that data set is highly similar to MS buying it from GitHub. Up to the minute an…
Except that selling data to third parties has never been Microsoft’s MO. It’s always been about getting fat checks from the worlds largest companies’ IT departments.
My point was that EvilCorps using the metadata from GitHub was an unavoidable eventuality IMO [and honestly, it would probably be a Good Thing for developers, but whatevs...]. As it stands, that dataset is now going to be owned be a single EvilCorp. One who has a distinct mercantile incentive to exploit, instead of resell, that data.
If the concern is corporate exploitation MS ownership is more likely to reduce the number of exploitative partners to 1. Ironically a net win, for those sensitive to metadata reuse.
Earlier quoted context omitted.
This is a bit unrelated, but I think it would be cool to have a decentralized way of making persistent URLs.
The one that seems to be gaining the most traction is IPFS[1]. /ipfs/ URLs are content-addressed (like git objects). As long as someone has a copy of the data somewhere on the IPFS network it will continue to be available, and if you manage to get a copy of the content from somewhere else you can try hashing it and make sure it matches. (And if it does you can `ipfs add` it and it will become available again, even if…
And with ipfs you are dependent on the ipfs own domain. To remove domain dependency it would have to be something not based on current DNS system.