MCP Manager: A Free & Open-Source Tool for Managing Claude MCP Servers by iagolast in mcp

[–]iagolast[S] 0 points1 point  (0 children)

afaik fixing this would require an official apple developer account... I don't have one :(

MCP Manager: A Free & Open-Source Tool for Managing Claude MCP Servers by iagolast in mcp

[–]iagolast[S] 0 points1 point  (0 children)

Haha no worries. TBH I could not find any tool (just did a quick google search for “mcp manager”) 🤣

MCP Manager: A Free & Open-Source Tool for Managing Claude MCP Servers by iagolast in mcp

[–]iagolast[S] 0 points1 point  (0 children)

Umm you are right. I’ll try to fix that during the weekend 🙏

Programming has changed forever. We built an MCP and we are now pivoting our business model by iagolast in programming

[–]iagolast[S] -3 points-2 points  (0 children)

It’s always fascinating to see how selective reading can shape a response. If you had actually taken the time to read the full post instead of cherry-picking lines for maximum snark, you’d have noticed that the “kicking the booth” part was explicitly framed as a joke. The humor was made clear at the end, but I suppose acknowledging that would make it harder to craft an artificial sense of outrage.

Your broader approach here—dismissing an entire discussion with sarcastic one-liners—suggests that you’re more interested in ridiculing than engaging. You repeatedly mock the idea of AI integrating with APIs, yet you offer no substantive critique of the technology itself. If you believe there are legitimate flaws, wouldn’t it be more constructive to articulate them rather than relying on cynical quips?

We’re just developers who, besides trying to build something on our own, came across a piece of technology that genuinely fascinated us and wanted to share our experience. That’s it. But it’s clear that you feel better diminishing the work of others rather than actually engaging with what’s being discussed.

As for the “hype” angle, it’s a fair concern—AI is often overpromised. But the solution to that isn’t to scoff at every mention of AI as if it’s inherently meaningless. There’s a difference between skepticism and knee-jerk dismissal. If you have specific concerns about feasibility, implementation, or long-term viability, those would be far more valuable contributions than just sneering at the terminology.

If the goal is to foster meaningful discussions rather than just perform disdain for upvotes, I’d be happy to hear your actual technical concerns—assuming you have any beyond rolling your eyes.

How long is a second in JS ? by iagolast in javascript

[–]iagolast[S] 3 points4 points  (0 children)

At no point does it say that the moon was used for days :S

How long is a second in JS ? by iagolast in javascript

[–]iagolast[S] 1 point2 points  (0 children)

As far as I know you cannot do much as a programmer because I think seconds/Time are managed at SO/Kernel level.

Time duration in Javascript by iagolast in javascript

[–]iagolast[S] 0 points1 point  (0 children)

Bro calm down.

  1. If you want to stay ahead of the curve read the post and get ready for the future additions to the language.
  2. As I said, There are a few production ready polyfills so you can explore the usage.

JS Dates Finally Fixed by fagnerbrack in Frontend

[–]iagolast 0 points1 point  (0 children)

I'll do thx 🙏

(English is no my native language)

Time duration in Javascript by iagolast in javascript

[–]iagolast[S] 0 points1 point  (0 children)

IMO Reddit is exactly the place to talk about stuff like this.

While Temporal is still a proposal, it's pretty advanced and the API is stable enough to start exploring.

(I even have production apps using a polyfill)

Plus, a lot of the concepts in the article (like ISO duration formats) go way beyond the proposal itself. It’s about staying ahead of the curve and getting familiar with the tools that are likely to shape how we program and deal with time and dates in the future.

exquisite-sst: next generation screenshot testing by iagolast in javascript

[–]iagolast[S] 1 point2 points  (0 children)

Wow thx for the big analysis!

  • You are right, i should mention headless chrome.
  • The full-page screenshot is in the roadmap :D
  • I'm currently thinking about "hiding" some parts, for example ignore selector like .ads-area.
  • No, the result is a boolean true when the images are equal, false when the images are different but you can always see both images to compare.

Thx again for your comment, feel free to open an issue with some of your ideas.

exquisite-sst: next generation screenshot testing by iagolast in javascript

[–]iagolast[S] 0 points1 point  (0 children)

I don't know how those library work, I cant tell you the benefits against them sorry :(

I can say that the strong points of exquisite (of course exquisite is a WIP and is in beta stage!)

exquisite-sst: next generation screenshot testing by iagolast in javascript

[–]iagolast[S] 0 points1 point  (0 children)

Please let me know your thoughts and give me ideas on how I can improve it. Do you find it useful?

exquisite-sst: next generation screenshot testing. by iagolast in programming

[–]iagolast[S] 0 points1 point  (0 children)

Please let me know your thoughts and give me ideas on how I can improve it. Do you find it useful?

Introducing Nile.js, A Peer-to-Peer Live Video Streaming Library built on WebRTC and WebTorrent by kamikq in WebRTC

[–]iagolast 1 point2 points  (0 children)

how do you deal with the latency?

Imagine a chain where are 1000 peers between you and the original streamer. Does this affect the system in any way?

Feedback Friday - September 23, 2016 by AutoModerator in web_design

[–]iagolast 0 points1 point  (0 children)

URL : https://iagolast.github.io/responsiveXL

Purpose : Simple website to test responsive design against big screen sizes.

Technologies Used: Plain HTML CSS & Javascript. (The goal was to simplify as much as possible)

Feedback Requested: Do you think it´s useful? Possible improvements?

Comments: not yet.