You mean for the employees that will write Java?
“Oracle” is usually about the DB, and that is paid by the core.
You mean for the employees that will write Java?
“Oracle” is usually about the DB, and that is paid by the core.
I think it was 5 that decided to change everything on the parser level, and 11 that decided to change everything on the modules level.
Outside of those, Java has always been extremely backwards compatible. But last time I checked the ecosystem still didn’t recover from that module semantics change.
The only time where the design actually changed, the designer made the point of moving the path away from whhere the desire path was pointing.
That comic captures it so incredibly well. It’s almost perfect.
Well, it seems to be always the case.
Either that or 9/10, but this time it’s that.
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.
Of all the games that I would expect to have a global ranking, that is the absolute last.
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
Israel has been claiming they are “a week away” from having the bomb for 30 years. They have been working on a bomb for 60 years, since the US worked with them to start their nuclear project.
Some 20 years ago they got in a situation where it would actually take a couple of months to make a bomb. They seem to have stopped there on purpose.
Is that the part that was confusing?
The Javascript literal interpretation of NaN never fails to amuse me.
Your point is that the terms on the first panel are more clear?
Well, either way, calling xenophobia as “barbarism” is a nice ironical way for the language to evolve.