Hacker Newsnew | past | comments | ask | show | jobs | submit | deep_origins's commentslogin

Big fan of Tambo and what the team has built. Started using it on a couple side projects and being able to use the zod schemas as source of truth for llm structured outputs is handy.

Awesome to meet another tambonaut.

We love zod, we also support standard schema and thus most other popular typing libraries.

I'm curious how you found us?


Excited to see JACoB in the wild! Very much appreciate the ability to support local models with Ollama.


*negative WAR


Anyone using Mikrotik these days? Been Mikro-curious for awhile and always see them thrown around as a Unifi alternative. Yet to hear of any firsthand implementations though.

[0] https://mikrotik.com/


As a network engineer, I've considered them for my house, the price is right, but:

1) Their main push seems to use a thick client for admin which is a big no to me, otherwise the web ui in theory looks ok-ish. 2) Looking at their cli guide, it was cryptic as hell to me, and I deal with everything from cisco, arista, aruba, juniper, fortinet, pan, whatever from a cli or gui.

This was mostly confirmed a few weeks back, another old network engineer friend of mine hit me up asking if I've ever dealt with Mikrotik, and said no, but I knew where he was going. He'd screwed with it for a day or so supposedly just trying to make some L3 vlans, and finally a day or so later told me he'd made it work, but has never dealt with anything so terrible to configure from either gui or cli after having tried both, and he's another 20yr+ network engineer like me I trust not to be stupid.

That was all I needed to hear for future consideration.


Mikrotik has had WinBox for as long as they've been around and there's a lot of inertia around using it, but WebFig and the CLI are the only things I use (though I do have The Dude running through Crossover because it's useful).

Where you run into problems with 'tik gear is the differences that L3HW acceleration introduced into the mix. They didn't do what every other switch vendor does and limit features to what the switch chip supports and hide everything that the CPU can't handle away, so you have multiple ways of approaching most issues which threw me for a look as somebody who had been running JunOS gear in his lab for a while.

Once you get a feel for it then it's pretty straightforward to work with everything, though somebody used to an older generation of NOS like classic IOS (and associated clones) would have an easier time than me.

For reference, here's the config for my CRS317 acting as my "core" switch: https://gist.github.com/snuxoll/d63a155aa2155f53736a99d1cb27...


For sure, VLAN config is one of the most extremely "How and why did anyone end up designing it this way?" thought-inducing areas of Mikrotik config.

But I will say that the boxes of theirs that I bought about ten years ago are still going strong, never had a device fail on me, still receiving OS updates, still able to export and re-import my config to any of a wide variety of newer devices when the time comes.

Clearly they're not the right choice for everybody, but there are certainly up sides, if you're willing to grapple with the config.


Their "thick client" (aka Winbox) is effectively replicated in the web UI at this point.

Yeah, the CLI is a bit weird, but it's built on the same API calls that the web UI makes. So they're oddly consistent.


What does “L3 VLAN” even mean?


I have half a dozen Mikrotik hAP AC and wAP AC devices with Openwrt used in various places for work and for home.

Rock-solid hardware and muuuch better UX that RouterOS.

Don't remember when I setup those, but probably well before Covid. Really fire-and-forget devices.


Check out Unison [0]. I use it to sync between macOS and Linux box.

[0] https://www.cis.upenn.edu/~bcpierce/unison/


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: