adkadskhj

Google has provided a platform that for years benefited off of extremists and only recently started taking action against it.

It provided multiple platforms that, like Facebook, optimized user clicks in ways that ended up causing significant harm. Radicalizing extremists and pushing racism, homophobia, misinformation, etc.

One may be objectively worse than the other, but lets not pretend that Google conveniently forgot "Do no evil" until it was notified of it's own actions by the public. Only with its back against the wall did it recognize the problem.

Old Google gave us Google, Gmail - new Google has been continually making it worse and/or more evil. Maps and Android are probably a bit more of a mix though.

Regardless i'm not questing what Google _was_. I'm commenting on what Google _is_.

Not being critical of the service, but can someone help me understand here? From what i understand pricing seems the same as S3, except cheaper. So same model, just cheaper?

I say that because the text makes me think "amazing, revolutionary" but when it's the same model i feel i'm missing something. Based on it's pricing page, this service seems mostly a big deal when compared to non-AWS services which have minimums (i didn't even know B2 had that, so TIL), correct?

I suppose it also front-loads the cost, relative to AWS S3. Ie i pay $50 now, and then no monthly fees until i run out of funds again? Which might be 5yr, might be 6mo, just depends on my usage - right?

It's a neat model. I'll probably use it on the pricing alone. Though my needs download files moderately frequently, so we'll see if it ends up being good for me. I'd like to see if their UI gives me a roadmap on pricing, or better yet alerts, so i have estimated alerts on when i need to re-up my subscription.

Calling it unlimited downloads/storage though feels weird. I mean sure, it is, but so is everyone by that metric no?

Still, neat though :)

So you propose solving that annoyance by disabling the tech entirely? Maybe we should disable the browser entirely, so now you don't have annoying sites to worry about at all!

Solving a minor UX concern, easily solved by defaults and settings mind you, by deleting the feature entirely is an absurd argument.

Getting ~11 hours of my life back from commutes a week alone is worth it. That's almost a full day! (assuming 16h wake cycles)

Would i prefer in-office if i didn't have to commute? Maybe. The downsides are just not worth the upsides, though. To me.

We're talking about Google employees here. Squint your eyes and they look like the same company.

Depends on how highly they value WFH. Another job might have higher "benefits". It's all relative to the persons desires.

Yup. My thought process here[1] is that real friendships only occur from time. So you need long hours with people, whom you either get along with or you don't. You can choose the group of people to increase your odds for sharing interests or personality overlaps to help your chances, but it still requires time.

This is why work friendships in my experience are quite easy, even for an introverted hermit like myself. Often common interests between people, and _tons_ of time bonding.

If i really cared about forming more friendships i'd do what you suggested - find groups that interest me and spend the time needed to form friendships. I'm also a little weird in that while i get along with a lot of people and i am (hopefully) easy to get along with, i'm generally not interested in relationships without common interests and activities. Because i don't like to socialize purely for the sake of socializing - i like building something together, or playing something together, or enjoying food together, or whatever it is i am actually interested in.. which is usually software.

[1]: Which is probably useless, as i'm generally an introvert who still has less friends than i'd prefer.

It's a game of incentives, imo.

Companies (and people), one way or another, will always have to be expected to be greedy. This is why i'm pro-capitalism and pro-government. We can't hope for corporations to _not_ be greedy just because it's "possible". We have to expect/assume they are, and act accordingly.

Just like we can't give government entities absolute power. Checks and balances are needed in all of this. Reality is messy.

Do you see another way?

> You may not like Go's convention (indeed, I don't love it although I think it works fine in practice), but the only error handling mechanism in Go is `if err != nil { ... }`. On the other hand Rust has many. This is not incompatible with your observation of "a standardized Result type". Here is a survey of the error handling landscape circa 2019: https://blog.yoshuawuyts.com/error-handling-survey/

By this definition, Go has many too. Go has lots of libraries to wrap error types, combine errors, preserve error data, etcetc.

