- graphical interface for neovim that looks exactly like sublimetext; ssh channel for working with remote neovim in local ui
- full range scanner / automatic database signal matcher for sdr
- browser+server framework for board games that can abstract the display and rules to the point where you can implement things from chess to warhammer
- sane backend for the chef server
- nicer interface / simplification for kvmtool so I could use it like unshare
- python static type analyser
- rc plane autopilot
- python modules security checker like sensiolab security:check for php
- some way of automatically namespacing apps started from home folder - for example any steam games
- everything that hurd needs to be as useable as linux at the moment
- a modern version of bullfrog's syndicate
- localised short-term weather forecast server using community supplied weather data (mini-wunderground-at-home)
I've been wanting to do something like this for tabletop card games.
* Provide an open standard to define the design and optionally, logic related data for cards. I'll come back to this
* Provide an API for people to manage decks, draws, discards etc.
* Provide another API to manage distribution of cards amongst players via achievements or payments (collecting card decks basically)
The idea behind this would be to allow people to build card games that are either played online or offline (by allowing people to download card decks). Grand scheme of things would include a "github for card games" kind of system. Big dreams, shit execution on my part :D
You may find Satellite Reign interesting: http://satellitereign.com/
Would love to understand more as I at times do think of writing a better chef.
For example things like document indexer which is used in 99.99% of cases to search for "some.attribute == 'hardcoded value'". Most of the other cases are prefix searches. This can be done in a normal database. Document storage where what chef really needs is ~5 extracted fields and a json blob that only client deals with. (Again - database is better) Message queue to the indexer which only exists to get broken and be a limiting factor. (extracting even 100 fields from json is not a huge work - just insert them as database rows and prevent the indexing delay) They go after new technologies, where a very conservative stack would be more than enough.
The server API is public, so I started working on a replacement using only python/flask/postgres. I got maybe 80% implemented (ignoring the enterprise namespaces). Then got discouraged because I discovered some API flaws which I thought were just too big - for example the API call to update and create a new node is exactly the same, which can make terrible mess by accident. (seen in real deployment) In the end I just started using salt which I think is a better solution overall.
If you use chef and would like to continue, I'm happy to send you the repo. (email in my profile) If you don't - I can only recommend migrating to something better (salt, ansible, etc. - your choice).
However, I would checkout salt. Thanks a bunch.
//[common tag]-[code checksum]-[comment checksum]-25
This could be updated automatically and be backward compatible with current system. You would just need some sort of hook in git/etc to calculate and update the check sums and issue warning/errors if code checksum changed, but the comment checksum didn’t.
A digital circuit IP or maybe separate USB dongle that does path tracing in hardware, maybe based on procedural generation from a built-in Forth.
Various business and government ideas built on Ethereum, promoted with the intention of displacing existing more centralized institutions with decentralized ones.
A backyard exchange website where people can rent out or share their backyards for tiny house 'parking' and/or high-tech gardening like aeroponics or aquaponics, or whatever they want besides being a big waste of space collecting dog crap.
A unification of computer science, programming, and math. Or, a metalanguage and representation tying together classical programming and mathematical notation with interactive and/or visual programming, with the common part reused in all types of informations systems.
A new operating system for virtual reality.
An isomorphic CMS built in react. This one I'll probably get to and leave as a proof of concept. I'm personally fine with over-engineering things for my amusement, but wouldn't want to subject clients to my woes. But, who knows — could end up working better than expected.
Interestingly enough, you'd have to first build something that can identify style right? So it would at least have to sit on top of a stylistic identifier? Or is there a better way around this?
Side note. I built a prototype of the stylistic identifier as a final year project. Never had time to pursue it afterwards.
Other than that a bunch more features for postgres.
Also, am a Java developer :)