1,710 karma · joined June 24, 2016
You do marginal pricing because otherwise providers will simply bid what they think the crossover price will be - marginal prices lower prices in the long run because providers try to improve their margins and lower their bids.
Also renewables bid on the spot and day ahead markets really low because their cost is almost entirely capex (and also most are under CfD anyway so may as well bid 0) - the spread isn't nearly as good as the data would imply. If you didn't use marginal pricing you'd have them bidding higher to cover their capex.
Not exactly two citizenships of the same country.
She is (maybe) entitled to Bangladeshi citizenship which is why the UK government was allowed under UK law to remove her British citizenship because British courts didn't consider her to be stateless.
The only people who can't have British citizenship removed are British citizens with no other citizenship or entitlement to a citizenship. I think in theory that means the British government is legally allowed to remove citizenship from any person from Northern Ireland if they justify it (since they're allowed to claim Irish citizenship under the Good Friday agreement).
The syntax ambiguity adds a lot of complexity to the grammar that makes parsing a lot more complicated than it needs to be.
Sticking `fn` in front fixes a lot of problems.
You can set it up so your devices can have two IPv6 addresses. The shifting address for external traffic, and a static one for local traffic. I think this is the default in many linux distros now.
It's a transverse mercator projection rather than a mercator as you might often see because it minimises distortion over the UK as a whole which means that the distortion is as you move away from the meridian, rather than as you move away from the equator (with a regular mercator I think all points have the grid aligned with true North)
This grid is setup such that it's origin is not on the prime meridian (at Greenwich), but 2deg west so only points on the line 2deg west are aligned with true north.
So now if two different websites embed the same remote font then visitors will have to download it separately for both sites.
- logs are generally proportional to the length of the job
- other artifacts also usually correlate to an extent
- some of the cost for Github will be for the entire time the job is active: e.g. active connections for log streaming etc. - it's largely correlated to the value the end-user gets out of it
- it's easy to bill for because they can already do billing that way on the hosted runners
- the costs are easy to predict for end-users
It's not like the rest of the Github platform is a per-user cost to run, but that's how Github charge for most features.
There is however the Salisbury convention which is that the HoL shouldn't block legislation that was a manifesto commitment of the governing party. That doesn't meant they can't amend it at all, but they can't substantively change it. It's also just a convention, not a rule.
The overall rules haven't changed.
Strictly speaking they've always been obligated to not break the Rust code, but the R4L developers have agreed to fix it on some subsystems behalf IIRC so Rust can be broken in the individual subsystem trees. But I think it's been the case all along that you can't send it to Linus if it breaks the Rust build, and you probably shouldn't send it to linux-next either.
The why is because it's safer: it reduces the validity period of private keys that could be used in a MITM attack if they're leaked. It also encourages automation of cert renewal which is also more secure. It also makes responding to incidents at certificate authorities more practical.
For a start-up it's much easier to just pay the Cloud tax than it is to hire people with the appropriate skill sets to manage hardware or to front the cost.
Larger companies on the other hand? Yeah, I don't see the reason to not self host.
It's still a bit silly though, their claimed reasoning probably doesn't really stack up for most of their config changes - I don't see it to be that likely that a 0.1->1->10->100 rollout over the period of 10 minutes would be a catastrophically bad idea for them for _most_ changes.
And to their credit, it does seem they want to change that.
The plugin situation is a mess largely because Wordpress isn't a nice piece of software.
It's popular, and functionally it's great, but the codebase is really showing its age. Wordpress has never properly rearchitected because it would break plugins on a scale that would endanger its dominance.
It's a common thing I've experienced and seen a lot of others say that the stricter the language is in what it accepts the more likely it is to be correct by the time you get it to run. It's not just a Rust thing (although I think Rust is _stricter_ and therefore this does hold true more of the time), it's something I've also experienced with C++ and Haskell.
So no, it's not a guarantee, but that quote was never about Rust's guarantees.
The fact that Rust gets to benefit from the project too is just an added bonus.
The most I can reach on mine is 132deg
The cold hard truth is that LIDARs are a crutch, they're not strictly necessary. We know this because humans can drive without a LIDAR, however they are a super useful crutch. They give you super high positional accuracy (something that's not always easy to estimate in a vision-only system). Radars are also a super useful crutch because they give really good radial velocity. (Little anecdote, when we finally got the Radars working properly at work it made a massive difference to the ability for our car to follow other cars, ACC, in a comfortable way).
Yes machine learning vision systems hallucinate, but so do humans. The trick for Tesla would be to get it good enough to where it hallucinates less than humans do (they're nowhere near yet - human's don't hallucinate very often).
It's also worth adding that last I checked the state of the art for object detection is early fusion where you chuck the LIDAR and Radar point clouds into a neural net with the camera input so it's not like you'd necessarily have the classical methods guardrails with the Lidar anyway.
Anyway, I don't think Tesla were wrong to not use LIDAR - they had good reasons to not go down that route. They were excessively expensive and the old style spinning LIDARs were not robust. You could not have sold them on a production car in 2018. Vision systems were improving a lot back then so the idea you could have a FSD on vision alone was plausible.
Spain has 40GW and GDP that's about 1/10th of China. Still, dividing China's capacity of 90GW by 10 still means they built a quarter of Spain's capacity in a month. Crazy.
The reason labs was started was to be able to produce different kinds of content, and to have a moat on technical data and quality of reviews that no one else can pull off.
Fixed costs and capital costs end up being shouldered by the consumer which ironically ends up pushing overall costs up.
The UK often has excess wind energy, and for Tilbury in particular that problem is set to grow as National Grid are building out massive grid capacity from the North Sea wind farms through Tilsbury