HNHacker News
TopNewBestAskShowJobs

kh_hk

1,163 karma · joined December 2, 2012

"Not craftsmen, my lord," he said. "I have no use for people who have learned the limits of the possible."

    ― Terry Pratchett, The Last Hero
submissionscomments
kh_hk··on Nue.js: Rethinking Reactivity
Not sure why but separation of concers was hammered so hard for a while that I cannot accept any inlined javascript or css at all. For me the reason is clear, I do not need to scan the html to know what a particular piece of code is doing and will just assume these ids are somewhere out there.

The first example of the site would become:

    <div>
      <h2>You clicked {count} times!</h2>
      <button id='decrement'>Decrement</button>
      <button id='increment'>Increment</button>

      <script>
        count = 0
        $('button#increment').on('click', () => { count++ })
        $('button#decrement').on('click', () => { count-- })
      </script>
    </div>
kh_hk··on Nue.js: Rethinking Reactivity
Patiently waiting until the pendulum swings back to async binding js events to elements by classes and ids and any inlining gets frowned upon.
kh_hk··on Privacy Nightmare on Wheels’: Every Car Brand Reviewed by Mozilla
1990 is a bit of a stretch, I draw my line around the '00s.
kh_hk··on Questionable $2,500 hoodie makes you look like you were plucked out of Minecraft
Clothing line for popular streamers I guess
kh_hk··on Solaris movie review and film summary (1976)
Fair, I do agree. Both the book and the film are truly masterpieces on their own
kh_hk··on Solaris movie review and film summary (1976)
Something I felt reading the book that I did not feel with the movie was a bit of horror sci-fi vibes. That alone to me is what makes Solaris one of Lem's top works, on which the crude descriptions add to the suspense and horror.
kh_hk··on Google Search Is Dying (2022)
And yet, I mistrust most product reviews that are on Reddit too, since marketers have found ways to control the hivemind
kh_hk··on ChatGPT and the AI Apocalypse
[spoiler alert]

An entity probing humans using our emotions and memories and generating fractal nonsense as a byproduct

kh_hk··on ChatGPT and the AI Apocalypse
Makes me think of Solaris too
kh_hk··on Ask HN: Those making $0/month or less on side projects – Show and tell
Thanks for replying and for providing feeds much on the same philosophy as citybikes. I guess the feed you mention is for Aachen [1]? Sometimes I take a very hands-off approach on the library contributions, so I do not know about specifics. At the moment our gbfs feeds come with a 'gbfs_href' field mentioning the source. Is there any way on which I can give more credit to the work you are doing? It would suck for our project to perpetuate the same kind of damage we receive from other projects, so this is important to me.

Will send you an email, happy to chat.

[1]: https://github.com/eskerda/pybikes/blob/86c8cca04b9e747fda1e...

kh_hk··on Ask HN: Those making $0/month or less on side projects – Show and tell
Citybikes: https://citybik.es

A bike sharing data aggregator. Started as an Android app for my local city, then an app for any city and then just decided to offer an API for free and let other people create apps, visualizations or research based on it.

Been running it for over 10 years. Major transport apps use it for bike sharing data (like moovit or citymapper) with zero contributions to our project. I am proud that there is at least one FOSS app for each major platform out there using the API, which kind of was my idea when offering the free API (and not big players leeching from it).

kh_hk··on The Legacy of Peer-to-Peer Systems
This is neat and clean https://torrents-csv.ml
kh_hk··on Oceanic+ on the Apple Watch Ultra and the perils of subscription based software
I was under the impression that this was not the case, since the pressure and other information seems to be available on their SDK docuementation

See https://developer.apple.com/documentation/coremotion/cmwater...

If this was locked to use only by the Oceanic app this wouldn't be such a big deal to me at least.

kh_hk··on Oceanic+ on the Apple Watch Ultra and the perils of subscription based software
Are you sure you can write apps that act as a diving app for the Garmin?
kh_hk··on Oceanic+ on the Apple Watch Ultra and the perils of subscription based software
Can you write apps for the Descent Mk?
kh_hk··on Oceanic+ on the Apple Watch Ultra and the perils of subscription based software
Just added that to the article. I do not see the OSTC as a general purpose programmable dive computer (under my own definition, that is).
kh_hk··on The Oceanic+ app comes to Apple Watch Ultra
This might be a pivotal moment on subscription based hardware. Apple is selling their hardware as a software platform _to_ companies that already sell their hardware. Will this force other companies selling dive computers to adapt and also use publish an app for Apple's platform?

As a diver it's clear to me that the target audience are future divers. We might delude ourselves on the pros and cons of our current dive computer, models and so on. But I am sure someone entering the sport will consider this along the other options.

My personal opinion, a big majority of recreational (shallow) diving does not even require a dive computer and it all comes into LARPing territory. It's good to know your depth and the time you spent underwater, that's all. I have seen people wearing a +1k USD dive computer diving at most <20m. Of course it's none of my business how they decide to part with their money.

