• 0 Posts
  • 69 Comments
Joined 3 年前
cake
Cake day: 2023年6月28日

help-circle




  • peak of UX

    Good UX.

    give an example

    Already have provided 1 of many examples: classing. Applying a type to the communication relevant to the business. To the process it could be scope, direction, decision ect. This can route, tag, extract, modify and move/copy messages automatically to target services.

    Just to be clear I am not advocating for building Microsoft Lotus notes (Teams), not at all. Quite the opposite.

    However jumping between apps is how mistakes are made, and evidence lost from laziness or “too busy”. IMO Email communications should only be handled by Outlook or a dedicated email client that has the depth of functionality for good communication. Addins provide the middleware between different products and services to integrate them. It can even be completely transparent to the user.

    Bringing this back to the topic. The shift to the web only Outlook means no more BYO libraries, no more .net , no more OS api, no more COM api. These provide an enormous amount of capability for addins to leverage and provide integration. Now with website Outlook, the api is incredibly limitted and entirely controlled by Microsoft, there is no BYO libraries and connectivity and those existing web api’s can and are removed at whim removing the ability to conduct business on 365.

    So if someone can build an app like Outlook that has rich email, calendaring and pure depth of functionality that it has. This would be a massive barrier removal if not in my oppinion the last barrier for mass business FOSS adoption.


  • So you’re advocating for slowing process, bad user experience, and duplicating shitty email functionality in every app to receive and send email limiting communications. Got it.

    people dont get familiar with UX

    Yes they do. Duplicating email into other systems that doesnt have anywhere near the same functionality and flow as their dedicated email app which is designed for email is frustrating, and restricts communication.

    ticketing system

    Wtf does classing have to do with ticketing systems. It applies to records management, project management, legal case management, the list goes on. It applies to most business

    using email for business process must die

    Oh my sweet summer child. I’ve got news for you: email is HOW business is conducted. That is not going away any time soon.


  • Your claim with the api is outright wrong. The difference is between client side and service only api the rest is hyperbole. That gap is MASSIVE functionally. Client api is responsive, fast, access to local OS and local hardware. Service side has its place, but its service limited only. Severely limits access to other services which is very important when moving data.

    You have conflated User Experience with User Interface. I didnt say UI for that obvious reason. The experience matters a lot. Having to open and process the same flow of task from one app to another app breaking concentration is bad fucking UX. Losing context is bad UX the list goes on. it reduces accuracy, & performance and ultimately productivity. Something as simple as classing becomes simple when the context of the conversation is very easy to get and more accurate when you dont duplicate an entire chain.


  • Highly doubt it, maybe a small organisation which would make sense by your comments.

    Outlooks feature list is huuge. Large list of functions in Calendering alone is unmatched.

    most of these things are dying out.

    Bollocks.

    The API is the backbone for large organisations that extends that large amount of Outlook functions beyond 365 limited services. That is being cut off in an anticompetitive move by Microsoft. It allows for information management and automation to be verified by people with simplicity and a familiar UX.



  • An Outlook replacement. The new web Outlook is absolute garbage with zero addin api like the old one had

    Make a replacement Outlook that connect to imap service or something that’s close to feature matching (calendaring ect) and its game over for two huge revenue streams. it’s a cornerstone of Enterprise 365 and they refuse to listen to clients.

    Everything else is “good enough” in FOSS but nothing gets close to Outlook functionally.



  • Thanks. Nix made me a convert back from Windows. Microsoft doesn’t innovate anymore like they used to. iMO the origional concepts that sparked nix and now others like it has been a breath of fresh air into a stagnated critical cornerstone of the industry. Imagine being able to install every version of a dependancy like say .net thats ever been released without it causing a problem.

    Install is imo better than even Windows, install from media, highly recommend kde plasma or gnome on your first round, but hey its nix, sky is the limit. Hardware will autodetect so long as you dont have anything out of ordinary.

    Config once cry once cant be over stated enough how good it is. As for your concern about changes its really simple. Make the change, run the update command from terminal, reboot and if it fails (rare) juat reboot again and select your previous config, it keeps as many configs as you want to. I now only maintain the last 5 and run a cleanup confidently.

    To update to the latest versions of apps and os its one command in terminal and nix checks your config for errors before updating. Some people run bleeding edge versions & update daily getting nightly apps, OS, and kernel even without issue. I sit on unstable, silly name, its stable as all hell, you just get the latest releases and features.

    My worst experience was moving to home manager, but it was well worth it. The error nix presented was meaningless, the real error was just buried and I had to use journald to find the meaningful error.

    What ever distro you use enjoy the freedom! Mint is great, Nix is great!




  • Mint is amazing and frankly if its working for you then I think you’ve found it. I stayed on mint for a long time until I relented to a nagging friend and tried out NIxOS and was amazed. If you have the technical skills and feel confident to push through the inital difficulty its well well worth it.

    So whats the good?

    1. Reproducibility. Ever been annoyed that someone cant help you because they either dont have the time or just cant reproduce the problem? Its no longer an issue. Dependancy is managed by design so configuration and state is transferable with as little as only two files.
    2. Declarative. Best way to decibe this is all the benefits of Arch and zero of the problems. Declare your configuration in a file and then have a life. Ive never saved so much time before with any distro. Imaging installing windows, configuring the OS, installing apps, configuring them only once, ever, never having to do that again. Reinstalls go straight back to the way you like it.
    3. Reliable. Ive never had a linux distro so stable. The risk and pain of change is a thing of the past.
    4. Largest and most up to date repo. Its simply unmatched.
    5. The list goes on to other areas like security, scalability and much more but lets leave it there.

    Whats the bad?

    1. Difficulty of entry. You need to have basic understanding on writting basic code to some degree as you define your config as a simple text file. I recommend vimjoyer on youtube he has some great simple intro videos that will help here.
    2. Using apps not in the repo. You will need to step up your config skills here to install that weird app you want. That is only unless you cant wait. If you have time the community is fantastic, a quick app request on the repo has a great chance of being picked up by some legend and added to the repo officially.
    3. The wiki, its no Arch wiki, thankfully you dont really need it. The community maintains a bunch of configs for hardware and apps on the repo which is weirdly not advertised half as much as it should be. Alternatively just search github for configs from other nixians.