Why is the commit frame not sufficient to determine whether the transaction was fully written or not? Is there a scenario where the commit frame is fsynced to disk but the proceeding data isn't?
> The data in the article proves Gary's point. Not only is income tax brought in less now, but more taxes are VAT
Does the article data show that? Looking at the tax % graph the ratio between Income+NI and VAT+Stamp duties has been pretty constant (apart from a brief time in the 70s)
> In other words, the poorer people in society are taking on a bigger share of taxes.
Seems unlikely. The article shows that high earners are paying are far greater share of income tax. Poorer people would need to be buying a crazy amount more stuff to offset that with VAT.
The UK is in a fairly unique position where its GDP per capita has been stagnant for decades. Which means it's slowly sinking under inflation. It's been going on for so long that the people at the bottom of the boat are now drowning (which I agree is deeply unfair). But no amount of redistributing people between the decks is going to actually fix the problem.
They give a lot of characters/vbucks away for free. I have a whole list of skins (including the 3 you mentioned) and have never spent any actual money on fortnite.
I can't deny they've made a crazy amount of money from convincing teenage boys that it's cool to buy outfits and play virtual dress-up. But compared to the must-have items of my youth at least you aren't excluded if you have no money.
If this is true why does Apollo need its own server at all? Couldn't the client make requests directly to the reddit api servers instead? Then each user could use their own api key, rather than Apollo having to pay millions for a single key that accommodates everyone.
I've just been practicing Ian's fastest knot for the last 10 minutes and I can definitely see the speed advantage already.
My only issue is in keeping the starting knot tight. I usually use the standard shoelace knot which makes it easy to keep tension on the lace at all times, and that keeps the starting knot tight. But I'm finding with Ian's fastest knot I lose tension when I'm pushing the two loops towards each other, which causes the starting knot to loosen slightly. Is that something that can be solved with more practice?
It might be fun to engineer a gzip stream that uncompresses to something huge, and then serve that instead. I wonder if you could compress it enough that the limiting factor becomes the clients disk write speed rather than the network.
It'd be amusing to see people fill their disks at a far faster rate than they expect their network connection to allow.
Thank you for writing that. I'm going through a rough patch at the moment and you've really given me a moment of clarity. I've realized that there is at least one person in my life that I should be considering a friend which I didn't previously, and one friend who I should really downgrade to an acquaintance.
If you ever find the time to write down more of your thoughts about friendships I'd definitely be interested in reading them.
I struggle to make new friends. The standard advice seems to be to go to meetups, do volunteering, and join sports clubs. I've tried those and can't get them to work for me. There's something more to it than just being in attendance.
I think you're definitely right about that tangible point where things change, and I never manage to quite get there. I don't know if that tipping point is something you can instigate or if you just have to leave it to chance.
I like your solution to prevent the kernel from interfering with your packets.
An alternative method I've used in the past is to add an iptables rule to silently drop the incoming packets. libpcap sees the packets before they are dropped, so you'll still be able to react to them, but the kernel will ignore them (and therefore won't attempt to RST them).
They are using node-webkit which means any javascript has unrestricted access to the nodejs api http://nodejs.org/api/. It wouldn't be hard to do something malicious with those low level filesystem, network and process modules.
I tend to stand behind the desk during the day and recline on the bed in the evenings. I do find reclining with the suspended monitor is very comfortable (sometimes i'll lie almost horizontal with the monitor directly above me) but I think I'd struggle to do a full days work like that.
I always feel guilty about how much I end up downloading from the npm registry. I keep my nodejs projects is separate dirs, so I end up downloading the same dependencies over and over again each time I start a new project.
I wish the --global install switch was cleverer and allowed you to have multiple versions of the same package installed at the same time. Then I could just symlink everything together which would save them bandwidth (and save me diskspace).
When rsync needs to update a file it saves the contents to a temporary file first and then copies it over at the end, which should be an atomic operation on most filesystems. So you shouldn't end up with half updated files (unless you use the --inplace switch), but you can end up in situations where half the files in a directory are updated and half are not, which can be just as bad.
Any plans to release the nodejs code? Coding in the browser is ok, but it'd be much nicer to be able to code in my usual editor and test locally using the nodejs version.
Streams are nice but in my experience there aren't many modules that let you use them. Most networking protocol modules will only let you specify a hostname and port to connect to, and not pass a stream to use. That's fine for the common case, but maybe I want to do something fun like send data encrypted with ssl, which is encoded using base 64, then stuffed in a dns query, then tunnelled over socks, via a unix pipe (and receive the reply via a completely different stack). It wouldn't be hard to chain streams together to achieve that, but then I'd have to rewrite modules to actually use it.
Even nodes own http module only does standard tcp. If it supported arbitrary streams then it'd be much more flexible, and we wouldn't need to do things like use a separate module to support https.
The same with the server part of these modules. They normally only let you specify a tcp port to listen to. Ideally there should be some sort of "stream server" interface that automatically sets up the stream chain and emits a connection event. The module could then listen for that event and use the corresponding stream for transferring the data. That way the module would be completely independent of the underlying protocol.
I don't understand why they didn't just provide an api to normal IP layer sockets, it would have given a lot more flexibility. I'm thinking the sort of lower level networking access you get in node.js
If people really wanted to send data over this weird semi-HTTP websocket protocol then someone could have implemented it as a js library on top of proper socket calls.
I'm guessing the main issue was cross-domain security, but I would have liked to see this solved using some sort of policy file that can be requested from the domain before connecting, like Flash does.
Same here, most man pages seem pretty good at documenting all the available options, but are pretty useless at explaining how the tool should actually be used.
I'd like to see someone dump all the common man pages into a public wiki so people could flesh out the usage examples and suggest alternative tools.
