Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
izietto
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
91.
▲
by
izietto
4y ago
Congratulations! I'll shyly say "Why not SourceHut?" the next time the GitHub vs GitLab vs BitBucket subject comes up in my team!
92.
▲
by
izietto
4y ago
> Because web browsers are supposed to render HTML, not markdown. Well, they render HTML, XML, XSLT, plain text, images, videos, even PDF nowadays
93.
▲
by
izietto
4y ago
Because many HN readers are developers, and developers deal with characters all the time
94.
▲
by
izietto
4y ago
Never heard about RUM extension, I'll give it a look. Thanks!
95.
▲
by
izietto
4y ago
You're right, that's actually what we implemented, application-level hooks, but they needed development and maintenance effort that come for free with the adapter we're using for OpenSearch integration, which also comes with
96.
▲
by
izietto
4y ago
We migrated FTS to OpenSearch from PostgreSQL a couple of months ago. Here the main issues we had with PostgreSQL FTS: - cross-tables FTS requires at least materialized views, which lock data for writing at refresh. This was too much worryi
97.
▲
by
izietto
4y ago
Yes, but to be fair it's awfully hard to find a free app that does the same without bloat due to any kind of ads. I'm going to buy this app just because of frustration due to that.
98.
▲
by
izietto
4y ago
It works now, good job ;)
99.
▲
by
izietto
4y ago
> What does it mean to put a scheme in a cname? It means that https:// shouldn't be mentioned in the DSN records > How can I solve the problem? You should edit your DNS records and remove it
100.
▲
by
izietto
4y ago
TBF I have been playing to Dota for seven years, and I've never spent 1 cent for it.
101.
▲
by
izietto
4y ago
> What makes a good REPL? 1. copy-paste of code with spaces must work 2. decent history handling (arrows to go up and down, Ctrl+R to search, it could be better with a fish-shell-like history handling) 3. syntax highlighting of returned
102.
▲
by
izietto
4y ago
> I get paid the same if it takes me 4 hours or 8 hours to complete my work. I'll take 4 hours and spend the rest of the day doing what I want This. working remotely you have the HUGE advantage of being able to work enough and spend
103.
▲
by
izietto
4y ago
It reminds me the lyrics of this song: https://www.musixmatch.com/lyrics/Radiohead/Fitter-Happier
104.
▲
by
izietto
4y ago
You can't imagine how much I long for phpBB forums, now that we are in the "golden" age of the FAANG web. Only users content, no ads masked by "smart AI suggests this content just for you", no 5 seconds long interac
105.
▲
by
izietto
4y ago
Nono, I agree with you, I think I was wrong above, as I wrote above it was probably just a psychological bug. But I still think there's much room of improvement with the tools we already have.
106.
▲
by
izietto
4y ago
Yes, but are they as fastest as possible? Take Ruby. One of the most common improvements you do as Rails developer to a Rails web app is adding `oj` gem, which replaces the default JSON ser/deser with a more performant one. But it does
107.
▲
by
izietto
4y ago
I guess that, since JSON is Javascript Object Notation, it should be faster for Javascript to serialize/deserialize it, but it might be just a psychological bug of mine. Anyway, my main point wants to be the fact that JSON serializatio
108.
▲
by
izietto
4y ago
I think that one underrated point about web apps performance is JSON serialization for non-JS languages. JavaScript is obviously fast with that, but non-JS languages exposing API, like Rails in a separated FE/BE architecture, spend muc
109.
▲
by
izietto
4y ago
Aren't there no-vax in US?
110.
▲
by
izietto
4y ago
bundle show gem-name bundle open gem-name Fix the last one
111.
▲
by
izietto
4y ago
> And the latest commit is "shifted all indentation per linter" by someone who didn't write the code IME it's not like that at all, commits like "shifted all indentation per linter" are not so common. It
112.
▲
by
izietto
4y ago
Im my previous company we used to write them and used to read them, and used to get frustrated when some old commit didn't have enough description. In this company noone cares and we even have squash & merge mode with description t
113.
▲
by
izietto
4y ago
> Why (comments) That's what we do in my current company, but I vastly preferred what we used to do in my previous company, which was: > Why (commit description) which prevents comments obsolescence and code dirt
114.
▲
by
izietto
4y ago
This one should have been the link. Thanks!
115.
▲
by
izietto
4y ago
It is as soon as you forget about that-but, speaking of myself, it is not because I'm aware of the fact that I'm using it
116.
▲
by
izietto
4y ago
You're right!! My father was a bersagliere, I remember he had that hat!
117.
▲
by
izietto
4y ago
I love it, can I bring one in Italy? EDIT Actually I discovered that it is a "gallo cedrone", it's fairly common here in Italy too, no need to import it from Scotland
118.
▲
by
izietto
5y ago
Flops have been released too (Copilot I'm looking at you)
119.
▲
by
izietto
5y ago
If I should point to something that isn't very good is the placeholder test, but the code is ok to me.
120.
▲
by
izietto
5y ago
I count 213 JS + 41 CSS = 254 lines
More ›