RamBox



  • In my quest to move my Macbook Pro to Korora, I have 2 things holding me back:

    1. Microsoft Teams native Linux client
    2. OnePassword native Linux client

    So far, MS Teams has no native client, and OnePassword, has something coming for Linux but it is still in early alpha release. Then I stumbled upon Rambox. Has anyone used this before?

    http://rambox.pro/



  • Sounds like all the other "all in one" things.

    I am willing to bet that it does nothing but wrap the web interface of all these various solutions. There are many of these types of wrapper programs.



  • @JaredBusch After a bit more research, yep, it looks that way. I think if I wait just a bit longer, Teams and OnePassword will be available on Linux, and then I'll make the full switch.



  • @fuznutz04 said in RamBox:

    @JaredBusch After a bit more research, yep, it looks that way. I think if I wait just a bit longer, Teams and OnePassword will be available on Linux, and then I'll make the full switch.

    Does Teams not work in a browser? I've used it and was not even aware of there being a client. Isn't it just like Slack which is just a wrapper around the browser anyway when you install a client?



  • @scottalanmiller

    Yes, it will work in a browser, I just like the client better. Most things MS, I use in a browser, (Outlook mainly) but with Teams, I like the client. It's not a deal breaker, but rather a preference.



  • @scottalanmiller said in RamBox:

    @fuznutz04 said in RamBox:

    @JaredBusch After a bit more research, yep, it looks that way. I think if I wait just a bit longer, Teams and OnePassword will be available on Linux, and then I'll make the full switch.

    Does Teams not work in a browser? I've used it and was not even aware of there being a client. Isn't it just like Slack which is just a wrapper around the browser anyway when you install a client?

    The Slack client is not just a wrapper for the slack web interface.

    Just as Outlook is not a wrapper for OWA.

    Both may use the web protocols to get the content to display, but there are many other pieces around that content that are built into the client.

    No matter how much you try to claim OWA is great, it is not. Outlook is a much better interface for Exchange email. But like all better things, the cost is generally not worth it for most users because they do not need those extra features.



  • @JaredBusch said in RamBox:

    No matter how much you try to claim OWA is great, it is not. Outlook is a much better interface for Exchange email.

    And vice versa. I don't think OWA is great, I think Outlook is terrible. I just think OWA is slightly better.



  • @JaredBusch said in RamBox:

    The Slack client is not just a wrapper for the slack web interface.

    Some of its clones are ACTUALLY wrappers.



  • @scottalanmiller said in RamBox:

    @JaredBusch said in RamBox:

    No matter how much you try to claim OWA is great, it is not. Outlook is a much better interface for Exchange email.

    And vice versa. I don't think OWA is great, I think Outlook is terrible. I just think OWA is slightly better.

    Yes, but it is your opinion. Not a gospel truth.

    And circles back to the point here. Just because something like Teams is available in a web interface does not mean that it is the desired use.



  • I never got the Slack app because I figured it was literally a wrapper. Downloading now.



  • @scottalanmiller said in RamBox:

    @JaredBusch said in RamBox:

    The Slack client is not just a wrapper for the slack web interface.

    Some of its clones are ACTUALLY wrappers.

    You mean some alternate slack clients? Of course.

    They are not clones. that would be theft. They are third party applications using API calls.



  • @scottalanmiller said in RamBox:

    I never got the Slack app because I figured it was literally a wrapper. Downloading now.

    The last time I used the Windows client it was noticeably different. But that was over a year ago. I have never been a big Slack user.



  • @JaredBusch said in RamBox:

    @scottalanmiller said in RamBox:

    I never got the Slack app because I figured it was literally a wrapper. Downloading now.

    The last time I used the Windows client it was noticeably different. But that was over a year ago. I have never been a big Slack user.

    Looks like a wrapper. It's pixel identical to the web page. No features or anything different from what I can tell.



  • So if it used to not be a wrapper, maybe Slack is cloning Rocket.Chat now rather than the other way around.



  • @JaredBusch I use OWA because I switch back and forth between my Windows Desktop at my home office, and my Macbook while I am in the office, and traveling. While I could run Outlook on both the Windows box, and run Outlook on the Mac side, I think the Mac Outlook version sucks. So, I use OWA.



  • @fuznutz04 said in RamBox:

    @JaredBusch I use OWA because I switch back and forth between my Windows Desktop at my home office, and my Macbook while I am in the office, and traveling. While I could run Outlook on both the Windows box, and run Outlook on the Mac side, I think the Mac Outlook version sucks. So, I use OWA.

    I find OWA more mobile as well, but Outlook does handle moving between devices pretty easily.



  • @scottalanmiller said in RamBox:

    @fuznutz04 said in RamBox:

    @JaredBusch I use OWA because I switch back and forth between my Windows Desktop at my home office, and my Macbook while I am in the office, and traveling. While I could run Outlook on both the Windows box, and run Outlook on the Mac side, I think the Mac Outlook version sucks. So, I use OWA.

    I find OWA more mobile as well, but Outlook does handle moving between devices pretty easily.

    Yes, it does. On the Linux side, would you use a local mail client, or still stick with OWA?

    If a native mail client, which one?



  • @fuznutz04 said in RamBox:

    @scottalanmiller said in RamBox:

    @fuznutz04 said in RamBox:

    @JaredBusch I use OWA because I switch back and forth between my Windows Desktop at my home office, and my Macbook while I am in the office, and traveling. While I could run Outlook on both the Windows box, and run Outlook on the Mac side, I think the Mac Outlook version sucks. So, I use OWA.

    I find OWA more mobile as well, but Outlook does handle moving between devices pretty easily.

    Yes, it does. On the Linux side, would you use a local mail client, or still stick with OWA?

    If a native mail client, which one?

    I use OWA. I tried Nylas, but something about my O365 account made it sluggish when it isn't with my other email. I don't use Exchange for my primary email, so OWA is fine. It's not Zimbra, that's kicking its butt in usability, but it is okay.

    It's nice to have moved back to something better than Exchange. I forgot how much I preferred it.



  • @scottalanmiller said in RamBox:

    So if it used to not be a wrapper, maybe Slack is cloning Rocket.Chat now rather than the other way around.

    They both use Electron to provide their "desktop clients".



  • @Romo said in RamBox:

    @scottalanmiller said in RamBox:

    So if it used to not be a wrapper, maybe Slack is cloning Rocket.Chat now rather than the other way around.

    They both use Electron to provide their "desktop clients".

    I knew that Rocket did. So Slack copied that from them?



  • @scottalanmiller said in RamBox:

    @Romo said in RamBox:

    @scottalanmiller said in RamBox:

    So if it used to not be a wrapper, maybe Slack is cloning Rocket.Chat now rather than the other way around.

    They both use Electron to provide their "desktop clients".

    I knew that Rocket did. So Slack copied that from them?

    Don't really know, I know they were using Electron for the windows app almost since the beginning and just last year change the mac version from MacGap to Electron as well.


Log in to reply