papers-we-love
Previous Serverless Version 0.5.x
Our great sponsors
papers-we-love | Previous Serverless Version 0.5.x | |
---|---|---|
69 | 90 | |
83,329 | 46,080 | |
1.5% | 0.4% | |
3.2 | 8.2 | |
3 days ago | 3 days ago | |
Shell | JavaScript | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
papers-we-love
-
The Top 10 GitHub Repositories Making Waves ππ
Papers We Love (PWL) is a community built around reading, discussing and learning more about academic computer science papers. This repository serves as a directory of some of the best papers the community can find, bringing together documents scattered across the web. You can also visit the Papers We Love site for more info.
- What led you to use Linux as your daily driver?
-
We have used too many levels of abstractions and now the future looks bleak
You might find the paper Out of the Tar Pit interesting if you haven't already read it: https://github.com/papers-we-love/papers-we-love/blob/main/d...
The ideas and approaches you talk about evoked some of the concepts from that paper for me. It talks a lot about separating accidental complexity and infrastructure so you can focus only on what is essential to define your solutions.
- Out Of The Tar Pit (2006) [pdf]
-
John McCarthyβs collection of numerical facts for use in elisp programs
Sure he was expecting a practical language and was designing one. Lisp was from day zero a project to implement a real programming language for a computer.
Earlier he experimented with IPL and also list processing programming on Fortran. The plan was to implement a Lisp compiler. At first the Lisp code McCarthy was experimenting with, was manually translated to machine code.
Then came up the idea to use EVAL as a base for an interpreter, which was implemented by manually translating the Lisp code to machine language. Around 1962 then a compiler followed.
https://github.com/papers-we-love/papers-we-love/blob/main/c...
-
Python: Just Write SQL
I'm in a 4th camp: we should be writing our applications against a relational data model and _not_ marshaling query results into and out of Objects at all.
Elaborations on this approach:
- https://github.com/papers-we-love/papers-we-love/blob/main/d...
- https://riffle.systems/essays/prelude/
- CS Journals and Magazines?
-
Ask HN: Incremental View Maintenance for SQLite?
The short ask: Anyone know of any projects that bring incremental view maintenance to SQLite?
The why:
Applications are usually read heavy. It is a sad state of affairs that, for these kinds of apps, we don't put more work on the write path to allow reads to benefit.
Would the whole No-SQL movement ever even have been a thing if relational databases had great support for materialized views that updated incrementally? I'd like to think not.
And more context:
I'm working to push the state of "functional relational programming" [1], [2] further forward. Materialized views with incremental updates are key to this. Bringing them to SQLite so they can be leveraged one the frontend would solve this whole quagmire of "state management libraries." I've been solving the data-sync problem in SQLite (https://vlcn.io/) and this piece is one of the next logical steps.
If nobody knows of an existing solution, would love to collaborate with someone on creating it.
[1] - https://github.com/papers-we-love/papers-we-love/blob/main/design/out-of-the-tar-pit.pdf
-
Good papers for high school students?
Here is a great Repo on GitHub named paers-we-love. You will surely find some great papers there and also some good other resources. Hope this helps.
-
I think Zig is hard but worth it
However, f and g are interchangeable anywhere else (this is not actually true because their addresses can be obtained and compared; showing that a C-like language retains its referential transparency despite the existence of so-called l-values was the point of what I think is the first paper to introduce the notion referential transparency to the study of programming languages: https://github.com/papers-we-love/papers-we-love/blob/main/l...)
Previous Serverless Version 0.5.x
-
The Top 10 GitHub Repositories Making Waves ππ
Github | Website
-
Invocation error - can't find any results helping me to solve this issue
i deployed a lambda and http api gateway using a serverless.com (sls) template as a start. I get the following error when it processes a specific request:
- Consulta: buenas practicas AWS
-
Deploying Lambdas from Zipped Code on S3 vs Image Repository
Have you tried serverless.com ? It lets you have infrastructure as code.
-
[p] I built an open source platform to deploy computationally intensive Python functions as serverless jobs, with no timeouts
- With Lambda, you manage creating and building the container yourself, as well as updating the Lambda function code. There are tools out there such as sst or serverless.com which help streamline this.
-
AWS Lambda, a good host for a rest API?
If you'd like to use Lambda, usually you need to engineer FOR it, from day one, you don't (often) get to choose some other framework and shoehorn it into Lambda and Serverless. There's some great frameworks to help deploy code into Lambda easily and create REST endpoints for things, one such frameworks is serverless.com that helps easily deploy to it, but it lacks a framework for doing REST that also supports local emulation (as easily). For that, I recommend a framework by AWS called Chalice. This is an amazing REST framework that runs a proxy that works locally and deploys exactly the same on Lambda, it is Python however.
-
How are you deploying cloud functions (GCF/Lambda/Firebase/whatever) from your monorepos?
I use serverless.com for AWS stuff.
- First time building microservice-based application
-
Key learnings after 10h diving into Lambda, js and Github Actions
After knocking out a README with a set of goals and a list of TODOs to check off as I made progress, I spent about 10 hours over a weekend trying to get something to work. I used serverless for making Lambda easier, Github Actions for the deploy pipeline and store my credentials; and sadly I rolled my own access_token refresh logic because I couldn't find a helper that just did that for me! wtf!?
-
Does anyone use serverless framework with Workers?
Does everyone who uses Workers just use wrangler cli and the cloudflare console UI for everything or is anyone using other tools like serverless framework (https://serverless.com) instead? Looks like they added some support for cloudflare but haven't tried it yet.
What are some alternatives?
Crafting Interpreters - Repository for the book "Crafting Interpreters"
Zappa - Serverless Python
Flowgorithm-macOS - Flowgorithm for Mac OS
apex
elm-architecture-tutorial - How to create modular Elm code that scales nicely with your app
python-lambda - A toolkit for developing and deploying serverless Python code in AWS Lambda.
clojure-style-guide - A community coding style guide for the Clojure programming language
drover - Drover is a command-line utility for deploying Python packages to Lambda functions.
git-internals-pdf - PDF on Git Internals
formidable - The most used, flexible, fast and streaming parser for multipart form data. Supports uploading to serverless environments, AWS S3, Azure, GCP or the filesystem. Used in production.
react-bits - β¨ React patterns, techniques, tips and tricks β¨
atlantis - Terraform Pull Request Automation