I'd love to see a size comparison of the DWARF encoding vs the binary search map. I have a strong suspicion that there's a neat perfect hash solution to this problem - perfect hashes can encode keys in single digit #bits, and you get faster lookups.
> Note that seccomp has limited visibility into recvmsg / sendmsg args because bpf can't dereference syscall arg pointers.
BPF programs attached to syscalls (via kprobe or fentry) can read arguments via helpers (bpf_probe_read_{user,kernel}). Seccomp uses "classic BPF" which has no concept of helpers or calls.
The FDA's report on third party servicing says this:
> The currently available objective evidence is not sufficient to conclude whether or not there is a
widespread public health concern related to servicing, including by third party servicers, of
medical devices that would justify imposing additional/different, burdensome regulatory
requirements at this time. Rather, the objective evidence indicates that many OEMs and third party entities provide high
quality, safe, and effective servicing of medical devices.
From my personal experience poking at a CPAP machine, there's nothing magical about it. All the sensors and active elements I could track down are available from the respective manufacturers in large quantities. The CPU is a freaking off the shelf STM32F4 with the jtag header still on the board. This is not some impossible to debug hyper-integrated design.
Except that's not how class linking works on Android :)
In particular, everything is compiled down to lookup tables and hash tables within each odex/oat. Your point still stands but the hit is much lower than you would think and given the slow speed of the superfluous reads, it ends up being a net positive for A LOT of cases.
This articles conflates a lot of things but it also has the priorities somewhat wrong.
1) fsync cost. Yes, fsyncs are dangerously slow in any Android app. (SQLite for example is a common culprit. Shared Prefs are another). HOWEVER, it's possible that flushes cause reads to be queued behind them (either in the kernel or on the device itself) which is even worse because
2) Random read cost is super super important. Android mmap's literally everything and demand paging is particularly common AND horrendous as a workflow. To add insult to injury, Android does not madvise the byte code or the resources as MADV_RANDOM, so read-ahead (or read-around) kicks in and you end up paging in 16KB-32KB where you only wanted 4KB.
Also, history has shown custom flash-based file system on Android to be a world of pain. yaffs, jffs have some pretty atrocious bugs/quirks. I'd much rather see the world unify on common file systems, optimized for flash-like storage, rather than OEMs shipping their own in-house broken file "systems" (I'm looking at you, Samsung).
Last I looked, no, but the immediate cause of nondeterminism I saw was the zip entry timestamps in the apk. I didn't bother looking further down the chain.
The Bod and in general the wider library system in Oxford (over 120 libraries!) was easily the best part of my undergrad academic life there. Having a dedicated space for studying, open 24/7, within 20m of my room was absolutely liberating and fundamental to the experience.
I sometimes wonder whether I should continue my education somewhere like Oxford, just so I can experience the focused concentration of a library again.
In this business, the big competitors all reserve a bunch of rooms in the hotels and manage their booking themselves. The hotel is then not allowed to touch these rooms.
The model here was to give the hotels a reception-desk piece of software and have them use it to maintain availability. A lot of the hotels that signed up had nothing like this, so it was definitely a win for them. Armed with exact availability, you can have a much better booking system (and of course, if the hotel only wanted to give you a chunk of their rooms, they're perfectly capable of doing that).
Hotels can sign up on their own (including local bank details, etc) and just need to be reviewed before showing up on the site. It supports i18n, scheduled payments, lots of bells and whistles.
The fact of the matter is that this failed because of market reasons (too small a market, dominated by big players, primarily) but it may have a niche somewhere else on this planet. :)
In this business, the big competitors all reserve a bunch of rooms in the hotels and manage their booking themselves. The hotel is then not allowed to touch these rooms.
The model here was to give the hotels a reception-desk piece of software and have them use it to maintain availability. A lot of the hotels that signed up had nothing like this, so it was definitely a win for them. Armed with exact availability, you can have a much better booking system (and of course, if the hotel only wanted to give you a chunk of their rooms, they're perfectly capable of doing that).
Hotels can sign up on their own (including local bank details, etc) and just need to be reviewed before showing up on the site. It supports i18n, scheduled payments, lots of bells and whistles.
The fact of the matter is that this failed because of market reasons (too small a market, dominated by big players, primarily) but it may have a niche somewhere else on this planet. :)
While I'm not arguing against your overall point, your example is not a good one. Volley was unnecessary. It only got attention because Google did it but the community was already on top of the issue. From shipping their own, newer Apache Client libs, through koush's ion and picasso, to Square's okhttp, networking on Android is full of good libraries to use. Volley didn't anything dramatic to this and, judging by the amount of attention it has received, it was someone's side project.
As someone just now learning how docker works, I absolutely agree.
Personally, I think there are some new-ish interesting immutability ideas that can be explored with regards to static files. It's not clear to me whether static assets (or even static sites) belong inside the container. I would be really interested in experienced folks' opinions on the immutability of the image. Where do you draw the line on what goes inside it and what's mounted in?
Book In Bulgaria - http://www.bookinbulgaria.com - It's a full-blown reservation system, with a hotel reception endpoint (so that availability is always accurate). Hotels can sign up themselves, and it also has fully automatic billing.
We've received really positive feedback from both hotels and tourists, it just turns out that Bulgaria is a really (really) tiny market.
It's either that or Twitter will be completely blocked in Turkey. They're playing a tough game but at least it's a game that the Turkish public can play too, as long as you're faster than the censors.
The alternative is for the government to take down the entire game field.
It looks like it's using tcp flow tuple + tcp_seq to join things.