Recent submissions

Comment · 10 years ago
OmniSharp powered intellisense and other features are easy enough to stick in VS Code. It's easier to package and deploy than MonoDevelop. Much easier (at least for me) to write extensions for VS Code. I see it as a win-win. MonoDevelop has always been a frustrating experience for me. While VS Code isn't perfect, I'm less frustrated using it than MonoDevelop.
Comment · 10 years ago
I wonder if it means a transition to Visual Studio Code at some point. I doubt it would happen soon, but I feel like there's a lot more support behind that IDE than MonoDevelop.
Comment · 10 years ago
I agree, I think SpaceX will have re-usable rockets with the Falcon 9 long before this is working. But I believe you could extend the jet-powered-rockets to larger launch vehicles than you could the tech in the Falcon 9. Plus, the tech might be able to be extended to have cheaper super-sonic flights. But that's long ways down the road.
Comment · 10 years ago
Comment · 11 years ago
Topshelf's documentation does need some more TLC -- if there's something specific you thought was lacking I can take a look at updating it.

I'm glad to hear you're getting value out of it! Last place I was at, we had about 30 distinct services running. It was a huge bonus to have Topshelf.

Comment · 11 years ago
You can, though you doing get to do it by using the ref/pull/## trick. That's just a connivence, you can get CI to do about anything.
Comment · 11 years ago
Talking to a lot of people at conferences and similar events, rebasing against the target branch before merging is pretty uncommon. Few people think a clean history is that important.

Personally I think, rebase + auto-squash/auto-fixit makes the history a lot easier when it's time to look back. It just happens so rarely I wonder if it's really worth the effort I expend on it.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton