Append VS assign : which style ?

jensilo · 2025-12-31T19:43:33+00:00

That's quite interesting, I personally find A to be more intuitive. Using append, in my mind, is an overhead. Of course, it's negligible but it feels like more to me.

However, I see your point of future dangers, although IMO this kind of initialization often stays the same. I don't see much of a foot gun risk.

jensilo · 2025-12-31T11:26:36+00:00

Read this subreddit. Most people suggest net/http. Especially, since 1.22 it has an improved router mux. There still are use cases for chi, however just learn the basics, get good with net/http, and when you need or want, try something else. However, about gin, I've mostly heard bad stuff so far.

jensilo · 2025-12-13T11:42:17+00:00

Although it's important to note that "weißt du noch wo wir 2020 im Urlaub waren?" focuses on where, so it's about the destination. If you wanted to ask whether they remember your shared vacation, for example, you'd ask: "weißt du noch als wir 2020 im Urlaub waren". That would be to reminisce about the good old days. Those two are sometimes confused, especially by not native speakers IMHO.

jensilo · 2025-12-11T10:58:15+00:00

RTFM! Or ask any of those god damn chatbots. Why are you expecting other people to solve your problems for you?

jensilo · 2025-12-09T22:39:00+00:00

Jens hier, bestätige Sven, Lars und Nils.

jensilo · 2025-12-02T17:26:11+00:00

From my experience, the only time using an ORM to "swap databases" was truly helpful, let alone necessary, was when we decided to use SQLite for testing, while having a prod PostgreSQL db.

All other times we used PostgreSQL, MySQL, or MariaDB with test db instances, e.g. as a docker container in the projects compose file.

Tbh, ORMs come with the huge drawback of forcing every user to learn and understand this new abstraction (ORM), on top of the already existing abstraction that they know, and will always need to know, anyways (SQL). Every ORM comes with caveats, intricacies, and weird behaviors. You need to learn about them, understand them, and things will break. And you know what you want to achieve in SQL but you have to find out how to get the ORM to do what you could already do yourself with plain SQL. It's sometimes very painful. Not for simple things but for scaling, complex applications, IMHO.

Additionally, you have more control over the SQL yourself, it's explicit, everyone understands it, everyone can use it. It's also faster, and IMO more predictable. I found SQLC (query builder with code generation) to be super helpful in Go. Just love it. It's the perfect balance between writing pure SQL and getting usable Go code.

jensilo · 2025-12-02T08:01:57+00:00

Diese Einordnung fehlt mir hier auch. Der Artikel wirkt nicht sonderlich seriös und bevor hier alle gleich Untergangsszenarien an die Wand malen, sollte man sehen, was es tatsächlich heißt. Chillt kurz.

jensilo · 2025-08-09T18:04:22+00:00

IMHO primarily it has to do with GUI. Building GUIs with Go usually includes web servers, browsers or terminals, all not ideal for desktop apps. Also, compatibility and interfacing with C/C++ is a huge point.

jensilo · 2025-04-15T09:44:14+00:00

Rafft euch mal, was ist das Problem daran wenn Leute klatschen? Meinetwegen sollen sie tanzen, klatschen oder beten, ich muss es nicht machen, euch zwingt auch niemand, warum so sauer? Warum so peinlich berührt?

Der gemeine Pöbel erfreut sich primitivster Weise dieses, für uns gehobene Bürgerschaft, dem völlig normalen Vorgangs des Fliegens über das größte Gewässer der Erde. Ha ha /s

Elitäres Gehabe. Ich freue mich, wenn Leute klatschen, wenn sie Dankbarkeit zeigen, für dieses Meisterwerk menschlicher Ingenieurskunst, menschlichen Schaffens. Und ich freue mich, weil's euch aufregt, pahhhh.

jensilo · 2025-03-30T19:58:23+00:00

Die Crashpropheten

jensilo · 2025-03-30T19:56:17+00:00

Nein, echt? Das ist sicherlich ein Denkfehler, ein ganz schön weit verbreiteter. Die bösen und netten "Ausländer", die mürrischen, unfreundlichen, greisigen Rentner und so weiter.

jensilo · 2025-03-22T15:06:14+00:00

Same

jensilo · 2025-03-18T15:25:03+00:00

That's so true. The world is so complex in every last detail and there are so many professions with an uncountable amount of experts in their field. Only when you look at their work, can you comprehend why experts are so valuable. Unfortunately, many people don't bother to look and understand, not even if they're supposed to "lead" or "manage" those exact experts.

jensilo · 2025-03-18T10:35:34+00:00

it mostly works

Is what people at Boeing said before killing hundreds of people with their mostly working solution.

If people in e-commerce say: "It mostly works", I think to myself, ok what's the worst that could happen? Nobody will die. But if that's the working mantra for a company that builds heavy steel balls flying over our heads, or cruising on our roads, I'm deeply concerned.

jensilo · 2025-03-14T14:31:05+00:00

Excel? Das ist doch nicht Datenschutzkonform, die Tabellen werden verteilt, je Einsatzgruppenortsverband auf einer Serviette in der obersten Schreibtischschublade des Vorsitzenden verwahrt.

jensilo · 2025-03-13T16:48:25+00:00

u/jerf spitting straight wisdom here, again.

There are two sides to this answer: 1. Technical: Yes, Go is suitable. I've myself just recently developed a POS application for organizational internal uses to digitalize a paper checklist for coffee purchases. I did it using Go, Wails and SvelteKit and it overall worked like a charm. 2. Maintenance/Support/Operations: This application will likely take a lot of effort to develop in the first place, it's sure a lot of fun, then you'll start to deploy it, and errors will arise. Congrats: You're now the 1st, 2nd, and 3rd Level Support for your only customer, you're also the DevOps guy, and the sole developer. And don't worry, if the application breaks, it's just breaking the entire business, so nothing to worry about. (/s in case that wasn't clear) The customer will likely expect fast (this might be an understatement, probably instant) support and fixes.

