kamstrup

joined 2 years ago
[–] kamstrup@programming.dev 1 points 4 days ago

That depends on what you count as a "test". In some langs/frameworks it is a lot, indeed.

[–] kamstrup@programming.dev 5 points 1 week ago (3 children)

Yeah. Totally agree on this. I spend maybe 3-4h a day reviewing code, and these are my thoughts....

The LLM generated tests I see are generally of very low quality. Perfectly fitting the bill of looking like a test, but not actually being a good test.

They often don't test the precise expected value. As an overly simplistic example: They rarely check 2+2==4. But just assert 2+2>0, or often just that 2+2 doesn't cause an error.

The tests often contain mountains of redundancy. Again, an oversimplified example: They have a test for 2+2, and another for 2+3.

There is never any attempt to make the tests nice to read for humans. It is always just heaps of boilerplate code. No helpers introduced, or affordances to simplify test setup.

Coupling the proclivity for boilerplate together with subtly redundant tests makes for some very poor programming. Worse than I'd expect from a junior, tbh.

And 1500 tests... That is not necessarily a lot! If that is the output of 1 month of pumping out code, I would say bare minimum

[–] kamstrup@programming.dev 14 points 2 months ago

This is just incorrect, sorry to break the news. Most modern electric cars are hardwired to phone home. In most models the surveillance is fused directly into critical components like the fuel pump or the braking system. You cannot just pull out some wires in the dashboard. If you disconnected these things the car is unlikely to work. These details have been covered by people who have worked in the industry

[–] kamstrup@programming.dev 4 points 2 months ago (1 children)

Most devs I know like recursion. Trouble is that many popular languages don't support tail recursion, but throw a stackoverflow error after a few thousand levels. So you have to keep track of max recursion depth manually, and it starts to look like a complicated solution

[–] kamstrup@programming.dev 1 points 2 months ago

Most devs I know like recursion. Trouble is that many popular languages don't support tail recursion, but throw a stackoverflow error after a few thousand levels. So you have to keep track of max recursion depth manually, and it starts to look like a complicated solution

[–] kamstrup@programming.dev 4 points 3 months ago (1 children)

9 times out of 10, this "vibe draft" sends people down a terrible path that they would have never ventured had there been an adult in the room. I swear I review so much code that sets off in the wrong direction because of this, and I am sick of it.

[–] kamstrup@programming.dev 9 points 3 months ago (5 children)

Forgejo supports SSO, and from a quick skim of the diff it looks like they support GitHub and OpenID logins.

[–] kamstrup@programming.dev 0 points 5 months ago

X11 is "complete" in the sense that we have followed it to the end of the road. X11 has a series of well documented fundamental problems that does not make it suitable for a modern OS. I will not belabor them here (except to note that security in particulat in X11, is exceptionally weak for modern standars). These issues are unfixable because they are built into core assumptions and behaviours of all legacy apps.

At some point there has to be a switch. There simply is not manpower to maintain 2 separate windowing systems. I am sure we would all want there to be an army of devs working on these things on maintain the 2 stacks. But that is not the timeline we live in. The number of devs working on these things is very low.

Was it too early? I don't know. There will never be 1-1 feature parity with 30 years of legacy apps. I honestly believe that fixing things like a11y are gonna be much more tenable with only a single windowing system.

[–] kamstrup@programming.dev 15 points 5 months ago* (last edited 5 months ago) (10 children)

For someone who has not used Gnome in 14+ years you sure seem to know a lot about it...

X11 has effectively already been deprecated for years, seeing little to no development on it. No one should be surprised.

And still, there are SEVERAL Long Term Support distros out there that will support X11 for the coming years. Please stop pretending that stuff will start breaking. It will not.

[–] kamstrup@programming.dev 7 points 6 months ago

I find that my projects hosted on codeberg are heavily deranked or entirely missing on the top mainstream search engines. My github projects are almost always top 3.

So if it is a library someone might gind useful it has to go in gh. My personal toys can stay on cb.

[–] kamstrup@programming.dev 15 points 7 months ago (1 children)

At least we still have Skype (new), Skype for Enterprise, and Windows Skype

 

The Go team is working on a new garbage collector called Green Tea.

 

In the original proof of concept for ranging over functions, iter.Pull was implemented via goroutines and channels, which has a massive overhead.

When I dug in to see what the released code did I was delighted to see that the go devs implemented actual coroutines to power it. Which is one of the only ways to get sensible performance from this.

Will the coro package be exposed as public API in the future? Here's to hoping ♥️

 

Go 1.22 will ship with "range over int" and experimental support for "range over func" 🥳

view more: next ›