587 karma · joined April 13, 2012
https://zserge.com
- https://github.com/zserge/anvil - a new reactive UI library for android. It totally changed the way I develop android apps now.
Also there is some tiny ones, but found useful over the years:
- https://bitbucket.org/zserge/jsmn/wiki/Home - JSMN, a very fast and lightweight JSON parser for embedded systems
- https://bitbucket.org/zserge/mucks - A wrapper for Tmux/Screen/DVTM to keep persistent terminal sessions. Usefule when you use terminal as an IDE
- https://bitbucket.org/zserge/gambiarra - minimalist Lua unit-testing library
In theory I can survive with any OS/platform, since my primary tools are tmux+vim+zsh. I use them for android development (Java, Kotlin), for web (JavaScript, Golang), for embedded systems (C, Lua).
So the only two apps that I keep always open is a full-screen terminal and a browser. Probably even Chrome OS would be comfortable for me :)
<dependency>
<groupId>co.trikita</groupId>
<artifactId>anvil</artifactId>
<version>0.0.2</version>
</dependency>
Gradle: compile 'co.trikita:anvil:0.0.2' All the huskies are eaten. There is no space
left in the diary And the beads of quick
words scatter over his spouse's sepia-shaded face
adding the date in question like a mole to her lovely cheek.
Next the snapshot of his sister. He doesn't spare his kin:
what's been reached is the highest possible latitude!
And like the silk stocking of a burlesque half-nude
queen it climbs up his thigh: gangrene.In fact, it fails to compile with -std=c99, it seems to require GNU extenstions, that's why they have -std=gnu99 in their Makefile. They use ##__VA_ARGS__, which is not in the C99 and AFAIK there is no portable way to make a workaround.
The whole idea of rockspec looks very nice to me and I totally support it.
But can I keep a global aka system rocktree and a per-project local trees? (Pardon my ignorance, I really don't know that). Per-project trees make deployment a lot easier.
Also, why can't "luarocks" or "moonrocks" be a single executable/script? Isn't it easier to get user just a download link instead of: "download it here, unpack, configure, make build, make install, now use it to install moonrocks"? (Also, I'm not saying that it's a very complex procedure, I know most people can do it easily, but that leaves an impression that the LuaRocks project is not very user-friendly).
If a community here wants to make things better - let's meet somehow and discuss it.
Then if, say, each of 5 Lua developers converts 1 package per day in their free time then in about three months the whole list of packages will be converted.
Anybody?
They seem to fixed the linker, leaving the networking issues open so far. And I'm not really sure about the *.so generation for Dalvik/ART, Java bindings generator tool and other planned tasks. I saw some mentions in the go.mobile repo a while ago, but this issue still doesn't have a release assigned: https://code.google.com/p/go/issues/detail?id=6342
It's an extension of a build system, not a language. It helps to specify build process details right in the source files that either depend on it, or provide necessary details for it. This approach worked for CGo, it worked for +build flags, so I don't see why it will not fit in this particular case.
One thing I worry is how to get the processor app during the build process. E.g. if bindata is used to embed a file - how will "github.com/jteeuwen/go-bindata" be installed?
Here's my two cents: https://bitbucket.org/zserge/mucks
Much-much simpler, and definitely less intuitive, but supports screen and dvtm as well: http://zserge.com/blog/mucks2.html