dlisboa

8 ms·

91.
by dlisboa 11mo ago
> Go programmer attitude is "do what I said, and trust that I read the library docs before I said it". I agree and think Go gets unjustly blamed for some things: most of the foot guns people say Go has are clearly laid out in t
92.
by dlisboa 11mo ago
Which can also be said about Rust and anyhow/thiserror. You won't see any decent project that don't use them, the language requires additional tooling for errors as well.
93.
by dlisboa 11mo ago
Yeah, they were down last week too. It's hard to run an open git forge on a small volunteer team, the workload is read and write heavy with endless "customers" (or bots).
94.
by dlisboa 11mo ago
https://status.codeberg.eu/status/codeberg Their reliability is not great unfortunately. Currently their 24h uptime is 89% for the main site. They are partially degraded right now. The 14 day uptime is 98% but I think
95.
by dlisboa 11mo ago
It was special. CSP wasn't anywhere near the common vocabulary back in 2009. Channels provide a different way of handling synchronization. Everything is "just another thing" if you ignore the advantage of abstraction.
96.
by dlisboa 11mo ago
It's ironic that https://substack.com/@davebarry uses a lot of AI-generated imagery. Maybe the death of vision is not exaggerated. I don't judge, I'm not an artist so if I wanted to express myself in image I&
97.
by dlisboa 11mo ago
I've used both and I don't know if they've been improved but both were terrible a few years ago (at least in our case). Very unstable and finicky. I last used Jenkins in 2017 and Gitlab in 2021, so I don't know how they
98.
by dlisboa 11mo ago
> In the not so distant past of the 1930s there were political parties advocating for the mass killing of people with disabilities Those parties still exist today. - https://www.reuters.com/business/media-telecom&#x2
99.
by dlisboa 11mo ago
> The road out of “developing country” took forever but now I see them producing great products in basically every industry. Did it? We're talking 1949 up to a few years ago. 70 odd years from mass starvation to having their own spa
100.
by dlisboa 11mo ago
> A 6GB RAM server that the end consumer purchases has 2GB of RAM running on AWS, 2GB on Azure and 2GB on GCP. That'd be very inefficient usage of compute. Memory access now has network latency, cache locality doesn't exist, pr
101.
by dlisboa 11mo ago
You make an assumption here that the software is also constant or static. > There's a constant low-level flow of "we switched from X to Y and got Z% speedup" articles on HN, and while the details of the articles are often
102.
by dlisboa 11mo ago
> If there is a slight positive note to all this, then it is that these outages are so large that customers usually seem to be quite understanding. Which only shows that chasing five 9s is worthless for almost all web products. The idea
103.
by dlisboa 11mo ago
> Most people, most of the time, doing most web work, are so thoroughly outclassed on speed by their web framework and server that the speed of their choice is irrelevant. Which means they should be selecting based on all the other relev
104.
by dlisboa 11mo ago
I know it's intentional but very amusing name considering the country of origin.
105.
by dlisboa 11mo ago
Inconvenient for those people. About 8 billion other people don’t live in that type of weather.
106.
by dlisboa 11mo ago
It just isn't. There's nothing stopping other languages from being that easy but very few even try. Go sees itself more as a total dev environment than just a language. There's integrated build tooling, package management, to
107.
by dlisboa 11mo ago
That's where we're at a marked disagreement. "It's just a way to get paid" reduces every human knowledge to a monetary transaction, so the value of any type of learning is only worth what is being paid for. Thankful
108.
by dlisboa 11mo ago
You like having the painting, you just don't like to paint. You can think of a painting and have it appear before you. That's OK, but surely you can see how painters wouldn't enjoy that in the slightest.
109.
by dlisboa 11mo ago
Once in the Netherlands I saw the simplest solution to pigeons: they stretched a fishing line an inch or two over the balcony railing, so when pigeons would try to land they’d land on the fishing line and be off balance, flying away to a mo
110.
by dlisboa 11mo ago
Just want to reiterate what the sibling commenter said, it's dead on with my experience. Static typing would be the main thing teams would've been better off with. I was big on dynamic languages, love Clojure/LISPs and still
111.
by dlisboa 11mo ago
Local first is really relevant if you have the potential of users losing connectivity or is building some sort of collaborative workflow and want updates to happen automatically (like Linear or Google Docs). Latency is not a real issue with
112.
by dlisboa 11mo ago
Yes, every web app I’ve worked on the past ~18 years has been with Rails. I’ve seen it all except an efficient app. Sure, Ruby and Rails never bankrupted these companies but they’d all have been better off with something else. Certain cloud
113.
by dlisboa 11mo ago
> The usual response to this complaint in the Ruby/Rails community is that optimizing for nanoseconds, or even milliseconds doesn't matter when the same operation also involves multiple database queries or API calls The problem
114.
by dlisboa 11mo ago
Go gets a lot of flack for getting some things wrong but it was a stable and productive language within a couple of years. If you look at the current Zig website the hello world example doesn’t compile because they changed the IO interface.
115.
by dlisboa 11mo ago
When I say Ruby is inefficient it’s not just the language, it’s stuff like this. I don’t fault the author but this kind of stuff is endemic. This way of handling attributes is monumentally less efficient than just using keyword attributes,
116.
by dlisboa 11mo ago
I somewhat agree. In general most apps are small where the language choice doesn’t really matter. Caching is also vastly underutilized, most apps are read-heavy and could serve a significant portion of their requests from some form of cachi
117.
by dlisboa 11mo ago
Most times it's better to just accept the dynamic nature of the language rather than do this kind of runtime type checking. You'd have to do this `.is_a?` dance for every type to have it be reliable. Even if you implement an &quot
118.
by dlisboa 11mo ago
Ruby is very slow so you gotta squeeze everything you can everywhere. Even a seemingly simple method will have to be scrutinized so that overall performance isn't impacted. It's death by a thousand cuts. See the commit that made i
119.
by dlisboa 11mo ago
Ruby is a dynamic language, `version_string` can be anything. The author uses `to_s` to coerce it into a string. There are problems with that: if I pass in an array it'll coerce into `"[1,2,3]".split(".").map(&:
120.
by dlisboa 11mo ago
Ruby trades away quite a few things for readability. It's beautiful but a lot is being hidden. Some of those languages would have you deal with the problem of allocating multiple arrays in the heap just to compare three numbers. Or giv

More ›