3 ms·

That doing all of this stuff via rpcs vs function calls is crazy I believe.

• iainmerrick 9y ago
  He's not totally wrong, but casting it as a 100% clear-cut decision -- with the RPC version as the obviously bad, "highly damaging" choice -- is just wilfully stupid and dishonest. It's clearly a tradeoff.
• pjmlp 9y ago
  Specially from security point of view. There is a reason why most of us learned our lesson and moved plugins out-of-process. Performance can still be achieved via shared memory, exposing much less data from the host process.
• emmelaich 9y ago
  Not only via rpc but json over rpc, because latency. He has a point but there's nothing to stop you bringing some of this in-process or caching aggressively.
• Too 9y ago
  Maybe if your code lives in a small bubble with everybody using the same IDE but definitely not for larger projects. For huge projects you want the build/index performance from a fast build server rather than a laptop, buildi environment inside a docker container, IDE in windows and build in linux, free choice of IDE rather than tighlty tied plugins. Though i fully agree that json might not be the best packaging.