merb

It really depends what you are doing. But copy and paste is super slow on iterm2, like coffee going slow.

Well because some php configurations had an absurdly low default max upload size, which made the rce way harder. Plesk for example ships with 2m for some reason.

btw I used iterm2 for years as well and sometimes tried others.

I now use ghostty it’s faster definitely. Yes it has some quirks which is hard to overcome as a iterm2 user. But I could live with it. I think ghostty is basically also the only alternative to iterm2

    The attack needs no authentication — only one public project that can hold the .org payload.

So probably not vulnerable if no public projects exist - ie self hosted has an needs auth for everything mode.

I have that aswell…

But I also updated pretty early.

Also they could’ve sent patches to at least some trusted members/maintainers/distros/hyperscalers/big Hosters/plesk/cpanel. It would’ve been easier to make some kind of coordinated release.

Also not announce it beforehand…

The vibe coded version probably work and are probably faster. But probably not more maintainable or easy to write new features for.

But for stuff like that, it is usually not often a problem since features are most often first built as a spec and a test(suite) which by itself makes the thing easier to maintain with vibe coding. Since the implementation in itself is not import, only that it works like the spec. But that works only for software that can have a well defined specification and a test(suite). Basically it only works for things that are formally verified through the spec, which is not a lot of things at the moment.

What did you want to accomplish with 5.04??

In Spanish or other European countries 5,04 would’ve been correct?

So 5.04 would either be invalid or 504 like Claude did.

Trust me, they need those. Because somewhere there are people on an old Citrix env that only contains some older browser versions

> Just because they published Open Source code at some point, you feel that you're entitled to free updates for the rest of your life?

No. That is not the expectation.

But using the open source brand going forward is a shitty move. If they want a commercial offering they should just rebrand and abandon the oss offering.

Bitwarden the company is not struggling.

Sorry but the elasticsearch thing was a big stupid take of elastic. It was big corpo against big corpo not the poor elastic company.

Changing licenses is a sick move and companies doing that should be fucked over, because the license made them big. Changing it later on means that they got greedy nothing more nothing less.

Without oss bitwarden would be a paid cloud like all the others that probably would’ve had a hard time getting trusted.

Well it used what was available at the time. Which was not a lot, that it even worked is insane

Well at the moment we do not use Gemini in an agentic framework. But as said the flash and flash lite families are basically their driving force in some of their applications in Google cloud, like document ai and its ocr capabilities are probably better when it comes to business documents than any other (at least in perf to cost to speed). We also drive Gemini lite in our application where customer can use it to generate simple automation, like an agentic framework but way way smaller scale. And while it struggles in more context heavy operations it still is a beast when feeding it one or two pdf documents and asking questions about them and it’s hella fast.

From a business perspective a frontier model does not make much sense anymore if you are not a startup. Neither for Amazon, nor for Google. Their clouds need models that are fast and perform well in their agent frameworks nothing were a frontier model excels at.

Most Google products even use flash lite underneath, so their frontier model is mostly used for distillation.

Sentry also has an errors only mode: https://develop.sentry.dev/self-hosted/optional-features/err...

I just compared typst with peachpdf (c#) and others to generate big reports, invoices, etc. coming from itext 4 the open source version which was lgpl. And was blown away. Itext was quite efficient because layouting did not do a full css thingy. Which peachpdf does, which of course produces a better looking pdf. But full css eval, could byte your ass with flow elements and div wrappers. You can be extremely non performant and ram hogging pretty fast, especially since peachpdf is not optimized.

However typst? God , it is so fast that downloading and rendering it inside a pdf viewer is the new bottleneck… it generates 2000 page pdfs in second with maximum of 2 gb , however most of the time it used 250mb memory. Peachpdf used 15-30gb for that, heck even itext used 4 gb. Cpu everything was so fucking fast, even while going through p/invoke.

I just fucking love it. I mean sometimes the syntax is weird, but it’s the best layout+data to pdf renderer.

Actually you can use foxpro with mssql and ole, you could than even add row level security for even more security

With Claude I never had that problem. However Claude does not use the pattern by default

I use that aswell since it can be used and expose a posix filesystem. This is helpful when we want to add s3 to existing storage like a nas. (Well we had some problems with it in the past tough)

Sadly most new projects do not offer posix anymore.

My plan for bigger things is mostly:

Generate multiple solutions- they do not to work 100% correctly. And than I check which I would prefer. Which is more to our applications taste.

And than I would take the vibe output as a kind of a ‚plan‘ which I use to implement but not follow 100% and at the end I take my solution and review it. I gain speed with that because I often can quickly see the pros and cons of a solution way better than when I would manually do it and hang on a major roadblock and also I even see such roadblocks in the vibe output - it’s mostly the part with an unnecessary amount of new code that looks nonsensical.

Fun thing Google cloud storage supported that for a long time now. Just AWS took its time.

Which gui? I’m on Mac and somehow I could never really be happy with gui‘s for git. Gitkraken is the last I tried and I found it too much cluttering. Paid choices weren’t that great aswell either (yet)

On servers with k8s the default is preempt based on prio, followed by oom kill and ‚newly’ memory qos:

https://kubernetes.io/docs/concepts/scheduling-eviction/pod-...

https://kubernetes.io/docs/concepts/configuration/manage-res...

https://kubernetes.io/docs/concepts/workloads/pods/pod-qos/#... (New feature)

So normally if you overcommit it might be undefined behavior if you not have enough memory. However if everything is fine pods can preempt based on prio to new nodes.

With the right settings only the faulty app might fail. Without it it can be a real pain to find the rouges

Some collectors editions do come without a game cd nowadays.

there isn't a market for gamers buying games on DVDs these days. BlueRay the same.

Of course there are voice that do want real disks but sadly that time is over. Digital sales won.

It‘s also cheaper than the murican ones from Google, Amazon, …. And tesseract was an example. Heck you can go xberg and use paddleocr. Most often layout is less of a problem for ocr. Most often you need high accuracy, which tools like these are often worse in the 95 percentile.

Tbf even with tesseract you already get shit ton of accuracy and you can probably do these 1000 pages for way less than 3.5€. For 3.5€ you can spin up a cloud instance with 8vCPU+32gb on gcloud for 11 hours (or 11 instances for an hour) which can do way more than 1000 pages per hour on tesseract. It takes you around 6 second per page +-4 seconds start/stop depending on what you are doing on that instance size without too much optimization (you can probably even run multiple processes on a single node)

Google documentai costs 1.5$ per 1000 which is probably better in quality and speed.

1000 Pages / 3.5€ this is expensive as hell. If this is not fastly superior than something like tesseract it is not worth it.

A little late reply:

Preferably I do not use a client on my machine to publish a package. That’s what I meant, modern registries should always support working with oidc providers to support publishing credentials from ci/cd systems. Sometimes called trusted publishing: https://repos.openssf.org/trusted-publishers-for-all-package...

It’s done via uprobes which allows ebpf to attach to users processes or libraries, basically like ld_preload but built into the kernel. First link that explains it https://blog.quarkslab.com/defeating-ebpf-uprobe-monitoring.... but there are many more links about it and it is a pretty useful tool for debugging in prod environments. (Also first link: https://blog.px.dev/ebpf-function-tracing/) this also the intended use case. px.dev is btw a cncf project which also helps for ebpf debugging in k8s (comes from new relic)