This much money will give you a very nice dive computer, albeit terribly complex and completely overkill for most of the rec. diving. If someone is willing to spend that much on a dive computer for rec diving, I guess an apple watch is money better spent? Let's just acknowledge that a Shearwater Perdix is a tough sell to someone that wants to spend this much but dives very very occasionally and shallow.

I am just sad about the subscription model and the implications this might have if/when it proves successful.

kh_hk··on 99Wh Battery Linux Laptop
Because that's what factories are producing
kh_hk··on Robot Framework: generic open source automation framework

    *** Test Cases ***
    Write my test using a DSL
        Read examples of the DSL
        Write a basic test and see that it works
        Write a complex test and find something missing
        Learn quirks about DSL
        Implement missing things on the language that the DSL was implemented on
        Write part of the test in said language
        Write part of the test in DSL matching regexes
        Run the test
        And it works 9 out of 10 times
        Install flaky extension
        Add flaky tag to test
        And it is green
        [Teardown] Reflect about my life as a software developer
kh_hk··on Ask HN: Inherited the worst code and tech team I have ever seen. How to fix it?
Maybe pessimistic: leave and find a place to work on something you enjoy. If you stay you will be left fighting everyone and doing all the grunt work by yourself whilst others keep pushing more code in for you to cleanup.
kh_hk··on Physical buttons outperform touchscreens in new cars, test finds
"I just thought I was in INSERT mode"
kh_hk··on Physical buttons outperform touchscreens in new cars, test finds
It's all fun until someone else tries to quit your car.
kh_hk··on Physical buttons outperform touchscreens in new cars, test finds
Happy if cars ditched the navigation screen altogether. Having an external GPS is not such a bad thing. Something you can remove, replace or upgrade.
kh_hk··on Docker Compose best practices for dev and prod
I apply this solution exclusively on the development environment. I have found that having the power to bail out to a shell whenever docker compose does not support something helps me iterate faster on my local dev (without affecting others).

The following is just a contrived example. Why would I do that? Because I can

    # Bring up services without a command
    #
    # usage:
    # nocmd.sh up -d service_name
    
    function _compose {
      docker-compose -f docker-compose.yml $@
    }
    
    function nocmd {
    cat << EOF
      services:
        $1:
          command: tail -f /dev/null
    EOF
    }
    
    function nocmd_compose {
      local service=${@: -1}
      _compose -f <(nocmd "$service") $@
    }
    
    nocmd_compose $@
kh_hk··on Docker Compose best practices for dev and prod
It's an anti-pattern just because you say so. This is a simplified example of a complex problem that needs arbitrary volume mounts. Using volume mounts to run software inside containers is a common dev pattern on scenarios where rebuilding takes too much time to quickly iterate. I am sorry, but unfortunately I cannot expand the issue further here to help you understand it, and I am happy too if you think I am over-engineering compose.
kh_hk··on Docker Compose best practices for dev and prod
Everything is simple until someone asks you to try and diagnose (and hopefully fix) a bug on an upgrade between two different versions of a piece of software that can be deployed using 5 different strategies or that has 20 moving services...
kh_hk··on Docker Compose best practices for dev and prod
It's a simple example, maybe too simple to get the point. What I want is to conditionally set things on a yaml file. If you have ever used a templating language, you know this problem

    services:
        redis:
            ...
    
        {{ if some_condition }}
            volumes:
                bla bla
        {{ end if }}
    
        {{ if some_other_condition }}
        another_service:
            ...
        {{ end if }}
    
    volumes:
        {{ for volume in volumes }}
            - ...
        {{ end for }}
kh_hk··on Docker Compose best practices for dev and prod
All I am saying is:

* docker compose could be better

* docker compose does not improve that much

* by mixing docker compose with templates you can get complex stuff going, but is not a much advertised feature.

Most of the "cool dev tool env" that appear are based on kubernetes, or something that is _not_ docker compose, which makes them difficult to adopt. I would like docker compose to improve on a direction that makes development easier, that's all.

kh_hk··on Docker Compose best practices for dev and prod
That's just the tip of the iceberg. My problem is that YAML is not a turing complete language (and dev environments are usually messy by their nature).
kh_hk··on Docker Compose best practices for dev and prod
For me the problem is that yaml (and the compose specificatio n) is not self sufficient to support complex scenarios. You will start by setting things and discovering that ENV vars * on the global scope of the compose specification are not supported so you end up having to template and output yaml.

Try having 40 microservices and quickly iterate between fixing bugs in them. Some you want mounted, others you want running unmounted. I understand the premise is already broken, you do not want 40 microservices, but that's not a precondition you can fix without a time machine.

[[* EDIT: by env vars on the global scope, I mean setting things on the global scope by using an env var, say, you want a certain volume named after an environment variable. You can only use ENVs as values.

    # this works
    foo: "${SOME_ENV}"
    # this does not
    ${SOME_ENV}: "foobar"
← PreviousPage 5 of 14Next →