Errors are one of the more similar things between Rust and Go, honestly.

> Go gives you less choice, and thus projects are more similar, and thus I suspect legacy Go code adds will be easier to maintain.

Side note, Go gives you less tools - but not often less choice. Eg if you need to iterate and map, you still need to iterate and map. Go didn't change your application needs simply because it inhibited your ability to execute. Instead, you do what you need despite Go. Which often amounts to repeated functions, loops of loops, functions in loops to use defers, etcetc - you reinvent wheels. Go didn't reduce the application complexity, it just gave you less tools to solve it.

While some argue less tools is easier. I argue less tools often results in poor, messy abstractions. Those are traits that fight maintenance more than ease it, in my mind.

By the end of my Go tour, i was tired and wanted off the simplicity ride. The language was a burden, to me.

> Never should a company like amazon have access to the biometric data itself.

Perhaps that's exactly the purpose.

I agree with you; A decision that has nothing to do with them is likely to suffer massive backlash. Because if the world doesn't fit their narrative, they will make it so.

I look forward to it. Not saying it's the best strategic move by Amazon, but day by day i grow more tired of the fallout of christians.

Yea, maybe it's just fringe christians.. but if there are reasonable people in their ranks, they're happily silent. They happily co-exist with extremists, and the affect that's having on society is frustrating to me.

If they just lived their life and didn't try to bully everyone else into alignment with their beliefs i'd be more sympathetic. But the less they get special treatment these days the more "Anti christian" they claim everyone is. As if the secular population is out there attacking them. Equality seems persecution to them.

Interesting. They mention porting is possible - what would that look like i wonder? Would you make your game run under both UE4 and Godot? Or do they attempt to put a layer between whatever engine you use and the actual console APIs?

Any idea why Godot does not do consoles? Is it a licensing problem, resources problem (ie technical difficulty), or..?

I'm curious because i'm dabbling in some gamedev and wanting to eventually ship mobile and console. I'm more focused on bleeding edge tooling though, Rust gamedev specifically, but i'm curious if the reasons Godot doesn't ship to console also means any Rust project won't be able to ever, either.

Is there something preventing opensource lowbudget projects from shipping to console? Are you forced to go UE4/etc if you want to ship consoles?

Is it.. not? Or rather, what would you prefer to call it?

I've long had that opinion - it is faith, in my mind. It's very logical faith, but faith nonetheless. Not in science exactly, but in the morals, honesty and competency in the results of those performing the science. It's faith that if i was to become an expert in the field, i'd be able to recreate their exact results and deem them correct.

Is this unsound in your mind? I'm fairly anti-religious but i have no problem describing my belief in science based outcomes as faith. It doesn't feel reductive, it feels honest - to me. It takes a leap of.. something, if not faith, to trust the results of results of humans. Some science is bad, some is good, but often you lack the expertise to determine which is which. So you logically go with the common assertions and proceed from there. I do think it's logical, but i don't think that precludes it from also being faith.

How would you phrase / reason through it?

I wonder how easy and cheap i could make these? Would be neat to slowly grow a stack of these on the wall with some Pi controller and feed Wifi messages to it.

Not sure why i like it, but i do.

While i love self hosted products, am i the only one often disappointed by the backend tooling _behind_ the self hosted app? This is no fault of the app devs (Monica in this case), because it just doesn't feel like there are many (any?) good self hosting backends. Namely data storage.

Example, to run Monica locally you have to run a MySQL server. This seems .. a lot, for the average user. It also exposes hardening issues, backup concerns, upgrades, etcetc. I want to stress i don't blame Monica here, there are almost no alternate options.

SQLite is the only thing i find really great, but that just covers SQL.. and frankly i still want more even from my SQL layer. I'd love a very, very resilient storage mechanism for users. Something easily backup able. Easily merge-able in the event the user accidentally forks backups[1].

