Wow, something weird is going on in your house. I literally never change my light bulbs, I was just thinking about this the other day when I was looking at my extra bulbs and considering where to store them. It occurred to me it's been literally years since I changed a bulb, whereas in the old days it used to be a regular occurrence.
Also it's not hard to work out how much electricity you are saving. If you are worried about a couple of bucks, it won't take much usage of a 80W bulb to blow through that.
Not just that, but the Liberals presented Turnbull as some sort of masterful IT expert on the extremely flimsy pretext that he made a shitload of money flipping an ISP two decades ago.
He has a slightly better grasp on some areas of technology than the average person perhaps, but certainly no more than the absolute bare minimum any communications minister should be required to have.
I agree that his actions as communications minister that contributed to this were horrible, but being given communications minister was essentially a punishment for crossing the line.
(1) The NBN falls under the portfolio, and the government knew they would have to deal with controlling the ever increasing costs of the program, which were hugely underestimated by Labour, and
(2) The person in the role of Communications minister would take the blame for the public realisation that the costs were going out of control and had to be cut.
(3) Any cut would result in a poorer NBN, because that's what cutting costs when you're building any product/service does.
So he was essentially handed that flaming pile of dog shit by Abbott, probably to lower the chance that Turnbull would ever be able to wrestle back power.
Turnbull's solution was to get the private sector to pay for a part of the network (FTTN instead of FTTH). So, costs would be managed, the 2020 target was still reachable, and it leaves the NBN open to improve the network to FTTH later on.
What could Turnbull have done better?
The bigger problem of the NBN is its business model, which charges Telcos for bandwidth on a total downloads basis rather than on a % use basis. This is what causes the poor service of the NBN. This could have been dealt with by Rudd, by using a different model for the NBN, as discussed above, but Turnbull couldn't do anything about that.
Does it bother you if a male candidate gets a position that maybe there's a better qualified female candidate who wasn't considered because "maybe she wants to start a family" or some bullshit? Do you let that (potential) bias affect your judgment of whether the guy "deserved" it?
Biases exist. Meritocracy is an illusion. Deal with it.
I think what's getting lost in this discussion is that Affirmative Action isn't a trigger for "hire a woman over the more qualified man".
All it mandates is that if on paper two candidates are equal scores, your process should pick the female/minority candidate. Historically, if you left it up to people in the organisation they'd go with their "gut" feelings and pick whomever was of a similar background to them.
If two candidates aren't equal, you always pick the better candidate.
> Does it bother you if a male candidate gets a position that maybe there's a better qualified female candidate who wasn't considered because "maybe she wants to start a family" or some bullshit?
Yes. I try and have a coherent worldview. And I don't think discrimination is useful for productivity.
I don't think we have any scroll event handlers on our blog (not 100% sure as I didn't implement the theme). It's a WP site, perhaps that's the common element -- although I don't think WP ships any JS itself...
My best guess would perhaps it's animated gifs triggering a bug in the browser for some reason?
My best guess would perhaps it's animated gifs triggering a bug in the browser for some reason?
That's plausible. Firefox has been buggy as an insect colony in recent releases, and other browsers didn't seem to have any problem with it.
In case it's useful to know: the page was also very slow to zoom at first in Firefox but then when I tried again a minute or two later it seemed to be back to normal. Again, this was a very obvious difference.
I've set up more vanilla cos here in Aus, but I'm (we're) pretty confused about all the tax implications of selling eBooks to domestic and international audiences, and my accountant doesn't seem to be much more clued in.
Any advice you can provide would be highly appreciated.
It's definitely a concern, but I think it's mitigated somewhat by the oplog-tailing approach. Writes go straight into Mongo, as usual, it's just reads from the oplog that potentially tie up resources on the webserver.
Those reads are throttled, so I think the net result of too many writes is just a choked up webserver, and slow "realtime". Potentially a future architecture moves the oplog processor onto it's own server and the effect is isolated to the realtime part.
So with oplog tailing, I can scale by adding multiple Meteor processes behind a reverse proxy with sticky sessions.
It seems that since oplog tailing doesn't work with a sharded database, then each additional Meteor process must also tail the entire oplog and evaluate all transactions for all Meteor processes.
How does this work for a site with, say, 100 transactions per second and a dozen subscriptions to observe? Does it saturate the Node event loop, or are there plenty of ticks left for the application?
And if I use 'skip' and 'limit' to page through large result sets, it looks like oplog tailing isn't an option. Is there a better way to keep the client data small and take advantage of oplog tailing?
You can also paginate by `$gt` and `$lt` operators. For example, if you have a list of posts, they are probably displayed in some order on the screen. Most likely they are ordered by date. You can maintain the pagination by presenting all posts older than X but newer than Y.
Fair question. Obviously that recommendation was supposed to be taken alongside the other recommendations about not touching too many records, so, yeah 'SELECT *' is probably not good.
What I meant here is thinking about making your publication queries simpler when designing your data models.
For instance, sometimes using denormalization you can use a simple equality selector rather than some more complex mongo selector. Mongo makes it possible to avoid the denormalization, but it might bite you as it means Meteor can't do a bunch of short-circuits that it might otherwise do on a simpler query.
