Being technically approved by Microsoft is not a proof of quality...
Read it twice then
Isn't search engines quicker than calling a LLM ? It might have a huge impact between a 20ms search engine call and a 2s LLM call for the end user.
I am always surprised that its considered legal. IMO that's the same as going on the street door by door and checking if one is left open to steal everything inside the house...
K/Q and vibecoded doesn't sounds good. I used Q with KDB+ for trading and we should ensure to have the right data / calculus as tiny errors might have huge impact ($).
LoopBack 3
picture recognition
I definitely don't like LoopBack in many ways : - custom relationship (hasMany - hasOne - belongsTo - etc.) - lack of documentation - readability - overriding and custom model methods - console output in bottom banner -…
Why don't you use Git and multiple work stations ?
404 in the page
I never use serverless because micro-services always works perfectly. Im lazy Thanks for sharing ! I think I won't switch to serverless (maybe this architecture require a specific use case ?)
Being technically approved by Microsoft is not a proof of quality...
Read it twice then
Isn't search engines quicker than calling a LLM ? It might have a huge impact between a 20ms search engine call and a 2s LLM call for the end user.
I am always surprised that its considered legal. IMO that's the same as going on the street door by door and checking if one is left open to steal everything inside the house...
K/Q and vibecoded doesn't sounds good. I used Q with KDB+ for trading and we should ensure to have the right data / calculus as tiny errors might have huge impact ($).
LoopBack 3
picture recognition
picture recognition
I definitely don't like LoopBack in many ways : - custom relationship (hasMany - hasOne - belongsTo - etc.) - lack of documentation - readability - overriding and custom model methods - console output in bottom banner -…
Why don't you use Git and multiple work stations ?
404 in the page
I never use serverless because micro-services always works perfectly. Im lazy Thanks for sharing ! I think I won't switch to serverless (maybe this architecture require a specific use case ?)