And here I am pooping out simple typescript... These articles always make me feel like I'm wasting my talents working on products that don't really have the need to leverage any understanding of what's happening under the hood at the CPU instructions level.
Maybe I'm too stupid to understand the article... How does this achieve performant querying for olap and oltp purposes?
Based on my understanding, olap queries will go to the parquet files which are stored in a columnar fashion and oltp style queries will go to a caching layer that sits on top of those parquet files?
What's the special sauce here? Seems like they're just caching the data which, for all intents and purposes, seems like the same solution of storing another copy of the data which is what they say they're avoiding.
one of the benefits of being on android and being able to sideload apps. Look up "revanced youtube" and you'll be able to turn off shorts.
ublock origin for blocking them on desktop. If you're on an iphone... uninstall youtube?
my quality of life has increased substantially... although sometimes the app bugs out and shorts still make it on my home page. I spend like 10 minutes scrolling through shorts and get a weird shock "how the fuck did I end up here?", restart the app and boom shorts gone again.
https://www.climbcation.com/ a site to help you come up with good climbing trip ideas where you filter based on climbing type, time of year, location, and your climbing abilities.
Does my wife also get this so she can be on the other side? Nevermind... I don't need the sad reality of her trying to swipe left and telling me she thinks the app is broken.
how do you and others get past all the permissions that onesec needs? They say everything remains on device; however, it's a closed source application so there's not really any way to confirm that besides looking at the packets that are going out of your phone.
this seems like an interesting idea I'd like to try but all the permissions it needs is terrifying to me... I understand why it needs them but there's no way for me to verify that they aren't doing anything funny with that access.
i'd disagree heavily with that... let's say you have an expense of an insurance policy that covers you for the next 10 years. You're paying for 10 years of service, that should be amortized over 10 years.
The lossy timeline solution basically means you skip updating the feed for some people who are above the number of reasonable followers. I get that
Seeing them get 96% improvements is insane, does that mean they have a ton of users following an unreasonable number of people or do they just have a very low number for reasonable followers. I doubt it's the latter since that would mean a lot of people would be missing updates.
How is it possible to get such massive improvements when you're only skipping a presumably small % of people per new post?
EDIT: nvm, I rethought about it, the issue is that a single user with millions of follows will constantly be written to which will slow down the fanout service when a celebrity makes a post since you're going through many db pages.
casualties refers to injuries as well as deaths. I think the citation they were looking for was for the ~2800 number. I don't think it's reasonable to say that 6/12 killed were civilians, so half of all casualties were civilian.
We dont know until we get more reports, like you said, it could be higher... but it could also be lower.
as a lowly application developer who is interested in how llms actually work, where's a good place to start? is there an article or book that most folks would recommend?
gyms are typically softer to give their clientele a feeling of progress. this makes people feel better and want to come back. if you're stuck at v3 for several months you'd be more likely to give up telling yourself you're not cut out for climbing... at least that's my(and many others') theory behind soft gyms