maxpert

Will wait for a Generics version. This is version is so not worth it!

For the record to this day I believe this aqua pill styled interface was way more clean and attractive than the flat design. I've never been fan of flat interfaces, it's the reason I hated Windows 8 onwards interfaces. Skeuomorphism was just perfect!

I promised myself I will stay patient, but I think I am on verge... It's everything I've dreamed off!

Sometime back I did a Golang based memcache server implementation with BoltDB (experimented with Pebble as well). I dropped that implementation out of fear that nobody will be interested in using it, have same question here I guess. Why would I drop the existing battle tested solution for something that might still have non-memory bugs.

Exactly reading article I for a second felt like author was either not fully aware of tooling, or doesn't care about the noise it will cause (potentially complex conflicts) checking node_modules will cause.

> MySQL is a pretty poor database, and you should strongly consider using Postgres instead.

Holy crap! I moved away from to Postgres way back in 2012 just for the features (at cost of connection complexity), but this is a plain blow to MySQL fan boys!

Would be nice to have some benchmarks against ES, Sonic, and Toshi. I am very much interested in stress-testing on large dataset.

Fibers!!! Who wants to bet we are a few releases away from async/await syntax now. Giving credit where it’s due Microsoft with C# pioneered the syntax and every classic (including a few modern) language has adopted the syntax.

I believe we are a few steps away from a fully builtin production ready server and db connection support.

I've used Shenandoah GC with great success and I recommend anyone considering ZGC (specially on Kube and container environments) to try Shenandoah first. You won't have to do additional work to enable large pages, yet your performance is pretty close.

Low Java knowledge and more Fan babel rather than true critique.

> This report describe pgagroal in relationship to 3 other PostgreSQL connection pool implementations, which we will call "a", "b" and "c".

Why? Just why! Please put up names rather than saving faces for other poolers!

Ahhh the sweet memories!!! Do use it with FTP and SFTP plugin to edit your PHP live!

Complexity, humans are not good at complexity beyond certain levels. One good example of such model is in React + Redux story. Based on single variable your view might have 10/20 changes and to this day I see people debating what is the right way to do it (React hooks vs Redux is latest episode).

Reading the comments here I wonder if there can be an opensource project doing the spec implementation, or define a spec for implementation. I can see people frustrated with Power Query or constant changes everywhere.

Reminds me of of good old PHP shared hosting days. It was so much fun to just write my code and then just drop the folder over Filezilla and everything just works!

Bug no problem! Live editing!

Hilarious! It takes dependency on is-odd and just does a not (`!`).

I think React is pretty soon gonna share same fate as jQuery. Svelte is slowly picking some steam, and with recent move of original author to Vercel I am more confident than ever that momentum is shifting. My friend directly got to work with Carmack, and him moving away directly from project should tell a lot about what the future of the hardware holds with FB.

Microsoft had to rewire itself in order to recover from Windows. Facebook (or Meta) needs same. Microsoft had to bring in a new leader, I think Zuck should step down, and bring somebody different before it's too late. I can imagine a fight for throne happening inside already.

You would only see the real value in these poolers in dire times. Screwing up apps or deploys leaking connections is really easy. If that happens you will bring down the whole DB. With these poolers you will not only be able to limit that but also enforce per user (service based if every service has it's own creds) limits. These tools are useful beyond certain scale and you will only realize there true value once you are working in distributed micro-service world specially when they are connecting to same DB.

Why can’t these schools make simple electron apps with these things disabled? I thought these are solved problems instead of landing duds in Chrome!

Awesome! How can I contribute?

I've used Toxiproxy to reproduce so many issues that I can't be thankful enough to authors for this awesome tool! I also found a docker based UI to adding toxics I just wish it ships out of box or as another binary/brew package. While cli is awesome for people who have mastered it for beginners it's one more thing to learn, having a UI just solves that.

I would love to learn a little more here. So for 30 second tail latency cases, doesn't Ruby HTTP client support a timeout with cancellation? The only useful case where I believe Async Ruby can help is the parallel requests cases.

Disclaimer: I am not a full time Ruby person, so if it sounds naive please feel free to point it out.

Who want's to bet competitors will copy notch on laptops now? Some will have punch holes too!

Intel is gonna be in deep trouble in couple of years. They are the PowerPC of modern era. IDK what held them back from reimagining the architecture for less power hungry processors and tooling. With Mac mainstream switching to ARM and Microsoft doing something similar, I think within next 5 - 10 years ARM is gonna take over Intel architecture in general.

Site not loading for me :(

Congratulations to the team. It’s rewarding to make it through, but don’t make the product shittier just because you are big now.

How is Cloudflare gonna coup up the price? These numbers are too good to be true (Sorry I am naive in how egress pricing works).

I don’t agree with this. Right now writing a basic LRU cache requires casting gloop in your code. The issues (specially 2 & 3) in article are manageable. But generics are genuinely holding me back from writing reusable code.

I converted from MySQL (before whole MariaDB and fork), and I've been happier with every new version. My biggest moment of joy was JSONB and it keeps getting better. Can we please make the connections lighter so that I don't have to use stuff like pgbouncer in the middle? I would love to see that in future versions.

Guilty of buying but worth every penny! I don’t think Google should be given enough liberty to track what I am reading and what deep links I am visiting.