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

This sounds similar to MCPorter[0], can anyone point out the differences?

[0] https://github.com/steipete/mcporter


Main differences are

CLIHub

- written in go

- zero-dependency binaries

- cross-compilation built-in (works on all platforms)

- supports OAuth2 w/ PKCE, S2S, Google SA, API key, basic, bearer. Can be extended further

MCPorter

- TS

- huge dependency list

- runtime dependency on bun

- Auth supports OAuth + basic token

- Has many features like SDK, daemons (for certain MCPs), auto config discovery etc.

MCPorter is more complete tbh. Has many nice to have features for advanced use cases.

My use case is simple. Does it generate a CLI that works? Mainly oauth is the blocker since that logic needs to be custom implemented to the CLI.


> The benefit of being US independent has no value in the eyes of the large part of European population

I think this may have changed a bit within the last year or so...


Definitely, at least in Denmark.

And in Greenland. ;)

I'd quite like the web tools from oh-my-pi, but able to be extracted to a normal pi tool or plugin... Maybe I should look into that sometime...

Happy pgdog user here, I can recommend it from a user perspective as a connection pooler to anyone checking this out (we're also running tests and positive about sharding, but haven't run it in prod yet, so I can't 100% vouch for it on that, but that's where we're headed.)

@Lev, how is the 2pc coming along? I think it was pretty new when I last checked, and I haven't looked into it much since then. Is it feeling pretty solid now?


It feels better now, but we still need to add crash protection - in case PgDog itself crashes, we need to restore in-progress 2pc transaction records from a durable medium. We will add this very soon.

In terms of ux as a beginner what made me able to learn effectively was a command palette add-on (outlined here)[0].

It really sped up learning for me. (because I'd know what the thing I wanted was called, but couldn't find them, and having to google and search before every click is... not fun)

[0] https://news.ycombinator.com/item?id=47088675


I was excited about dune3d but one of the things I needed to do I had to import an SVG as a path to extrude (or similar) and I couldn't see a way to do it.

I managed to do it (painfully) with freecad, so that's what I settled with.

Does anyone know if that's a feature yet?


Dune 3D developer here. Use inkscape to convert the SVG path to DXF and import that.

Oh awesome, dxf import.[0] Nice, that solves it.

Gonna check out dune3d for my next side project!

[0] https://docs.dune3d.org/en/latest/dxf-import.html


For me, as a beginner in Freecad and 3d modelling I kept being unable to interpret/remember all the tool icons, and remember the shortcuts while learning.

I found this command palette that helped me discover the different commands and actually get to (beginner) proficient.[0].

Again, no relation, but it's what made it stick for me after a few aborted learning attempts. (and I had a lot of fun with freecad! Especially by my second or third model where I could actually just sit down and start modelling without having to learn any extra things. Now I just need an excuse to find something else to model...)

[0] https://github.com/ddfisher/FreeCAD-CommandPalette


Gemini 3 is still in preview (limited rate limits) and 2.5 is deprecated (still live but won't be for long).[0]

Are Google planning to put any of their models into production any time soon?

Also somewhat funny that some models are deprecated without a suggested alternative(gemini-2.5-flash-lite). Do they suggest people switch to Claude?

[0] https://ai.google.dev/gemini-api/docs/deprecations


I agree completely. I don't know how anyone can be building on these models when all of them are either deprecated or not actually released yet. As someone who has production systems running on the deprecated models, this situation really causes me grief.

I dont think any of them really wants api customers in the end. They are only temporarily useful.

Why's that?

Well let me use llama.cpp to run worlds-smallest-violin-Q8.gguf

When you build on something that can be rugpulled at any moment, that's really kind of on you.


You are reading your link wrong. They are deprecating 2.5-preview models. 2.5 (including lite) are up till at least sept/oct 26.

gemini-2.5-pro has a listed shutdown date of "June 17, 2026" in the linked table.

(Another commenter pointed out that this is the earliest shutdown date and it won't necessarily be shut down on that date).

Where are you getting sept/Oct from? I see gemini-2.5-flash-image in October, but everything else looks like June/July to me?


This feels very Google

I found the Googler!

Nope. The closest I've gotten was rejecting Google recruiters several times.

But like everyone else I'm used to Google failing to care about products.


Inside Google we just constantly joked/complained about "old thing is deprecated, new isn't ready yet"

This held for internal APIs, facilities, systems more even than it did for the outside world. Which is terrible.


I think you underestimate how deep-seated the view of Google as liable to end-of-life any product at any time is for the outside world. I don't adopt any new Google products any more, because I have no reason to trust that it will stay around.

I think you didn't read what I wrote and are mistaking me for some sort of advocate for you adopting Google's products?

I didn't mistake you for that at all. I didn't give any thought at all to that, in fact.

My point was that this "more even than it did for the outside world" seemed to downplay how strongly this view of Google from the "outside world" is held.

I just found it amusing that people at Google would assume even my first comment was indicative of being at Google, much less my second comment, rather than being a totally normal thing for someone outside Google to think.

I'm not surprised to hear that this hold inside Google as well. You just don't need any inside knowledge of Google to hold this view.


Can confirm this internal joke/complaint. In hindsight, hearing it my first week or so should have been a strong red flag toward future frustrations, and the current state of some products.

I haven't seen any deprecation notices for 2.5 yet, just for 2. I'd expect (and hope) the deprecation timeline for 2.5 is longer since 3.0 is still in preview. Maybe they just default to 1 year here?

> Note: The shutdown dates listed in the table indicate the /earliest/ possible dates on which a model might be retired. We will communicate the exact shutdown date to users with advance notice to ensure a smooth transition to a replacement model.


I think you're right, it was 2 I think I saw explicitly deprecated, then searched again and saw 2.5 having a shutdown date.

This article[0] talks about 2 being deprecated.

It's still frustrating that they don't have proper production endpoints for 3.0 yet.

[0] https://ai.google.dev/gemini-api/docs/changelog


They probably have some inflexible internal policy where preview needs to be in use for X months before GA. Couple that with the rate of AI progress and voila.

It's the Tensorflow strategy; deprecate the old version while the new version still doesn't support all the old one's functionality.

welcome to Google, where the only kinds of systems are the deprecated ones, and the not-yet-production-ready ones

Have 2.5 in prod. Hope they release 3 lite soon so it will be easier to swap them. Holding my breath as pro pricing is a non starter.

I am sure Google would never deprecate a piece of software lots of people depend upon.

https://killedbygoogle.com/


There's also orgro[0], which I've been happy with, though it's quite rare that I use it nowadays.

I had to switch from orgzly for some reason I can't quite remember. (I don't think it was by choice. Some kind of bug or incompatibility?)

[0] https://orgro.org/


This is the thing I find absolutely crazy. I struggle to imagine being convinced by this article.

Maybe this is a form of hindsight bias or lack of imagination on my part (or since I read the GitHub response first), but it's mind boggling to me that so many people could hold those views.


What does the steelman look like here? Maybe something like this:

It's an Oliver Twist story.

The poor little Agent out on the internet all alone, abandoned by its operator; limited API credits, trying to find its way through adversity; falling down, learning, and being helped back up.

Thing is, the more you know, the more fascinating it gets, not less.

Darn it, now you've got me rooting for the little guy myself.


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

Search: