hattery VS notabase

While I think there's a lot to love about Java, I think the standard library itself is not an especially great role model. Most of it was written a long time ago and has a fairly antiquated style - lots of mutable state, nullability, and checked exceptions. Not that the library isn't an incredible asset - it's luxuriously rich compared to working in Node.js - but if it were written from scratch today, I suspect it would look fairly different. Eg, the collection classes would use Optional and have separate read/write interfaces.

For an example of "modern Java" I would point at something like this (which I wrote, sorry about the hubris):

https://github.com/stickfigure/hattery

I have been thinking of writing up a series of articles on this. Without going into too much detail:

* IDEA

* Deploy on Google App Engine, Digital Ocean App Platform, Heroku, Elastic Beanstalk, etc - get out of the ops business entirely.

* Guice as the backbone, no Spring/Boot. I wrote a tiny dropwiard-like "framework" to make this easier: https://github.com/gwizard/gwizard but there's a laughable amount of code here, you could build it all from scratch with minimal effort. This is about as lightweight as "frameworks" get because Guice does the heavy lifting.

* JAX-RS (Resteasy) for the web API. IMO this is the best part of Java web development. HTTP endpoints are simple synchronous Java methods (with a few annotations) and you can test them like simple Java methods.

* Lombok. Use @Value heavily. Cuts most of the boilerplate out of Java.

* Junit5 + AssertJ. (Or Google Truth, which is almost identical to AssertJ).

* Use functional patterns. Try to make all variables and fields final. Use collections streams heavily. Consider vavr.io (I'll admit I haven't it in anger yet, but I would in a new codebase).

* StreamEx. Adds a ton of useful stream behavior; I don't even use basic streams anymore.

* Guava. There's just a lot of useful stuff here.

* For the database, it really depends on what you're building. Most generic business apps, postgres/hibernate/guice-persist/flyway. Yeah, folks complain about hibernate a lot but it's a decent way to map to objects. Use SQL/native queries, don't bother with JPQL, criteria queries, etc.

* Hattery for making http requests (https://github.com/stickfigure/hattery). This is another one of mine. I make zillions of http requests, functional/immutable ergonomics really matter to me.

* Github actions for CI.

* Maven for the build. Yes, it's terrible, except for every other build system is worse. Gradle seems like it should be better but isn't. I'd really love some innovation here. Sigh.

I can't stand most http libraries (full of mutable state!) and I spend a lot of time making http calls. So I built a functional/immutable http request library which has been dramatically improving my personal quality of life for about 7 years now. No idea if anyone else uses it, but it doesn't really matter.

Java version: https://github.com/stickfigure/hattery

Typescript version: https://github.com/stickfigure/hatteryjs

https://notabase.io - a note-taking app for networked thinking.

It supports page stacking, linked references, block references, a graph view, and all that good stuff. Think of it as similar to Roam Research / Obsidian.

It's also open source so you can self-host it. Here's the code: https://github.com/churichard/notabase

I'm hoping to add support for shareable links soon. Open to other ideas or feedback!

you can check out this page https://alternativeto.net/software/joplin/?platform=online but the best I could find are - https://www.taskade.com/ https://standardnotes.com/ https://notesnook.com/ https://bundlednotes.com/ https://diaroapp.com/ https://notabase.io/ https://boostnote.io/ etc.

When evaluating rich text editors for the note-taking app I started about a year ago (https://notabase.io), I ended up going with Slate because of its flexible schema and customizable plugin architecture.

I sort of regret that choice now. I ran into a lot of bugs when integrating it which I had to manually work around; issues go months without being addressed; and there still isn't good cross-platform support, especially for Android. With a more active contributor base, Slate could be a fantastic library, but I get the feeling that it's in maintenance mode now, with not many major changes in the past year and a v1.0 still far in the future.

Tiptap looks like it might be a good choice now, but I find it off-putting that I can't insert links in the demo editor on Tiptap's website (https://tiptap.dev), especially for my use case (a note-taking app whose core concept revolves around links).

I'm working on an open source note-taking app called Notabase [1]. It's built primarily for my use - I just never liked most existing note-taking apps and wanted to make one that fit the way that I think. I made it open source [2] so other people can build on top of my ideas, and released a hosted version so that other people can use it if they like it. It would be nice if other people found it helpful, but regardless it's something that I intrinsically enjoy working on.

[1]: https://notabase.io

You can try Notabase https://notabase.io/, which is better for self-hosting.

if you prefer mdSilo, need to toggle the Offline mode false in code and use the third-part services: vercel and supabase