3 ms·
you can't ignore "legacy" applications if your new technology needs acceptance and deployment first and foremost to get out of the toy stage. besides, think of
by pyvpx 11y ago
you can't ignore "legacy" applications if your new technology needs acceptance and deployment first and foremost to get out of the toy stage.
besides, think of all the future cool stuff you can more easily build on top of rump kernel (almost a year in the IRC channel and I still can't recall how I'm supposed to refer to...it) rather than being "stuck" with just Erlang on LINC or Haskell on HalVM etc.
- masklinn 11y agoI'm not saying you can ignore legacy applications but "the future" implies it's the goal. If rump is only for legacy application until they're reworked or replaced it's not the future, it's a transitional tool, and the future doesn't contain rump.