louiskottmann

You do realize "Claude" actually wrote CSS for you and thus you need that language to strive ?

Such an uninsightful comment.

Best leveraged debt on the US economy ever.

Taste only matter insofar you work is shared.

AI lets people get personalized software for "free" as derivative of existing work. Think adobe suite but with the 5% that an individual needs.

Then taste loses value as everyone has their own software.

That's where I am in that train of thought at least. Pretty grim I know.

And I think it's naïve to believe only the US can make the hardware and has the brainpower to develop this technology.

Who's right ?

CachyOs with Niri and DankMaterialShell is what finally broke out of Ubuntu with Gnome.

It's slick, modern, efficient, and up to date.

I encourage trying that or similar.

Given they ingested basically the whole internet and then some, you cannot possibly be serious when you mean it's worth less than 10 billions.

The totality of the content on internet is worth several orders of magnitude more.

Isn't it perfectly reasonable to require an account for any use, and to ensure that making one has a high level difficulty anubis challenge or delay ?

Claude really doesn't have that much market share. It's the most expensive by a mile but when you count token market share they're in the low %.

And everyone else is close enough in terms of quality, their tiny advantage if any is insufficient. Let's not even talk speed.

OpenAI is competing with chinese models.

Thoughtfully and coherently factorized, abiding a set of architectural rules (i.e: we compose "this" way here, re-evaluated as we go) and following up-to-date framework conventions. LLMs are terrible at this.

Chosing OOP or FP is irrelevant, fundamentals matter more

Docker-compose setup (nothing fancy) on a dedicated server.

Usage is work, family and personal notes.

Acknowledged yes, adressed no.

Using dendrite at the time was a bet on the future : "use it now and you won't have to migrate".

You can also migrate by replicating messages, or mirroring new messages via a bridge.

In my opinion they tried nothing and they're all out of options.

AFAIR there is a doc about migration from synapse, that they promised to automate once dendrite would be production ready, which it never became.

Remark half-way in the rant they are using dendrite, an experimental matrix server implementation that has been abandonned. Thus ranting about it is cheeky at best.

I have been using synapse for years with little issue.

And you immediately lose the ability to do `crontab -l` on any server to know its scheduled tasks.

Now you get to look around the myriad of places where you can put systemd files, and figure out which ones are base services and which ones are custom, with no general convention to go about it. Nope.

History repeats itself : it ends in blood. Always does.

As the concentration of power happens, the people who concentrate it become bigger and bigger targets.

There is no alternative to wealth distribution.

This is borderline adversarial propaganda.

While the incident did happen, a lot of actions were taken and most of the data was recovered. OVH now also keeps backups even for clients that don't pay for it.

I was hit by that datacenter catastrophe and got my data back almost immediately, in a new VM.

I've been using them for years with little issue (no more than happened on my AWS or Azure accounts, I would say less because it's less of a mess in general).

Stop spreading false rumors.

That's my take as well, I find fixing poor/overengineered LLM code taxing.

The linked article does not speak of tests, it speaks of a team that failed to properly review an LLM refactor then proceeds to blame the tooling.

LLMs are good at writing tests in my experience.

The trick is in the mud between what's yours and what's theirs. The induced doubt is lucrative.

I find the thought daunting but the reality surprisingly easy.

You just keep up as you go, as long as you keep things close to the framework it's fine.

I've been a Rails DevOps and nowadays a web one-man-show with it for over 10 years and I'd do it again.

Not many frameworks have been thriving that long, and there's good reason.

It packs everything, is tidy and productive, with a pleasant language to read and write.

In the latest Stackoverflow survey, it's back at the "top 5 of desired stacks to use for next project" over a decade after its inception !

Give it a try.

You could get rich by solving ARC 2 tasks yourself instead of forwarding the work to an LLM, given a client willing to pay LLM rate.

People will find a way to not need as much RAM, and thus the devices that require it.

Same way the price of groceries going up means people buy only what they need and ditch the superfluous.

First of all, ruby-lsp does a great job at this, and the recent Herb helps with frontend templates.

This is enough to navigate between controllers, models and libs, unless you're trying hard to be clever which you shouldn't.

Then, in Rails, things have a canonical place in the codebase, that is consistent between codebases.

This is in contrast to languages and frameworks where every codebase is setup differently, but the static typing helps find code wherever it's hidden without pain, and thus without need for cleanup and thoughtful design.

To each their own, I prefer power for me, and pain for whoever drifts from the convention.

This is so obviously right.

I may add that investors are mostly US-centric, and so will the bubble-bursting chaos that ensues.

That's indeed a good example of prior full trusting of the browser by the server.

I appreciate that, but in the case of TLS or CSRF tokens the server is not blindly trusting the browser in the way Sec-Fetch-Site makes it.

This is a massive change for cache in webapp templates as it makes their rendering more stable and thus more cacheable.

A key component here is that we are trusting the user's browser to not be tampered with, as it is the browser that sets the Sec-Fetch-Site header and guarantees it has not been tampered with.

I wonder if that's a new thing ? Do we already rely on browsers being correct in their implementation for something equally fundamental ?

This is my take as well. I've never come accross a JS project where the built-in datastructures were exclusively used.

One package for lists, one for sorting, and down the rabbit hole you go.

As history showed us numerous times, it doesn't even have to be the best to win. It rarely is, really. See the most pervasive programming languages for that.