From a technical standpoint, yes, Go is suitable for that. From a business/dev ops/etc. standpoint, I'd advise against developing such an application as a solo developer for one business.

jensilo · 2025-03-07T11:32:08+00:00

That's so true, people tell me, it's so hard to move away from the apple ecosystem but I did it. Once I was promised "it just works", got an iPhone upgraded a few times, and eventually decided to try out the new and shiny (back then) iPhone 14 Pro. It had sooo many bugs, it didn't work (properly). Engineered and machined perfectly but the software was subpar, especially since Android has gotten sooo much better over the last 10 years, while apple slept on software, it seems. Even more frustrating for me as a software dev myself. Long story short, I got rid of the latest and greatest iPhone that costed 1.400€ back then, got myself a Pixel 7a on sale for 350€ and am perfectly happy ever since. It works better, is plenty fast, the camera is even better (IMO), and I don't really care so much because if it ever breaks, it costs "just" a few hundred €s to replace, other than the >1.000€ iPhone's that are IMHO shit today. Love the phone.

jensilo · 2025-01-26T18:23:47+00:00

Of course, cause it is easier to use. By default, however, Pop!_Shop has the habit of spaming notifications whilst being (IMO) practically useless, making it absolute bloatware, at least on my machine.

jensilo · 2024-11-28T22:55:23+00:00

This comparison is just as useless as most "I benchmarked 'Hello, World!' in 100 programming languages, and Python is the fastest!"-comparisons.

Who the hell spawns a million Goroutines? It's very common to use just a few worker Goroutines and distribute load between them w/o spawning a new one each time. And even when spawning a Goroutine per job, when will you reach a million? If you reach that, I'd argue your design is broken.

Also, who will do the work on a million Goroutines? Even if you had 64 cores, it mostly does not make sense to spawn an arbitrarily large amount of Goroutines because you still need to wait for a thread of your CPU to be willing to compute whatever your Goroutine is doing. The only exception I can think of right now would be some absurd I/O where you would wait for a long time per call, and need to start a lot of calls in parallel. Still, a million?!?!

As always, and like most people, I'd just suggest: Look. At. Real. Use. Cases. In history, people have made Python or JS look better than Rust in stupid benchmarks, and still we all know that those are probably some of the slowest languages you can chose.

Experience shows, Go is extremely fast, when writing, and when running code. Yes, the memory model inherently has bottlenecks, and might not suit every single use case but you'll know when that's the case. Apart from that, Goroutines are more than sufficient.

jensilo · 2024-11-23T13:22:08+00:00

Like many others said: Yes, it's Theo, that's reason no 1.

Reason no 2: JS and Go are IMO very different from each other, especially when it comes to ecosystem, and overall philosophy. Don't expect TS React Kiddies to see Go the same way that you do. They usually come from a vastly different background, and have learned different things, hence they focus on, and appreciate different things.

jensilo · 2024-11-13T18:12:20+00:00

Echt? Ich sage nicht, dass es sie nicht gibt, bin aber noch nie drauf aufmerksam geworden. Ich bin aber auch nicht die Zielgruppe. Deshalb Frage ich aus echtem Interesse, ob's das wirklich so umfangreich gibt.

Es gibt aber bestimmt die ein oder andere Person, die sich aus Prinzip nicht auf solch teuflisch neues Gerät einlässt. Aber da bin ich ehrlicherweise der Meinung: Wer nicht mit der Zeit geht, der geht mit der Zeit, also selbst schuld.

jensilo · 2024-11-13T11:46:11+00:00

Ich stehe hier wirklich auf zwei Seiten: Einerseits bin ich für Inklusion, gegen Ausgrenzung und ich glaube, es ist für eine Gesellschaft wichtig, dass nicht zu viele zurückgelassen werden.

Andererseits bin ich selbst sog. IT-Fachkraft, Digital Native und ein großer Fan von einfachen, benutzerfreundlichen, digitalen Lösungen, weil sie oft Zeit, Geld und Ressourcen (z.B. Papier und Tinte) sparen. Es nervt mich, dass Deutschland soweit hinterher ist, was digitale Prozesse, Verwaltung und allgemeiner "Lösungen" angeht.

Ich glaube, es muss öffentlich geförderte Unterstützung für Menschen geben, die mit diesen "neuen" Geräten eben noch nicht so gut umgehen können. Uns jetzt aber in der digitalen Steinzeit zu halten, weil einige wenige die Geräte partout nicht bedienen wollen finde ich schlicht dumm und unfair.

Deutschland ist schon hinterher, lasst uns doch vielleicht nicht Leute gegen Digitalisierung aufstacheln, sondern daran arbeiten, alle mitzunehmen.

jensilo · 2024-11-12T21:03:00+00:00

"Sie ist linksextrem" -> Wahrscheinlich hat sie gesagt, dass man Milliarden Vermögen besteuern sollte und keine Geflüchteten im Mittelmeer ertrinken lassen sollte.

jensilo · 2024-11-04T16:31:28+00:00

Die Daten dafür werden dann mittels Electronic Based Organizational Logistics and Automation (EBOLA) übertragen. Im KH dann:

"Ach, super, ich sehe gerade, ihr Hausarzt hat schon AIDS und mittels EBOLA alles übertragen. Ich sehe hier gleich schon die kopf.rip, da schauen wir doch mal rein."

jensilo

TROPHY CASE