ragall

11 ms·

301.
by ragall 8mo ago
It is correct. Just because your livelihood might hinge on a specific project doesn't mean that its developers have any obligation to accept your patches. It means you have to be very careful in choosing which project you hitch your wa
302.
by ragall 8mo ago
> Quick questions; as this project clearly exists in a community-less vacuum It clearly does not, however the members of the community need to know their place.
303.
by ragall 8mo ago
> If you use open source software, you are expected to contribute. No, not in a million years.
304.
by ragall 8mo ago
> It is sane but not rational, sometimes factually correct in places, highly offensive, and inflammatory. Calling this offensive and inflammatory can only come from someone who is extremely conflict-avoidant. For my Italian sensibilities
305.
by ragall 8mo ago
The only thing I get from your reply is that I'm sorry HN doesn't allow blocking users.
306.
by ragall 8mo ago
Postel's law was a precept of the Internet of the 80's and 90's, when due to the primitive software engineering practices at that time, implementations couldn't be tested properly. That lead to many cases of poor interop
307.
by ragall 8mo ago
There's a very good reason: we need the users to be aware of this, and exert self-restraint in communications with the developer team otherwise public fora become untenable and the core team, to avoid being pestered, will be forced to
308.
by ragall 8mo ago
> It's highly offensive and inflammatory. It is sane and factually correct. > Plenty of open source projects consider themselves a community which welcome newcomers, take governance seriously Rich is taking governance very seriou
309.
by ragall 8mo ago
> Then make it private You don't get to decide that. > It's a reckless disregard of other people's time and nerves. Build labyrinths and scatter them around the internet. Leave manholes uncovered. That's a *you* pr
310.
by ragall 8mo ago
Dissatisfaction n. 3 is the essence of the problem: "Because Clojure is a language and other people's jobs and lives depend on it, the project no longer feels like someone's personal project which invites a more democratic co
311.
by ragall 8mo ago
The RFC says a SHOULD is to be treated like a MUST, but well-justified exceptions are allowed.
312.
by ragall 8mo ago
The RFC says a SHOULD is to be treated like a MUST, but well-justified exceptions are allowed.
313.
by ragall 8mo ago
I subjectively did based on my experience.
314.
by ragall 8mo ago
Perhaps, but why should one do it when it's a bad model ? Jury because it's possible ?
315.
by ragall 8mo ago
> What they should have done is adopt Heroku as their internal Platform-as-a-Service From what I saw, Heroku was unsuitable for a serious large company. Deploy-on-push is a nice UX for a small company, but once you need something more st
316.
by ragall 8mo ago
> for example, the engineer may be deciding whether to use a linked list or binary tree and the LLM is implementing it with the available code stack approved by the company At this point it's a slightly more sophisticated version of
317.
by ragall 8mo ago
Sure, that's why I think that it will mostly be SaaS businesses doing the DSLs, because the business contracts allow for more accountability than having employees do poor reviews, accumulating tech debt, that will only become visible
318.
by ragall 8mo ago
> I agree. Additionally, a company can own and update a business language of their own design at their own pace and need. Yes, although I was more thinking of this being in most cases a SaaS offering because the implementation of the DSL
319.
by ragall 8mo ago
> Now you could say a piece of software completely written by a coding agent is just another abstraction You're almost there. The current code-generating LLMs will be a dead end because it takes more time to thoroughly review a piec
320.
by ragall 8mo ago
Isn't that how things should be ?
321.
by ragall 8mo ago
My take from all this is that OCI, being essentially a .tar.gz, is a bad image format. A smarter solution would either use a seekable archive format like zip, or profile the container startup to make a list of essential files, and put those
322.
by ragall 8mo ago
In what way is Fly's pricing unpredictable ?
323.
by ragall 8mo ago
It also depends on your legal system and how much discretion it allows managers. Let me give you an example: my startup used to allow people to expense a car rental when travelling to HQ in the Bay Area, which was in general cheaper than Ub
324.
by ragall 8mo ago
> There are many places where you have to talk to a vendor with no list price Which many places ?
325.
by ragall 8mo ago
It already is like that, but not because of the cloud. Those of us who begun with computers in the era of the command line were forced to learn the internals of operating systems, and many ended up turning this hobby into a job. Youngsters
326.
by ragall 8mo ago
Cloud was never cheaper. It was as convenient.
327.
by ragall 8mo ago
Distributed systems can partly fail in many subtly different ways, and you almost never notice it because there are people on-call taking care of them.
328.
by ragall 8mo ago
In a way. It means that you can get new capacity most often, but the transition windows where a service gets resized (or mutated in general) has to be minimised and carefully controlled by ops.
329.
by ragall 8mo ago
I do agree that Azure seems to be a lot worse: its control plane(s) seems to be much more centralized than the other two.
330.
by ragall 8mo ago
All 3 hyperscalers have vulnerabilities in their control planes: they're either single point of failure like AWS with us-east-1, or global meaning that a faulty release can take it down entirely; and take AZ resilience to mean that exi

More ›