As per the article: "The biggest difference between the two boars is that the Orange Pi RV has a 1.5 GHz StarFive JH7110 quad-core processor, while the new Orange Pi RV2 has a an octa-core Ky X1 chip with a 2 TOPS AI accelerator."
I opened the comments before the website as I was sure this would be another of those sources available clickbait. Why is this kind of disingenuous move not enforced in the title guidelines of HN is beyond me.
Is known in a wider area eg. ajver in Turkey. It's okay, the texture can be a bit glooey sometimes. (Sidenote: in Turkish they have different words for heat from temperature and heat from hot peppers - anyone chip in here?)
On heat tolerance, do some genetic thing where people get one, two or three receptors[1] which give different sensitivity to different people. I had a GF who would struggle with the level of capsaicin I literally wouldn't even notice. I knew a guy who would snack on scotch bonnet peppers straight, which would be impossibly agonising for me.
Turkish word for heat when related to temperature is "sıcak", when related to peppers is "acı".
But "acı" can also mean bitter. You have to look at the context to understand. However things can both be spicy and bitter. In that case it gets complicated :)
The problem is all of those can be ambiguous. "Hot" can mean high temperature, "spicy" can mean e.g. lots of garlic or cumin, or any other spices, and "piquant" can mean tart like citrus.
Perhaps the lack of a dedicated mapping to "capsaicin sensation" stems historically from England's reputedly bland cuisine...
Okay, in light of recent UK events I get the subtext :-)
But I don't think it's fair to call UK food bland. Done properly it's very good, but what it's not (usually) is heavily seasoned. In no way does that require it to be tasteless, and done properly it isn't.
My understanding is that UK food was on a par with other European countries in medieval times. By the 1950s to 1970s, it was pretty bad though. No doubt some of this was down to wartime rationing. Perhaps some of it was due to protestant fear of anything too enjoyable.
There is a reason there are thousands of Indian restuarants in England and approximately zero English restaurants in India. ;0)
Thankfully, food has improved vastly in the UK since the 70s.
Yes, there are none at the moment, however, we plan on open-sourcing filters, effects, transitions, and components needed to build UI interfaces faster.
This looks great, I'll definitely give it a try.
As many mentioned already, having classic columns and a JSON(B) column seems to be a common solution.
How do you handle data validation for the JSON documents?
My current project uses Django for metadata. I've been thinking about creating a layer similar to model fields in Django. You would declare a JSON "model" through those fields and assign it to the actual model JSON field.
You can just specify a model/DTO object and serialize it as JSON when saving. Many frameworks do that automatically so you don't need to think about it. At work we just annotate the field in the model as a json-field, and the framework will handle the json-conversion automatically and store the other fields in the model as regular database columns.
Adding fields is not an issue, as it will simply be missing a value when de-serializing. Your business logic will need to handle its absence, but that is no different than using MongoDB or "classic" table columns
That's a very low cost approach, I love it!
I still think the Django ecosystem would benefit from a standardized/packaged approach including migrations. I'll ponder a bit more
