nyir
Location: Berlin, Germany
Remote: OK
Willing to relocate: yes
Technologies: Go, Scala, Java, Python, PostgreSQL, Common Lisp
Résumé/CV: https://macrolet.net/data/main.pdf
Email: olof plus hn at macrolet dot net
LinkedIn: https://www.linkedin.com/in/olof-joachim-frahm-6b27b2275
Lately I'm working on a variety of pieces, predominantly backend, including leveraging the Go compiler toolchain for source code transformation, but also a Scala-based graph traversal DSL. Actually looking to relocate for the right opportunity. Location: Berlin, Germany
Remote: OK
Willing to relocate: yes
Technologies: Go, Scala, Java, Python, PostgreSQL, Common Lisp
Résumé/CV: https://macrolet.net/data/main.pdf
Email: olof plus hn at macrolet dot net
LinkedIn: https://www.linkedin.com/in/olof-joachim-frahm-6b27b2275
Lately I'm working on a variety of pieces, predominantly backend, including leveraging the Go compiler toolchain for source code transformation, but also a Scala-based graph traversal DSL. Actually looking to relocate for the right opportunity. Location: Berlin, Germany
Remote: OK
Willing to relocate: yes
Technologies: Go, Scala, Java, Python, PostgreSQL, Common Lisp
Résumé/CV: https://macrolet.net/data/main.pdf
Email: olof plus hn at macrolet dot net
LinkedIn: https://www.linkedin.com/in/olof-joachim-frahm-6b27b2275
Lately I'm working on a variety of pieces, predominantly backend, including leveraging the Go compiler toolchain for source code transformation, but also a Scala-based graph traversal DSL. Location: Berlin, Germany
Remote: OK
Willing to relocate: yes
Technologies: Go, Scala, Java, Python, PostgreSQL, Common Lisp
Résumé/CV: https://macrolet.net/data/main.pdf
Email: olof plus hn at macrolet dot net
LinkedIn: https://www.linkedin.com/in/olof-joachim-frahm-6b27b2275 Location: Berlin, Germany
Remote: OK
Willing to relocate: yes
Technologies: Go, Scala, Java, Python, PostgreSQL, Common Lisp
Résumé/CV: https://macrolet.net/data/main.pdf
Email: olof plus hn at macrolet dot net
LinkedIn: https://www.linkedin.com/in/olof-joachim-frahm-6b27b2275 Location: Berlin, Germany
Remote: Yes
Willing to relocate: Yes
Technologies: Go, Java, Scala, PostgreSQL, Python, Common Lisp, ...
Résumé/CV: https://macrolet.net/data/main.pdf
Email: hn AT macrolet DOT netBiggest dislike is the on-screen keyboard. On the one hand it's usable with the two trackpads, but, I still take way to long to enter text, even compared to a phone screen. It's also very slow to appear and bugs out too often. I really hope that that can be improved so it can pop up and disappear without noticeable delay.
I'm not sure about underpowered, I was actually quite happy to install some rather resource-intensive (Windows!) games and while it's getting quite warm, I never ran out of battery immediately, but yes, if you've got to save energy, better turn on all the options for that. And that's actually quite cool to be able to turn down energy consumption on a whim, or with per-game profiles, etc.
As long as they're going to optimise the experience more and not just keep it as-is, because "it works fine", then it could be a really good platform going forward.
Same question for the dock though, is it worth it?
The JSON library makes sense, there are several ones and they're all making different decisions wrt. representing the JSON types. I wonder if anyone made a comparison of them with https://news.ycombinator.com/item?id=20724672, that would be useful.
Lastly, I'd always add "be wary of pathnames", even though I was (am) a big fan of the concept in general, it's just sometimes a bit fiddly with regards to physical filenames that can appear on various systems (that's e.g. why SBCL's `native-namestring` can be necessary, http://www.sbcl.org/manual/#Pathnames).
Really cool project though, one of the few that made it outside of uni.
And thankfully LuaLaTex was ready enough at that time, I can't imagine how bad it would've been to do this in pure Tex ...
And you keep the copyright notice, otherwise you're violating the license.
If it's based on the same design (i.e. same file formats, mechanisms, etc.) then the issue is still not giving credit and pointing out the design it's based on. Doesn't cost them a thing and gives a lot of goodwill from people.
Like, if someone uses my code, I'm happy, if they copy the idea and present it as their own that's dishonest.
On that note is there a good conversion (as in, make it into a USB keyboard) write-up for mechanical typewriters? I've seen one commercial kit before, but didn't follow through so far, even though I've got two still lying around.
Just speculation, I kinda agree in that I doubt yet another optimisation package is gonna be so useful.
Oh, but actually, maybe that's the case, I'll pay more attention to the reaction if someone "doesn't like" to.
Is that somehow locale specific? I've never had people ask me to do something like that until I had interactions with US-based folks.
Personally I find it very odd to phrase it like that and it basically achieves the complete opposite of that intent (so I've to actively ignore it and read it as the actual assignment that it was meant as).