261 karma · joined June 7, 2018
More often then not, innovation comes from a reduced number of people doing things differently, and it's very hard to assemble a team of engineers which is willing or even capable of doing this sort of work.
This also comes back to the "decision shielding" from working different hours: it's very common for managers or people averse to risks to try to stick to solutions they know, even if they are suboptimal or do not fit the problem very nicely.
Anyone capable of doing more will soon realize they are spending most of their time solving mismatches between what solution was used/implemented and the problem they were trying to solve. If they don't find an alternative or a way around these limitations, they will leave.
For instance, Go does not give you the option to handle this yourself: you cannot write a library for implementing goroutines or a scheduler, since it's embed in every program. That's why it's called runtime. In Rust, every bit of async implementation (futures, schedulers, etc) is a library, with some language support for easing type inference and declarations. This should already tell you why they took this approach.
Regarding async/await and function colors (from the article you posted), I would much rather prefer Rust to use an effect system for implementing this. However, since effects are still much into research and there is no major language which is pushing on this direction (maybe OCaml in a few years?) it seems like a long shot for now.
Keep in mind Python was considered niche 10 years ago.
"Essentially any" can be better stated indeed as it is too broad, but I can't think of a definition right now that doesn't require a few pages of text.
Bad bad point. There are statically-typed languages with fairly complex type systems. There are even dependently typed languages which check essentially any property of you values and can be used to prove your program correct.
> Most of the work in making sure that your program is correct [...] goes into developing comprehensive tests.
Tests can only show the presence of bugs, never the absence of them. This is not me speaking, this is Dijkstra.
It is ok to prefer one method over the other, but there's clearly an aura of opinion on the statements of this article. It would be better for the reader to explicitly differentiate fact from opinion there.
If he had said, for instance, that every child needs to be molested, that would be more in line with your example. And that would no longer be acceptable.
Outright racism and similar views are indeed less tolerated nowadays, but this is a whole discussion by itself. I'll just add that, from my POV, they cross the line from the "opinion realm", which together with a number of other arguments justifies non-tolerance of these views.
I find it really odd this myoptic view: he is defending a coworker, which is not alive anymore to defend himself. He did not say the victim is lying, he is talking about how Minsky possibly didn't do anything wrong himself.
Is everyone aware there was a protest against the ones involved at MIT (including Minsky)? How would you feel if someone protested against you if you were innocent?
> [...] opining that 14-year-old girls have free will [..]
Not in the US, but that does not apply to a good number of countries is Western Europe, South America, etc.
Now, I do not agree with everything Stallman said, but he has the right to be wrong. Why can't he be wrong? Is he not entitled to an opinion which does not conform to the majority?
Silencing people we don't agree with is a slippery slope, specially when appealing to some absolute morality standard. I see this happening too much lately, including here.
He did not transfer the guilt to the victim nor defended anything wrong that Minsky may have done.
This scenario seems entirely plausible for me. The deceased is not here to defend himself, so I guess it's up to his friends/family/coworkers to defend his reputation.
Also, about the age of consent, I find it ludicrous that a number of people do not know the age of consent on most of the western world is usually 16 or less. Some are even saying "some european countries still have 16 or 14 y/o as age of consent..." as if the age of consent is going to increase in the short term.
Spoiler alert: USA is the odd one out, and it's more in line with Turkey than Western Europe. Let this information sink in for a moment.
You can have the same issue if programming in any other language, including C: excessive indirections, inefficient algorithms, bad abstractions, excessive use of unnecessary libraries, etc.
It's indeed easier to "bloat" your resulting binary in C++ or Rust given the easiness to do higher-level abstractions; since you can more easily program complex solutions you also need to consider your design and the trade-offs on your code.
I'd also like to point out that, in comparison:
* Rust bloat is a speck compared to hundreds of megabytes for a similar Python program + runtime including the same amount of code.
* Rust bloat can be mostly optimized away for systems that really care about excess/unused code - you have #![no_std], disabling of backtraces, aborting on panic, and a lot of other optimizations that throw away a big portion of extra functionality not needed for things like embedded. You have little alternative on things like Go besides removing debugging symbols and doing tricks like "dynamic decompression" (which could also be applied to Rust programs to further reduce their size, btw).
Bottom line is: Rust makes it easier for you to "just add a new library" and it also make you more mindful of the bloat, but we need to keep it in perspective.
Libraries can be implemented by 3rd parties and maybe later adopted as standard libraries or become de-facto standards. That's how it has been done for most popular languages out there, and I think it's a smart decision.
And how do you know I don't? Are you going to tell me you didn't notice my username?
> Your link is basically saying things are getting better, but who knows, they can get worse in the future, [...]
It uses apropriate language regarding future events. Do you have a crystal ball?
A complex system is hard to predict, but you can have an idea of how turning some knobs is going to affect things in the long run.
Also: using caution when talking about the future is what resonable people do; the ones full of certainty about the future are usually polititians of some particular kind.
> Did you know Brazil has more than 400 state-owned companies?
And do you know Canada has 250+?
The USA also has tons of state-owned companies, it just happen that they are owned by states not by the federal government. Most of them are called "public-benefit corporations", which are very similar in the way they operate (often treated as a synonym), see:
https://en.wikipedia.org/wiki/Public-benefit_corporation
Now getting a proper number is not an easy task though, as each state keeps them independently. I have some numbers for New York if you want to have a look:
https://en.wikipedia.org/wiki/New_York_state_public-benefit_...
If every state has at least half of these (~25), you get around a thousand (1000). Yes, three zeroes. And I'm not counting local authorities.
Considering half again (~250), that would push the number to twelve thousand (12000)!
Say what you want about the specifics, but that looks like a very big number for me.
> Like 15s of google?
If 15s of Google is already more factually correct than your sources, maybe you can start there.
Last, but not least, not really into responding all your comment. I've spent some time talking to people defending Bolsonaro. They end up the same way as the guys defending Lula: ridiculed.
Take this as a word of advice: polititians do not deserve your loyalty, specially the ones full of certainty and bringing the "I'll fix everything" motto. I've seen the same thing at least since voting in Brazil became a thing again (hint: Collor). You are not the first and not the last, but you can be one less gullible person to buy into the propaganda. Think about it.
Have a good day.
I would much rather pay a fair amount (more or less $15-$30 per year, which is what I pay on my landline), and then subscribe to a number of them.
This for me looks like a more sustainable model, but I guess that's not what their finance departments think.
I guess that's the idea of Go, to restrict the language power by giving just the functionality the designers think the programmer should have, but to not allow anything too fancy.
However, if you put some thought to it, it really sounds silly when you know that this will only limit your ability to actually use the language and not really "simplify" anything, since it only adds to the general cognitive load of the language - in this case, one more exceptional case.
It's noticeable that there are a lot of differences, and some things seem to have been deliberately made different (even if they are in essence very similar and only syntactically different), so for me it looks a bit odd that most references to Rust on his blog nowadays are of adversarial nature (ie, "look how better we are than Rust").
Last, but not least, it also doesn't help with the big picture that the one continuously posting links about Zig here is just self-promoting their own creation...
Anyway, just my $0.02
"Nobody uses them / they don't work / where are they?" were the answers, all which have good replies if you google for 5 minutes.
Hard to discuss with someone that considers what they know as everything that exists out there. It's a myoptic view of the present and the future.
IMHO, this happens when one has more opinion than knowledge. Pike, unfortunately, seems to suffer from a similar problem.
Not only the default newline handling causes rules to become cluttered the more complex your macros get but the resubstitution of already parsed tokens recursively and the quoting that needs to be considered to avoid this can cause surprises - specially as the number of macros grows bigger.
Maybe for config files or configuring source files m4 is great, but for anything more complex that need to be easier to read and understood, I'd avoid m4.
There are a ton of lines I could go to discuss your points, from "meat is not equal to beef" to "could one live healthily only on the things you listed?" (hint: no).
I see tons of articles with statements of journalists but no real evidence, if you want to discuss with references I suggest going to better sources. Actually, I suggest checking your references as well - this was written on [4]:
"[a major report into the environmental impact of meat eating claimed] eating some meat was good for the planet because some habitats benefited from grazing."
So yeah, even your references "disproving" what I'm saying are actually are actually agreeing with me to a certain extent.
Last, but not least, it's not about who eats what but about sustainable systems - either the system works as a cycle or it will eventually run off. You need to look at the bigger picture.
Perennials combined with animals can be made into a much more self-sustainable cycle.
Be careful with numbers, they can be useful but fail to show the full picture at the same time.
IOW, 100 calories of fat are very different from 100 calories of sugar, and that's completely erased when everything is standardized as a simple "calorie".
Also, there's nothing obfuscated here, and everything is explicit if you know the syntax.
The alternative is not caring and leaving everything for a GC and/or validating values with runtime checks instead. There are other languages which chose these approaches.
For the ones that still want "fake news" completely banned, I have a question: who is going to decide what is true and what is not? A company? The government? Will we have "commissions of truth" deciding what can be published or not? Will the users "vote" on what can be published or not?
Please come with a proper solution and stop arguing for something you and nobody else want. Thanks.
Also, infant/child mortality was much higher at that time - if you count people that lived past the 30s life expectancy was likely not that different from nowadays.