Having the URL system also makes them so much better for sharing. Imagine being able to share a link that someone could click and it would open up your shared image inside of photoshop.
From what I have seen it looks like Mozilla and Firefox are really leading in WASM. All these detailed posts explaining it in easy to understand terms are amazing as well.
I had a play with rust at the start of the year while I was evaluating if it would be good for the api backend for my new website. I was using rocket as a framework. The language itself seemed quite ready for use and the book was very helpful but I found all the libraries I needed were half finished and didn't have the features I needed or if they did they had docs that assume you will read the source code and work most of it out yourself. I spent ages trying to work out how to set up postgres with it and got stuck on stuff about connection pools and multithreading.
I ended up just using rails in api mode which is a shame because it chews up the limited memory on my server.
Most of these issues would go away if I was a rust pro and I could just write my own libraries and read the source but it really didn't feel like rust was helping me become productive fast like ruby did.
Ruby is also a dynamically type, interpreted language with a GIL, that's much older than Rust. You're sacrificing a lot in terms of speed and correctness up front to get something that's easier to jump into.
Rust crates should have documentation though. Rust has great tooling around writing docs in comments and generating the documentation from those. Rust is also statically typed, which makes it easier to reason about what a function does without the docs. In fact, lifetimes give you even more information about the relationship between inputs and outputs than a normal statically typed language.
I have never felt a typed language slows me down. In a dynamic language you still have to mentally understand what the type of a function is. You can't just throw any data in to it and have it work.
One often doesn’t need TypeScript. TS solves some classes of problems that would otherwise become crippling in projects of certain sizes and of certain levels of complexity, but, by design, JavaScript tends to happily let you throw any data into functions and have it work (by some definition of “work”).
If you define work as not throwing an error. You can't just put anything in to a function and have it return a useful result. Thats why typed language programs like haskell programs often define datatypes that are just an Int because user_id is not the same kind of data as product_id even if they are just an int.
I always found it easier to improve the time waiting for postgres by tuning critical queries than to track down runaway memory usage and tune garbage collection. I also felt like I spent a lot of my wall clock time during active development waiting for apps to start up and run tests or whatever. There are best practices which speak to most of this, but they were hard won.
But that doesn't come for free with Rust. You still have optimize the DB. And then does it really matter which language you use, since the DB is still going consume most of the time generating a web page anyway, right?
My point was that I found the database to be the easier bottleneck to optimize. The other bottlenecks I mentioned, which I found more difficult to optimize - memory usage, GC, and startup time - are things for which Rust has a good story.
You should really be memcaching the database aggressively. I got it to the point that PHP was taking more time than the database for most pages because most pages DON'T need to be updated that frequently.
Maybe. I also tried Haskell and Yesod but had the same issues. It seems the size of the userbase for a language/framework massively impacts how fast I can do things. With haskell I was posting multiple questions on stack overflow every day but with ruby I find almost everything I need already answered.
Bitmessage had this and it would burn up my laptop cpu trying to send a text message but spammers with gpu farms could still take out the whole network with no troubles.
Seems like in a mature implementation your phone/laptop would route the message to a GPU farm and the work requirement could be scaled appropriately. And for whitelisted everyday contacts the computation cost could be zero.
I got a bike light on ebay and after a few months the battery failed. Even though legally I have 1 year warranty I just can't be bothered arguing with a seller for days and then having to pay return shipping which is almost as much as the light is. I ended up getting a light at the store. Cost me a little bit more but the quality is soooo much better and the battery can be replaced rather than having a sealed plastic casing.
If I ever have a problem with this light its only a 3 minute ride back to the store to return it and I know they won't try and dispute it.
It might be worth reaching out to Ebay and asking for a return—they have ridiculously consumer-friendly return policies, and even if the merchant doesn't want the return, Ebay can force it and hold it against their PayPal earnings.
Maybe 20 actual users but google+ is filled with accounts from google users and automatically posted with content from other sites like comments on youtube.
It literally says in the article that they will not ignore calls to locations on the list and they will only keep the information in mind when responding.
Aware of that, however I don't see how it can work in any situation to be honest.
A ) I have an illegal thing in my house, but I register for "please dont shoot me etc". Party B calls the police, door is still likely to be kicked in.
B ) I don't have an illegal thing in my house, I register for "please dont shoot me etc". Party B calls the police, door is still likely to be kicked in.
And at what point does it become meaningless if the majority of residential addresses are on the list?
> wonder how a normal person won't get shot because they make some weird movement.
They do all the time. I saw a video where American police were yelling confusing instructions at a drunk guy clearly trying to do what they ask but unable to work out what they want and when he fell over they opened fire at him because he made a quick movement.
But its almost justified. I have seen videos where someone moves their arm just a bit and the police start shooting instantly before I even know what has happened and a gun falls out of the dead targets pocket.
Thats just what happens when any random stranger could be carrying a gun. Its almost unheard of for someone to be wrongly shot by police in Australia (Probably has happened but its no where near like America)
> Thats just what happens when any random stranger could be carrying a gun.
I'm not so sure about that. Admittedly I haven't spent the time to do reliable research, but I get the distinct impression that fewer people here are actively carrying weapons today than in, say, the 1950s. Yet over time the police seem to have an increasing amount of military gear, generally seem more on edge when I encounter them in public, and it feels much more like an "Us vs Them" thing is going on. It also concerns me that I can't seem to identify a clear root cause for why that would be happening.
You wouldn't want to be mentally ill though. Two cases spring to mind where (young, inexperienced) police shot people without cause. In one case, at a large park, shot a youth, with no one nearby, because he had a $2 steak knife. In another case, in the person's home, where the police had forcefully entered because of a report they might have been suicidal.
That's really sad, and I don't doubt at all that these things happen, but they are so uncommon, even for the mentally ill, it just isn't something I'm worried about. I've actually been pretty impressed at how restrained QPS officers are with how they deal with drunk and psychotic people. I was involved in a fair bit of this while working as a doctor in ED, as well as while working in a psychiatric unit.
If I was going to be mentally ill, I think Australia would be towards the top of my list somewhere of places I'd want to be.
It's probably kept secret because if we knew how easy it was to steal their data that would be bad for their image. Most companies have little to no security other than "no one will think to request this url". Could be a past or present employee who knows all the unprotected systems and wanted to make some extra money selling the data.
