Plastic is better for the environment than everything else.
Plastic is better for the environment than everything else.
It’s done less and less because recycling plastic bottles is better.
Glass bottles are much much worse for the environment.
What’s the point of your schema if the receiving end is JavaScript, for example? You can convert a string to BigNumber, but you’ll get wrong data if you’re sending a number.
Why are you so ignorant?
Well, the issue is that JSON is based on JS types, but other languages can interpret the values in different ways. For example, Rust can interpret a number as a 64 bit int, but JS will always interpret a number as a double. So you cannot rely on numbers to represent data correctly between systems you don’t control or systems written in different languages.
Yaml is cancer.
What that means is that you cannot rely on numbers in JSON. Just use strings.
Well, apart from float numbers and booleans, all other types can only be represented by a string in JSON. Date with timezone? String. BigNumber/Decimal? String. Enum? String. Everything is a string in JSON, so why bother?
I know how React Native works and it doesn’t fix anything. For example, if the underlying toolkit punishes you for deep nesting - you’re still fucked. Google recommends to have 10 or less levels of nesting, which is bonkers to any web developer. There is similar advice for iOS, Mac and Windows (not sure about GTK and Qt, haven’t used them for over a decade). Each platform has its own solution, so you end up with custom code for each and at that point or doesn’t matter if you’re coding in C or JS.
I vote for nanoid.
There are several issues with native development without a browser layer.
First of all, native UI toolkits are very different and making a robust cross platform app is pretty much impossible. So, the traditional approach is to use one toolkit, which will be native to one platform, and then let your other users deal with it. For example, GTK apps on Windows and Mac look and feel like shit.
Another approach is to use a custom cross platform toolkit, which doesn’t use anything native at all. If enough work and thought is put in such application, it can be a very pleasant experience. But often it’s shit for all users.
The second issue is that it can be quite hard to manage fluid window sizes and to build a proper responsive UI with native toolkits. Some are better at it, some are worse. Native toolkits also tend to punish developers for deep nesting of components making UI development even more painful.
HTML + CSS solves all that. It’s responsive by design, everyone is used to web apps already, nesting is not a problem at all, etc.
Sex. The reason is sex.
I guess you live in a country with loads of spare IP addresses. Here in the UK they change every few days and IPs get rotated between all ISPs, so you can’t even deduct which ISP I’m using. And sometimes my IP is not even a mainland UK IP, but some weird shit from across the world, because Empire, lol.
Your IP changes all the time, it doesn’t matter. The best someone can deduct from your IP is the country.
I would also like to add some of the higher level features available in most assembly languages.
Modern assembly languages have even more higher level features, like macros support. And some are even hardware agnostic, like intermediate representation assembly language used in LLVM.
Guess what, assembly is also a high level language, lol.
1st level is direct binary code as was done with punch cards. Assembly language is a 2nd level language. C is a level above, thus it’s level 3.
You should remember that the gun death rate in the US is only three times lower than in Ukraine during an active war. US is a fucking war zone!