Also, writing memory safe code honestly isn’t that hard. It just requires a different approach to problem solving, that just like any other design pattern, once you learn and get used to it, is easy.

the CVE list would disagree with you.

I am of no help here, but your post made me think of this. https://youtu.be/tbazGVrbN-g

You can write cross platform mobile (and desktop and even browser) apps with Kotlin.

that's so weird because I got an email inviting me to participate and I haven't ever been considered a 'prolific poster'. I'm only at 60k and 12 years. I had no clue I was invited until I looked in my spam folder.

I have been using Hey for two years now and I like it a lot. Less about privacy and more about, “I don’t want all this junk mail and advertising”

I never said that standardization was bad,

I never said you did.

what I said was that the references for standard measures were more useful. We don’t carry around rods for poking oxen much anymore, so that unit of measure is rightly confined to history.

I just showed you exactly how that is not the case. A measurement saying a foot is as long as your own foot is completely useless in every context except the one where you do the measuring and never communicate it to anyone else. The same applies to literally every imperial unit. I also went on to show you that metric units were also based on standard measurements, like kilogram being exactly the weight of a litre of water. You conveniently ignored the fact that imperial was using weird standards while metric used useful, convertible standards. Please try converting 1cu ft of water to weight in imperial, with the 'standard' that it's the length of your foot, not someone else's foot.

And please do stop referring to imperial units as 'standard' measures. That doesn't mean what you think it does.

I really cannot tell if you're joking or not...

They released lightning about 3 years before the first USB-C phones

3 and a half years before the first usb c phones showed up in china. It was 4 years until it showed up anywhere else.

so they could have worked with the standard,

They literally did work together to create the standard.

delay the connector switch a bit,

You seriously have to be joking. Stop working on getting rid of their shit 30 pin connector that everyone had been complaining about for literally a decade? Why in the world would they stop development for something that was never guaranteed to actually make it out of a standards body? Standards don't just pop up at a set time. They had no clue USB Type-C would succeed or if it did, how long it would take. Not only that, but it's not like they just started developing lightning in 2012. They had to have been developing it for several years, along with the phones to go with it. This is honestly the most ridiculous suggestion I think I've seen in this thread.

They could even have released the first USB-C phone if they’re so keen on being “innovative”.

... they were innovative. They released the first symmetrical connector for a phone, ~4 years before anyone else. Theirs was (and still is) thinner and more robust than other phone connectors. You're literally just trying to rewrite history.

That would have save their users from 10 years of incompatible connectors.

dude.. like.. are you seriously joking? why in the world do you think this?

But Apple never cared about standards, on the contrary they choose lock-in over standards whenever they can.

... this is where you clearly reveal that you are ignorant on this topic. Apple (and every tech giant) collaborates on standards all the time. Please. seriously. Go look at any standard and you will find apple, google, facebook, etc. on the standards body.

You might go 'oh iMessage'. Well apple did try to create a standard for iMessage. Carriers didn't want it

Just because you believe all the apple hate doesn't mean it's true. Just like believing that Google sells your data doesn't mean it's true. Sometimes you have to research stuff yourself.

Dude. The connector allows for different sets of pins. This is not mushing up different concepts. I’ve actually soldered usb c connectors. I’ve even designed PCBs that needed to support PD. Have you read the USB spec? I have. It’s clear you don’t actually understand how complicated the connector itself is.

It is all over the place. The connector allows for all of those things and doesn’t guarantee any of them. Along with that cables don’t even have a guarantee of being bidirectional, a problem with the usb c spec, not with the USB standards.

Also you kind of proved the point. USB C is confusing because it pretends to be universal (see literally the hundreds of comments in this thread) even though it most definitely isn’t.

I can agree with most of that, but my point wasn’t that you should be “tinkering” with your build file, but that as time goes on and your project grows and your team grows you should be making improvements. No active project sits still, and having a tool like maven that is incredibly rigid and hard to use and modify makes that growth incredibly painful.

For example, you can easily start with gradle with just a few lines. You don’t need to worry about plugins, extra tasks, etc. Then as your project grows you can add in things like mutation testing, integration testing, plugins to share your configuration between all your projects. This growth is incredibly easy with a build tool that uses a DSL rather than one that is purely descriptive.

Yes, it’s massive pain if you pick up someone’s project and they’ve made a mess of things. But if you actually work with competent people this generally isn’t a problem. And it shouldn’t be a problem if you’re using open source projects that have a decent number of users.

How do you keep it on then?