Java requiring you to write every exception that can happen in your code isn’t helpful.
Explicit error types are great, but Java managed to make them on a way where you get almost none of the upside and is so full of downsides that indoctrinated a generation into thinking knowing your errors is bad.
The amount of people on the internet seriously complaining that both Rust error handling sucks and that .unwrap(); is too verbose is just staggering.
The horseshoe is absolutely real. Social democracy (like the stuff that candidate proposes) is on the middle, and both sides go out into a corrupt authoritarian government where the elites own everything.
Even if you want it to be human readable, you don’t need to include the name into every field and use balanced separators.
Any CSV variant would be an improvement already.
About the title; my condolences.
Lots of "maybe"s, I see…
On which of those application types there are developers that write most of one of the halves, but do not touch the other half?
(Oh, yeah, on the phone apps, but only the ones that are a web site cached on the phone.)
The entire meme is about web-dev. That split between backend and frontend isn’t anywhere else. (And is stupid for the web too, but well, that’s what web-dev do.)
maybe that’s all the customer needs
The food truck is often better than the restaurant experience in every dimension… The same is valid for the app analogies.
How many people worked on it is not a dimension that counts.
It’s a nicer syntax for inline styles.
If you want to use inline styles everywhere, it’s great.
I guess some people write code, and some people also read and maintain it.
but whatever chemicals they add to these things makes just 1 small burger feel like you overate.
That’s usually a feature of good food. I agree that it’s odd that a hamburger would be that way, but usually what causes that is fiber.
Yeah:
parseInt("a") -> NoT a NuMbEr
The Javascript literal interpretation of NaN never fails to amuse me.
who will happily come in and sort out your security issues later
I really doubt anybody will be happy about it, even after considering the size of the fees. And also, you have a very high estimation of the capacity of those people to notice they have to call you, I really doubt it’s deserved.
Hum… I’d put good odds in they getting some now.
Being able to know things was good though. I hope scientific articles last a while longer.
The restaurant has exactly the average quality of everybody that cooks.
Not of restaurant chefs or people good at cooking. Everybody that cooks.
Some declarations terminate on the name, other declarations go one requiring more tokens. In C, the only thing that differentiates them is the type.
Parenthesis in particular are completely ambiguous. But asterisks and square brackets also create problems.
Good, now invent a keyword for variables you don’t want to declare the type. And now that you have a mix of keywords and identifiers on the same place, you can never update your language again.
Also, make the function declarations not use a keyword too, so you get the full C-style madness of code that changes meaning depending on what libraries you import.
Well, it seems to be always the case.
Either that or 9/10, but this time it’s that.