rupy
adama-lang
rupy | adama-lang | |
---|---|---|
31 | 26 | |
136 | 104 | |
- | - | |
1.1 | 9.9 | |
about 1 year ago | 8 days ago | |
Java | Java | |
- | GNU Affero General Public License v3.0 |
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.
rupy
-
Considerations for a long-running Raspberry Pi
I have been running a Raspberry 2 cluster for 10 years: http://host.rupy.se
A few weeks back the first SD card to fail got so corrupted it failed to reboot!
My key learning is use oversized cards, because then the bitcycle will wear slower!
I'm going from 32GB to 256/512/1024!
-
What Kind of Asynchronous Is Right for You?
How this article does not mention SSE, comet or chunking escapes me.
What does their definition of event-driven really look like in practice.
Nobody has a clue.
Here is the ideal event driven system, it's async-to-async: https://github.com/tinspin/rupy/wiki/Fuse
The example is not working because I had to shut down the services for multiple reasons, but the high level of it is that you use 4 (potentially different) threads to do one request/response middle man transaction.
That way you have _zero_ io-wait or idling. I'm surprised nobody has copied this approach since I invented it 10 years ago. I understand why though you need your entire chain to be async and that means rewriting everything and that is a big risk when it's hard to debug.
But if you succeed you can build something that is 10x perf/watt than all other implementations. Which is going to be important when interest rates go higher and crash our entire industry.
-
An unknown Swedish startup’s €3B bid to build a green rival to AWS
The hardware is peaking.
So software is where you can make the difference: http://host.rupy.se
- Sandstorm: Open-source platform for self-hosting web app
-
You Want Modules, Not Microservices
I think we're all confused over the definition. Also one might understand what all the proponents are talking about better if they think about this more as a process and not some technological solution:
https://github.com/tinspin/rupy/wiki/Process
All input I have is you want your code to run on many machines, in fact you want it to run the same on all machines you need to deliver and preferably more. Vertically and horizontally at the same time, so your services only call localhost but in many separate places.
This in turn mandates a distributed database. And later you discover it has to be capable of async-to-async = no blocking ever anywhere in the whole solution.
The way I do this is I hot-deploy my applications async. to all servers in the cluster, this is what a cluster node looks like in practice (the name next to Host: is the node): http://host.rupy.se if you click "api & metrics" you'll see the services.
With this not only do you get scalability, but also redundancy and development is maintained at live coding levels.
-
I wish my web server were in the corner of my room
I have hosted my own web server both physically and codevise since 2014.
It's on a Raspberry 2 cluster:
http://host.rupy.se
Since 2016 i have my own database also coded from scratch:
http://root.rupy.se
We need to implement HTTP/1.1 with less bloat, a C non-blocking web server that can share memory between threads is probably the most interesting project for humans right now, is anyone working on that?
-
Ask HN: Free and open source distributed database written in C++ or C
I have one in Java: https://github.com/tinspin/rupy
Here is the 2000 lines of code of the entire database: http://root.rupy.se/code?path=/Root.java
And here you can try it out: http://root.rupy.se
-
Dokku – Free Heroku Alternative
The smallest PaaS you have ever seen is one order of magnitude larger than mine: https://github.com/tinspin/rupy
And I bet you the same goes for performance, if not two!
-
Server-Sent Events: the alternative to WebSockets you should be using
The data is here: http://fuse.rupy.se/about.html
Under Performance. Per watt the fuse/rupy platform completely crushes all competition because of 2 reasons:
- Event driven protocol design, averages at about 4 messages/player/second (means you cannot do spraying or headshots f.ex. which is another feature in my game design opinion).
- Java's memory model with atomic concurrency which needs a VM and GC (C++ copied that memory model in C++11, but it failed completely because they lack both VM and GC, but that model is still to this day the one C++ uses), you can read more about this here: https://github.com/tinspin/rupy/wiki
You can argue those points are bad arguments, but if you look at performance per watt with some consideration for developer friendlyness, I'm pretty sure in 100 years we will still be coding minimalist JavaSE on the server and vanilla C (compiled with C++ compiler) on the client.
- Jodd – The Unbearable Lightness of Java
adama-lang
-
Outstanding Programmers
I'm just a tryhard. However, I've been coding since a child out of a weird love/obsession. Nothing super successful in the public space, but I retired at 40 to spend time building my cathedral: https://www.adama-platform.com/
my history: https://www.adama-platform.com/2024/01/28/euler.html
-
UI = F(statesⁿ)
I'm in the camp of f = ui(state), and the reason for this is the extreme of streaming games where UI = frame buffer. I'm inventing my own framework for radically simplifying traditional Web apps via RxHTML which works great for crud apps. However, games requires more insight into state machines and what-not.
In terms of the logic, I wrote an entire platform to simplify multi-player board games which I'm evolving to tackle various businesses. https://www.adama-platform.com/
-
Single-Dose Psilocybin for Major Depressive Disorder a Randomized Clinical Trial
For context, I was not raised religious at all and kind of thought a bunch of it was hokum.
But then I did a heroic dose, and I went to the church of engineering where I saw the entire construction of the machines use from the transistor all the way up to the platform I'm building.
My faith is more a faith that humanity is worth it, and I've come to see "The Lord" as an appropriate metaphor for the collective conciseness of several billion people living their lives.
At core, I'm rejecting nihilism as a valid way to live, and I'm writing an essay to outline the way.
In this, I also reject cynicism, and this is because it offers nothing.
The way forward is to embrace the responsibility that comes with great knowledge and to build an organization that helps push technology forward. This is why my platform is open source ( https://www.adama-platform.com/ ), and I'm working very hard to get my handful of clients in a good place.
- Building a Reddit Clone with AI
-
Don't Write a Programming Language
I'll take the bait and provide evidence on why you should write a programming language.
First, it's technically very difficult, but you will gain deeper insight into the art of the craft. So, if you are a TC chaser or career minded person, then spending half a year writing a language will help you master the coding aspect of the game. I've started many languages since I started college, and each one was instructional. (I'm now 40 and an early retiree)
Second, it's fun.
Third, it may turn into something new. If some people don't write a new programming language, then we are stuck with what we have. This advice basically admits that the status quo is good enough.
The authors saying that the language, as a project, is a lifetime appointment? Well, this reveals everything. I believe if you want to do a programming language, then you must be willing to invest at least a decade or two.
So, here, I am at forty preparing to launch a SaaS around a language that I designed ( http://www.adama-lang.org/ ). The kicker, I believe, is that a project like this requires wandering the desert alone for quite a while.
I'm preparing to launch, and I just started to load test my shiny new production cluster. Low and behold, it sucks. Fortunately, I have a tremendous number of dashboards and isolated it to how I'm interacting with RDS. I've got my work cut out for me which I'll write about.
However, I have a potentially interesting business precisely because I evolved a language which solved a niche use-case. The number of problems that I have had to solve up to this point is not for the faint of heart. Life and reality are harsh mistress.
So, maybe, yes, you can save yourself some heartache by not writing a language. Perhaps, a better way to think or phase this is "Writing a programming language is a lonely affair that will most likely end in tragedy after a long death march".
-
The Harsh Truth of Video Games Programming
I want to make games, but even some years ago I realized it was not a great path for a multitude of reason (many of which are in this article).
My path, and what I recommend, is do something hard and important which pays the bills at a premium. I did infrastructure work, and I was lucky to have a great decade long career allowing me to "retire early".
Now, I can work on a game at my pace building the tools that I see fit. I'm focused on board games because they have a timeless quality about them. I'm developing an entire SaaS platform and programming language to make the network goo beyond easy. http://www.adama-lang.org/
As I'm getting close to some kind of launch for the SaaS, my next thing is to build up my own web based IDE with a release-often ideology such that I can build a Roblox for online 2D board games. Honestly, I'm having a blast because I'm not suffering tools which are going to fade.
-
Why my projects keep failing
I like to call such a list a "wall of shame", and I have my own over here: http://jeffrey.io/wall-of-shame.html
What has helped me over the years is that I view tech as art, and so these projects are only market failures. Your growth as a technologist is manifest, and it's important to see side projects as a form of practice.
If you can move past the failure label and see everything as successful at something, then you feel a whole lot better. A discipline that I have had for decades now is to write a postmortem on why I believe a project is a failure because that crystalizes my learning.
My history helped me excel as a principal engineer which put me towards an early retirement where I can now focus on my ultimate side project: Adama ( http://www.adama-lang.org/ ) which I am turning into a new kind of PaaS thing.
Here is the crazy thing: I already know that I'm making several mistakes as I have no customers and no one asking me for anything. This is an exceptionally lonely way to start a project as the OP and others have noted, but I'm enjoying it well enough.
-
Ask HN: Who Wants to Collaborate?
I'm working on http://www.adama-lang.org/ which started as a programming language for board games, and it is turning into a reactive privacy-focused data store for Jamstack.
I hope to launch in coming month an "Early Access" edition.
While I do intend to turn this into a business, I'm primarily focusing on small projects to amuse myself. I'm going to break every rule in the business with my LLC. The #1 company value is sleep.
-
Store SQLite in Cloudflare Durable Objects
I actually think this is onto something that I'm finding in a different way. Instead of a massive database, what if we had a key-value store mapping keys to tiny databases.
This is, to some degree, what I'm building over at http://www.adama-lang.org/ without a full SQL engine. Each document has tables, and the tables can be indexed. I have yet to find a usecase (in my domain) which requires joins. HOWEVER, I've had a ton of fun building it and I'm getting ready to start making games.
I do believe it would be amazing to have a key-logger service where a reducer like sqlite/adama could come into collapse the log into a single file.
The closest I see is from the Boki paper ( https://www.cs.utexas.edu/~zjia/boki-sosp21.pdf ) which was presented at SOSP21.
-
The WebSocket Handbook
CRDT solve a part of your problem, and an important consideration is whether or not you want off-line editing. If you don't need off-line editing, then a WebSocket can do it.
I'm actually using my project to build a collaborative IDE (designer like Figma): http://www.adama-lang.org/
I'm going to be launching it as a SaaS soon so people can spin up a new back-end without managing an infrastructure.
What are some alternatives?
huproxy
SyncedStore - SyncedStore CRDT is an easy-to-use library for building live, collaborative applications that sync automatically.
cmdg - Command line Gmail client
builder - Multiplayer game framework
Nullboard - Nullboard is a minimalist kanban board, focused on compactness and readability.
coughdrop - Open source web-based AAC app
cakephp-swagger-bake - Automatically generate OpenAPI, Swagger, and Redoc documentation from your existing CakePHP code.
github-to-sqlite - Save data from GitHub to a SQLite database
dbmate - :rocket: A lightweight, framework-agnostic database migration tool.
quickjs-emscripten - Safely execute untrusted Javascript in your Javascript, and execute synchronous code that uses async functions
Aerospike - Aerospike Database Server – flash-optimized, in-memory, nosql database
Crate - CrateDB is a distributed and scalable SQL database for storing and analyzing massive amounts of data in near real-time, even with complex queries. It is PostgreSQL-compatible, and based on Lucene.