5 ms·

These things come and go. One could have been just as wrong to focus on Silverlight, OpenSolaris, SmallTalk, etc, etc, etc, or even your own company's ABI....

by rch 8y ago

These things come and go. One could have been just as wrong to focus on Silverlight, OpenSolaris, SmallTalk, etc, etc, etc, or even your own company's ABI.... And is it really wrong to spend a couple of years becoming an expert Plan 9 user just because it doesn't take over the world? I still think it's all (mostly) time well spent.

bluehazed 8y ago
It is never a waste of time to become a Plan 9 user!
chaostheory 8y ago
The risk is less when the technology is open source. With open source, at the very least you or someone else can help steward the technology if it's that important to your company.
coldtea 8y ago
>And is it really wrong to spend a couple of years becoming an expert Plan 9 user just because it doesn't take over the world? I still think it's all (mostly) time well spent. https://en.wikipedia.org/wiki/Opportunity_cost https://en.wikipedia.org/wiki/Opportunity_cost
- sterlind 8y ago
  it's hard to gauge opportunity cost, since architectures fade in and out of popularity and patterns succeed where the frameworks that introduced them fail. I doubt Rob Pike and Ken Thompson would give up the experience of writing Plan 9; its lessons persist in Go and other systems they've designed. Google's tech stack was pioneered by systems programmers who built their career writing for supercomputers, forced to target commodity hardware. Patterns have a much longer shelf-life than their originating products.
  - coldtea 8y ago
    >it's hard to gauge opportunity cost, since architectures fade in and out of popularity and patterns succeed where the frameworks that introduced them fail. It might be hard but it's also necessary. That's true for many other things that are hard. What would the opposite be? Have people adopting any new technology and losing several years of their lives studying a doomed fad because without evaluating its long term potential and opportunity cost because it's "hard" and "architectures fade in and out of popularity"? Instead, we should encourage people to do the hard thing, and evaluate things that they intend to study and their opportunity cost before they devote any substantial time with them. Some will still get it wrong and invest in the wrong tech, but overall doing due diligence before jumping in will be better than just blindly going for whatever catches their fancy or is hyped. >I doubt Rob Pike and Ken Thompson would give up the experience of writing Plan 9; its lessons persist in Go and other systems they've designed. That was their job and they were paid for it. And Plan9 was also their own creation and original research. That's not the same as some third party devoting themselves to a new technology just because it looks cool, it's hyped at the moment, etc.

by rch 8y ago

bluehazed 8y ago

It is never a waste of time to become a Plan 9 user!

chaostheory 8y ago

The risk is less when the technology is open source. With open source, at the very least you or someone else can help steward the technology if it's that important to your company.

coldtea 8y ago

>And is it really wrong to spend a couple of years becoming an expert Plan 9 user just because it doesn't take over the world? I still think it's all (mostly) time well spent. https://en.wikipedia.org/wiki/Opportunity_cost https://en.wikipedia.org/wiki/Opportunity_cost

sterlind 8y ago
it's hard to gauge opportunity cost, since architectures fade in and out of popularity and patterns succeed where the frameworks that introduced them fail. I doubt Rob Pike and Ken Thompson would give up the experience of writing Plan 9; its lessons persist in Go and other systems they've designed. Google's tech stack was pioneered by systems programmers who built their career writing for supercomputers, forced to target commodity hardware. Patterns have a much longer shelf-life than their originating products.
- coldtea 8y ago
  >it's hard to gauge opportunity cost, since architectures fade in and out of popularity and patterns succeed where the frameworks that introduced them fail. It might be hard but it's also necessary. That's true for many other things that are hard. What would the opposite be? Have people adopting any new technology and losing several years of their lives studying a doomed fad because without evaluating its long term potential and opportunity cost because it's "hard" and "architectures fade in and out of popularity"? Instead, we should encourage people to do the hard thing, and evaluate things that they intend to study and their opportunity cost before they devote any substantial time with them. Some will still get it wrong and invest in the wrong tech, but overall doing due diligence before jumping in will be better than just blindly going for whatever catches their fancy or is hyped. >I doubt Rob Pike and Ken Thompson would give up the experience of writing Plan 9; its lessons persist in Go and other systems they've designed. That was their job and they were paid for it. And Plan9 was also their own creation and original research. That's not the same as some third party devoting themselves to a new technology just because it looks cool, it's hyped at the moment, etc.