> by the way they are pushing development of so many products...
"They" are many different people (developers or contributors). As an open-source project, people focus on what they like or may need.
Furthermore, V has a native backend, in addition to others: C, JavaScript, WASM, etc... They've stated (on their website) that their plan is to eventually make the native backend the primary, as they close in on 1.0. The other backends can be seen, for those that have actually used or know of the language, by checking out the -b flag.
It is important to note that (at the time of writing this comment) the native backend can compile only three examples in the `examples/` directory in the V compiler codebase:
hello_world.v
fizz_buzz.v
rune.v
All the other examples fail to compile when V is used with the `-b native` flag.
But are they compensated or are we dealing with disguised wage theft[1]? A lot of times, when it's time to pay all that overtime or when someone finally speaks up about it, suddenly the "fun" stops.
Then there is the not speaking out, resulting in: 1) Burn out and quit. 2) Company dumps or fires them after burning them out. Then does the same to the new ones. Until something obvious or tragic stops them. 3) Quiet destruction of personal lives. Sometimes leading to significant health and/or mental problems, related to stress, and even suicide in some cases.
Balance is necessary, because otherwise it can be like playing with fire. It's all "fun and games", until people get or realized they got burned.
That's an interesting point. Agree that readability is somewhat subjective, but many programmers find .map, .filter, .reduce, etc... as more convenient and provides clarity as to their intentions. Many languages (like Vlang, Java, Python, etc...), arguably also have them to more closely align themselves with the functional programming paradigm.
For simple combinations I agree (maybe 2-long chains with very simple conditions and transforms - but for such things loops are also trivial to read).
But I have seen "functional contraptions of horror" where those functions are both chained and nested which were completely undecipherable by mere humans.
And at least from my personal impression, people who are a fan of this type of functional style are also more likely to create such horrors (which they themselves of course find totally readable and superior to "unreadable" loops) - I suspect that there's often a bit of cargo-culting going on.
That's not true. There are many natural and biodegradable alternatives for plastics that could be used, but aren't, and get blocked by oil companies and those they are paying off. Just like when action or laws against climate change are mentioned, there is a wave of opposition that traces back to oil money as well.
Basically, oil companies are being allowed to wreck havoc on the planet and our health, for the sake of maintaining their profits. The problem is the clock is ticking, and one can keep their head in the sand and pretend to ignore the danger for only so long, before inevitable reality happens.
If anything, such companies using keyloggers should be forced to openly state such practices to any potential employees. If they are really so proud of it, then don't be sneaky, let potential employees know about such practices and choose not to work for them.
Companies that need keyloggers, often have dysfunctional management and processes to evaluate employees, so need to resort to such desperate measures.
It doesn't appear to be as simple as that. She worked at the company for 18 years. If she was unproductive and committing fraud for all of the 18 years there, then that is a reflection of how incompetent her managers and the company's processes are.
To be employed by them, for so long, means that she was likely productive for most of her time there (then slacked off at some point) and/or how employees are managed and evaluated at that company is completely dysfunctional.
I honestly think the company being too dysfunctional to be aware of her behavior is more likely than her being a productive employee for more than a decade and then deciding to do no work.
> I don’t like the privacy implications. However it sounds like her litigation was baseless so at least making her visible helps future employers avoid her and risk of litigation.
But the privacy implications should not be ignored, and it appears the company and media organizations seek to do further damage and harm, beyond what was required to win the case.
The ability of people to change or their right to seek future employment elsewhere, can't be ignored or purposely inhibited without creating more legal and litigation issues.
Many other languages give the backwards compatibility promise. For instance Vlang (https://vlang.io), does as well. But in their case, they limit it to a 3 year backward compatibility promise, which kind of makes more sense (also due to them being in beta). It gives them more flexibility to make needed changes to the language, but enough stability to limit issues for users. Though in general, such more open languages are going to be more responsive to users and their requests/needs, because of how they are structured.
The problem with Cloudflare is they purposely attempt to break user privacy by dangling websites as carrots. It's deception that they are attempting to determine if the person is human or not, because often they won't even show you the CAPTCHA. Even if you do get to the CAPTCHA, sucessfully doing it usually won't give you access to the website either. So, what is the point?
They want people to disable any privacy protections or push usage of browsers that have no to less privacy protections, in order to access the website they are blocking. This has nothing to do with if a user is an actual threat or bot, but is more a strategy to shape what browsers are used and destroy user privacy.
Cloudflare is also very aware of the numerous and constant complaints about what they are doing, coming from users and for years. They are ignored, because they have something else in mind.
"They" are many different people (developers or contributors). As an open-source project, people focus on what they like or may need.
Furthermore, V has a native backend, in addition to others: C, JavaScript, WASM, etc... They've stated (on their website) that their plan is to eventually make the native backend the primary, as they close in on 1.0. The other backends can be seen, for those that have actually used or know of the language, by checking out the -b flag.