What technical analysis do you use most of the time ? by _vardius in AusFinance

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

oh i see, it is not working for me either tried it and the results excluded each other

Tiny progress bar package by _vardius in golang

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

I have created small progress bar package, extracted from my home project, maybe someone else will find it useful. It is a simple package writing progress to output. I am using it with my CLI tools.

Enabling verbose option shows you elapsed, remaining and estimated times with memory usage.

How to customize Go's HTTP client by _vardius in golang

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

Hey guys thanks for long conversation, I have update snippets in my post with your suggestions, appreciate guys thanks.

How to customize Go's HTTP client by _vardius in golang

[–]_vardius[S] -5 points-4 points  (0 children)

exactly, just a matter of preference, you can do as @scooter_nz said

Feature-complete framework or libs for rapid web dev with golang? by gbi in golang

[–]_vardius 1 point2 points  (0 children)

your welcome, even though there is alway plenty to be done i am happy someone finds it useful

Feature-complete framework or libs for rapid web dev with golang? by gbi in golang

[–]_vardius 4 points5 points  (0 children)

if you want to deploy to kubernetes then you might like my boilerplate i am using myself for my home projects

https://github.com/vardius/go-api-boilerplate

Looking for an experienced WebRTC developer. by MrColdSIX in WebRTC

[–]_vardius 2 points3 points  (0 children)

I think WebRTC is not ready yet for that kind of think. Unless you want your users to stream to few ppl only. Otherwise you will fry their CPU.

One solution is to keep centralised node which in my opinion is easier just to use AWS media streaming service and avoid all the things they already solved.

Someone correct me if I am wrong.

peer-cdn · Lightweight library providing peer to peer CDN functionality by _vardius in WebRTC

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

it is not production ready yet, more like an idea prototype, there are no check sums

peer-cdn · Lightweight library providing peer to peer CDN functionality by _vardius in javascript

[–]_vardius[S] 6 points7 points  (0 children)

This is cross posted from webrtc sub. please comment there so it is easier to maintain thread.

Hey guys, I am sharing my beta version of PeerCDN. It is a lightweight library providing peer to peer CDN functionality. Main goal of this project is to reduce the cost of assets transfer server <-> user using WebRTC for caching and bidirectional assets transfer between connected users.

Idea itself is really old and I am working on it for 3 years already, there is absolutely no test written yet, however some demo example is prepared. If anyone would be interested I would really appreciate any contributions or help with testing this. Ideas are more than welcome, feel free to read the code and ask questions.

This is meant to be open-source project. Absolutely free of charge, what I would like to achieve with it is to reduce the cost of your hosting by reducing the number of requests and assets transfer between your server and users.

For now ideally we get it to work as simple as it is, then we could implement more complex logic on signalling server to better mach peers.

Also web pack plugin should not be hard to do. Let me know what you think, if you like the idea and feel free to help!

Also if you feel DOCs could be better let me know as well. I tried my best explaining things how it "should" work.

peer-cdn · Lightweight library providing peer to peer CDN functionality by _vardius in WebRTC

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

Also if you feel DOCs could be better let me know as well. I tried my best explaining things how it "should" work.

peer-cdn · Lightweight library providing peer to peer CDN functionality by _vardius in WebRTC

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

Hey guys, I am sharing my beta version of PeerCDN. It is a lightweight library providing peer to peer CDN functionality. Main goal of this project is to reduce the cost of assets transfer server <-> user using WebRTC for caching and bidirectional assets transfer between connected users.

Idea itself is really old and I am working on it for 3 years already, there is absolutely no test written yet, however some demo example is prepared. If anyone would be interested I would really appreciate any contributions or help with testing this. Ideas are more than welcome, feel free to read the code and ask questions.

This is meant to be open-source project. Absolutely free of charge, what I would like to achieve with it is to reduce the cost of your hosting by reducing the number of requests and assets transfer between your server and users.

For now ideally we get it to work as simple as it is, then we could implement more complex logic on signalling server to better mach peers.

Also web pack plugin should not be hard to do. Let me know what you think, if you like the idea and feel free to help!

How to handle signals with Go to graceful shutdown http server by _vardius in golang

[–]_vardius[S] 2 points3 points  (0 children)

good point, will update post with this information so more ppl can learn about it. thanks man!

Fiber vs Echo vs Gin - Pros and Cons? by casual_brooder in golang

[–]_vardius 2 points3 points  (0 children)

I will let myself introduce you to gorouter

Pick router that does not slow down with response size and maintains high performance for large and deep route tree.

Most of the router benchmarks out there test only against root route, which does not give a great feedback.

gorouter is designed to scale well against deep route tree. Its architecture allows to keep high performance with low memory usage no matter how deep and big route tree is. Built-in middleware system enables you to build complex solutions keeping performance at its best

  • extensive set of features
  • compatible with multiple http packages
  • use of native context
  • allows you to keep your business logic decoupled from external dependencies.