Yeah, if you add tons of extra rules and tools, it can become almost as pleasant as the main Python or Ruby experience.

Almost.

Either way, the funny thing is that Postgres can do both too. You may not want to use it for those, but you absolutely can.

I think the OP is trying to talk about SQLite, so yeah, he could really be talking about carrying it on his phone.

But it’s just such a weird word to use there that I can’t really be sure.

What do you mean by “portable”?

You should put this at the code, or at the flag documentation. The one place you it can’t go at all is in a commit message.

There’s no appropriate time or place for Scrum or any other “agile” methodology that has a name.

There may be some appropriate usage for some methodology your team creates in a meeting. Never for those pre-packaged ones.

marked EXE

Ok, I’m taking from it that you use a permanent marker pen… I just don’t know why you execute your files, but since paper guillotines are so fun to use, I’m assuming it’s just for amusement.

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.

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.

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.

Yeah:

parseInt("a") -> NoT a NuMbEr

The Javascript literal interpretation of NaN never fails to amuse me.