TextMate VS OkHttp

I mostly work on MacOS these days and previously my general purpose text editor wax Textmate: https://github.com/textmate/textmate

Last official release was 2021, so I looked for something more regularely updated, and found CudaText. Definitely very Sublime-ish, and I like it so far.

Textmate 2.0 got open-sourced https://github.com/textmate/textmate but it looks pretty much abandoned/finished.

If you want something like TextMate maybe use TextMate? https://macromates.com

Use a native editor. VS Code is IMHO awful. Someone mentioned Sublime which is fast and has some nice features, but its non-native UI is IMHO ugly and clumsy. You might like it for similarity to VS Code, I guess. If you want something much more "Mac", though: https://macromates.com

I know no one talks about it anymore but TextMate 2 is still actively being developed and I find it excellent.

https://macromates.com/

TextMate is a well-known code editor for developers who code on a Mac system.

See, VSCode itself utilizes grammar files called “tmLanguage” files to tokenize your code. This tokenizer is borrowed from TextMate.

We will use Square’s Mock Webserver to spin up a mock server which we can use to simulate real api's request to the get coffee endpoint.

OkHttp Documentation

mockwebserver -> https://github.com/square/okhttp/tree/master/mockwebserver

I searched in the OkHttp GitHub project for an advice on which values may be suitable for Android apps nowadays but found no answers (only this old issue which does not help). Since we share a single OkHttp client Singleton for all our retrofit APIs and even Coil, I wonder if the default 5 maxRequestsPerHost is really enough.

You can technically add a Content-Length header for each part. It's not forbidden by the RFC, but nor is it common. It caused [problems](https://github.com/square/okhttp/issues/2138) for OkHttp, and they eventually removed it. Might be fine for internal-only use, though.

Boundaries are a lot like UUIDs, and rely on the same logic. When generating random data, once you have enough bits, the odds are against that sequence of bits ever having been generated before in the universe.

Lets be specific. This is the gradle build file for Squares okhttp client library. How exactly would your bld tool "predict" or "help" with all the parameters needed? There is no need to be defensive. Replace those large build files with your own, show where your approach is better and then understanding will lead to better solutions.

And adding to that: The asynchttpclient library is just a thin wrapper around OkHttp3, so it might be easier to just go with that instead: https://square.github.io/okhttp/

Retrofit in combination with OkHttp for fetching data from server (which hopefully already exists)

OkHttp