Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
cplli
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
cplli
1y ago
What the top commenter probably failed to mention, and jensneuse tried to explain is that sync.Pool makes an assumption that the size cost of pooled items are similar. If you are pooling buffers (eg: []byte) or any other type with backing m
2.
▲
by
cplli
2y ago
Yes, when using Alpine in a container context you're getting the "MINI ROOT FILESYSTEM" [1] experience; the parity differences are in the kernel (they're easily ""fixable"" and the team is open to ena
3.
▲
by
cplli
2y ago
Alpine is a solid distro for servers from my experience. The only bad experiences I've had with it, come from the lack of parity between the x86_64 and aarch64 virt images. So our x86_64 setup doesn't work without building our ow
4.
▲
by
cplli
3y ago
Don’t forget to update your regex appropriately (/s hopefully)
5.
▲
by
cplli
3y ago
First thing that comes to mind is an overhaul mod for OpenTTD which has a "Steeltown" economy that resembles the AIST Steel Wheel. https://grf.farm/firs/4.15.1/html/economies.html#steeltown
6.
▲
by
cplli
3y ago
Threads are Phase 3 https://github.com/WebAssembly/proposals You can also check out: https://webassembly.org/roadmap/ And for Go, the proposal project on Github has many interesting conversations
7.
▲
by
cplli
3y ago
Personally tried it, it can handle logs nicely. And from their page, many more things https://clickhouse.com/use-cases
8.
▲
by
cplli
3y ago
Now we need a tool called NeighbourhoodWatch to monitor the cluster monitors.
9.
▲
by
cplli
3y ago
Currently migrating from it (not writing any new files to it), but keeping it for read/shared files. The migration plan is to eventually move everything to a DS923 (Synology), with most files being mirrored on client machines and weekl
10.
▲
by
cplli
3y ago
I cannot possibly trust Nextcloud again. I was very skeptical to begin with, because it's a rather large and complex project built on PHP over many years (call this a personal/subjective view). But what really made my decision wa
11.
▲
by
cplli
3y ago
Someone will definitely get 42.zip or 42kb.zip just to host a “zip bomb as a service”. On a more serious note, new gTLDs are so spammy, and “.zip” as others have mentioned will surely lead to some surprises somewhere.
12.
▲
by
cplli
3y ago
For caching the query results you get from your database. Also it's easier to spin up Redis and replicate it closer to your user than doing that with your main database. From my experience anyway.
13.
▲
by
cplli
4y ago
An article on a site that has a cookie banner the size of my mobile screen :)
14.
▲
Ask HN: Has anyone self/on-prem hosted a container registry
2 points
by
cplli
4y ago
|
1 comments
15.
▲
by
cplli
4y ago
I also only have Caddy running locally to proxy different dev environments and serve certain files, and it is an exceptional tool, but I would never deploy it in production: 1) Nginx configs are (from my experience) easier to template (in o
16.
▲
by
cplli
4y ago
Ok, I'll have to look more in-depth into the Microsoft link, they link to many more pages including a whitepaper. Regarding all the blockchain centric DID methods, would someone wanting to validate a DID (eg: did:thecoin:whatever_would
17.
▲
by
cplli
4y ago
> lined up the tech in their products Link? Or an explanation as to what this means? > before it becomes available in a shop nearby Meaning what exactly? If you're saying Microsoft will implement DIDs, my question is, "Which
18.
▲
by
cplli
4y ago
I was initially pretty hyped when I read the abstract for DIDs, bookmarked the spec and read it later. The "spec" is a bunch of buzzwords and vague generic "concepts". The DIDs themselves mean basically nothing, it'
19.
▲
by
cplli
4y ago
IANAL, but shouldn't a data deletion request also apply to the data inside backups, even when no recovery is planned? Edit: I am also skeptical about the logs part, I don't think logs can be a magical excuse to log everything that
20.
▲
by
cplli
4y ago
https://theuselessweb.com/
21.
▲
by
cplli
4y ago
I wouldn't throw Jetbrains in the same boat. I quite like their pricing model. You get to keep the last version, so you're basically paying for updates in the end (which are worth it IMO). On top of that, you get a discount after
22.
▲
by
cplli
4y ago
Considering some of the people on there, the HN title could be "famous & infamous", or as the project puts it on the page, "Notable". Still, very awesome project!
23.
▲
by
cplli
4y ago
Thank you so much for this news! I have completely missed it. I've been scaling with terraform for so long, I didn't login to the dashboard to see the news pop-up. This is great, not only can you drop IPv4, you can also drop both
24.
▲
by
cplli
4y ago
Car colours is something that sometimes worries me, brighter colours are sold as 'extra', while greys are default/cheaper. This leads to some cars basically camouflaging with the road, especially at times like dawn or dusk. T
25.
▲
by
cplli
4y ago
Link to core specification: https://www.w3.org/TR/did-core/ And a link to the recent discussion on HN: Mozilla and Google Objections Overruled on “Decentralized Identifiers” by W3C https://news.ycombina
26.
▲
Decentralized Identifiers (DIDs) v1.0 Becomes a W3C Recommendation
(w3.org)
3 points
by
cplli
4y ago
|
1 comments
27.
▲
by
cplli
5y ago
I guess the workspaces[1] get overshadowed by Fuzzing and Generics. But I find em pretty useful. [1]: https://go.googlesource.com/proposal/+/master/design/45713-w...
28.
▲
by
cplli
5y ago
Actually used them for a short while. I didn't like the additional step in my pipeline to build the docs, also they don't/didn't offer an interactive option. Other than that it looked pretty nice.
29.
▲
by
cplli
5y ago
I write the OpenAPI spec by hand as I haven’t found any tool to match my needs (nor is the API changing too often). And for the frontend to display the docs I couldn’t be any happier with https://stoplight.io/ (using their
30.
▲
by
cplli
5y ago
Another thing to consider (at least something that I sometimes do myself) is that some people may open a story to read for later (or even at the time) but never come back to upvote the post or engage in conversation.
More ›