cheepin

All of the things you mentioned are designed and tested incrementally. Furthermore software has been used on Mars missions in the past, and that software was also developed incrementally. It’s proposed as the best way because it’s a way that has a track record

That’s a pretty solid endorsement. Where do you work?

Rust memory management is automatic. Object destructors run when the object exits scope without needing explicit management by the programmer

Here's why: https://bconnected.berkeley.edu/projects/google-cost-reducti...

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

I recently had a recruiter from them email for hybrid positions with no remote so take that as you will

Edit: 15 remote engineering positions open out of 219 total on their career site

This isn’t correct for a=5, b=0, c=0. It would return true while OP’s example would return false

He was almost assuredly talking about enforcing carbon tax. Enforcing working hours limits has already been accomplished in many countries.

"An estimated 95% of all cars sold in the U.S. have automatic drive, versus less than 20% in Europe and Japan, where stick-shift is the overwhelming transmission of choice."

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...

The discussion he referenced, if you haven't seen it: https://news.ycombinator.com/item?id=13267537

Or you can call map_err to do an on-the-spot transformation if you don't have a general way to go from Error A to Error B.

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.

If you are measuring response in nanoseconds, 100 microseconds is still a lot.

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.

In my experience they don't really stand out other than being a bit slow (for which it actually got ticketed).

They seem to just be very conservative.

DDOS usually occurs via a botnet of infected networked devices. Thus, the attacker is getting their resources for "free" since their host is unknowingly wasting CPU and bandwidth during the attack, while the defender is paying for theirs.

> Is there an equivalent guide to the compile-time representation of important constructs for those trying to learn C/C++?

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.

http://www.agner.org/optimize/optimizing_cpp.pdf

I read through the Rust book, and the problem I was having with it and the other docs is that it was hard to map the Rust concepts with what actually runs when it is compiled. For a language that touts "uncompromising performance", it was difficult for me to find performance characteristics of the underlying abstractions and std library (for example, are algebraic data structures just tagged unions or does the compiler do more fancy things with them? What about iterators?). I'd really like to see a "Rust for C/C++ devs" guide that helps you figure out if you were using [some C++ feature] the way to get that behavior/performance with idiomatic Rust.

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.

Suppose a company raised money at some implied valuation. If they raise money again at a lower implied value, you call it a down round.

> But now, the XYZ Candy Company building also has become a Pokémon Gym. Players from miles around aggregate to that location because the name and logo are depicted in the app as a Pokémon Gym location. At what point does this mean the app is using the copyrighted design in violation of the copyright registration?

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?

To people confused about the link, copy and paste it instead. The owner of that site is trolling people with the HN referrer.

(2013)

> artificial value to killing them

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...)

That's a pretty painful option compared to just handling rough objects. I've rendered touchID almost entirely ineffective just by grip taping a skateboard.

The answer to your question though is that, at least on the phone's side, it would require your passcode to login

Rhymes with scone

They did not even attempt to get it to send a fresh backup to iCloud before they reset it making it impossible.

[0] http://daringfireball.net/2016/02/san_bernardino_password_re...

This is an interesting solution that I haven't heard before. It certainly seems to solve some of the problems with current copyright, but how do you evaluate the value of a copyrighted work? Off the top of my head, taxing recent past sales of it won't work because a rights holder can just sit on a work keeping it from public domain for free (status quo), and estimating some sort of earning potential doesn't seem great either.

> With: Everything.

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.