322 karma · joined February 25, 2016
The size of the GitLab is constantly growing and Meltano is adding to GitLabs capabilities, not subtracting. We've hired 2 very awesome Python developers for Meltano specifically. They each have tons of experience in the ELT space.
All this to say, that no one at GitLab has turned their eyes away from GitLab, it's the opposite. This business is here to help GitLab as our first customer. Rather than having GitLab struggle to get it's data tools together, and make business decisions based on that data, we've devoted a whole team to provide a solution while helping the community at the same time.
The idea is to give users a set of default extractors (which are the ones we use internally, so they are battle tested), along with loaders, transformers etc. With documentation on how to build their own. For our MVP, and possibly into the future, it will work similar to Wordpress plugins where you have an extractor directory that you place your extractor which is written following our protocol, and the UI will recognize it and give you choices of extractors to run, same for loaders, and so on.
We do not want to be chasing down every last corner case, for extractors (except for our own) because that's just not a good long term solution, needing constant maintenance (as we've seen already). With user contributions, I believe it can work.
A lot of the solutions out there are fantastic but aren't up to the tasks we are looking for. Why shouldn't the whole life cycle be in one tool, be open source, and be version controllable? That's what we are looking for in a tool.
For me, facts don't help. Visualizing it helps. See https://flightaware.com/live/. I love thinking about the fact that all of those planes that you see on that map will land safely because there will not be any airline deaths in the United States today or this month or most likely this year or for years to come. Many will go through turbulence worse than you've experienced. Some will have to return to the gate for little issues. But all will take off and land and be fine.
Until the recent Southwest accident this year there wasn't an airline accident in the US since 2009. If you fly in the US there aren't deaths per day, per month or even per year. The US went 9 years for 1 death on large scheduled commercial flights.
Even if one plane on that map had one accident with 1 death, today... You aren't lucky enough to be on that plane. If you told me that one plane on that map had Madonna on it, I'd tell you I'm just wouldn't be lucky enough to be on that plane.
Compare the turbulence you feel on the plane to the turbulence in your car. More often than not you will experience way more bumps in your car. The turbulence in your car is more dangerous to you than the turbulence on a plane.
If you want less turbulence than sit closer to the wings. The plane pivots around the wings and I often sit there and see people bouncing around in the front and back but barely feel anything from where I sit.
The larger the aircraft the more experienced the pilots are. The airline jobs used to be (not sure now) hard to get, so you are always going to have extremely qualified people flying your plane. Even when flying on (what my mom calls) a putt putt plane, the pilots on those aircraft have so many hours of flying it's insane. Airlines pilots are often just really boring people (sorry pilots). Your flight may be one of 4 they are doing that day and one of 12 they are doing that week depending on the distance.
Everything is planned out. I mean everything. Even the extremely rare idea of an engine failing during take off. You will be fine even if that happens. http://qr.ae/TUIWQI. Which it won't happen to you, again you just aren't lucky enough.
The turbulence you are scared of is not what brings planes down. They can withstand insane amount of turbulence, way more than you can imagine. That is why the wings flex. So even if you have turbulence that pops opens the luggage bins, it just isn't the thing that causes a plane to crash. A plane doesn't even bat an eyelid from that type of turbulence.
The things that have caused planes of the past to crash, have a really nil chance of happening today, because when bad things happen they fix them so they never ever ever happen again. Millions and millions of dollars go towards researching and fixing the problem.
Even small accidents cost airliners insane amounts of money and horrible PR. That recent Southwest flight accident will wind up costing Southwest Airlines > $100 million dollars. You can bet that they are going to research the crap out of that accident to make sure nothing like that ever happens again.
If all that fails, go to your doctor and tell him that anxiety is preventing you from living your live because of a fear of flying (it is) and he will prescribe you an anti anxiety medication to take ONLY on flights. After which, I promise, you will LOVE flying and you can live your life again.
The idea is that there's a lot of different users using git and I want to make it accessible for everyone.
The plan is:
1. Split up the files.
2. Get rid of the as much of the dispatcher.js as we can and have web pack do the routing dynamically. That would eliminate most of 1 large confusing file (dispatcher.js). JS is still cached for the pages you visit but it isn't 1.5mb of JS it would be ~20kb of JS.
Also, I am wondering if you were looking at a much older version of GitLab with the discussion and the UI being unreadable. We've made a ton of improvements to our UI in the past year. If you are looking at a recent version, can you tell me what is unreadable about the discussions and the UI in general? That way we can fix it.
Here is a link to our current CSS Refactor plan which will reduce the size of our CSS significantly and reduce render times. https://gitlab.com/gitlab-org/gitlab-ce/issues/42325.
We've got a lot in the pipeline. In the process we won't be shipping any new features, unless you call blazing speed a feature.
Just because a doctor hasn't solved your problem yet, doesn't mean you should give up. You don't want to take advice, and self diagnose with web advice.
Now pretend I didn't say all that, and check out BPPV. If it is BPPV, then you can have someone do the Epley maneuver on you and you'll be fine. Dizziness is incredibly stressful, and the rest of your symptoms can be associated with stress. The fact that it comes in waves makes me think that it could be the crystals in your ears moving around.
But seriously. Don't take medical advice from someone who isn't a doctor.
> with 100 megawatts of capacity.
Isn't megawatts the measurement of power? Wouldn't Watt Hours be the measurement for capacity? Sometimes people use Apmere Hours also. Like the Chevy Bolt has 60 kWh of capacity.
> Why write something that exists?
B/c it's good to have more than 1 opinion. If someone has successfully started a startup or 2, I would want to hear their story. Looks like the writers have some experience. I'm not big into relying on 1 bible.
Funny thing, I have built a full fledged production 2d/3d application in JS. It was less complex than what GL has to do, and it was 670kb fully minified and obfuscated. We are constantly looking for ways at GL to make our file size smaller and our JS faster. It is something we are actively putting our time towards.