Hacker News: ssfak

New comment by ssfak in "Using HTTP/2 Cleartext for a server in Go 1.24"

ssfak — Mon, 25 May 2026 12:21:48 +0000

New comment by ssfak in "Migrating from Go to Rust"

ssfak — Mon, 25 May 2026 09:06:06 +0000

In Go you can ignore the error value though, and use directly the returned value (`int` in your example). In Rust you cannot do that, you need to unwrap the Result or use the `?`

Background Jobs in Go with Asynq and Valkey

ssfak — Sun, 05 Apr 2026 15:26:54 +0000

Article URL: https://josephgoksu.com/blog/background-jobs-in-go-asynq-valkey/

Comments URL: https://news.ycombinator.com/item?id=47650396

Points: 4

# Comments: 0

New comment by ssfak in "Found a simple tool for database modeling: dbdiagram.io"

ssfak — Sun, 27 Apr 2025 19:08:55 +0000

chartsdb[1][2] can be installed locally (or run through Docker) and import your database schema

[1]: https://chartdb.io/ [2]: https://github.com/chartdb/chartdb

New comment by ssfak in "PostgreSQL 17"

ssfak — Fri, 27 Sep 2024 09:00:59 +0000

Using the pg_duckdb[1] is an option, if you can install extensions on your setup.

[1]. https://github.com/duckdb/pg_duckdb

New comment by ssfak in "Maestro: Netflix's Workflow Orchestrator"

ssfak — Tue, 23 Jul 2024 06:34:19 +0000

For Python tasks you can check Prefect, among others..

New comment by ssfak in "Surprising things about HTTP"

ssfak — Thu, 09 Jun 2022 10:40:22 +0000

I was expecting something like sending a payload with GET requests is not prohibited by the standard...

GraphQL Subscriptions: Why We Use SSE/Fetch over WebSockets

ssfak — Fri, 29 Apr 2022 02:16:40 +0000

Article URL: https://wundergraph.com/blog/deprecate_graphql_subscriptions_over_websockets

Comments URL: https://news.ycombinator.com/item?id=31200625

Points: 1

# Comments: 0

New comment by ssfak in "The Problem with C (2020)"

ssfak — Tue, 01 Feb 2022 10:07:08 +0000

More adequate title would be "C++ problems with C"..

New comment by ssfak in "Best Practices for Using Functional Programming in Python"

ssfak — Wed, 05 Dec 2018 15:41:43 +0000

Indeed, "Mostly functional" programming does not work: https://queue.acm.org/detail.cfm?id=2611829

New comment by ssfak in "Gene name errors are widespread in the scientific literature (2016) [pdf]"

ssfak — Mon, 08 Oct 2018 08:54:18 +0000

The findings are well known, but I find it a bit ironic that the authors provide supplementary material as an Excel file...

New comment by ssfak in "Clojure Design Patterns"

ssfak — Fri, 24 Nov 2017 17:10:39 +0000

..and closures

New comment by ssfak in "Show HN: WebSocket-first development"

ssfak — Mon, 13 Feb 2017 20:48:46 +0000

I believe in the majority of cases SSE are a better technology than web sockets (e.g. WS do not seem to conform to HTTP/2.0, SSE offer transparent (browser-supported) reconnects, SSE event ids allow for replay, etc). The downside is no support in IE/Edge (you can vote at https://goo.gl/bd8V1K), no binary content (but again usually JSON is enough) and no fully bidirectional communication.

A good talk at the matter can be found at https://youtu.be/NDDp7BiSad4

New comment by ssfak in "RethinkDB versus PostgreSQL: my personal experience"

ssfak — Sat, 11 Feb 2017 07:10:49 +0000

I am a bit puzzled about the scalability of listen/notify in Postgres and its use in the article. Each "listener" in the code requires a connection in the database so it's not a good design to have one listen "query" for each user. You will probably need a dedicated connection in a thread (or a limited number of connections) for the database listening functionality. You can possibly use some async PG driver but still on the database end I am not sure how efficient and scalable this solution will be.

I can assume that this is a good solution if you don't have (need) a high rate of "notify" statements and a high number of subscribers waiting on "listen". Any comments on these limits of PostgreSQL?

New comment by ssfak in "Neanderthals were people too"

ssfak — Fri, 13 Jan 2017 06:54:16 +0000

cough sci-hub.cc cough

New comment by ssfak in "From Python to Go and Back Again"

ssfak — Sat, 17 Oct 2015 09:03:56 +0000

Doesn't a TLS terminator proxy solve this? E.g. I usually put my application services behind HTTPS-enabled nginx and it works wonderfully.

New comment by ssfak in "PostgreSQL Magic"

ssfak — Fri, 11 Sep 2015 08:01:07 +0000

For windows functions a good tutorial can be found at http://tapoueh.org/blog/2013/08/20-Window-Functions

Postgresql also has good support for SQL-99 : http://www.slideshare.net/MarkusWinand/modern-sql

WITH clauses (CTE) are great, but they are "optimization fences" in Postgresql : http://blog.2ndquadrant.com/postgresql-ctes-are-optimization...

New comment by ssfak in "Things I do to be consistently happy"

ssfak — Mon, 20 Aug 2012 12:08:54 +0000

Well, he recommends to stick to a specific schedule (having a walk at 21:30, going to sleep at 22:00, waking up at 06:00, etc) The exact times do not really matter, but sticking to a specific time schedule is problematic IMHO when you have a family because of the non-determinism introduced (especially by the kids).. Unless everyone in your family agrees to follow (and stick to) a similar schedule..

New comment by ssfak in "Make HTTP requests from your browser"

ssfak — Mon, 09 Jan 2012 09:35:31 +0000

Somewhat similar but more useful for debugging "HTTP caching" by Mark Nottingham: redbot (http://redbot.org/)

New comment by ssfak in "Some People Understand REST and HTTP"

ssfak — Mon, 08 Aug 2011 09:20:16 +0000

> This re-imagines passwords as nouns. As a side effect, you get a complete log of whenever anyone changes their password or requests to reset it. > Want to enforce password reuse policies? Do analysis of password lifetimes? Track down malicious abuse of your password reset system? > Those things are now pretty easy with a schema like this

I am also proponent of the more "resource oriented" view of an application but I fail to see how the CRUD approach you proposed is unique in order to support the above.. Because, all of the things that you mentioned can be also implemented/supported if you transmit the tokens in query strings. I.e. /password/:token and /reset_password/?token=:token are more or less the same thing from the REST point of view although the first is more user friendly, cache friedly, etc. After all URIs are opaque to the client: http://www.w3.org/DesignIssues/Axioms.html#opaque and that's where HATEOAS enters so the client just needs to know a single (bookmark) URI and the hypermedia will guide to the creation of the rest resource identifiers needed by the application (HATEOAS is indeed the "highest level" of REST: http://martinfowler.com/articles/richardsonMaturityModel.htm...).

Unless you mean that by following the 'noun'-oriented view of the password tokens you can easily spot these operations in the apache logs.. to which I agree if you also include the user id in these URIs...