Hi. Author of the article/gist here. It was actually written in Spring of last year, I think. I've just updated it because, as people have said, many of the issues have been addressed one way or the other:
* The KafkaREST proxy makes life a little easier
* librdkafka makes life a lot easier, especially when you can just download a thin wrapper around it for your chosen language
* I am no longer working at the place that chose Kafka 0.8 following no testing at all for their use case, and refused to back down through months of hell both writing code and trying to keep clusters available
* The people at Confluent have done a lot of good work since then, both on Kafka itself and on various auxiliary tools/products.
So yeah, I would probably look at Kafka again today if I needed that kind of functionality. Screw ZooKeeper though.
React is not "eating Angular's lunch". The only reason it seems that way is that it is impossible to have a conversation about Angular on the internet without a horde of React zealots turning up and banging on about it.
Recommending React to somebody who's considering Angular is like recommending tyres to somebody who's shopping for a car.
My advice would be to compile your CoffeeScript to JS, then start from there. That's assuming that CoffeeScript still produces readable, idiomatic JavaScript...?
As of TypeScript 1.8(?) you can set an "allowJs: true" flag in tsconfig.json, which tells TypeScript to include JS files in your build.
Then you can just manually add type annotations and ES2015/2016 goodness to your code and change the suffix to '.ts' on a file-by-file approach.
I'm doing this at the moment with a fairly large AngularJS 1.5 project, using Webpack with awesome-typescript-loader as the build system, and it's working perfectly so far.
As I said in the comment you were commenting on, there is a JVM and a Mono VM. The IDE is running as two processes, one on the JVM (running the IntelliJ shell) and one on, currently, a Mono VM (running the ReSharper engine). They use IPC with a custom protocol to send UI events and ViewModel updates between the processes.
No, they don't plan to integrate Roslyn and they tend to get a bit cross when people ask. They've been working on their C# code intelligence engine for 10 years in ReSharper, and it does stuff way beyond what Roslyn provides at present. I love Roslyn, and I'm using it for code analysis stuff, but it's not a contender for R# yet.
Finally, a proper C# IDE on not-Windows. I've been working with ASP.NET 5 on Linux for the last year and Sublime, Atom, VSCode, etc. are all painful. Sublime is surely dead, and anything based on Electron kills my 2-core CPU and my battery. I was in the talk here at NDC London where they demo'd Rider, and I can confirm that it is very fast and he showed the Mac process view and it was barely hitting the CPU, even with a JVM and a Mono VM running. And when it's all running on .NET Core it should be even faster.
Not a valid comparison. Torvalds still actively rules Linux in every sense. If he'd just created it then buggered off leaving it half-finished, then complained when other people tried to finish it, then yes, he'd be a prima-donna/prick.
If you believe in free will, I'd be very interested to know your beliefs as to whence it derives. If the universe is bound by a set of consistent physical laws governing the behaviour of all energy/matter, then every interaction is predetermined by the combination of those laws and whatever the initial state was. Free will therefore requires a supernatural component that is not subject to those laws and processes. Even at a more macro level, every decision you make is necessarily based on a combination of genetics and the contents of your memory, i.e. the sum of your experiences, and the interaction between those elements.
What we like to call free will is just the deterministic result of processes to complex to be understood, modelled or predicted.
One could imagine the concept recurring outward, since time has no meaning. Maybe when egg has lived all the lives he moves to the next level and finds that he was both egg and the "god", teaching himself.
I make Zudio (http://zud.io), a tool for managing Azure storage, which uses Azure storage for its own system data. I've made it a goal since day one of developing it that I wouldn't use any other tool, and I've successfully stuck to that. It's been an excellent way to drive the development forward.
There is Hadoop, Microsoft have been pursuing it aggressively recently.
SciPy type stuff is best handled using F#, which also works on Mono, and has some features that I haven't seen in any other languages (e.g. Type Providers).
There are multiple .NET web frameworks, including Microsoft's own ASP.NET MVC and Web API, but also OSS efforts like FubuMVC, Nancy, ServiceStack, Simple.Web and more, most of which work as well on Mono as on MS .NET.
As you say, the Node story on Windows has improved lately, and most current languages work as well on Windows as on any other platform.
C# itself is probably second only to JavaScript in terms of cross-platform development: Xamarin for Mac and mobile; Mono for Linux (yes, it's incomplete, but Linux people should be used to that); Unity for game development across consoles, mobile devices, web and traditional PCs. By "cross-platform" I don't necessarily mean write-once-run-everywhere, which results in lowest common denominator dreck anyway, but the ability to reuse your skills and some code in many different environments and domains.
That "feature" would be better with an explicit language construct such as *args or params args[], though. As with so many complaints about JavaScript, it's the default behaviour that is a problem.
* The KafkaREST proxy makes life a little easier * librdkafka makes life a lot easier, especially when you can just download a thin wrapper around it for your chosen language * I am no longer working at the place that chose Kafka 0.8 following no testing at all for their use case, and refused to back down through months of hell both writing code and trying to keep clusters available * The people at Confluent have done a lot of good work since then, both on Kafka itself and on various auxiliary tools/products.
So yeah, I would probably look at Kafka again today if I needed that kind of functionality. Screw ZooKeeper though.