I think, some of the issues here is that first nextcloud tries to be compatible with any managed / mutualized hosting.
They also treat every "module"/"apps" whatever you call it, as completely distinct spa without proving much of a sdk/framework.
Which mean each app, add is own deps, manage is own build, etc...
Also don't forget that app can even be a part of a screen not the whole thing
sorry but that is simply not true...
I think there are areas where it can be, probably those more remote, or where there are less contributors
but at least in western europe, the map is built and maintained by individuals like me. Maybe helped with external datas but still carefully handpicked and integrated by individuals
Elium | Senior Software Engineer Front-End | Belgium | Full time, onsite/Remote (EU time zone) | https://elium.com
Elium is a knowledge-sharing platform that helps users capture, curate and share essential information and successfully collaborate.
Our stack is React, GraphQL, Relay, Webpack, Python, PostgreSQL, React Native.
Apply here: https://apply.workable.com/elium/j/7DCB66650F/
Get in touch with us: [email protected]
Elium | Software Engineer Front-End | Belgium | Full time, open to remote (EU time zone) | https://elium.com
Elium is a knowledge-sharing platform that helps users capture, curate and share essential information and successfully collaborate.
Our stack is React, GraphQL, Relay, Webpack, Python, PostgreSQL, React Native.
Nice I was looking to test this at work... But not sure if login does not work for me (and my buddy) or something else.... But we kept beeing redirected to the login button
Yeah but what it state here is that if you want to add a limit on field size, then add a check constraint... Much easier to deal with than changing type
It's me or a lot of those points don't explain anything?
I totally get they don't want to open source it as a company but don't try to give false reason for it.
It's not because it's open source that you can't have quality, central design, or good documentation.
I've used the mysql FDW for a project at work, it was really helpfull. We've replaced an old "ETL" using a bunch of hard to maintain scripts to mysql_fdw and some materialized view.
It was easier for us because it helps write maintainable logic, you can easily sync multiple databases, multiple servers, without much changes.
A few things to note though:
- we had issues with 0000-00-00 dates that are valid in mysql but not in postgres. So we had to write include a convertion in plsql into the mat view.
- We stumble upon a bug in mysql_fdw, in which the selected row is skipped if the size of a column exceed a given size. This is reaaaaally hard to catch and really bad experience as you won't get any error, notice or warning.
- we had trouble with a few type casting like json and others.
got it running on osx, first it didn't worked (nothing suggested), then i've restarted it and it seems to work.
pretty basic, but it more or less match my needs.
the only thing that i miss is the file icons or app icons:
it show you multiple match but the icons are all the same, dark, so you can't quickly disambiguate them
I'm pretty happy with gitlab too,
but if i had to compare it with github i would go:
- gitlab.com is neat but often has 5XX or is often pretty slow
- doc is somewhat messy i rarely find what i'm looking for.
- UI/UX get better but still confusing.
- notifications are not clear and i often get what i don't want (my own things) and not what i want (what other did)
Nice! Good release !...
One thing that make the user experience way less friendly and make me worry about pushing as our main repo is the git push/pull speed....
Coming from GitHub or bitbucket it feels really slow. But I don't give up hope!
I'm also in the process of moving from jenkins to gitlab... and until now, the process is pretty smooth and easy ...
gitlab-ci is easier to grasp and to work with... the only issues i got is about things like publishing build results (lints check or test results /counts ) althoug there is basic support for artifacts. it's not easily possible (at least for now) to fetch the artifacts for a given commit or branch without doing multiple api calls.
They also treat every "module"/"apps" whatever you call it, as completely distinct spa without proving much of a sdk/framework. Which mean each app, add is own deps, manage is own build, etc...
Also don't forget that app can even be a part of a screen not the whole thing