http://www.nextbus.com/xmlFeedDocs/NextBusXMLFeed.pdf
http://webservices.nextbus.com/service/publicXMLFeed?command=agencyList
Obtain a list of available transit agencies.
http://www.nextbus.com/xmlFeedDocs/NextBusXMLFeed.pdf
http://webservices.nextbus.com/service/publicXMLFeed?command=agencyList
Obtain a list of available transit agencies.
# Assumptions: | |
# | |
# * After the merge is complete, the directory should exist in the target repository and not exist in the source | |
# repository. In other words, this is a move, not a cross-reference: we never want to be able to push commits | |
# back to the source repository, or merge further changes from the source repository. If you want to do that | |
# instead, a subtree merge is what you're looking for. | |
# | |
# * The directory doesn't exist in the target repository yet. | |
# | |
# In this example, we're moving the "/openstack-swift/" directory from jclouds/jclouds-labs-openstack to |
This document was originally written several years ago. At the time I was working as an execution core verification engineer at Arm. The following points are coloured heavily by working in and around the execution cores of various processors. Apply a pinch of salt; points contain varying degrees of opinion.
It is still my opinion that RISC-V could be much better designed; though I will also say that if I was building a 32 or 64-bit CPU today I'd likely implement the architecture to benefit from the existing tooling.
Mostly based upon the RISC-V ISA spec v2.0. Some updates have been made for v2.2
The RISC-V ISA has pursued minimalism to a fault. There is a large emphasis on minimizing instruction count, normalizing encoding, etc. This pursuit of minimalism has resulted in false orthogonalities (such as reusing the same instruction for branches, calls and returns) and a requirement for superfluous instructions which impacts code density both in terms of size and
/** | |
* A bookmarklet for viewing the largest contentful paint in a page. | |
* Will show each LCP after the bookmarklet is clicked. | |
* | |
* To install: | |
* 1. Copy the code starting from the line beginning `javascript:` | |
* 2. Add a new bookmark in Chrome, and paste the code in as the URL. | |
**/ | |
javascript:(function(){ | |
try { |
Major Linux distributions as of today are unpredictable as targets for independent software vendors trying to publish applications because they are lacking guarantees regarding what software is part of the software stack supported by the operating system vendor.
Reasonably policies would be needed to improve the situation and give outside software developers targeting Linux distributions enough lead time to anticipate changes.
https://github.com/libfuse/libfuse/releases/tag/fuse-3.0.0 was released in December 2016. Now, 5 years later, we are seeing this new major version as a problem, which goes like this: