I dunno, are you sure you can manually write correct de/serializaiton for JSON and XML so strings, floats and integer formats correctly get parsed between JavaScript, Java, Python, Go, Rust, C++ and any other languages?
Do you want to maintain that and debug that? Do you want to do all of that without help of a compiler enforcing the schema and failing compiles/CI when someone accidentally changes the schema?
Because you get all of that with protobuf if you use them appropriately.
You can of course build all of this yourself... and maybe it'll even be as efficient, performant and supported. Maybe.
That would make sense if protobuf was complex, bloated, slow. But it's not, so the question should be why not use it, unless you are doing browser stuff.
I am curious about what kind of friction you encountered. Were you generating ad-hoc protobuf messages?
Assuming you were using Protobufs as they are usually used, meaning under generated code, I saw no difference between using it in Javascript and any other language in my experience. The wire format is beyond your concern. At least it is no more of your concern than it is in any other environment.
There are a number of different generator implementations for Javascript/Typescript. Some of them have some peculiar design choices. Is that where you found issue? I would certainly agree with that, but others aren't so bad. That doesn't really have anything to do with the browser, though. You'd have the same problem using protobufs under Node.js.
I don't know what you're arguing about here because the farmers in EU are aggressively fighting against regulation to curtail chemicals, environmental controls and minimum healthy food quality mandates.
Yes, and WHY are they doing that? Could it be because they can't fairly compete against imported products from countries where farmers DON'T have those regulations?
I love your optimism. What you'll see is return to 2000s where you may have had "Symbian" as the operating system, but the phones weren't compatible between themselves and apps broke and didn't work across manufacturers (or even product lines) because there was noone enforcing compatibility.
I wonder if you forgot that or you're too young to remember what kind of bizarre hell mobile development was at that time.
Heck, even early Android was really hard to develop for because CTS suite didn't cover enough and all of us spent hours upon hours (and many dollars) trying to reproduce and fix Samsung, Huawei, HTC and other bugs.
I never said it's going to be smoother than it is right now, just that Google will lose control.
8 of the top 10 manufacturers are Chinese, the last two are Samsung (which definitely isn't going to side with Google) ... and Google themselves.
If Google doesn't publish AOSP anymore, Pixels will be the only phone with their software on it, Samsung might attempt something alone and the rest will pick up the development from a Chinese government consortium which will be the de-facto default mobile platform instead of the Google one.
The Tyrant Philosopher series became (surprisingly) my favorite series from him. There's just something about the way how he depicts colonization and pressure to destroy other cultures and minorities that's oddly compelling.
reply