I don't think they were offering up Go as an alternative to C, but rather giving an example of an OpenSSL implementation in a language that isn't C. Rust is mentioned because the prior comment called for the creation of a pure-Rust OpenSSL library as proof that Rust can be used in this context. No such things exists, but they were trying to offer up a similar example to prove the same point.
Thank you so much for saying this. I agree wholeheartedly and think this is a very important point to make. Really, the whole pattern of Why Don't You Know This Already is nothing but harmful. When someone learns something new and shares it, we shouldn't look down on them or demean them for not knowing it already. We all learn different things at different times, and not every CS program teaches the same things. Some are more math focused, some are more engineering focused, and even within those bounds there's space for a huge degree of variation. Let's not put people down because their degree didn't happen to teach something. Let's appreciate their excitement for learning that thing now.
Rust by Example was actually not originally a Rust team project. It was an independent work that was handed over to the Rust team for maintenance by the original author.
As I understand, it received basic polishing and updates to make sure it was correct, but hasn't been edited much beyond that.
I shied away from the word "kind" simply because that has a specific meaning in type theory that doesn't fit here. Higher-kinded types are a must-requested feature for Rust, and I didn't want to confuse readers into thinking this has some connection to Rust's string types.
> The package system for the rust language actually relies on github, as many found out during outage.
This is not quite correct (although close to it). Cargo doesn't rely on GitHub, but it expects that there is some publicly-accessible git repository from which it can pull the source for any crate, and most crates use GitHub. So it's not a particular choice of Cargo, but a side-effect of GitHub's popularity in the community, and the fact that Cargo does not host source code itself.
Did you try using rust-gdb or rust-lldb? They're wrappers for gdb and lldb respectively that make working with Rust code a lot nicer. They ship with the Rust compiler.
These types of articles are always frustrating, in that they very rarely provide an even halfway decent explanation of the math or science involved (if they do, it is buried deep), and are instead little more than a repetitive explanation of the importance of the work, judged by quotes from as many people as humanly possible. This article (which says very little) is still probably too long with all the fluff added around the actual discovery.
Here (http://www.slate.com/articles/news_and_politics/explainer/20...) is an interesting article about this issue from 2009. It says that while some states require the availability of information like name and badge numbers, many do not. However, some police department's will still implement policies requiring it be provided if requested. This is out of date and not terribly detailed, so I'd be curious to hear from someone with more complete or up-to-date information.
1. The people providing the reviews are other students. How qualified are university students to decide if someone has the potential to be best in the world at anything? That classification is both highly subjective and would generally be expected to require some expert-level knowledge of the field the person is being judged in (which an undergraduate student is unlikely to have).
2. The students only seem to come from a small collection of schools, which unfairly disadvantages skilled students from schools not on the list.
3. The site entirely lacks filtering options, so I am unable to see the top people in the algorithms category, for instance. Furthermore, the listing order seems to be completely static, obscuring students who do not happen to get top placement.
In essence, this is a selection of students from select universities, chosen as the "best" through dubious methods, and then displayed in a static order that greatly advantages some of them over others.
I'm not suggesting that combat-based games aren't fun. I've spent countless hours playing first-person shooters and the like, and they can be absolutely wonderful. However, I am also interested in video games as an artistic (not -commercial) medium, and I think that going to combat as the core mechanic just by reflex can limit games in that respect.
As far as Bioshock is concerned, I think it does a decent job with the story, but more importantly I think it represented just another step forward for video games as an artistic medium. It showed that games with a concept or philosophical point could have market appeal, and it paved the way for greater interest in such games down the road. There are stories and ideas that video games, through their interactivity, are uniquely suited to tell, and as a relatively new medium people are still figuring out what its strengths are, and how to make real art with it.
You may not care for video games as an art form. You may only be interested in them as a source of entertainment. That's fine! That's wonderful! We can have both! I am simply happy to see increased interest in video games as art, and I think that something as simple as moving beyond the idea of combat as the core mechanic is an important step toward realizing all that video games can be.
It's interesting that the author's first idea was a combat-based game. For some reason, the world of game development has to a large degree becomes fixated on the idea of combat and violence. So games that don't necessarily need it have it anyway, even when it doesn't make sense (see Ludonarrative Dissonance in Bioshock). Always picking violence as the go-to gameplay mechanic is so limiting, and it's exciting to see games that avoid it and go for something more appropriate to the concept.
It's already been said, but this whole debacle is ridiculous. The fact that a judge was even willing to give Microsoft (a third-party organization) control over another company's property without that company being allowed to know what's happening is horrifying.
The rise of gluten-free dieting as a fad has some interesting effects for people who actually have celiac disease or gluten sensitivity. On the one hand, increased awareness has made gluten-free food more available, on the other, the stigma against people eating gluten-free has risen. So people who have an actual medical reason not to eat gluten get lumped into a fad diet group.
I have a friend with Hashimoto's Thyroiditis. In recent years several studies have found a potential connection between Hashimoto's and celiac disease (it is still being actively studied, and the link is not conclusive), and so some doctors are beginning to suggest that people with Hashimoto's remove gluten from their diet. My friend did, and sure enough saw some thyroid improvement afterward. She is now entirely gluten free (and has been for over a year), and is often irritated at people judging or questioning her gluten-free diet because they immediately assume it is nothing more than capitulation to an idiotic fad.
I'm not suggesting they trust another dev with their IP. Perhaps I phrased things poorly. I think it could be potentially worthwhile to make their platform more open to allow devs to introduce their own IP on it. I also think that Nintendo could be doing more to get older gamers who grew up on their games to play Nintendo again (including, yes, potentially making games available on non-Nintendo platform).
Would console sales suffer? I'm not so sure. The market for, say, tablet games may not be the same market that exists for Nintendo DS games or WiiU games.
More than anything, it seems that Nintendo has just decided to do nothing to fix the situation. Even small-scale experiments in expanding their marketplace reach or opening up their platform may potentially encourage investors in their ability to get things back on track again.
It's a little sad to see things the way they are. Nintendo has a load of beloved IP, and a generation of developers who would likely love to build for a Nintendo platform. But they've failed to capitalize on either.
It seems some intellectuals take pride in being difficult to understand. As if that difficulty is proof of their intelligence. So they use big words and write big ideas, and wonder why so few others appreciate their brilliance. The truth is that it is often harder to make the big ideas easy than it is to make them hard, and that the goal of the people who do the latter is not to spread knowledge but to show off just how clever they are. I dislike this sort of writing for exactly that reason (and, interestingly, it is almost exactly this sort of writing which Orwell took to task in "Politics and the English Language"), that it is more interested in being noticed than in being understood.