When your application uses the URL fetch API to make an HTTP request, the development web server makes the request directly from your computer. The behavior may differ from when your application runs on App Engine if you use a proxy server for accessing websites.
> If anything, a microkernel is always more bloated because of the extra code needed to do all the process sync.
there are more than two types.
We have fretted recently because the plan9 kernel is struggling to fit on a floppy disk when loaded up as an installer with most things turned on.
The whole of plan9, kernel, userspace, 386 binaries & sources for 6 architectures fit into 200Mb uncompressed (and the whole shooting match compiles in 15 minutes).
Linux is a re-implementation of an OS that was already considered dead by it's maintainers.
"Not only is UNIX dead, it's starting to smell really bad." Rob Pike circa 1991.
see also "Sometimes when you fill a vacuum, it still sucks."
Does plan9 support 15 different archs with all of their quirks and subarchitectures? WiFi stack? Support for different power modes? Framebuffers? Kernel probes, high resolution timers, extended inbuilt security APIs?
The beauty of plan9 comes from the interface to the userland, not from implementation details and features. If you wanted to add al those features to plan9 I seriously doubt you could get it as lean and quick as Linux.
Yeah, there is the FUSE project: filesystem in a userspace. There are lots of interesting filesystems using this e.g. NTFS-3G, sshfs or ferrisfuse. These projects are valuable and most of them doesn't belong to the kernel as they use userspace libraries for network protocols and xml parsing.
Unfortunately native disk file systems like NTFS-3G is lot more slower than their native counterparts.
&totse users ran tests of zfs-fuse back in the day and found that it was actually noticeably slower than native ext3. From that, I'm inclined to argue the opposite: filesystems should almost definitely be in-kernel. Granted, their tests were on Linux, not on a modern microkernel.
I wouldn't use Fuse as your benchmark. All of plan9's filesystems are userspace (except the one that uses a dedicated machine). They can saturate 10gbe so your objections really concern Fuse and it's hosts.
If those are the columns this isn't 'precise' postal code data. The log/lat is just the 'centroid' of the postal code. At least in the US, most -- if not all -- postal codes are irregularly shaped, so it's not like you can pull up precise GPS data on the perimeter of the postal code (i.e. in order to draw it on a map).
it's called "the Unix philosophy". invented by Doug McIlroy, probably before you were born