qaz

joined 3 years ago
MODERATOR OF
[–] qaz@lemmy.world 2 points 4 hours ago

S&P 500 (Standard and Poor's 500) is a stock market index tracking the stock performance of 500 leading companies listed on stock exchanges in the United States. It is one of the most commonly followed equity indices and includes approximately 80% of the total market capitalization of U.S. public companies, with an aggregate market cap of more than $61.1 trillion as of December 31, 2025.

Wikipedia

[–] qaz@lemmy.world 4 points 1 day ago* (last edited 1 day ago)

Go seems like a good option to begin with; you can do a lot with it, and it's not that complicated but does expose you to concepts like pointers.

There are plenty of very "serious" systems written in Go (e.g. Kubernetes), it's not a toy language.

[–] qaz@lemmy.world 58 points 2 days ago (2 children)

Everyone could've seen it coming from mile away

[–] qaz@lemmy.world 3 points 4 days ago

I have a weighted blanket but the problem is that it's too warm

[–] qaz@lemmy.world 3 points 4 days ago

Some time ago I saw a video of a Pigeon trying to impress a Falcon, perhaps this could be the reason

 
[–] qaz@lemmy.world 4 points 1 week ago* (last edited 1 week ago) (1 children)

It's been a while, but I think it's based on a trick to add comments to Markdown. I tried it with Tesseract, and none of the lines rendered, but only if I add an empty line in front.

It's a bit of a hack, but it can use existing endpoints and only needs some minor changes on the client side. The alternative would be implementing support for it in Lemmy, Mbin, PieFed, etc. but that probably takes a while and can also be done later when it has proven its usefulness.

Edit: I think I found the explanation behind the syntax https://stackoverflow.com/questions/4823468/comments-in-markdown

[–] qaz@lemmy.world 3 points 1 week ago

I'm not looking forward to finding out my PR has ended up in the spam folder 😔

[–] qaz@lemmy.world 5 points 1 week ago

It was an image from this GitHub issue, but it seems GitHub now adds a JWT to image links that expires?

[–] qaz@lemmy.world 5 points 1 week ago

I really doubt he would have used AI for writing the policy against it after listening to him, but regardless. I do agree with you that it won't go away, and we'll have to find appropriate solutions to deal with it.

[–] qaz@lemmy.world 14 points 1 week ago (3 children)

I know, I opened an issue on Voyager's GitHub last year to suggest changes

[–] qaz@lemmy.world 15 points 1 week ago* (last edited 1 week ago)

Some communities don't have specific rules, and some have several. It can be quite hard to judge why something is breaking rules. On the video's community for example people often report videos, so I have to go through the entire thing to figure out what's wrong with it (and some people post videos that are more than an hour). Sometimes content is reported because of something the people who created it did, something that is not apparent when watching the video.

[–] qaz@lemmy.world 15 points 1 week ago (3 children)

I don't. It shows that projects are getting flooded by low quality AI submissions to the point where they feel they need to ban it despite the difficulty of enforcing it.

I worry that at some point many online spaces will deteriorate because real interactions and content are drowned out by AI.

 

Context: Voyager shows these options which results in a large amount of reports just being "Breaks community rules" with no info or reason whatsoever.

2
submitted 1 week ago* (last edited 1 week ago) by qaz@lemmy.world to c/database@lemmy.ml
 

An interesting point for me was that they acknowledged the flaws in their previous benchmarks.

We owe a word on durability. The previous round of benchmark results ran with fsync disabled for every engine - leaving each database's writes in the OS page cache rather than flushed to disk. Every database in the comparison ran with the same setting, so nothing was being "fudged" relative to the other engines, but we didn't make the setting explicit, and the headline numbers ended up describing a workload that most production deployments would not likely run.This round is different. Every database in these benchmarks runs with full disk durability enabled - fsync on, WAL flushed on every commit, no buffered writes hiding behind the page cache. The configuration files for each engine are checked into the  so anyone can audit them. The numbers above are what each engine sustains when every committed transaction is on disk before the client gets an acknowledgement. That's slower than the cache-friendly numbers you'll find in some marketing posts, ours included, but it's the only honest way to compare databases that are going to outlive a power outage.

 

NOS

 
 

Credit goes to u/Mylenn

 

cross-posted from: https://lemmy.world/post/47074737

Spotted in the wild:

Paper from JABDE:

Credit goes to u/TobyWasBestSpiderMan for the original post

https://jabde.com/

view more: next ›