What I did is a straight forward model, yet it's still complex. The way to figure it out how it works by observation from earth without tools we have now it's insane. How Copernicus, Kepler, Galilei, Newton, Hubble, Einstein figure it out it just amazing. Science deserves all the kudos!
I've just published the first batch of patches and new features. I've learnt a lot during the process and from the comments which was one of the main goals, so I'm really happy about this process. Thanks again!
Not in the sim right now — it's purely Newtonian (symplectic leapfrog, classical gravity). I show the concept on the last slide ("Einstein: gravity is curved spacetime") — a curve in space wrapping around a star/planet that pulls nearby objects into the well. The quantitative case, Mercury's ~43″/century perihelion precession, I'd add next as a 1PN correction — haven't gotten to it yet. Will try to figure it out how to show this
It works pretty well on iPhone, except the descriptive text fills most of the bottom half of the screen, overlapping the sim which is centered on the screen.
If the sim were instead centered on the free space (the top half of the screen) it’d be perfect.
> But there is no competing product (suite) that offers comparable functionality. Many companies have built entire workflows (not just development related) around Jira, and have huge knowledge bases in Confluence. Switching would come with a lot of effort.
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.
One could say Jira is like SAP. Theoretically it's just a software, but in the end there is so much customization that the business starts to revolve around its processes.
True that, but it's not their fault, it's just their turf. They need to solve business needs for core processes in a sufficiently generic way to be applicable to any big enterprise. The only way to achieve this is through heavy configuration/parameterization.
Meteor was first ever magic web technology I've ever used. The fetching from backend that you wouldn't even see in developer tools, one code base for frontend backend, straight forward cli, developer selection between jquery/react/angular, kadira, build-in simple cordova
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).
reply