HN user

narrowtux

390 karma
Posts4
Comments147
View on HN

Truly a great library. I have become so reliant on it, because I can basically have a guarantee that some complex process will run eventually, instead of manually catching and handling every error that might happen and write the 50th retry logic manually.

The typical way to do schema migration is to compose a list of ALTER TABLE statements. This becomes hard to track the latest schema state as the migration accumulates. It's more intuitive for the developers to specify the desired state. Ideally, PostgreSQL could allow developers to specify the desired CREATE TABLE schema, the engine then reconcile it with the latest schema, figure out the diff, and plan the migration path internally.

This is a terrible idea. The behaviour of engines that do this is unpredictable and suddenly you lose data because the engine deleted a column.

Think about having one plane (the entire glass) pressing 2 microswitches. Debouncing one switch is hard enough, now you've got to debounce 2, and detect if the user was doing a really fast double click, or just pressed in the center of the mouse.

Organic Maps 3 years ago

I still want some app that makes the awesome brouter algorithm usable on iOS. They have an android app which is "easy" to do since the routing module is written in Java, but alas, iOS doesn't support Java.

IMO, brouter generates the best routes for bicycling with lots of options to customize for what kind of riding you want to do (road, trekking, gravel, recreational, commuting, safe and quiet vs. quick, etc.).

Right now I use brouter-web on my iPhone but it's really hard to use since the UI is really small and it's very simple to accidentally place a waypoint. After that, I send the GPX file to my bike computer.

Then I'm afraid it's not possible. The reason the input switch takes so long is because of the HDID negotiation.

A video mixer acts as the source and sink for the output and the inputs respectively, where a HDMI switch will just physically disconnect and connect the output port to a different input port, meaning the HDID negotiation has to be re-done every time.

That is usually out of the question, because raster tiles don't allow you to customize the map (colors, which features to display at which zoom levels, etc). I find openstreetmap way too busy as a backdrop for data.

As I've said, the solutions are there, and there is an actual demand for cheap vector tile hosting without all of the other cruft that is bundled in the commercial solutions but isn't actually needed.

There are lots of usecases for apps that don't need these advanced features, and just want a nice backdrop for their geo data.

The current offerings of google, mapbox, bing, etc are prohibitively expensive when you just need a small subset of their features.

The company I work for is a happy customer of maptiler.com which even offers routing and reverse geocoding. It might not be as great and up to date as google's, but it's more than enough for our apps.

Yea, I wouldn't have a problem with that regulation if it would be applied to only these critical areas. But it seems that they want to apply this directive to all software that's sold in the EU.

To be fair, I haven't read the actual draft, just read some reporting about the implications for open source software.

I'm so tired of it all. Countless times it has been tried to enact laws like this. And it's not just this surveillance law that depresses me, reading up on the cyber resilience act just feels to me like it will suck even more fun out of software development, at least in a professional context.

If you were a big corporation who doesn't want to buy a license but speed up dev time, couldn't you just let your devs use mold for development to have faster recompilation cycles, but link the official binaries with some other, slower linker?

Honestly I wish there were mail, calendar and contact apps for other systems, as good as apples with solid webdav/caldav support. Thunderbird is kind of lacking in all aspects.

Just Say No 4 years ago

This is slightly off-topic, but reading your responses on this thread just rub me the wrong way. You're acting like you're entitled for open-source devs to support you and value your contributions for the sole reason that they might put a line on their resume?

As if you had the right to be angry at somebody just because they had the audacity to open source code and struggling with maintaining it.

Of course it is simple to say "communicate this clearly" in hindsight. And I kind of did that. Still there are users who expect more from me than I can give.

Just Say No 4 years ago

As a user, I can't think of anything more frustrating to spend hours or even days on an issue on an open source project that "welcomes" issues and contributions and then creating a detailed GitHub Issue only for it to be responded with with author's "No" and immediately closed.

The article also discusses that. Of course there are better ways to do this than just closing it wihtout comment, even though the end result is still saying "no" to it.

I have open-sourced a library that I wrote for an in-production app at work, and it got a little too popular for me to handle like most open source "consumers" (even though they don't pay me) expect.

Every time there's a feature/pull request, I not only have to think about if the code is correct, but also if it would introduce breaking changes in the way it is used in that production app.

It's very mentally draining to visit the issues page of that repository, because it's full of people needing help or wanting to contribute work. But I can't handle them all within an acceptable timespan.

Every few months I take half an hour to clean up there, and then the issues list is already filled with disgruntled users.

The response to an issue of "contributions are welcome" or "you can fork it" are inappropriate because the filing of an issue is not a request to fix. It is an issue reporting mechanism. But too often, maintainers become chippy about reported issues.

I agree in hindsight that it probably would've been better to just turn off the pull requests feature when creating a repository if you can't commit yourself to the potential workload it creates.

Saying no is fine but please be honest and upfront on a repository's README. If someone says "this is open source but it's mainly a personal project and/or library and I will aggressively close issues", then that does wonders to set expectations. And I think that's the key idea. Setting expectations, upfront, is the key to effective communication.

Most of the time you don't realize that you really can't handle all that workload when you're still in the "honeymoon" phase of the thing you're open-sourcing. What are you supposed to do when it gets to the point where it's just overwhelming you to even look at the issues list?

RawTherapee 4 years ago

I would love to use the open source alternatives to Lightroom, but I find the cloud offering too convenient. The photos are available from everywhere, even on my phone I can import photos directly from the SD card and start doing light edits. When I arrive home, all the photos have already been copied to my computer where I can finish the project on the big screen.

Is there something that approximates this "effortless" experience using some cloud service and the freedom to use whatever software to manage and convert the photos?

Old Elbe Tunnel 4 years ago

Right now the "Alte Elbtunnel" is undergoing maintenance in one of the two tunnels. Since as long as I've lived here, it hasn't been open to cars, but the large elevators previously used for cars are still serving bicyclists and pedestrians during the daytime. They get quite full during rush hour.

I use the tunnel 3-4 times per week!