alceta

> Sorry, this post has been removed by the moderators of r/jira.

Good to know they value this kind of information /s

Same here. I was actively showing the (scammed) live stream to my 4yo daughter, and had to switch back to the live version for yet another 10minutes of wait.

Quite the embarassment, I think I begin to understand how my parents feel when they are completely unaware of some technical aspects I try to explain, and how easy it would be to scam them. Seems like it is getting easier to scam me, too.

To be fair, once they switched to Fakelon, it was quite clear. But I started the same stream again later as the YT app does not properly highlight the channel's name before clicking.

lazygit (https://github.com/jesseduffield/lazygit) is enlightenmentware for me. It helps me navigate Git commands I forget all the time, like using the reflog to undo things, custom patches, or rebase --onto.

It makes working with Git a lot more fun, and I giggle like a little child whenever one of the weirder things work out again.

Core maintainer of OpenProject here. We do welcome all outside contributions, but please note that while the application relies heavily on Ruby/Rails for backend, API and rendering, a large portion is also Angular/Typescript.

This will sometimes make it harder for developers to start working with OpenProject since for many topics, you will need both (e.g., API changes and frontend work). Especially so since the application has evolved for more than 10 years.

We recently did work on a "big picture" documentation for new developers to understand some of the concepts at play: https://docs.openproject.org/development/concepts/

Core maintainer here, I agree that this should be more discoverable. I will forward this to include a comparison link on the feature page itself.

Core contributor of OpenProject Here, this ist an Epic that ist high up in the roadmap but due to its complexity has been pushed out the past two releases.

This is something where we know it's painfully missing and is being planned and actively worked on.

Absolutely second that Freelancer was an amazing game, I loved both the single player and (modded) MP with role playing. Tried Eve Online but it's just a completely different genre.

As a user that made the switch to bitwarden the last time 1Password tried their shift to the membership-only options some 1-2 years ago, it is an excellent replacement. I do miss some better search / sorting functionality, but otherwise this works great with a local server that I maintain for keeping my Mac, Ubuntu, Windows and Android devices in sync.

Told my wife a few years ago that I do get goosebumps and she wouldn't believe me, so I know of at least one person who doesn't

I cannot upvote this enough. We have long decided what to do with our painful angularjs application with thousands of beginner mistakes due to people learning a framework while using it.

In the end, we were able to partially migrate to angular 4 at the time using ngUpgrade while still using parts of the application in angularjs 1.6. luckily we started looking into typescript beforehand, making it even easier.

It took us 3 months to completely migrate with only a tiny fraction of legacy bundle of code now still running on angularjs until it's being converted

Since then I have done every major upgrade without fears. I wholeheartedly recommend it for medium-large applications (we have around 50k cloc typescript now).

Angular + Typescript keeps us and our frontend saner than before.

One thing I sorely miss is the performance of my manual webpack / angularjs build, with 15seconds initial build and 1-2 seconds incrementals... It's now at least double with the angular cli, but at least fully managed.

Current stable version Ruby 2.6.2 with --jit is actually faster than Python 3 according to this: https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

Went exactly the same route a few weeks ago deciding between a new macbook pro or something else and went for the P1. Had some troubles with the UEFI due to outdated firmware (be sure to update that first thing) and other than that, I'm quite happy with the results. Battery life could be better, the fans are indeed more aggressive and I miss some of the touch gestures (swipe for browsing) that I didn't yet get to set up. My previous device was a late '14 MBP and that still works fine but is getting slow and quite hot.

We went with CKEditor5 with a commonmark backend and I cannot recommend it more highly. commonmark data is converted upon initially opening and when closing the editor, allowing all native functionality to happen efficiently.

However I do note that we do not yet have a production ready backend for collaborative editing. I would suggest to use their service if possible, since we're developing an open source product it would not be an option for us.

There is a quite leaning curve when implementing new plugins due to the strict separation of model and data (commonmark in our case) and user-facing views.

I can fully second this approach. We migrated away from a plain AngularJS application in 2016. The sheer number of bugs we have since been able to prevent by the (ever improving) strictness checks of Typescript is staggering.

And all that, with what I believe is excellent documentation and support. I mean you're getting a getting started comment from the lead managers on the project

Thanks Daniel!

My Firefox Klar (Focus in German market) does have multiple tabs. But since the entire application is shorter-lived, I never tend to have many tabs open.

As a long time 1password user (at least since 2009), I switched to Bitwarden late last year and did not regret it.

I did not look into it mainly because we cannot afford a rewrite, and the ngUpgrade module provided us with a way to write new code without replacing everything in one go (and breaking the entire frontend in between).

Wow, great. Did not look into that before, many thanks for pointing that out.

I was joyfully expecting this upgrade and checked the release notes daily during the RC phase. Don't let the quick 'major' version changes shock you, upgrading 4 -> 5 was easy and I expect the same for this upgrade.

A big thanks to everyone involved in shaping this release and ensuring the upgradability for the past major versions, including the huge effort in making it possible to continuously migrate from AngularJS. <3

If you care for the details behind my experiences:

We have begun migrating a ~80k loc AngularJS codebase first to TypeScript in 2016, which was the preparation for the Angular upgrade starting Q1 this year. Now we are roughly 80% migrated to Angular 5 (in the meantime we did the upgrade from 4 to 5 in a few hours thanks to https://update.angular.io/), the rest running with ui-router hybrid [1] and ngUpgrade [2] and now are looking forward to moving the rest to Angular and upgrading to 6.0.

Coming from AngularJS where many things are done without a proper reason, I have started to embrace and even somewhat love Angular for the niceties it brings it. When you already embraced TypeScript, it is a breeze to work with and I cannot recommend it enough (for large-scale frontends this is).

The one pitfall I always ended up with during the migration was that AngularJS attribute directives cannot be converted to Angular and then downgraded (In the hybrid app, the entry component is always(?) AngularJS and up from there), which is a large part of the remaining AngularJS code. There are a few workarounds but they did not seem to work properly. If anyone has suggestions on that part.

[1] https://github.com/ui-router/angular-hybrid [2] https://angular.io/guide/upgrade

You're writing that users suffer from edge cases from the individual webdriver implementations. My experience as someone working with gecko and chromedriver on a daily basis is that the number of edge cases stemming from browser behavior (such as moving to, clicking, and focusing on elements) is a much more frequent pain than differences in the webdriver implementation.

We use bootsnap for the development more of our rails Backend / Monolith and it's a breeze for startup especially when running single tests locally. I have never experienced any issues since we introduced it last autumn.

It will not help too much for production or testing environments if you do not have specific timing requirements on startup.

It's a completely different type of shoe compared to things like spring which will result in a world of pain in specific situations if you're not constantly aware of what it does.

In Ruby, the exact same problem applies since you can publish gems in one version and tag them in another - in the very same fashion as the article describes.

Well then let me thank and congratulate you for your efforts in building this.

As a long-time dash user in the past, devdocs felt like home and just works nicely and without any unnecessary features.

Your note is very appreciated. I'm currently in the early stages of deciding on an editor/framework that we need to build upon for custom features. CKEditor just went up the list after looking at it.

ProseMirror was up there from recommendations from a colleague who has worked with CodeMirror as a basis for a collaborative editor before, but it needs more work for basic features.

If anyone even remotely involved with the maintenance and development of pg reads this thread - Thank you! - for all your efforts in building and improving a first class product that keeps me amazed at the strides it takes with each major. release.

I'm tired of these superlatives like 'THE best editor', it adds nothing to the quality of a blog entry.

Looks nice, Looking forward to the live demo :)

We're currently employing OpenProject[1], a Chili/Redmine fork with extensive Agile/Scrum[2] functionality. Despite all valid points against Redmine being bloated, it provides many features often lacking elsewhere (Auth Providers such as LDAP / Single-Sign On, Plugins).

[1] http://openproject.org/ [2] https://www.openproject.org/projects/openproject/wiki/Agile_...

I very much enjoyed the author's Blog series on a blog written in Flask [1]. I did not (yet) buy and read the book, but from his style on the blog, I can only assume it is a great resource on Flask.

[1] http://blog.miguelgrinberg.com/post/the-flask-mega-tutorial-...

There's a difference in all variations he wrote to have stumbled upon. For demonstration, the Google Translate tool pronounces it correctly using the Listen button on the left [1]. The correct one, 'Hügel', is different from both 'Hugel' and 'Hoogle', which can be pronounced as in English (cf., Google) and German (e.g., comparable to Woog [2]).

Even if the 'right spelling' is still wrong from the german word origin, hoogle is probably easier to pronounce in english than using 'huegel' and most certainly easier to type without the umlaut anyway. Still, that remark ('[...] spent some time with google to find the right spelling') made me smile, as none of these variants are really correct.

[1] https://translate.google.de/#de/en/Hugel%20ist%20kein%20Hueg... [2] https://translate.google.de/#de/en/Woog

I opened the comments track to say exactly this. Every lecturer with any connection to software would bring this up. It felt like the bad (as in, people have died from Therac-25 malfunctions) running gag of my CS studies. Other popular bug choices were the Pentium Bug from 1994 or the Mars Climate Orbiter.