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.
What if you soak them in high fructose corn syrup first?
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 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.
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=false and 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.
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.
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.
Pragmatism is putting tomatoes with the vegetables because of taste, which is one of the most important parts of food.
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".
I'm a bit disappointed that nobody mentioned Rust yet.
Guess it's not only Typescript that likes to argue with the developer while missing the entire point...
Report -> I'm in this picture and I don't like it
Post funny things about programming here! (Or just rant about your favourite programming language.)