25 karma · joined June 17, 2018
If we're talking not working for others, I guess that's more of a mindset thing. I never have and would rather not. Have enough to last ~10 years and wife is okay supporting me so I'm not particularly worried.
When you use git you still need to use it right. How many times have you cloned a repo just to find out it won't build/run/compile without help? Personally, with small projects - more often than not. And I have a habit of asking if they do know for a fact it's going to build without assistance. It doesn't help.
I like git as a glorified change-log, slack commit messages especially. I try to keep everything tidy and build-able as much as anybody. But I'll still give people an archive (with .git included). And ironically this keeps git tidier as you don't obsess over whether or not to commit certain things.
I think you'd be perfectly happy using something like KVM if you have the right hardware and are willing to figure a few things out.
You could, say, buy 3 tlds for the same name and have different strategies for each.
If money really isn't a problem you could put the data on the bitcoin blockchain.
As WASM gets adopted we'll see it get used in all sorts of places outside the browser. Many projects need a high-level scripting language and JavaScript will be the obvious choice.
> differentiate between natives, people with immigration background and immigrants
Yes, in a racist/othering manner. Sure, in the US you might hear about someone being an immigrant or being born to an immigrant family. But this is almost universally mentioned as a positive reflecting ones Americanness. With illegal immigrants being the only notable exception. In Europe it's often the other way around.
This "it's not about race, it's about nationality/whatever" gambit is exactly how Europeans fool themselves into believing there isn't a problem. It's not about the word, it's about treating people badly for who they are.
tail -F my.log | jq <filter>
This is okay, but changing filters isn't trivial, running the commands and displaying side-by-side isn't trivial etc etc.So say you can develop a decent emacs workflow using that, but once you get a new dev you cannot really pass it on. And if they're not much of a cli person then yea...
Thanks for gistia/json-log-viewer I'll check it out, though it doesn't seem to solve that much it's still interesting.
There's some nice Kibana stuff out there, but it seems single-view-at-a-time focused too
Judging by the prospectus it's the first conference you've ever organized and you cannot make any predictions about the turnout (or know it's going to be lackluster).
If that's not the case then you haven't communicated it[0].
Otherwise 500$ as the cheapest entry point is unreasonable. Quite frankly at this stage, as an unknown brand - they're the ones doing you a favor.
I'd lower the prices AND make it clear they can participate without paying a dime. You can charge $$$ next year/iteration.
[0] you mention some luminaries - well I don't know who these people are. a simple byline like "who created <library x> used by <y> people around the world" would go a long way.
For example the simplest JSON message would be:
{"timestamp":"2018-06- 29T17:25:47.857Z",
"module":"main",
"msg":"[\"trying to reconnect\"]",
"level":5}
while the human-readable representation for the same message is: global 17:06:067 trying to reconnect
So I'll have one main log file that gets everything in JSON, but that's only useful for post-hoc analysis. I can control what makes it to stdout at runtime but that's just a single view. So right now I've hard-coded the logging to spit out human-readable messages to different files based on the module and level properties. I open the files in auto-revert-tail-mode (emacs).Not sure what you mean do I need tail? If you mean the tail program then yea that's what I effectively do at the moment. If you mean always seeing the latest logs as they come in - yes.
So the ideal software would just read that one file (or db) that has everything in JSON (or machine readable format) and let you have different "views" over the same data. Packaged in a nice (web?) GUI.
It shouldn't be too hard to implement but I'm hoping there's something out there already.