I only use languages that don't have a centralized community, except for maybe a mailing list. (in my FOSS projects, I use Rust at my job.) That alone rules out trannies and other mentally unwell oversocialized queers. In the best case, the "language" is just a stable specification with multiple conforming implementations.
int
func1(
int a,
double *b,
char *c
)
I work with a client that does e-commerce and some of their business cases are implemented as exceptions. There are several services that each log ~10k exceptions every single day as a part of regular business flow. I imagine that back in the day someone would fix it because it makes the logs look like a nightmare to navigate but nowadays this stuff is in the cloud and filtering out these false exceptions using built-in tools is not a big deal, so no one gives a shit.
the cherry on top is how he uses
xx as a loop variable
I always use either x, y, or z. Am I doing wrong?
He's just intilising the list to 0. Can't he just do
global.story_array = { 0 };yes use i, j, or k as index variables unless you have a good reason to use something else
I thought any letter could be used, though I'm guessing that it's good practice to use i, j, or k as index variables.
Yeah, that's more my style.
As our resident JS defender, I must remind you that Javascript was not delivered unto the web by a proclamation of God, but by being the least bad option compared to every other attempt at what it did:
Can't you just use shared_ptr to a string object? Even if it's pure C it's still possible to make a shared_ptr type struct that doesn't limit you by type.
sure but thats not exactly trivial either and only takes care of the memory management. you would still need to implement all the operations you might/will want to perform on the strings on top of that
google is trying to do that nowadays
that may have been part of it, but a big issue was that the sandboxing was shit and java still has a slight reputation for being insecure as fuck
All the other options trying to compete with JavaScript were all paid and property. So naturally the option that didn't cost any licencing fees and already worked on every browser won out as the standard default option.
The problem with Applets is that the first versions of Java were incredibly slow. Like probably a few orders of magnitude slower than current JS. They were also just completely at the wrong part of the spectrum on sandboxing - so sandboxed that you didn't get native styling or keybindings or integration with the desktop environment, but not sandboxed enough to prevent near constant security vulnerabilities. The download and initializing times were long but they were often faster than a comparable flash application.
This hasn't really been a thing for like two decades at this point. Not since Java got generic types.
ngl that's probably not the biggest problem for early java, "a few orders of magnitude slower than current js" is more than fast enough to do most of the stuff that scripts in web browsers do, even today
the biggest part of this is that you can use any random browser (firefox's spidermonkey implementation has its own jit too) and you will get a reasonably quick language with access to apis that just about work on anything