It would be kind of difficult to have binary packages unless you have a stable ABI, and Rust doesn't have that yet. If and when it does get a stable ABI, binary packages would at least become a possibility. There are good reasons why Rust didn't want to commit to a stable ABI initially, but perhaps at some point the benefits will outweigh the costs.
The US also has lots of federally owned land which is "public" but used primarily by ranchers for grazing their cattle. It's not that unusual of an arrangement, and the ranchers have way more political pull than environmentalists.
We have very similar signs in the Blue Hills Reservation just outside Boston, but the hours are rather more restricted (I think it's just Tuesdays). So it's not completely unheard of even in the relatively urban Northeast, probably because the deer situation really is getting that dire.
I think the main culprit was Perl's mess of an OO system. While technically it was the same at its core as the Python one, the almost complete lack of syntax to support OO and lack of standards (especially in those earlier days) for objects to interoperate made it needlessly complicated for most people and people moved to languages where they could just write "class Foo".
People always take up space though. The scaling problem comes in when people take up considerably more space when traveling than when stationary, so the transportation infrastructure ends up taking up more space than the thing you're transporting people to.
Or rather `let mut usage: &str`. Rust actually is kind of similar to C here in that the pointer and pointee can be separately const or mutable. But in Rust "const" is the default and mut needing to be explicitly declared, whereas with C it's the other way around.
Anecdote, but a telling one: in my previous round of job-hunting, I had a success rate of exactly 0% with whiteboard coding interviews and a success rate of 100% with other interview methods. That's a pretty stark correlation.
Not really. OpenGL in particular has to do a surprising amount of work on every call, to make sure the state hasn't changed and to update all sorts of things if it has, to manage the various buffers and make sure they're mapped in the right place, and then to go down through all the abstraction layers until you end up in the code that actually writes stuff into the command buffer. It's not going to be a syscall level of overhead, though it may end up being that if stuff needs to get mapped into the GPU address space, but it's definitely going to be more than the dozen instruction overhead of going from JITed to native C++ code.
You don't need to work with SQL strings though, you can work with ASTs or other higher level abstractions, and with Rust's macros and the infer_schema! machinery you can probably find a way to project the SQL types into Rust's type systems to keep things more or less type-safe. But then again, I've never tried to write such a thing, so maybe it's not quite as easy as that. I've definitely used a similar query-builder library in the past though and while it definitely had its benefits over raw SQL, it also led to some abuses where bits and pieces were used to compose gargantuan queries that nobody would have ever thought to write by hand.
This is absolutely the right answer, even though it's not the option that I personally took. If you want to invest in actual property, it should be because you would enjoy having a side job as a property manager, and possibly because you also need a place to live. I own a small duplex, but most of the actual profit from it comes in the form of imputed rent and from the fact that I'm also the property manager and don't have to pay one.
It's hard to say whether the long distance trains are viable as a transportation service, because they're also in the "land cruise" business and oddly enough that part seems even less profitable. It's the source of a lot of the expenses, especially for things like food service. Amtrak has actually tried cutting the diner on one of the Florida trains and dropping sleeper prices by $100, and is making considerably more money on that train, so there's still some potential to get close to 100% cost recovery on LD service if Amtrak gets out of running the land cruise business, which it seems reluctant to do because of tradition.
> Thank goodness the early Pentiums stopped that madness
The idea of a separate co-processor that only did floating point ended with the 387. The 487SX (that was the coprocessor for the 486SX) was actually a 487DX (i.e. a full 486, with an FPU) that took over the system entirely and disabled the 486SX. But that whole scheme was still its own special kind of madness.
Maybe there's a reason it's in a repository labeled "deprecated", namely that it's deprecated. The replacement serialization framework, serde, has exactly one appearance of "unsafe", in a function that is only compiled when you explicitly enable the "unstable" feature flag and that in fact appears to be a reasonably safe use of unsafe.
Those are drivers for the regular GPUs that you plug into a PCI slot on an ARM server. I don't think they'd work with the onboard GPU on the Tegra SoC.
NVIDIA has actually contributed some code to Nouveau to make sure that it will work with the Tegra platform (the graphics engine there, unlike on every x86 platform, isn't behind a PCI bus). Also, the display part of the Tegra SoCs is entirely different from what the desktop chips have and is controlled by an open source driver written by NVIDIA (tegradc).
I've been developing a small self-contained web app to serve as a scoreboard for roller derby. It consists of a server written in Rust that mostly serves a bunch of static pages and javascript files, as well as a JSON API that the javascript calls into to provide the dynamism. Thus far, serde-json has been an amazingly low-friction way to design JSON APIs, and Rocket has been a relatively convenient way to organize web apps.
The closest competitor to my app is written in Java and needs about 200 MB of memory at steady state just on the server. My version runs with an RSS of about 3 MB and considerably better performance.
There's no a priori reason that property rights should survive a person's death, and plenty of arguments against allowing hereditary accumulation of wealth. Note also that currently the first $5.5 million is exempt, which is more than enough for the vast majority of individuals and even quite a few small businesses.
For some historical context, mod_perl development only started in 1996, and it got to version 1.0 in August of 1997, which is probably the first version that anyone would seriously consider for "high traffic use cases". It caught on pretty quickly after that, though, rapidly killing off any prospects something like this WebL might have had.
The limits on "price gouging" that Amtrak is subject to thanks to Congressional micromanagement have not necessarily been a benefit. Trains run empty during the middle of the week, yet prices are still rather high compared to buses. But they can't lower mid-week prices, because then they'd also have to lower peak prices, which would just mean those holiday weekend trains selling out even faster and bringing in less revenue.
> It is the government's place to regulate how prices get advertised.
Indeed, the government has already done this, to mandate that advertised prices are all-inclusive, with all the taxes, fees, charges and so on included in the advertised price you see when you're searching for tickets. Before that regulation, airline tickets were more like phone bills where the taxes, fees, charges, tolls, surtaxes, surcharges, sur-fees, and so on mean you pay $65/month for a "$40/month" plan.
Dynamic routing is fascinating, but also potentially frustrating for the rider. Your trip to work could take 10 minutes, or it could take 30 minutes, depending on who else wants to ride at the same time and how "dynamic" your bus routing gets. With a scheduled service, at least you know when the bus will show up. Of course, if it only runs once an hour and not at the time you want, you may still opt for the "flexible" option, but it's not guaranteed to be a win in all cases.
Works just fine on the NEC, where it's been in use for over a decade. The real problem is that this was a huge unfunded mandate imposed by Congress on the railroads, both public and private, which is why they've been less than eager to meet the deadlines. In some particular cases, notably Caltrain, it's been a disaster, but that's because they decided that they have totally unique requirements and want a totally custom system rather than going with either of the relatively proven solutions.
Speaking as someone who is currently developing a web app with Rust: no, not yet. It's getting there, certainly, but the tools just aren't ready for general use yet and there's still likely to be a lot of change before things stabilize. In particular, tokio is still at 0.1, and many of the web frameworks have yet to move their internals to be based on it. Foundational pieces like serde and diesel have yet to reach 1.0, but are at least usable on the stable version of the compiler now. More bleeding-edge frameworks like Rocket.rs still require nightly though, and will continue to do so until procedural macros are stabilized.
I would assume that this is due to Prop 13, which limits local property taxes to 1% of assessed value, which means that municipalities have to drive up the price of land if they want to collect more revenue. In most other places without these limits, the actual amount of property tax is more or less the same regardless of whether you live in an expensive or cheap city, and the latter just have higher rates to collect the revenue they need.
The ethos of suburbia is conspicuous consumption, especially conspicuous consumption of land, and actually using it to produce something useful makes it more of an investment. This is also why it's illegal to carve off part of your house and rent it out, generally hard to keep boarders, illegal to actually engage in any kind of business in your house, and so on. I guess the ideal is to be like the landed gentry in their country manor, which also explains the obsession with lawns.
It's a good question. Whoever is responsible for the road/bike lane should probably be doing some traffic counts to see how things are working out, but who knows if they've bothered to collect the data.
One problem with just going by your impressions is that cars take up an awful lot of space and a road can look full of cars, even if they don't represent a majority of people. On the typical NYC (or Boston) street, pedestrians outnumber cars 10:1, but get much less than half the space. For another example, the Dan Ryan Expressway in Chicago has 7 lanes in each direction, and two subway tracks in the middle. The subway can (and likely does) carry more people than all the expressway lanes.
Another problem is that in urban settings specifically, the capacity of a road is pretty much always limited by conflicting traffic at intersections, and so the exact number of lanes doesn't actually make a difference as long as it's enough to feed cars through the green lights at an optimal rate.
Which rustup command is that? I could only find "doc" which opens the documentation in a browser, which is not much help if you've got no internet.
Ah... I see. You have to run "rustup component list" and it'll print out a whole bunch of things that you can install like cargo and rustc and 44 different versions of std and also somewhere in there the docs. And then you have to know that that the thing you have to pass to "rustup component add" is not the string you get out of "rustup component list" (something like "rust-docs-armv7-unknown-linux-gnueabihf") but in fact just "rust-docs". And none of this seems documented anywhere in the help text in rustup itself, at least not the 1.0.0 version that I have.
Wifi spectrum usage is also managed to a large extent by spatial separation. There are still fairly strict power limits on 2.4GHz devices which ensure that they have a relatively short range, so while your neighbor might interfere with your wifi, neither of you are going to have any effect at all on someone even half a mile away.
Wait, that thing is a button? I never knew that. I guess you can tell because when you hover over it, the status bar on your browser says "javascript:void(0)". I feel like this bit of design might just be a little bit too flat.
You don't need to go all the way to space to die of hypoxia, cruising altitude for modern jets is plenty good for that: https://en.wikipedia.org/wiki/Helios_Airways_Flight_522 (and several other examples of non-airliner "ghost planes" that I'm too lazy to look up)