Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)UR
Posts
7
Comments
599
Joined
2 yr. ago

  • I have two pieces of software I cannot live without, to the point that I would rewrite them for Linux if it came to that. Running Windows as a VM using Virtual Box has been a nice experience so far. (Given that both software are not CPU nor GPU heavy and could run on a tree if need be.)

  • It's because there is no clear indication of where a block ends.

    Here is some sample code. I find it difficult to tell how many indentations I have or where I need to write if I want to continue at a certain level.

     python
        
    import time
    import aiohttp
    
    """
    Retreives the data from RSS URL and return the status codes as well as the data. Return -1 if something went wrong.
    """
    async def get_rss_feed(rss_url):
        async with aiohttp.ClientSession() as session:
            try:
                retry_count = 0
                while retry_count < 5:
                    async with session.get(rss_url) as resp:
                        if resp.status == 200:
                            return {'status': resp.status, 'data': await resp.text()}
                        else:
                            retry_count += 1
                            time.sleep(60)
                if retry_count == 5:
                    raise ValueError('To many failed connection attempts', retry_count)
            except aiohttp.InvalidURL as error:
                return {'status': -1, 'data': f"Error: {rss_url} is not a valid URL.", 'error': error}
            except aiohttp.ClientConnectorError as error:
                return {'status': -1, 'data': f"Error: Could not connect to {rss_url}.", 'error': error}
            except ValueError as error:
                return {'status': -1, 'data': f"Error: Could not connect to {rss_url} after {retry_count} attempts.", 'error': error}
    
      
  • Too much nested code was likely part of the problem, but not being able to easily tell where a block of coded ended without seeing the top of the block made it difficult to work with.

  • Never used it, only used Debian based versions. I tried my hand at Fedora and OpenSUSE but no apt made me change back. Not because it better (or worse, for all I know), just that I know apt and didn't want to take the time to learn rpm etc.

  • I remember the Quantum release. They remade how the browser handled tabs, and with the new release you could handle (almost) unlimited number of tabs. I tried this buy opening as many tabs as I could, it worked flawlessly. I can't even remember how it was before that, except that it was RAM intensive.