23 karma · joined August 14, 2015
Also when it comes to pricing, it helps to know the market. She will list a house for 8% under market value because she knows it will draw interest and end in a bidding war with escalation clauses.
She also knows other agents and other lenders and that's very important when you have a timeline. One offer may look good but you know the agent and know they will give you an artifically high offer and then ask for 10's of thousands in remedies. Or if you're trying to get a deal done on a timeline so you can get another house and a buyer comes in with a lender that's just notoriously bad at doing things on time. You may take an offer for a few thousand less when you know a deal will end on time.
Like most things, you get what you pay for and there's plenty of people out there willing to take your money and do nothing. There are good realtors and bad ones.
2. As for base64, I'm not sure of a better way to support sending raw image data over JSON (in REST mode) In some ways I think GRPC is a better medium than JSON (it supports either) as GRPC supports sending the RAW bytes. What leads you to believe GRPC isn't the right transport? Plus you can do it in a stream format if you want to do a lot of video.
The only limitations I can think of are that Tensorflow supports a myriad of CPU optimizations so providing a single container image that has all the right options is basically impossible. I created one that has what I think are some of the better options (AVX, SSE4.X) and then an image that basically should run on any 64 bit intel compatible CPU. To get optimized options you need to build the docker container yourself which can take the better part of a day on slower CPUs.
With that said, I also provide ARM32 and ARM64 containers that actually run semi-okay on Raspberry Pis and and other ARM SBCs. I can run the inception model on a Pi4 on a 1080p image in about 5 seconds which is pretty good IMO.