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

While they're very good compared to the alternatives, I wonder why they haven't pushed more into that direction, e.g. what I've wanted to put into a plugin when tinkering with the PSI was simple composable operations, similar to Vim operations, like "rotate if/else branch" (while correctly negating and simplifying the test expression), or "convert if to case/switch/..." (and back and only if it's feasible).

What hardware do you have issues with nowadays? I agree it used to be problematic, though lately the only remaining thing I'm struggling with is (some) printers. Then again, thankfully I haven't had to set them up on Windows either.

  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: 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 net

It's great, just not fantastic (yet). I'm kind of eager for further hardware revisions, but on the other hand, I've already used it a lot when I otherwise wouldn't have had the option to start up the big desktop for gaming (commuting, or even just to use some time in between things). And while I bought a Switch before, the main benefit here is of course the entire Steam library being available, so no buying the same title more than once.

Biggest 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?

Ditto, had it only once that they complained the signature on separate documents was identical. Well, just wrote it down a couple more times in case I run into that again.

TikZ/PGF had a graph layouting implementation for about a decade now, c.f. "Part IV - Graph Drawing" in the manual. And apparently `dot2tex` can also render TikZ instructions, so going via Graphviz is possible too.

At least it's using some OSS, like osquery, c.f. <https://cdn.drata.com/agent/osquery/queries.json>, so you can easily see quite a bit of what it's going to gather.

Great points on the list too, even though I still think they're more the acceptable trade-offs kind of bad. I.e., yes, of course `caddddr` will be unreadable, probably, so just don't. `declaim` has a sharp edge for a reason, but you can also make things better by increasing the debug and safety level, that's a great idea I really haven't seen repeated elsewhere.

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).

The top answer on SO that I found (https://unix.stackexchange.com/a/344463/91434) also uses this way of determining whether the device is being used - is that really the best way, or is there anything to actually query the device? E.g. my webcam has a light already that is only active when images are being captured(?), shouldn't it be possible to query that bit of information directly?

Source for the 20%? Anecdotally I've never heard anyone being asked for one, other corrupt behaviour though for sure, things regarding land ownership, or zoning violations.

Got a Classic one on a job and fell in love with it too, so I recently bought a used one and now a replacement battery (just have to actually do the replacement ... will be fun given it's not made for it). The keyboard is just lovely and especially coming from ThinkPads the cursor is super good too. Hope I can keep it alive for a long time!

Just a former student who participated in the first version (let's say draft) of it, which had no really interesting algorithms in it yet, just the overall graph framework and integration with the rest of PGF/TikZ.

Really cool project though, one of the few that made it outside of uni.

Wow, that was a long time ago, very fun project to work on. But yeah, without deep knowledge of the TeX side you'd likely still struggle a bit to understand how the two sides interact, at least it was a bit of a struggle for me, maybe / hopefully it got a bit better in the meantime.

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 ...

You use it.

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.

Select the US layout, not all of the games seem to have all layouts available.

Love this so much. The small display is also definitely something I'd like on a phone simply to display small information bits that then don't need the full powered up display.

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.

If what I've seen is representative, there could be a big opportunity in overhauling the short/medium term forecasting piece in a lot of those companies and adding in a versatile timeseries and analysis platform, which would then allow you to do more accurate forecastings more often (and given the number of readings you're gonna get that might need some thought). And since you're already developing something new you can probably get a nicer architecture out of the whole thing anyway, which might allow you to use all that data in more ways than just for that single purpose. Getting rid of some lock-in from certain database vendors in the long-term might also be nice.

Just speculation, I kinda agree in that I doubt yet another optimisation package is gonna be so useful.

From how I've been reading these interactions the last one isn't actually all that up to discussion. That's exactly what's been annoying me about it. If it were, then yes, exactly like you described it would be a sensible next level after the "please do X". And for most people I'd indeed (correctly) understand it that way, just not, as the parent described, from some particular backgrounds.

Oh, but actually, maybe that's the case, I'll pay more attention to the reaction if someone "doesn't like" to.

It's a common social technique among adults with authority to frame requests as a question

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).

Yeah that's been around for some time http://clhs.lisp.se/Body/m_cond.htm

While as a fan of one particular language I tend to agree, I found http://www.jerf.org/iri/post/2908 a somewhat convincing argument that perhaps my view isn't so well-rounded as I thought.

As in: It's everywhere.

And you have variance in the industries, location, travel requirements presumably, etc. Sure. But with a project of this size and scope I'd be impressed if they'd be able to find (great) devs wanting to work on it below 65-70k and not quit after a year. IMHO and so on based on way smaller projects.

Not GNOME, but the implications for GTK and a whole load of libraries that are being worked on to support these changes. Like especially GTK is just not a stable target. I used GTK 1 and 2, and especially the incompatible changes in 3 and removal of features are just super annoying (many examples, we already had the introduction of header bars etc., there was always a little triangle in the status bar that was just cut, lots of deprecated widgets, ...). And if you look at the plans for 4(!) there's more fundamental changes coming.

And personally I still don't want to touch Qt, but it might just come to that. I don't think I'm up for yet another rewrite with a toolkit that can't be stable for ten years. That might sound grumpy, but also consider GIMP is still working on the port to GTK 3 ...

That's what I was thinking, having used RDF a bit. I liked that the article touched on some more intricate details, things like the timestamp when a fact was added, or disputed facts (well, tags ...). But obviously it gets complicated quite quickly.