seriesf

The EV market has already hit a plateau, suggesting that it has exhausted the customer base for very expensive cars with short ranges. September 2019 sales were down (US and global) vs 2018, and 2019 Q3 sales were down vs Q3 2018 as well (also for the US and globally). These sales figures suggest that EVs need something new, like lower prices or more utility, to start growing again.

It does have a lot of features but my beef with it is how its integration into Debian still leaves all the misleading old cruft laying about. Take the MySQL server package. Suppose you want to change the limit of how much shared memory it can use. Well, the package comes with an init script, let’s put the ulimit statement in there. Restart. No effect. Ok, limits.conf. Restart. No effect. Ok, edit mysqld_safe script. Restart. No effect. Oh I figured it out, systemd ignores all these things and you have to set limits in its service file. But if you set it to ‘unlimited’ it silently ignores the statement. You have to say ‘infinity’ for some reason.

All this crud has just been left here to confuse users and I hate it.

That isn't accurate. Sonos works perfectly well on an isolated network, reading your music from a local SMB share or getting it from the line-level input of any Sonos on the network.

Happy Entrez user for many years. Please don't break it :-)

The C++ proto implementation is just already tuned to an absurd degree and it is hard to beat. Any place where copying was an important problem has already been eradicated with aliasing (ctype declarations) so flatbuffers' supposed advantage isn't there to begin with. It's much more important to eliminate branches, stores, and other costs in generated code.

I worked on trying to make flatbuffers work at google and it just never was as fast as proto2/c++. I guess the author of this piece would describe me as an amateur because like the authors of protocol buffers I only have about thirty years of industry experience. AMA.

They are the same size as UTF-8 numbers but much slower to decode. I think the more-bit format is the only glaring mistake in proto that can never be fixed.

Yes but proto 3 was also a mistake. Throwing away presence entirely was wrong and not preserving unknowns was also wrong. Proto 2 forever, imho.

You can just skip messages, strings, and byte arrays you don’t need or can’t decode. They are length-prefixed. Also there’s nothing about proto that prevents it from being aliased to its network buffers (zero copy). The GPs complaint stems from their own ignorance, nothing to do with the nature of protos.

I’ve seen applications that need more than 256MB just for compiled code cache.

The fact that many large and lucrative code bases are written in c++ should disabuse you of the idea that c++ is suicidal.

Sacramento is majority-renter according to the Census, and is the fifth most competitive (ie worst, from buyer’s perspective) housing market in America according to Redfin. I can’t imagine why you think there is “plenty” here.

Housing is so expensive that you'd have to pay ~$50k/year even for those jobs. That's the big problem: anything you do on the demand side, like paying people higher wages, or giving them housing vouchers, goes directly into the landlords' pockets.

The last available vacancy rate in Sacramento was 2.9%, the lowest ever reported. They don’t have “lots of supply”.