tuesday

It’s happening #MechanicalKeyboardMeetupPrague2020 Massive Thanks to @CandyKeysStore and @NovelKeys for sponsoring today’s meetup ❤️🙏🏻

@coderabbitai do you guys know something we don't?

In microsoft language that means they've start to use opencode instead of claude code, so you can enjoy more of an ai slop os

@gristwatch how it feels to be a half life fan

the half life 3 copium is keeping me awake (2am in the morning)

this was peak computing btw

I've bought a laptop with 16GBs of RAM. Suffice to say I'm in the swap for 50% of my time because every other app is electron based and rest is being eaten by docker. Truly worst era of software. But I can blame them, you spit this garbage out in a week.

lost at the awards won at life

Also, I think if something will kill the current hype of linux it's going to be this behaviour.

Can we like... push political views away when developing software. Since when does it affect how well a program is written. Only thing it's doing, is killin OSS communities bcs of arbitrary issues made up by a bunch of maintainers. We should do better.

If you make open source software, you are the bearer and bringer of gifts. Don't let anyone tell you how to define "open" or "source". Just pick a license, stick to the terms, and tell people they can accept the code with gratitude or they can fuck right off.

I hate ffmpeg (I love it)

the touchbar was actually goated. I miss it so much.

Tomorrow, I’m uploading my first YouTube video to my personal channel in 9 years Wish me luck 😂

I would like to see a decision flowchart, how we as a human spieces got to the point that we're building terminal interface with web browser language which was originally supposed to animate html.

@aarondfrancis When researching parts for my car (I'm taking it a track a lot so a lot of research goes into it), it oftens takes wrong lead in the forums and based on the lead it then base it's entire search on it, so often the entire research is wrong - but it's promising! 😅

Gemini Deep Research has totally altered the way I use Google. Instead of trawling forums, videos, and old docs, Gemini does it for me. It looked at ~200 different sources (!) to help debug a remote resolution issue. Not sure what it means for SEO, but it's a huge time saver.

Why does it look so good, and why do I want it so bad.

I read this article about software development, which I knew about because I saw Prime reacting to it: notashelf.dev/posts/curse-of… For the most part I think it is fine: a relatively young programmer is doing the healthy work of introspecting on what he should really be doing. But there's one part of the article that I think is a deep mistake, and the author doesn't know it's so wrong because he has never experienced the alternative: "Software doesn’t stay solved. Every solution you write starts to rot the moment it exists. Not now, not later, but eventually. Libraries deprecate. APIs change. Performance regressions creep in. Your once-perfect tool breaks silently because libfoo.so is now libfoo.so.2. 2 I have had scripts silently fail because a website changed its HTML layout. I have had configuration formats break because of upstream version bumps. I have had Docker containers die because Alpine Linux rotated a mirror URL. In each case, the immediate emotional response was not just inconvenience but something that moreso resembles guilt." Yes, this is true in much of the programming world. But there is another world in which people build things that last much longer. I have done it many times. I shipped a binary for this game Braid in 2009 that you can still download and play on Steam 16 years later. If you are pretty young (like 35), you can run binaries on Windows that were compiled before you were even born, which is amazing given how hard they have been trying to f up Windows lately. On an emulator like MAME, you can play arcade games programmed in 1979. If today's software "technology" is so much better, why does it fall apart like tissue paper? The author is not wrong about the cited decay. But this decay is not inherent to the practice of software. It's due to choices made, usually foolishly, by the people designing the systems being interacted with. And, it's due to a lack of knowing better, non-exposure to the sector of programmers who are very concerned with their code lasting a long time, actually. The way you make code last a long time is you minimize dependencies that are likely to change and, to the extent you must take such dependencies, you minimize the contact surface between your program and those dependencies. The actual algorithms you program, the actual functioning machinery you build, is a mathematical object defined by the semantics of your programming language, and mathematical objects are eternal, they will last far longer than your human life. The goal then is to avoid introducing decay into the system. You must build an oasis of peace that is insulated from this constant bombardment of horrible decisions, and only hesitantly interface into the outside world. This means, for example: If you are shipping on iOS, you only reluctantly use any functions iOS gives you, because when you use them, Tim Apple will come along and break your program next year for arbitrary pointless reasons, because Tim Apple does not respect you or anyone you know. This means a program cannot last forever on iOS, because Tim Apple likes breaking your things and watching you submissively clean them up. But the core of your program, which could be 95% of the code, is fine, and you can deploy it elsewhere. This means you have to insulate from Linux userspace, because of all the jackass decision making that introduces constant incompatibilities while somehow never making the system better. Using a library dependency to do font rendering or sparse matrix math? That dependency gets checked into your source tree, a copy of exactly the version you use. Ten years later you can pull down that source and recompile, and it works, because your program is a mathematical object. If you want to upgrade to something newer that has bug fixes and so forth, you are free to do so, but you are also free not to do so, and your program still works. (And how many of these bug fixes do you really need? Your program worked correctly when you shipped it to the greatest extent you could measure, because you are a skillful software engineer who wants to ship things of a high quality). Everyone who got into programming for the joy of it knows, at some level, that the magic of programs is that they represent complexity that is replicable over time (and thus they exist outside of time). But the trashy programmer culture of the past 20 years stopped aspiring to this, and now has forgotten it is even possible. And so long as people have forgotten, decisions will continue to be made that make the problem worse. There are programmers who only write glue code, and who think that's what programming is; to these people what I have written above will not make sense. But the good news for that contingent is, they can always just stop writing glue code and start doing something else! If today's software "technology" is so good, why do you think it needs so much glue? Maybe there is a stylistic problem. So if you are looking for what to do in the world of software that can represent a lasting contribution, maybe this is food for thought. @NotAShelf @ThePrimeagen

@_honza ;)

What are you reading? honza.pokorny.ca/reading/

@_honza Sometimes I find drew's opinion on things a bit contradictory however sometimes he make's a really strong arguments in his blog posts. But in this case I think this was the trigger - which makes sense as it's stupid github.com/martinvonz/jj/…

ok this post didn’t stay up long git.sr.ht/~sircmpwn/drew…

This.