Not all topics warrant certainty, but given the power of news outlets forming opinion and thereby influencing the population's behavior, I do think certain topics demand responsible reporting which doesn't report anything at all if uncertain. It's the same as a good police detective not disclosing speculations to the media because they pursue many leads but only conclude one, and you don't want a mob go lynch people. The same logic applies to news outlets forming people's opinions. That's why I think there's a need for, admittedly few, certain-report-only news agencies. That way, if you read posts on TheSun or E!Online, you get accustomed to not taking it seriously, forming doubt that this is most likely speculation. Once something gets confirmed unquestionably, it can migrate to one of the few vetted-only news outlets, if that's something they cover.
That said, our weather models are pretty good but not good enough to make certain predictions that far away into the future, but they can for the next few hours.
It's like a software company's model of code branches. The Apple/Google/whatever filesystem team works on something, it gets pushed into their level of production branch, then it percolates up to the shared production kernel branch, and after a couple more layers it hits the common branch, which is what public production binaries are made from and consists of kernel, userland, foobar modules all merged together. Not all software shops operate this way, but it's what size of a project can demand after it hits certain amount. The linux kernel works this way too, to name a successful non-commercial project. You can argue this doesn't prevent regressions, and that's true, but it's hard to deny there would be more regressions (aka false reporting) with unfiltered (aka unvetted) reporting.
I'm still waiting for the day that there's a responsible entity that only ever publishes things when they're 100% certain and is willing to bet their freedom (going to prison) on it. But given how information and influencing of opinions is a market and means control of the population, I'm afraid this won't happen with official support, and only be seen as the crazy lunatics news agency that publishes stuff a week or month later after having vetted things.
I'd like to say leave speed reporting to the Twittersphere and mandate a clear label on unvetted news reports on any network, but I doubt politics can have such influence on the media. I would love it if the news reports had a watermark that says fresh-and-unvetted just like "preliminary results" or "consult your doctor before taking".
First we have to encourage and support critical thinking, but too much of it may lead to some influencers misusing it to support causes which deny past and current crimes of humanity on itself and the planet.
I cannot use st because it still has corner cases that xterm works well but st doesn't yet, and I find the need to patch the sources hard to maintain when a new release comes out and has refactorings included.
But I must say that st's font rendering of Unicode is more complete than rxvt-unicode or xterm. With the same font configured in all three, st is the one that manages to render the most glyphs of plan9port's unicode sample file. Would be great to have the same in urxvt or xterm.
Strictly speaking that doesn't say it includes one, just that there's room for one. But I hope you're right. I've looked at the PDF instructions and still wasn't any wiser.
From the description on website, it appears to not bundle the computer, just the case and hdd. So, if we consider the HDD to be 60EURO max, having compared to other WD blue mobile disks (couldn't find the exact model listed anywhere), then that leaves you with 10EURO for the case. The total of 70EUROs may or may not include shipping, I couldn't figure that out without trying to place an order. It's not cheap, but that pricing isn't expensive either. If it includes a Pi 2, then it's cheap.
How do you deal with the fact that some video tracks do not provide the needed cross-frame data or the times you're cutting are at unfortunate points which would require a re-encoding because a quick byte copy of the existing stream doesn't work or at the very least will complain later about missing things like color info (although it's played back correctly by mpv)?
I should add 3, Erlang's bit syntax, which would be a perfect and natural fit for the target of Rust code. It's a very natural DSL to parse or build (complex) bit streams. You don't necessarily have to add bit syntax comprehensions.
I feel your pain, but the features will land when deemed stable. Without more frequent releases, those features would get into a release even later, so more frequent releases are a win either way.
> It's actually more of a sibling in the family who ran away from home at the age of 6 and fell in with the crowd on the wrong side of the tracks.
> Initially Rust was very much like ocaml. It isn't anymore :) Many of the normally-in-functional-languages features in Rust come from these days. Others were lost and re-added later. It's a very complex history.
Yeah, having tried Rust in those days, I kinda stopped when it broke every week, and was then surprised with the surface of 1.0. It seemed like a different person to talk to.
I've made my peace with the C'ification of Rust as the price to pay for attracting a large crowd of developers who grew up with C, C++, C#, Java, JavaScript, Ruby, Python, the list goes on. It's a reasonable sacrifice to make, but the two mentioned basic features aren't complex things to wish for.
> could you elaborate? I'm not familiar with this feature (only have dabbled in sml).
Imagine being able to hoist your match clauses into function head (signature?).
Not all languages with support for that force you to repeat the function name, and there are good arguments for/against. For example in Erlang, when you define an anonymous function, you do not repeat it:
OldEnough = fun(21) -> true;
(_) -> false
end,
Now, this may seem like a stupid little feature, but trust me when I say it's a natural feature to use like recursive functions after you're used to it.
I know, that's why I wrote "when", knowing it's been considered, but it doesn't appear to be missed by enough developers. I'm just spoiled having used those two features, and anytime someone cites the ML family as part of Rust's influence, it reminds me of these two basic, missing features.
Regarding semantics, without having thought about the Rust semantics too much, I'd suggest to check out the most prominent uses for recursive functions in OCaml, SML or Haskell, then try to consider that as the sweet spot to support in Rust.
We are discouraged from writing recursive functions, which comes naturally when expressing many algorithms. Missing TCO is one cited reason to avoid it, so I gather we're not supposed to, generally speaking.
This wasn't one of the question of the survey, but while having the right crowd around, I have to ask.
When will Rust get
1. function head patterns like other languages in the ML family, although Rust isn't really part of the family, but rather a distant cousin from another continent, which once played with ML and family during a summer vacation
2. support for naturally writing recursive functions
I don't know if it's US production influence, but seasons 1 and 2 plus the bonus holiday episode were, compared to season 3, raw and felt more real. If I had to explain it, I'd say it's because it was a pure British production. I really hoped after the bad 1st episode that it would get better, but it didn't achieve the same positive effect as the previous seasons.
That said, if the content of season 3 manages to push some of the concerns outlined into the general public's perception and highlights them, then it's a good thing and well achieved.
The thing that stuck and was funniest for me was from the worst episode (ep 1) about the adapter and planned obsolescence.
Since San Junipero is mentioned here positively, I should add that it didn't work for me and seemed like ep 1 just too long for the content, but that's a subjective thing I guess. I kinda found it uninteresting and boring and honestly the ideas brought forward not crazy or exciting. Maybe it's because having lived in the tech world, the concepts are just as old as the availability electricity or even anyone who watched the matrix or read the mangas it's based on would find it "old".
Playtest reminded of the No End House creepypasta.
My favorite episode, despite the plot flaws, was Hated in the Nation, and that one almost saved the season. In light of InternetOf*, it was the episode I enjoyed the most.
Has this been proven yet? I'm under the impression that we're still in the stages of better not believing any side of the arguments because any secrets - if they exist - will be fresh and well hidden for the moment. If you ask me, I would be very careful claiming to know who orchestrated what.
That said, our weather models are pretty good but not good enough to make certain predictions that far away into the future, but they can for the next few hours.
It's like a software company's model of code branches. The Apple/Google/whatever filesystem team works on something, it gets pushed into their level of production branch, then it percolates up to the shared production kernel branch, and after a couple more layers it hits the common branch, which is what public production binaries are made from and consists of kernel, userland, foobar modules all merged together. Not all software shops operate this way, but it's what size of a project can demand after it hits certain amount. The linux kernel works this way too, to name a successful non-commercial project. You can argue this doesn't prevent regressions, and that's true, but it's hard to deny there would be more regressions (aka false reporting) with unfiltered (aka unvetted) reporting.