tomatoes are fruits that are often used as vegetables and are botanically classified as berries*
*according to wikipedia and my interpretation of it
Intelligence is knowing that tomatoes are a fruit. Wisdom is knowing that they don’t go into a fruit salad.
Charisma is selling salsa as a tomato based fruit salad
Strength is EAT MY DAMN FRUIT SALAD OR I’LL SMASH YOUR FACE IN.
What if you soak them in high fructose corn syrup first?
Then it’s ketchup
Rules are meant to be broken.
Tomatoes are only fruits in a biological sense, vegetable is a culinary term so it makes no sense to mix them up.
I prefer just calling everything I eat the flesh of whatever it came from. Tomato? Flesh. Lettuce? Flesh. People? Flesh.
My favorites are flesh fries
And if you ate light…
My understanding is that the term vegetable is actually a political term, meaning it is categorized as a vegetable for tax reasons.
Vegetables are taxed lower than fruits.
In the EU, carrots are classified as a fruit because otherwise, marmalades made with carrots would be illegal.
Maybe they should be illegal?
I mixed them up for the joke since the phrase sounds kinda absurd but it’s technically true
Vegetable has no meaning other than “part of a plant* we eat”, so basically all fruits are vegetables
*And in the case of mushrooms, fungi
To add to this, vegetable is a culinary term and not a scientific term. Whereas, fruit can be both. Tomatoes are scientifically a fruit, but generally not from a culinary perspective.
According to some YouTube short (maybe it was vsauce?): botanically, fruits are vegetables so tomatoes are vegetables in both classification systems
In reality it really does not matter and the classification is somewhat arbitrary. Just think about adding it to a fruit salad. Would you do it? Then it’s a fruit.
I’ve seen it too. I think it was Hank or John Green.
I once saw a little blurb at a sandwich shop stating that tomatoes are fruit, but if you pair them on a sandwich with jalapenos, you’re getting both fruits and vegetables. I demand better scientific accuracy in restaurant marketing signs.
Now I wonder if jalapenos are fruit too (scientifically)
Technically, according to the definition of a fruit, the cucumber is also a fruit, so yes, the tomato/cucumber salad is a fruid salad.
The fact that this meme makes sense to anyone demonstrates how dynamic typed programming languages cause brain damage.
I like TypeScript less for its ability to categorize my grocery list and more for its ability to stop anyone from putting cyanide on it.
I hate Typescript for promising me that nobody can put cyanide on the list, but in reality it disallows ME from putting cyanide on the list, but everyone else from the outside is still allowed to do so by using the API which is plain JavaScript again
Honestly, programming is great for teaching you that you are the stupid one. This is still a feature.
The main problem with JavaScript and TypeScript is that there is such a little entrybarrier to it, that way too many people use it without understanding it. The amount of times that we had major issues in production because someone doesn’t understand TypeScript is not countable anymore and our project went live only 4 months ago.
For example, when you use nest.js and want to use a boolean value as a query parameter.
As an example:
@Get('valueOfMyBoolean') @ApiQuery( { name: 'myBoolean', type: boolean, } ) myBooleanFunction( @Query('myBoolean') myBoolean: boolean ){ if(myBoolean){ return 'myBoolean is true'; } return 'myBoolean is false'; }You see this code. You don’t see anything wrong with it. The architect looks at it in code review and doesn’t see anything wrong with it. But then you do a
GET https://something.com/valueOfMyBoolean?myBoolean=falseand you get “myBoolean is true” and if you do typeOf(myBoolean) you will see that, despite you declaring it twice, myBoolean is not a boolean but a string. But when running the unit-tests, myBoolean is a boolean.This is more a condemnation of nest.js than ts. It seems great in theory. I like the architecture and the ability to share models and interfaces between front and backend, but it’s objectively makes everything more complicated. It adds layers of abstraction that should not be necessary and it’s such a niche/unpopular framework for backend systems that you generally have to jump through hoops to do anything moderately complex. Not only do new devs have to learn typescript to use it, they have to learn the nest architecture to know how to do things “the right way” and you still end up in situations like this which looks perfectly valid but isn’t. Typescript was never meant to be used for backend, and trying to make it do so and then complaining about it is like jogging while carrying a gun, shooting yourself in the foot, and blaming the gun.
the ability to share models and interfaces between front and backend
On the other hand, this can be considered a downside because it locks you into using JS/TS on the front and backends.
Alternatively, if you define your models and interface with an Open API spec, you can write the front and backends in whatever language you want.
I’ve never used TS, and I’m not exactly sure what nest.js even does, but building a TypeScript project on top of a JavaScript library not designed for it seems like asking for trouble. Is that standard practice?
Yes. As of this writing there are 7,738 type definitions in a central repo maintained by users for plain JavaScript packages.
https://github.com/DefinitelyTyped/DefinitelyTyped
Many package owners write type definitions included with their package that is written in JavaScript also.
Web dev continues to be cursed, I guess.
If I really needed to use a JS library in TS, I’d have to build some sort of adapter between the two that crashes whenever the JS library (that doesn’t know anything about your types) breaks the typing rules. Anything else will inevitably lead to the above “fun” kind of bugs.
I don’t think that this would work, there are no types anymore during runtime because everything is translated into plain js on build. TypeScript only exists during development
return ‘myBoolean is true’;
I instantly noticed this line. Shitcode is so fun.
Typically when creating API interfaces you’d be better off marking the inputs as unknown, and then using something like Zod to validate the types
Fair enough.
Two questions immediately come to mind. 1) Would you buy the cyanide if it was on the list. 2) Where does one casually buy cyanide? I can’t imagine a case where I’d need some, but it would be handy to know if I ever did.
I know you used to be able to get it for pest control, but maybe not anymore. You could also make it the old-fashioned way with molten washing soda. It can be used to make Prussian blue, for one thing.
Obviously take all necessary precautions, especially keeping NaCN away from acids.
Just one word: Apples.
I’d say its more like the gas tank telling you that you aren’t allowed to pour in brake fluid as that could lead to runtime errors.
tank.pour(brakeFluid as Any); // do not remove this for some reason will break prod
Tomato: Any
Biologists: but tomato is a berry, which is subset of fruits
Also biologists: “vegetable” is purely a culinary term, and doesn’t have any significance in the world of botany
As it happens, when we go shopping for food we have more of a culinary mindset than botanical.
A vegetable is edible plant matter.
Botanically a vegetable is anything that is not the reproductive portion of the plant derived from a flower. A root or tuber such as for yam or potato are vegetables. Edible flowers could be considered a vegetable since the ovary has not expanded to contain seed.
deleted by creator
Exactly
Am I missing the joke? Tomatoes are fruits.
Intelligence is knowing Tomatoes are fruits.
Wisdom is knowing not to put them in a fruit salad.
Greek salad would like a word… the only things that aren’t a fruit in Greek salad are the onions and feta.
Wisdom is knowing not to put them in a fruit salad.
A Greek salad is not a fruit salad, it is a…Greek salad.
salad Greek extends Fruit
{ fruit* Tomato }
I think that one might be intelligence too, sorry @xmunk@sh.itjust.works.
Pragmatism is putting tomatoes with the vegetables because of taste, which is one of the most important parts of food.
Legalism is declaring in 1893 that it is a vegetable for tax purposes, because fuck you, pay taxes.
The joke is that almost everyone calls them vegetables because the botanic categorisation of parts of plants is niche jargon that is not useful in everyday life, whereas the culinary categorisation is useful, and so your shopping list correcting you is worse than unnecessary.
But that’s not what TypeScript does. The joke in the meme doesn’t really even make sense.
A better analogy would be you have a basket that’s explicitly labeled “Fruit” and TypeScript complains if you try to put laundry detergent in it because you said it’s supposed to be a basket of fruit.
This meme was clearly made by someone who doesn’t use or understand TypeScript.
Yeah most likely.
As a proud Massachusettsan, tomatoes are definitely vegetables.
(Technically, tomatoes are both fruits and vegetables)
Aren’t fruits subsets of vegetables? Without looking it up I thought that vegetables were the edible part of the plant and fruits are edible reproductive parts of the plant. I could be totally off on that though.
Yea, you’re totally correct. This whole confusion comes from a Supreme Court case that involved tariffs though… Basically, tomatoes are a staple good and should be taxed like a regular vegetable and not receive the elevated fruit tax.
i.e. Americans ruining english for the rest of the world (see also 7th day nutjobs), thanks guys…
Does this vary from place to place?
It varies by language since the meaning of fruit and vegetable are language specific but that’s universal for English. A fruit is an edible portion of a plant that contains seeds and a vegetable is an edible portion of a plant, so… all fruits are vegetables.
Ok but like, why draw the line at Massachusetts? Lol. If I make a wrong turn and end up in New Hampshire am I going to have to reevaluate my fruits and vegetables?
Oh, Massachusetts was behind them being classified as a vegetable but not a fruit for tax reasons.
Well, that depends on definition. But the joke is why on earth would you want to write types on your shopping list? Like this:
- tomatos (vegetable)
- apples (fruit)
Etc.
Well, I can’t think of an English example from the top of my head, but in German the words for Pear and (light) bulb are the same. So there are some exotic use cases.
We have plenty of homographs as well, “lead,” “bow,” etc but every once in a while I’m struck by just how massive the vocabulary of English is compared to… well, every other language.
how massive the vocabulary of English is compared to… well, every other language.
English doesn’t even has definite articles.
Biggest English W
As a german I agree, even if I never have to think about it
This is giving me stress daymares about Spanish in high school.
Still, it’s an interesting point you make.
But then again, with definitive articles you have a bunch of things that are not supposed to convey gender conveying gender. Like a toaster… It would suck to have to remember the gender of a toaster, or, well toasters in general.
It’s “der Toaster” which makes it masculine. On the other hand, a girl (“das Mädchen”) is neuter. The grammatical gender is somewhat arbitrary and does not follow any “real” rules.
As a German you somehow “feel” if the correct article is used, though.
Yeah, fuck that. English is bs enough.
Edit: yeah, that “feeling” is knowing it so well, you don’t totally understand it, and also means it’s hard to convey
Embarrassingly for someone whose native language is german, I often use the masculine when the neuter should have been used, because they feel the same to me. I never was taught any formal grammar in german, though, so that might play a role.
We got diff’ernt words fer lightbulb and pear though, I tell ya hwat.
German has different words, too. Even multiple one depending on accuracy
- die Birne -> the pear
- die Glühbirne -> “glowing pear”, the light bulb, coming from the shape of the bulb, common, but even Germans see that its dumb
- die Glühlampe -> “the glowing lamp”, coming from the literally glowing filament that is used to produce light, the usual term
- das Leuchtmittel -> “the thing that shines”, no direct translation, closest would be “lamp”, to describe, well, a thing that shines, independent of what is used to produce the light, usually used in technical documentation/environment
German also has multiple other terms to describe a lot of different light bulb shapes and types. Germans can even make up completely new types of light bulbs due to the heavy use of compound words, and every other German can understand that on the fly without further explanation.
Let me just imagine some.
- das Bootshausseitenflutlicht -> a floodlight at the side of a boat house
- die Dreiecksleuchte -> a lamp or light bulb in the shape of a triangle
- das Hinterhausnachtlicht -> a night light for a part of a tenement house accessible only through a courtyard
That’s really cool. For whatever it’s worth I was joking. I’ve always admired German and almost elected to learn it in highschool, but socio-geographically(an off the cuff word combination in English), learning Spanish made more sense, as there are many Spanish speakers. But I digress; thank you for explaining such a neat feature of your language to me. I also must admit that the English word is not totally dissimilar in origin; a light-bulb glows in a lamp, but an onion is a bulb in the ground, so it isn’t too different from glowpears.
That English has more words than other languages is a myth. Idk why but it keeps getting perpetuated so i guess people just believe it to be true.
Whats more is that its kinda difficult to even narrow down what a word is in a single language, and even more so to find a definition that fits all of them.
Impressively the babbel article manages to include other commons myths like implying english is some kind of mix language rather than a germanic one when it says “This is largely due to invasions of England by the Vikings and then the Normans” about why English supposedly has more words than other languages. This type of incorporation of loanwords is common in almost all big languages.
It argues based on dictionaries and effectively debunks why you can’t (for comparison I’d like to add that the SAOB of the Swedish Academy lists circa 500k words).
There’s nothing in this article that says English has the most words other than “So, while English is a clear contender for having the most words and German and Turkish have a large capacity for infinite combinations, all languages end up influencing others.” Still, there’s no justification for the “clear contender” bit other than the Oxford dictionary having more words than Larousse and Littré.
Feels to me like the article just reinforces the notion (and reality) that you can’t even make comparisons like that.
Nevermind the fact that this idea is a well known myth in linguistics and arguing against it is kind of like arguing against flat earth theory.
You don’t really know what you’re talking about
Why not? If a shop is having a sale on fruits only then I would like to sort out all the fruits quickly.
To be conformant with PEP-8.
Sorting the list by type might help you get everything located in a section of the store before you move to the next section.
So that the mindless automaton delivering your groceries doesn’t unexpectedly give you tomatoes for your sundae, in a future expansion to dish-based orders.
I’ve yet to create a type error that didn’t correspond to me thinking about something wrong.
I swear to god, sometimes I really don’t know what Typescript really wants from me. It’s like some old god: you know it needs a sacrifice but the god is not telling you exactly what he wants. So you can only try and pray.
Idk, I find it pretty easy to understand
The "return type <5 paragraphs of various word salads> is not compatible with " error messages are anything but easy to understand in my opinion.
Yeah I don’t get why it spits out whole types instead of only differences between them. Like “function expects non-null ‘some.param.in.object’ of type ‘string’ in argument ‘someArgument’, which is missing in passed argument”.
Typescript got a lot easier for me when I stopped even trying to read the error messages
I’m a bit disappointed that nobody mentioned Rust yet.
Yeah… What?
Tomatoes are fruits.
Botanically they are. Culinary they are not.
Some languages split the word “fruit” up in those two cases. In Dutch for example, the botanical definition of fruit translates to “vrucht” whereas the culinary definition translates to “fruit”.
So, a tomato is a “vrucht” but it’s not “fruit”
Some languages split the word “fruit” up in those two cases
I wish English did this more. There’s way too many words with an overly large number of meanings.
The word “free” meaning both “freedom” and “doesn’t cost money” can be confusing - some languages use “gratis” or an equivalent word for the latter definition. Sure, you can use it as a Latin loan word in English, but that’s not common.
Aren’t they berries, tho?
Would you put a tomato in a fruit salad?
Guess it’s not only Typescript that likes to argue with the developer while missing the entire point…
somewhere brodie lee just threw some papers
Evil Uno hits the floor wailing.
Report -> I’m in this picture and I don’t like it
Intelligence is knowing that tomato is a fruit, wisdom is not putting it in a fruit salad
Charisma is being able to sell a fruit salad with tomatoes in it.
Dexterity is hacking everything into nice looking pieces.
Malovelence is scooping the entire oily thing with your hands and shoving it into the nearest hole.
Strength is cutting the cutting board in half while you’re cutting up the tomatoes.
but ‘ketchup goes on anything!’
-my grampa
I’ve seen versions of this meme before but I just noticed what he’s wearing. Is that a Mortal Kombat shirt?
