I used to blindly rely on google maps until it misdirected me on my way to Redwood National Park. It led me to a house in the mountains that had a sign saying something like - google maps has misdirected you and there is no path through this house to the Redwood national park. It was a place where even the cellphone did not work. This happened ~6 years ago and hopefully google fixed it by now.
>If you had a database and some separate messaging like ZeroMQ, Rabbit, Kafka, you’re going to get race conditions. There’s always going to be a potential race where you have two messages - one is going to the disk and one is going to the network. If someone else is listening and sees both of them, they could potentially get them in either order. So it’s much, much simpler to just have one path. Foundation is really fast, so it works great.
Having difficulty parsing this justification. How will a client code listening to an event get two events - one from network, and one from disk in case of any of the queuing systems mentioned here? I am also curious to know how the FoundationDB act like a messaging system apart more than a message store?
I sincerely think that the present corporate culture can suck the air out of anyone's life and force to seek contentment elsewhere very soon. Doing a research work and solve problems, where one does not have to seek approval (easier when you NL next to your name), on a daily basis can keep one engaged and energized.
Feels like a nice dream interrupted for most of the googlers. Probably they felt tenured and even 6 months of severance cannot assuage the hurt feeling. Looking around and doing some reality check might help. Every company is trying to improve the bottom line when the topline is not moving up. The layoff didn't just happen this year, it has been in the corporate world all the time.
If there are true friends in the company then they will find a way to reach out. Others are just lunch/coffee buddies and they might be already enjoying their pastime with someone else. Find a way to put this in the rear-view mirror as soon as possible.
Few missing details that are crucial to usage within an organization:
1. what is the type of service instrumentation needed to capture the data? Wonder why this is needed when typically the data is already captured in an APM log? The instrumentation might add performance and security concerns.
2. what is the sampling logic to capture the traffic? It might compromise the fidelity of the test data and give a false sense of test accuracy.
3. what is the duration of data capture? Is it a week's or month's or quarterly data? Meeting 90% coverage on a week's production sample data will provide a false metric.
4. can it faithfully handle data privacy and customer anonymization? This is critical for API's dealing with PCI and other sensitive data.
The Generative AI is the AI for the masses. While people were getting overhyped with all the possibilities and promises of AI and deep learning etc. it is for the first time that they can also tinker and get surprised by its results. People feel creative interacting with it.
>“Depositors shouldn’t get anything beyond the insured $250,000”. Then what do we do with the billions in remaining assets? Appropriate them, and leave small and mid businesses hanged to dry?
To me such statements feel like - either you are with me or against the humanity. Of course, the government should not gobble the money that belongs to the depositors and the fund should be distributed fairly to the depositors post liquidation. But making whole the deposits through the tax payers money will not be right. This is a business failure and what is insured is only what is guaranteed to be paid back. That is the risk business take when they engage in such transactions.
Individuals who had more than $250k sitting in bank account must be well-off and prudent enough to decipher the FDIC insurance limit.
I am sure there is momentary thrill of achieving minimalism but alas the world is not so simple anymore. I would refer the OP and the community here to the paper from the creator of PostgreSQL: http://cs.brown.edu/~ugur/fits_all.pdf
Used to be a fountain pen fan and have used WinSung about 35 years ago and have very pleasant memories of the writing coming out of it. Wasn't cheap by Indian standard but the other pens mentioned here were unavailable to masses back then.
I am kurutoga fan as well. Love the rotating lead and consistent writing due to that. Sadly I keep losing the eraser cap and can't seem to find it online. Any suggestion?
Worked on implementing such functions as part of larger project to mimic CATIA in Xenix system. I was and still fascinated with computer graphics and it was a dream project to work straight out of school. At that time we relied heavily on the computer graphics book by Foley et. al. It should be still a comprehensive book for someone trying to wet his feet and beyond in computer graphics.
I have used TransferWise, Moneygram in the past for international transfers. Good thing about these services is that they let you know in advance the conversion rates and fees which, for some reason, the banks won't let you know until the money gets transferred. I personally don't care about the fees as long as the final amount is better than what other services could offer.
Now a days I have been using skrill and have been impressed with the speed of delivery and the conversion rate. The rates are better than TranseferWise and Moneygram and some of the transfers were done in 1 day! It also allows debit card to be used without any fee which is quite convenient. Although I wonder how do they save money compared to using the ACH payment?
I agree with the opening sentence that there is no large company pushing or rather peddling it. But the fact that it supports FP with immutability is really a well positioned design and with little bit of practice programmers get the hang of it very fast. Lack of for loop should not be an alienating factor, according to me. With NIF one can integrate with native code easily so, a team does not have to re-write the entire codebase just because Erlang has been chosen.
Given its support of functional language, built-in fault-tolerance, asynchronous message passing, and scalability, one would assume that it should ride the current wave of distributed computing. Any reason why it is relegated to a niche technology?