This was my thought too. Your tool is great at finding vulnerabilities, and we want software to be secure for everyone, secure code should not be out of reach to those who can't afford it.

Scan everyone's code, for free. Make all code as secure as an llm can make it as a baseline.

This feels like it misses the point. Tokens = money. The real differentiator is time and effort.

Llm's will find your issues faster, but not necessarily more accurately than a domain expert. But experts cost money and effort takes longer to apply.

Are llm's going to reduce everyone's wages because they are cheap labour?

In Greek mythology, Procrustes (/proʊˈkrʌstiːz/; Greek: Προκρούστης Prokroustes, "the stretcher [who hammers out the metal]"), also known as Prokoptas, Damastes (Δαμαστής, "subduer") or Polypemon, was a rogue smith and bandit from Attica who attacked people by stretching them or cutting off their legs, so as to force them to fit the size of an iron bed

I can't figure out if you meant that or not, it kinda fits. (No pun intended)

well yes and no, i meant https://en.wikipedia.org/wiki/Orthogonal_Procrustes_problem which, yes, is named for that stretchster

It's perfectly fine and usable for me. More so than the app or the 'new' Reddit design. I exclusively use the old design.

I see aot if these kinda of links to GitHub repositories with the user obviously keen on showing people, but they then describe what it is / does using specialist / domain language which can make it quite hard to get just what it is I'm looking at, or what I can do with it, and where / why it would be useful. I do wish people would consider their audience after posting 'look at this thing' links, and that people might not quite be as familiar with acronyms and domain specific terminology without a bit more of a plain speaking background description as to what is being shown off! Maybe even some screenshots too.

I mean, I can follow ops intent to a general degree, it sounds interesting, but ..

> I mean, I can follow ops intent to a general degree, it sounds interesting, but ..

Thanks for trying to meet me halfway. I hope I can bridge the gap.

The repository is the codebase for a GUI toolkit. It runs ruby scripts that make use of a custom templating language (like html), and a super class that provides similar component technology you'd likely find in vue or react. (Hokusai::Block).

When the ruby script is run from the binary built from the codebase (hokusai-pocket), it spawns a window with your application. There are releases for x86 linux, windows, and osx - and also arm64 linux. You just write your application, and run it with `hokusai-pocket run:target=app.rb`

The hokusai-pocket binary also include a command for publishing your application as a standalone binary for different platforms, but I'm currently working on that.

So all in all, it is a gui toolkit + runner that you can download for x86 linux, windows, and osx to dynamically run desktop applications.

I mentioned cutting its teeth on a photoshop clone. Here's a screenshot: https://file.skinnyjames.net/demo.gif

3 things currently; some fun toys..

Web based two player bingo race game in an attempt to drag significant other away from mobile phone. :p

Optimised gravity sim, everyone loves a good gravity sim. Event driven physics and aiming for 10000 spheres at 60fps.

Alife simulation where critters can read and write symbols into/from their environment to see if we can't get some kind of rudimentary communication evolved.

Nothing super serious, but fun gadgets to tinker with :)

designers are creatives and will always believe the visual elements of a design need to be updated, refreshed, modernized etc.. then we get flavour of the month nand new trends in visual language and ui design that things must be updated to.

As soon as UI design became a creative visual thing rather than a functional thing , everything started to go crazy in UI land..

That is because they know the users. Users are very sensitive to this: if the outside wasn't changed then the internals cannot be much improved. You see this with cars, cars need a new design otherwise customer will think nothing much changed. Customer will usually buy newer over better because they think newer must have improvements, and styling signals new. Same with computers, all the disappointments when apple releases a new macbook without changing the exterior....

I'm finding the oppostire with copilot. A request is a prompt, with some caveats around whats generating the prompt. I am quite happily working with opus 4.6 at 3x cost and about 1/3 oor the month in I'm stting at ~25% usage of a pro+ subscription. I find it quite easy to track my usage and rate of usage.

The overall context windows are smaller with copilot I believe, but it dfoesnt appear to be hurting my work.

I'm using it for approx 4 hours a day most days. Generally one shotting fun ideas I thoroughly plan out in planning mode first, and I have my own verison of the idea->plan->analyse-> document implementation phases -> implement via agent loop. simulations, games, stuff-im-curious about and resurrecting old projects that never really got off the ground.

Different techniques appropriate in different situations, I would decide on what's appropriate given the goals you have. Whichg is nearly always the answer to X is a better way than Y arguments.

Ok? Not bad to be able to throw something like that together with minimal effort. Works nicely enough.

It's pretty, but almost exclusively focused on ATI/AMD and Nvidia with an intel thrown in for fun. Not actually a list of important GPUs.