| Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.155 Safari/537.36 | |
| Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/600.7.12 (KHTML, like Gecko) Version/8.0.7 Safari/600.7.12 | |
| Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 | |
| Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/600.8.9 (KHTML, like Gecko) Version/8.0.8 Safari/600.8.9 | |
| Mozilla/5.0 (iPhone; CPU iPhone OS 8_2 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) CriOS/44.0.2403.67 Mobile/12D508 Safari/600.1.4 | |
| Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.155 Safari/537.36 | |
| Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Firefox/38.0 | |
| Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2049.0 Safari/537.36 | |
| Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10240 | |
| Mozilla/5.0 |
The problem with large language models is that you can’t run these locally on your laptop. Thanks to Georgi Gerganov and his llama.cpp project, it is now possible to run Meta’s LLaMA on a single computer without a dedicated GPU.
There are multiple steps involved in running LLaMA locally on a M1 Mac after downloading the model weights.
| // Load the AWS SDK for JS | |
| const AWS = require("aws-sdk"); | |
| // Set a region to interact with (make sure it's the same as the region of your table) | |
| AWS.config.update({region: 'eu-west-2'}); | |
| // Set a table name that we can use later on | |
| const tableName = "people" | |
| // Create the Service interface for DynamoDB |
| 1. Edit ~/.bash_profile and add the following line to show full path before the $ prompt. | |
| For example, as user@hostname:path/to/directory$ | |
| # show path before the $ prompt | |
| export PS1='\u@\H:\w$ ' | |
| 2. Save file and restart terminal or run source command | |
| $ source ~/.bash_profile |
| main() { | |
| var name = 'Alex'; // or whatever your name is! | |
| print('Hello $name!'); // Hello Alex! | |
| } |
| main() { | |
| print('Hello World!'); | |
| } |
| void main() { | |
| var a = 42; | |
| a = 'hello'; | |
| } |
| % | |
| Simple things should be simple, complex things should be possible. | |
| The Wiki Way: Quick Collaboration on the Web, Bo Leuf, Ward | |
| Cunningham | |
| % | |
| Simplicity is the soul of efficiency. | |
| Austin Freeman | |
| % | |
| I have yet to see any problem, however complicated, which, when you | |
| looked at it in the right way, did not become still more complicated. |
| % | |
| Simple things should be simple, complex things should be possible. | |
| The Wiki Way: Quick Collaboration on the Web, Bo Leuf, Ward | |
| Cunningham | |
| % | |
| Simplicity is the soul of efficiency. | |
| Austin Freeman | |
| % | |
| I have yet to see any problem, however complicated, which, when you | |
| looked at it in the right way, did not become still more complicated. |
On Mar 28, 2013 Dan Allen explained how to deploy to github-pages automatically. Many other GitHub users like Steve Klabnik and Domenic Denicola followed with the same approach:
Use an OAuth token with public_repo or repo permission to access the Github account over HTTPS inside a virtual build environment.
The same applies to Travis CI's built-in abilities, and there are more restrictions as deploying GitHub Releases works only for tags, not for branches.
The token grants write access for all of your (public) repositories and
