602 karma · joined March 24, 2014
TLDR: Google Workspace for Education rug pulled schools on their "unlimited" plans, and the deadline is coming up to avoid paying extra fees. This was communicated in advance, but maybe still a bit quick for a large institution
Edit: 15 remote engineering positions open out of 219 total on their career site
Still a good market globally, if not in the US. I'm more worried about EVs taking over than automatic transmissions.
http://www.nydailynews.com/autos/americans-driving-stick-shi...
I still sometimes make mistakes reading rust code with the ? at the end of the line, but it's just a question of what type is it and does the line return. Both of which are handled by the compiler in the end, so you get a little bit of extra knowledge that even if you misread the line of code, there's often limits to how much damage you can cause.
However, it may be good enough for games at well below 1% of your time budget for a 60 fps game assuming cache locality is good enough so you don't waste too much time fetching from main memory.
They seem to just be very conservative.
Definitely. It was taught in school and there's pretty good guides for it online (maybe not caught up to c++11 and beyond, but the fundamentals are there). You're right that it is not readily available for most languages, but when you need to get serious about performance you either are going to have a guide or spend a lot of time looking at assembly/bytecode. To be fair, I'd probably still have to inspect generated code sometimes, but it's nice to have good instincts for how things run to guide your design/implementation so you can spend less time looking at assembly.
Another thing that is still tricky for me is figuring out when I should use 'unsafe' blocks in my code. Is it to be avoided if at all possible, or should I go there any time the 'safe' part of the language is making it difficult to express what I want? The meme that Rust is C++ without SegFaults and or race conditions is a bit misleading since the actual guarantee is that you don't get SegFaults or Race conditions outside of Unsafe blocks, and any nontrivial project will make use of unsafe blocks.
All the pictures used are taken from public property iirc. Wouldn't the copyright for the picture taken and the copyright of the building be two separate things, the former belonging to the taker and licensed to the company? If not, is Google Maps compelled to censor their street views of copyrighted architecture?
Another way to think about it is an artificial value to keeping the population going. All the animals will eventually die yielding a reward, but if you can keep a population going, the reward will keep coming.
The "solution" for countries who wanted to remove invasive species is to embrace pretty heavy handed comprehensive enforcement. (See http://www.scientificamerican.com/article/canada-declares-wa...)
The answer to your question though is that, at least on the phone's side, it would require your passcode to login
[0] http://daringfireball.net/2016/02/san_bernardino_password_re...
This may be nitpicking but certain classes of programs cannot be realistically built with Haskell. Anytime you need to tightly control latency (soft realtime) won't really work since you have both a garbage collector and lazy evaluation. Memory constrained systems are pretty tough as well since you don't really get insight into allocation/deallocation, which also makes structuring your data into a particular memory layout tricky compared to C(++) for instance.
Not to say that Haskell isn't awesome. It should probably be used for more systems. It just can't be the "hammer" to make every problem into a nail.
Look here: http://try.ocamlpro.com/
Try this code:
let g() = 5 g() == 5 g != 5
First line defines the function. Second line should evaluate to true. Third line doesn't type check because a function is not the same type as a literal.
This study isn't a contradiction. It just says that micronutrients matter, which is pretty uncontroversial.
http://examine.com/faq/does-metabolism-vary-between-two-peop...
This means among other things, it will be easier for Apple to abandon the idea if it ends up not being worth it, since it is such a small part of the UX of the devices, or even replace it with some other mode of interaction.
1.) Delete their harassing posts and/or report them.
2.) Use the privacy settings so they can't see or interact with me
3.) Not use the service if it isn't contributing to my well-being
It's hardly inescapable, and I was just using Facebook's options as examples because I know it's interface pretty well. Similar things could be said for most of these places. Unlike the schoolyard scenario, no one is forcing you to engage with the bullies: you can almost always block/ignore.