Having tried to build a much simpler jankier version of the same thing, I agree that Rust is great for a) performance and b) making compilers for query languages. In particular, algebraic data types are great for representing syntax trees and matching is great for operating on them, with optimization represented as transformations from one tree to another. My compiler had a couple of two passes, one to parse the query into a parse tree and the other to do some type checking and name resolution. The execution engine operated on this second tree form, which was fast enough for my purposes.
I'm curious what your queries get compiled into and how you end up doing optimization on them: are they parse trees, or bytecode, or native code (is that what "JIT optimizations" refers to)?
I would think that the reason few women are "Juniors" is because the assumption is that they will likely marry and lose the family name anyway. I'm not actually sure what happens to the suffix when Sue Smith Jr, daughter of Sue Smith Sr. becomes Sue Roberts or whatever, but presumably the suffix is dropped at that point since it is no longer needed for disambiguation.
It captures the spatial externalities, as opposed to the US system of minimum parking requirements and on-street parking, which sets aside valuable urban space that could be used for more housing (or stores or whatever) and wastes considerable amounts of capital (underground garages are very expensive) on making it easier to drive and not actually produce the environmental benefits of living in a city.
There are also situations where a sticky note can be a vital piece of safety equipment because an instrument is malfunctioning. And even though the pilot knows the instrument is showing bogus data, they're so used to looking at it that they will instinctively do so and react to its bogus indications, so the safest thing is to hide it from view entirely. Fortunately there's enough redundancy in the information from the basic instruments that even if one of them fails, you can still fly the plane by extrapolating the missing information from the other ones.
The microsecond level competition comes from the fact that the HFTs can't compete on price below one cent, because the minimum quote increment is one cent. So they have to compete with each other on speed. There have been proposals to allow sub-penny quotes, and thus let the HFTs compete more on price and possibly bring spreads down even further, but those proposals don't seem to have gone anywhere.
Is pixel perfect UI really what you even want these days? With high-DPI screens and screen scaling being a thing, not everyone's pixels are the same. And that's not even talking about accessibility for people with low vision who want text to be big and readable.
Aren't there also linker issues with cross-building for some targets like i686-pc-windows-msvc? At least, I don't think I ever got it to work properly but I don't recall what the exact problem was.
Expanding on this a little, the developers who can survive in the current restricted environment are not going to be happy about getting more competition, and are likely to favor a relatively restricted environment like the one that they currently operate in. The benefits of a looser regulatory environment would accrue to all the people who might want to be developers but can't, due to the high bureaucratic hurdles that only the large corporations or the truly dedicated can overcome.
In California with Prop 13, the current tax payers' property tax rates are well below those of newcomers regardless. So they have no incentive to change things, since their taxes stay at the same low rate either way, whereas in a normal state, I have an incentive to get as much new development in my town as possible to add to the tax base, especially if that new development is stuff that doesn't require lots of expensive infrastructure or tax subsidies.
Each new major generation of NVIDIA GPU was accompanied by an upgrade to the power transformer to the building that the software teams sat in, because it turned out during bringup that the building was already exceeding the capacity of the transformer.
> pressure on hospitals to find ways to reduce prices
This might be the case if hospitals had to actually show their prices rather than sending bills after the fact for a price you aren't allowed to know when you consent to treatment. It might also help if competition were allowed, but for hospitals it is pretty much not in a lot of states. To open a new hospital in many states, you need a "certificate of need", which is basically a document demonstrating that you won't be competing with the existing hospitals. So much for "free market health care".
Not only does Japan have a homeownership rate similar to the US, but a pretty significant fraction of those owners own single family detached homes, which make up the bulk of Japanese suburbs. The main difference from the US is the different zoning regime which doesn't force homeowners to pay for a minimum quota of land in order to buy a house, and suburban houses on 1000 square foot lots are not uncommon.
> Also, if you have a bunch of `mod.rs` files open in your editor, you have no idea what module they corresponds to, as they all say `mod.rs`. Now they'll say the file name instead.
This is probably the most important reason to make the change tbh. It doesn't seem like a big thing but it's one of those ergonomic papercuts that will make the user experience subtly better once it's fixed.
And the market in SF and other Bay Area cities is _really small_. I recently read that Cupertino has only a dozen houses on the market total, and SF may have as many as hundreds or even a couple thousand (in a city with a population over 800,000). Actually, I just looked at Zillow and there are 17 properties on the market in Cupertino, which had about 20,000 households as of 2010.
Good to see that building Servo on ARM will return "i686" as the cpu architecture. Because there are plenty of sites that will just match /arm/ in the user agent string and redirect you to the mobile version, regardless of what your user agent actually is. Which is supremely annoying to those of use with ARM desktops (a tiny minority, I admit).
Unfortunately, it doesn't always work out that way, because congestion tends to be the limiting factor for demand for car trips thanks to a very low perceived marginal cost. So as soon as congestion reduces somewhat, that extra capacity suddenly makes it more attractive for the marginal driver to take a marginal trip, and traffic increases (but not quite all the way back up to its original level).
The problem is that the number of such places is small and generally not growing particularly fast because transit isn't being expanded all that much (and often expansion comes in the form of rail lines to suburban park and rides), while zoning often prevents infill growth in existing neighborhoods. As a result, there is a scarcity of such places in many metro areas and they are becoming increasingly expensive as a result. California's proposed SB827 is an attempt to change this, and hopefully some progress will be made in this direction soon.
That's easy enough: Google is sufficiently big and well known that even if they have an alarmingly high false negative rate, they will never run out applicants, and "weeding out" even a lot of high quality applicants doesn't substantially reduce the average competence of the remaining pool. And the company is big enough that it can absorb the occasional false positive as well, especially when it comes to people who know their algorithms but not, say, how to work on a team effectively.
As a point of comparison, Massachusetts does not have a mortgage interest deduction for individual homeowners, but for landlords income is computed using the federal Schedule E with only a few state-specific adjustments, so mortgage interest is still deductible. Of course landlords also pay tax on their rental income (minus expenses of course), while individual homeowners don't have to pay any tax on imputed rent.
You've got a profitable site that you developed, so you're already a developer. Yes, you can do this, and the money coming into your bank account is solid evidence of that.
Typically hardware will have the base layer, a cursor layer, and possibly a video overlay. But in many cases, the video "overlay" is actually emulated by the driver using a shader to do the colorspace conversion and the texture hardware to do scaling.
I mean, it sort of does and sort of doesn't, but the hardware manufacturers just aren't used to thinking about things in the proper way. Just like the hardware is a black box with no user serviceable parts inside, as far as they're concerned the firmware (because that's still how they think of the OS and everything on it) is a single binary blob with no user serviceable parts inside, even if it's actually just linux and Android. And just like all the hardware parts are designed and qualified for a particular design, the same goes for the software: when you buy your hardware you get a software with it and that's that. As far as they're concerned it's just another component like a screen that gets customized to work with everything else and goes in the box, then is never touched again.
The point is that the rail is already there, and the rail line is already pretty much the best in the US, and already has electrification, that the commuter rail trains don't use for entirely stupid reasons. And sure, buses are great, but one comumter rail train carries the same number of passengers as literally 20 buses. Given that the tracks to Providence are already there, some relatively minor improvements can make the trains suck much less. Your bus idea on the other hand seems like a good alternative to the South Coast Rail boondoggle.
It's not about the absolute wealth of the neighborhood so much as customers per linear foot of fiber (with some scaling for how hard it is to lay that fiber). Apartment buildings with lots of potential customers can end up being much more attractive than mansions with huge yards and one customer in each, even if the mansions' uptake rate is 100% and the apartments' uptake rate is much lower.
> I live in Boston suburbs, my roundtrip commute to work is about 3 hours. Picking up strangers along the way without losing a lot of time, I save the environment a little bit
The DC area has already has a system for doing just this and there is no app involved. It's called "slugging". Because there are HOV restrictions on some major highways requiring you to have 2 or 3 people in the car to use them, an informal market developed between drivers and riders meeting at suburban parking lots. There's no cash changing hands because the payoff for the driver is the ability to use the HOV lanes (or the HOV-only highway in the case of I-66) for a much faster commute.
Amsterdam has plenty of suburbs, they just look different from US suburbs because of the different land-use and planning approach that they have in the Netherlands. Interestingly, Amsterdam actually does have urban freeways, though they run in a ring a couple miles out rather than right through the urban center. But they've also invested a lot in their train network and most people commute that way. I wish I had more to say about Dutch land use planning, but unfortunately I just don't know most of the details.
The thing is, Amsterdam in the 70s looked a lot like DC does today, with no protected bike lanes and cars parking all over the place. So change is possible, as evidenced by Amsterdam and Copenhagen, but any shift away from driving and cars requires better alternatives, including bikes but also including trains and buses and metros. And DC isn't doing to great with that last one.
From what I understand, at the physical level PCI-E uses an 8b10b encoding, which allows the clock to be recovered from the data. Each lane's clock might still be skewed with respect to other lanes, but there's some deskew logic that detects and corrects for this skew. I'm not 100% sure when the skew detection happens. It might be negotiated as part of link negotiation, or possibly it gets detected at the start of a packet, which has a special 8b10b symbol that's not used for data so it's easy to spot.