Happy to answer questions — and feedback on the physics or the explanations is very welcome. This project might be totally inaccurate in terms of real physics, this is how i do understand this on my own - i'm happy to confront this with reality

Comments URL: https://news.ycombinator.com/item?id=48459837

Points: 217

# Comments: 56

Exactly. Other products comes with opinionated workflow or are much easier (and simpler) to use. Once you setup Jira way you wanted (good luck with that) and able to maintain this setup for all of your projects you're stuck with Jira forever - you won't be able to export all of your content to another software. The whole process takes ages and its a nightmare of going thought totally different UX pages, unintuitive settings, slow UI, setting up extremely expensive plugins (why till today you need to buy tempo to get basic functionality like time tracking) etc.

It's called vendor lock. Nobody ever got fired for buying Jira

Other products are not for every business, have limited settings - but are quicker, saves you time and are able to be useful since day one.

All of the companies are using Jira differently, even if you're familiar with this, and you have been using Jira in all you provious jobs for years you still need to have onboarding on how does Jira works in current company - as for instance I've worked with Asana in 3 totally different companies and workflow was the same.

Never ever have I seen such a rich product that had everything and was easy to learn - back then their todo tutorial took less then 1 hour, after you had fully working todo app.

Yet too much magic was not what developers wanted, during the process you felt like loosing control over the processes you don't understand nor have access too.

Compering this to building a standard app back then with REST API, and backbone/angular/react frontend seems like saving tons of time, yet developers decided on the latter in most of the cases.

> It soon became clear that the community was splitting into two camps: those who appreciated Meteor’s clear value proposition of simplifying web development by providing an all-in-one environment, and those who wanted more openness towards the npm ecosystem to avoid being left behind by the rest of the webdev community.

That seems to be a case. Also lack of people that wanted to use this in production and cost of developers.

My last app in meteor was written in 2017, after hitting success everything died, even after adding 10x more CPU and RAM. Problem was that Mongo/Magic was sending too much data, multiplying this by few thousands users caused killing node.js server in seconds. Using Kadira profiling and 2 nights of coding problem was solved and app was running fine, both web and mobile (meteor cordova). Client was happy, same with users - it was success. After investor came in, they decided it must be rewritten, because at that time, there were only 2 or 3 companies in Poland that knew that technology - investor decided its a bottleneck - whole thing was rewritten to Java Spring and Angular (or something similar).

PS. I wrote a post about the case in 2018 https://medium.com/qunabu-interactive/tuszama-case-study-met...

Comments URL: https://news.ycombinator.com/item?id=31861954

Points: 2

# Comments: 0

out of the box you get free `jitsi` but you can attach your own instance as well

There are some issues like accessibility, browser features like search or text highlighting, lazy loading etc. What HTML provides out of the box must be implemented from scratch.