fjrieiekd

As a citizen of one of those countries, this fails spectacularly when your family doctor does -not- know best or just doesn’t care about his job, yet due to the huge scarcity of family doctors, will never lose any of his clientele.

Why not have both? :) as far as "backup of human civilization" goes though, Mars has more potential: water, atmosphere (thin though it may be), higher gravity, and a day similar to earth. If the s ever htf on earth, a mars colony has a better chance of surviving one day without earth's help.

I guess for me the question is if that will matter or we get strong AI first.

There's also Swift's approach, which looks like exceptions but is really similar to Rust's approach under the hood. Swift also requires failable calls to be prefixed by "try" which makes them even easier to spot than the postfix "?" that Rust uses.

Rust seems really great as infrastructure level code, but the tooling still has a lot of rough dyes when it comes to mobile development.

I think Swift could play a decent role here if it ever gets good android support as it already enjoys first-class support on iOS. I also agree in that Swift feels very nice. :)

The tooling for Swift is certainly miles better on iOS, but I do like Rust as a language. On Android the most comprehensive solution I've seen is Xamarin, but last time I tried it (which was years ago), I wasn't a fan of the GUI and the perf was worse than Dalvik. Hopefully that has improved now.

And even on Android this functionality has a lot of holes. As an example, just try to find a robust way of sending an email with multiple attachments that only shows email apps and doesn't crash some of those apps.

But what are your earnings? Serious question, not trying to antagonize. There is still a tradeoff, right? Those in the valley work like dogs but there's also a lot of money out there.

This is a pretty neat idea -- I think I'll try this the next time I need to work on numeric code.

Anyone here using Rust on mobile? That's the potential usecase that interests me the most, but given that the tooling still has a lot to be desired, and a lot of mobile code is vendor-specific anyways, I'm not sure it makes that much more sense than just duplicating those shared parts between Swift and Java.

I could see it for small modular parts that are better suited for native code and when one doesn't want to use C, perhaps, or, of course, for infrastructure-level projects like Servo.

I just wonder if I'm barking up the wrong tree because much of the Rust interest I see seems more heavily weighted in infrastructure and backend, not in user-facing code.

Swift does support this also, but they limited it so they could also get rid of semicolons entirely.

In fairness, it's harder to learn Rust as one has to be aware of when and when not to put semi-colons, otherwise the compiler chokes with an unhelpful error. It also looks very weird to see a trailing value just hanging at the end of a long function.

I much prefer the decisions Swift made in this area, with no semicolons and implicit returns only for short functions.

This isn't to knock Rust or the work that you guys do, just a part of the language that can be learned, but does impose a speed bump during that learning process.

Even new diesel trucks from Japan do this in places like the Caribbean. Maybe the standards are lower but I haven't seen a similar problem with new gas cars.

Diesel can be really nasty, much worse than modern gas cars. Even having a diesel truck in front of me is enough to make me gag. It's one of the things I don't like about Europe or certain Caribbean islands where diesel is very popular. Luckily it's not as popular in North America.

And since Android 4.4, access to external SD cards has been restricted unless you use an annoying API or have a rooted device.

Rust is getting there but still lacks type-level integers, and macros are waiting for macros 2.0. It would also be neat to have the ability to run any function at compile time, but I don't think that's in the cards.

How much will that Dell be worth vs the MacBook in 3 years? While not a fan of the newest MacBook, I don't have to be because they -last-.

My main beef with SpiderOak is that I have no way of verifying these claims, so why should I use it over, say, Crashplan, which actually does do a better job of backup. I'll just use a tool like Veracrypt when I need the extra layer of protection, and Crashplan does a better job of incremental backup of these files, too, while SpiderOak uploads the entire file each time.

If the spectrum is good, and there's no flicker, I think this could make sense in the kitchen or hallways. I haven't been that pleased with the LEDs I've seen but they are still better than CFLs and show more promise.

In the living room or especially the bedroom and bathroom, I prefer dimmer lighting with less blue spectrum. My 29W halogen incandescent on the night table doesn't exactly burn through a lot of electricity and has the most pleasing light in my eyes. Until there's a LED that can perfectly match that, I'll stick with that until these bulbs get banned, too.

LLVM Kaleidoscope, or if you'd like to start with your own toy CPU, then nand2tetris on Coursera.

There's still the flicker and glare, and an unnatural "look". LEDs are not as bad as CFL's, I'll grant you that, but still not as good as an incandescent for the living room or bedroom.

Which bothers me less, as it's much darker, contains less blue light with flux or night shift, and doesn't flicker as many bulbs from the hardware store do.

Needs better build support, CI testing and better tooling to match C++ on mobile.

This is why I didn't jump on the spiral CFL bandwagon and why I won't jump on the LED bandwagon for some time to come. Good old-fashioned incandescents may be less efficient to run in summer, but they are heaven to my eyes compared with the crap being sold today. I'll gladly pay for lighting that doesn't make me nauseous or make everything look horrible.

Elon musk was born in South Africa, and spent time in Canada before moving to the US. My point was more about it being possible for these people to achieve their heights in the US, while their place of birth is less important. Jeff was lucky in that he didn't have to immigrate. :)

In IT, Canada is pretty good, too, and scores higher than the US on some business indicators. There is probably more paperwork involved since there are no LLCs so you'd need a corp, but it's very manageable with an accountant's help. I also haven't heard of patent trolls or lawsuits being a problem, which is something that would scare me if I lived in the US.

Of course, if your business is in maple syrup or something else with heavy government intervention, then your experience will likely be quite different. :)

You'd be surprised. I'm not sure if you've ever spent significant time in Europe, but it's not a fairy-tale land. You would also be surprised at how insular and "right-wing" they can be.

As a non-American, what I see is that many Americans, especially those commenting here, suffer from a particularly virulent form of "the grass is greener over there" syndrome. Europe is a beautiful place, but behind the beauty lies ugliness of a different kind. The US has many problems, but there's also a reason why Silicon Valley and people like Elon Musk and Jeff Bezos are in the States.

If you value knowing your place in the social hierarchy and having less and paying more for it, then by all means, adopt the European model. However, as jblow said above, there are so many bright spots in the US, too, so maybe it's better to just work on the rough spots instead of always looking over the fence.

I love Rust and I've been following it for a while now, hoping to use it more in my line of work. However, I still find that support for Rust on Android and iOS is still lacking, compared to C and C++. These platforms are technically supported, but they aren't tier one and don't seem to be widely used.

This doesn't matter that much for hobby programming, but for production work I'd be happier if there was a clear and easy path for adding Rust to the build system, and having the tools integrate into my chain, with great support for debugging and testing. I'm happy to deal with the extra work myself when I'm doing it for fun, but otherwise, compared to the first class support in Xcode or even the NDK, Rust is still far behind.

For me to feel comfortable in taking the risk in choosing a non-vendor-sponsored language like Rust, I need to be confident that my tools will work and won't break on me, integrate poorly or fail in unexpected ways. If Rust was on par with C/C++ support, it would definitely be a very compelling solution.

Sublime with the Rust plugin. It works well for small projects but I haven't yet tried this with a large project.

This is a good one -- I think there's a point after a few years where one realizes just how little they actually know, even if they are otherwise quite proficient. It's ok to not be the smartest guy in the room or have the ability to come up with your own algorithms, compilers, etc...

keep on learning and make use of what you learned, and don't be afraid to be less than perfect and make mistakes.