I’m definitely looking forward to Unpack[…]. This makes kwargs typing manageable for the first time.
The rest is nice too, but no game changers.
I’m definitely looking forward to Unpack[…]. This makes kwargs typing manageable for the first time.
The rest is nice too, but no game changers.
New money laundering scheme?
Just rewatched “The Visitor”. Can’t believe I forgot about that one. I’m definitely not crying right now, no no. Thank you.
How much power does this thing draw?
They don’t want you to see the “if benchmark_xyz { do less work }” blocks of code.
The way I perceive PRQL is somewhat like SQLAlchemy-Core (the SQL expression layer, not the ORM). Almost a 1:1 mapping to SQL but softening the rough edges in SQL when constructing more complex queries dynamically, in particular: no function calls, no real variables, only string concatenation. While SQLAlchemy-Core lets you even extract sub-queries into variables, I don’t know about how powerful PRQL is in this regard.
From what I see from the docs I’m rather hopeful though.
The one argument that even flies understand:
Switch light on outside of my room. -> Get out!
Sir, your washing machine will arrive on Wednesday. Be sure to be at home at around 3.
Can the ozone be countered by a reverse polarity static charge? Not sure how the laser printer do it, but recent printers barely emit ozone. I think it should be possible.
Can the ozone be countered by a reverse polarity static charge? Not sure how the laser printer do it, but recent printers barely emit ozone. I think it should be possible.
That would invalidate their position as “we’re just a platform and not liable for the things our users post”. They’d have to take responsibility then and I’m not sure they’ve got the resources for that.
That’s true. I posted more here in the last 2 months than on the other site in years.
Don’t anthropomorphize social networks, they hate that.
In order to compete in user experience we need to up our game. We need to set up communities which collect, categorize and funnel user requests upstream. These features should be focused on:
This is meant to be a proxy between average users and tech enthusiasts who know how to do pull requests or open GitHub issues. Moderators of these communities would do it for them. This would enable us to gain visibility in the needs of the users.
This is only a part of what needs to be done, but I think this can be done quickly.
🖕=👍
Honestly, there isn’t much else we can do. Spread the word that there are better alternatives to Threads and don’t let them join us. If you prevent “If you can’t beat them, join them.” then that’s a step in the right direction (survival of the network).
The audience is not the problem. Meta’s mere presence on the network will be. We are now at a critical point in the struggle to survive as a network, and it’s not looking good.
If we continue like today, the network effect (Google it) would eventually lead to ActivityPub being the de facto too-big-to-fail standard in all of the web. We aren’t there yet, though. Meta knows this too and doesn’t want it to happen, because extracting value from a diverse network is way harder than from a centralized user base. The fact that they even want to federate in the first place (shouldn’t be in their interest!) rings alarm bells.
Burn me once, shame on you. Burn me twice, shame on me. Big corporations want mainly one thing: gobble up as much value exclusively to themselves. They will take whatever means necessary to get there. The strategies to privatize public resources (XMPP, ActivityPub, etc.) are known. They look great for the public on the outside, but over the years will erode the value for everybody BUT them. In order to not let it get as far, many (including me) are of the conviction to not even give them a finger, let alone the whole hand.
The trick is to assign someone the responsibility of the upgrade and give them the authority to tell the other developers how their newly added code shall look like. This will get you there eventually.
Seen it work on a >1 million SLOC project.