Walkman

Oh man, my heart breaks when I see yet another auth framework _yet again_ on HN front page, because I work for a company selling Identity Access Management solutions, so I'm not allowed to work on my dream authentication framework [1] for obvious legal reasons. I know a lot of problems regarding authentication and SSO, and I have such a simple solution in my head for a lot of use cases which would be useful for a lot of companies. It is especially annoying because I see how companies pay millions of dollars for fucking terrible solutions I don't think it's fair.

The only way I could start working on this if I quit my job, but that might not be very ethical thing to do. Any advice what should I do? What would you do?

[1]: https://github.com/kissgyorgy/fancy-auth

I implemented something like this not long ago:

    class Api(AsyncApi):
        def __init__(self, token):
            try:
                self._loop = asyncio.get_event_loop()
            except RuntimeError:
                # when running in a thread, get_event_loop doesn't create another one
                self._loop = asyncio.new_event_loop()
                asyncio.set_event_loop(self._loop)

            self._session = aiohttp.ClientSession(loop=self._loop)
            super().__init__(token, self._loop, self._session)

        @lru_cache(maxsize=None)
        def __getattribute__(self, name):
            attr = super().__getattribute__(name)
            if name.startswith("_") or not asyncio.iscoroutinefunction(attr):
                return attr

            def call_sync(*args, **kwargs):
                coro = attr(*args, **kwargs)
                return self._loop.run_until_complete(coro)

            return call_sync

It can run when there is no loop or even when a loop is already running.

Python. It changed my life significantly. I have a job I love, I earn good money. Not sure I could have reached what I did under a couple of years with other languages, because Python let me focus on learning all kind of things beside it, because it was fairly easy to pick up.

The choice of not using Kubernetes?

Unfortunately python3 returns with an "Illegal instruction" and doesn't start :( Would be very cool if it would be possible to run Python on this!

Or you can just literally record it with https://asciinema.org/ and embed like a video. The text will be selectable even!

The title in this case is not very clear because it's out of context. Should be something like "the Microsoft acquisition of GitHub is complete" to be more factual and instantly understandable.

    Unless you already know your users will want man pages, I wouldn’t bother also outputting them as they just aren’t used often enough anymore.

I don't know where this is coming from, me and my colleagues are reading man pages every day. I would be interested how much others read them.

You probably don't want to use this the same way you don't want to use random Docker images from the docker hub. I don't see the use case for this.

It's just a not very well explained rant of some shitty libraries and a lot of legacy code. If you want to read about REAL complaints, read Armin Ronacher thought about it instead: http://lucumr.pocoo.org/2014/5/12/everything-about-unicode/

We automate everything we can, but I never felt for a single moment that I will have no job tomorrow if I do this, there is always so much problems to solve, so much to do.

I disagree with this. I think you are not passive watching live coding almost the same way like you are pair programming and you are the observer.

But you can do that by reading code of Open Source projects, which is more effective IMO.

Genuine question: What is the appeal of watching live coding? Who watches these? I'm watching code all day long, arguing about it, understanding it on my workplace, if I get home, there is no way I want to watch another guy live coding. Maybe doing my own thing when I'm free and not tied to a gazillion rules of how to do things.

hmm, then Pyside2 API must have changed significantly. I only used Pyside 1.

The now-official bindings (Qt for Python as mentioned in the article) has a waaay more Pythonic API. I actually liked it. The advantage of PyQt5 is that you can look up the Qt documentation.

Every hardware can be cheaper than AWS if you build it yourself, that's not the point. The ongoing cost of maintaining and improving it, and the necessary knowledge might not. Also instead of building your own hardware, you can build the app instead. I thought these are obvious for anyone.

I made the same thing for command line: https://github.com/kissgyorgy/interactive-youtube-dl

You obviously did not dig in :D There are absolutely terrible parts, would not recommend!

Actually I would be fine with that, if it would be viable. Unfortunately, it is not.

Yes, of course! See my comment above.

I'm not saying this because of my rigid opinion, but because of productivity. I WISH Mercurial was the one who caught on, because everyone says it's better, more intuitive (oh, and it's written in Python which I absolutely love) but this is not the case, Git won and people should accept that.

To put another way; I HATE git, I LOVE Mercurial, but Git won, it's ubiquitous and Mercurial is not that much better.

Again, the difference in that case is that llvm is probably an order of magnitude better than gcc. Mercurial is not.

You might be right on one hand, but do you think Git is "stagnating"? I don't think so.

> You use Git so everyone else should use Git?

Almost everyone is using Git nowadays, so the rest should use Git also, yes, instead of wasting brain cycles, even worse huge efforts to support Mercurial instead of improving existing features in GitLab.

I'm not at all against progress, innovation or opinions, but I hate complexity, wasted effort and somebody forcing me to learn yet another tool just because...

That comparisong is not fair, but anyway, no need for new languages today, we should improve the existing ones. See UncleBob's opinion on these: http://blog.cleancoder.com/uncle-bob/2015/08/06/LetTheMagicD...

C is just terrible, it has to be improved, but the "Git vs Mercurial" is not the same topic, because Mercurial is not THAT MUCH better to worth to replace it or make thing more complex.

Yes, Exactly! mercurial is not THAT MUCH better, so it doesn't worth spreading. If it contain good ideas, we should try to incorporate some into Git, instead of making every tool more complex.

Yes! Absolutely! So I can focus on innovating where it matters (the product I'm developing). It alao would mean those things would be extremely polished (because a lot of people affected and interested to make it good). Also I would not need to learn so much random stuff I don't really care about.

It's GitLab, not MercurialLab. Hope they realize this and refuse to merge. I really like shared tooling and knowledge, so if Git dominates everywhere, all you have to do is learn git and that's it. It's a significant overhead to learn yet another VCS just because it is a little nicer. I hate wasted efforts.

The thing about files is that they are never going away and they are simple like a rock. If you want to avoid any type of lock-in ever, just store things in files.