jsk2600

I find it ironic that we developers prefer to use CLI because it's quick, efficient, stable, etc., but what we then deliver to people as web apps is quite the opposite experience.

>The green screens tend to be much quicker and more responsive than the web frontends that are developed to replace them.

Agree! Back in 2005, I was involved in a project to build a web front end as a replacement for the 'green screen' IBM terminal UI connecting to AS400 (IIRC). All users hated the web frontend with passion, and to this day, I do not see web tech that could compete in terms of data entry speed, responsiveness, and productivity. I still think about this a lot when building stuff these days. I'm hoping one day I'll find an excuse to try textualize.io or something like this for the next project :)

The "thin blue line" is a term that typically refers to the concept of the police as the line between law-and-order and chaos in society.[1] The "blue" in "thin blue line" refers to the blue color of the uniforms of many police departments.

[1] https://en.wikipedia.org/wiki/Thin_blue_line

This one is good: https://artificialanalysis.ai/

Also, it's usually far easier to support ten customers vs 3,333.

Thank you. I've seen 'only-on-Vercel features' mentioned in the past, but so far, I have yet to find any specific examples of classic 'vendor-lock' in a sense 'if you use this it will not work anywhere except for Vercel'. AFAIK you can self-host NextJS apps with docker, albeit some features may not be as efficient as on Vercel they will work. This seems to be the case for both of the examples mentioned—ISR [1] and image optimization can be done on CloudFlare for example. Am I missing something? Don't get me wrong I'm not affiliated with Vercel, I'd like to think we can still switch from Vercel-hosted NextJS to self-hosted Docker in the future if we want which was my impression so far.

[1] https://stackoverflow.com/questions/75526234/how-can-i-use-n...

Hi, we are building our product in NextJS, and I was wondering what you meant by lock-in and less interoperability. Thanks!

It's down for many: https://downdetector.com/status/twitter/

NoMachine.

Any plans to support Kotlin ?

This is interesting and has great potential to grow when PSD2 goes live in EU (early 2018). I wonder what authors plans are regarding this.

We've been using Algolia in production for 8 months and moved to self-hosted elasticsearch. Small dataset, 2,5million records in 10 indexes IIRC, data structures and filtering were quite complex.

Algolia Pros:

* very nice UI/dashboard, stats, lots of options, flexible

* documentation is nice, 'onboarding' was not an issue

* it worked reliably most of the time

Cons:

* lock-in/proprietary. Think twice if you want to base your business on it.

* you have trust them with very sensitive customers data

* it is expensive. We reduced costs from $800/month to 40$/month by moving to self-hosted open source solution with same level/quality of customer experience.

* guys at Algolia like to rewrite client libraries and make them completely backwards incompatible. Good luck rewriting almost everything.

* support is incompetent and honestly it was useless in our case. I don't want to share details here in public as lots of people were involved in the case, but their support is disaster and for us that was major reason to migrate away. We had major issues for 2 weeks and in the end had to debug&fix problem in their client library by our developer. Long story, but that one was disaster.

In short, it wasn't extremely horrible experience overall, product is nice in general, but elasticsearch is very very good and Algolia just couldn't justify price tag, sorry.

Thank you !

>instead of always blindly returning an error, one could wrap them in higher level errors and build a sort of error trace

Isn't that basically just reinventing exceptions, sort-of ?

Sorry for off-topic question, but is this considered good golang code ? https://github.com/wallix/awless/blob/master/stats/stats.go

I'm considering learning go but amount of 'return err' and 'return nil, 0, err' is instant turn-off. Is this best-practice error handling in go ? Thanks !