I often think i want something like Camlistore (Perkeep). Something that can store both structured and unstructured data (sql/files/etc). Something versioned, easily immutable. Something users can rsync around without fear of losing/corrupting anything. Something that apps themselves can push around for automated backups to cloud storage if desired. Super, robust. Something that doesn't require running any servers - just run the app.

I know a bunch of people are working on immutable databases, but i often see them (DoltDB) focused on being MySQL but with Git. I think i want Camlistore - a true data-dump for end users, but with better interfaces for App developers. Eg give app developers a true SQL interface, with a dumb file interface, etc.

I'm working on my own solution for this, but i doubt it'll be anything more than a toydb. I hope someone with great skill solves this problem :)

[1]: Merging is never easy, but some systems can definitely make it easier or more complicated.

> Can you show some evidence that's less than two decades old though? ;)

I don't agree with the GP comment, but, i doubt they'd make this mistake again even if they believe it.

Well yea, i wasn't saying `[char]` _is_ a `str`, rather i was positing that the GP comment was asking why it's a `str` than some hypothetical `[unsized_char]`.

I think `char` _would_ work, if it was similarly unsized like a single piece of `str`. The Problem is .. as i see it, that `[unsized_char]` seems odd.

Yea but i don't think that's what GP was asking, imo. Rather than `[str]`, i think they were asking why it's `str` and not `[char]`, no?

Just as `[u8]` is to `Vec<u8>`, `[char]` is hypothetically to `Vec<char>`.. and `Vec<char>` is basically a `String`, no?

_edit_: Though looking at the docs, `char` is 4 always bytes, so i guess that's where the breakdown would be? `char` would need to be unsized i guess, but then it would be an awkward `[unsized_char]`, which is like two unsized types.... hence `str` maybe?

I wasn't saying it does, i'm saying _we already have to do that_. Ie, this isn't a new problem. It's a well understood problem, because language is not concrete nor so well defined as to be always explicit.

It's only during when the .. "person" talks. Which makes it quite noticeable to me because it starts and stops. It is rather faint, so i might not even notice it if it was consistent.

Well i use the term courts loosely here, as it is besides my point - my point was simply that humans _already_ interpret word as allowed or not.

We do not allow all english that isn't strictly defined as bad, i thought. I can threaten you in ways that will get me in trouble but are not, by themselves, a threat. English is not that simple.

So my point is merely that it seems to be the precedent is already set for humans to moderate human english. It is not a programming language to be parsed and verified.

Not that i agree with the GP comment, but isn't that exactly the point of courts?

Eg death threats and all sorts of illegal wording are inaccurate in the literal, programming sense. Humans (courts/etc) interpret and ultimately rule if a set of vague concepts is in violation.

If it wasn't for this capability it would be hilariously easy to avoid almost all repercussion from written/spoken word by just adding a dash of vagueness to the subject. Throw in a pinch of speaking in code and you'll never be charged for any crime, yay!

I loosely agree with you, but lets not pretend that english is even remotely as well defined as a programming language in all cases.

In an example[1], it sounds decent but i noticed a fuzzy white noise whenever the voice is talking. Is this the algorithm, or compression? If it's the algorithm, why?

[1]: https://soundcloud.com/user-565970875/pocket-article-wavernn...

I'm so confused on what you're saying. Are you saying it _isn't_ what commit last occurred on the given line?

How would you explain this UI? https://github.com/git/git/blame/master/blame.c

Ie, what does blame mean to you?

Yea, it strikes me as a poor name. Cheeky perhaps. I once had someone take me aside and ask me if it was rude to use "blame" in github to figure out who touched a specific line. They thought the name implied some sort of finger pointing and fault.

I keep trying to switch back to Vim but the selection-first workflows and multicursor really keep me Kakoune.

I really want to like Vim again though, for Onivim (2). Looks so pretty.

I was a Vim user for years, tried out Kakoune and never went back. I think for many Vim users there are many possible improvements. Hell, even as a Kakoune user i'd still like to see tweaks.

But, i agree with the GP comment - i don't see anything on this intro page that tells me why i'd want to use it.