It's glorious. The year has finally come. It's nice to feel excited about tech sometimes, especially when the company isn't completely horrible, and more competition! Great! Microsoft's move really, Sony and Nintendo are doing pretty okay!
Yep, we're not! (From a hc'er). Zach announced that slack has gifted us half a decade of enterprise+. Whilst slack's behaviour is worrying, it probably wouldn't make sense to cut all ties. Either way- another 5 years to migrate! :-)
I feel like there's a bit of survivorship bias here. Not saying that vibe coding is completely useless, but you still have to review the code it produces in order to make the most of it really. It isn't completely autonomous (yet) to the point where it can scale to any of the examples you mentioned imo.
In principle, not at all. But there is no way to do this properly at all. No matter how secure the companies that do this say it is, it's another possible vulnerability.
You can't play whack a mole with the internet. People will always find a way to move smut or whatever on the internet. It takes no time at all to spin up more and more sites, and there's a million ways around them (vpns, etc).
All it does it just push people to more and more fringe sites, when moderation is likely to be lax and the content more extreme. Ideally it wouldn't be viewed at all, but it's just how the internet is.
It also sets a terrible precedent for censorship- in the UK, we've already seen, on Reddit for example, subreddits dedicated to quitting addictions being age gated, and it'll only get worse.
The European Commission's proposed interim solution for age verification (ageverification.dev) is actually pretty good vs the shitshow of the US and UK.
It works like this:
1. You contact an age verification provider (e.g., national eID schemes, banks, or mobile operators) and provide proof of identity, which they will verify possibly against government databases or whatever, etc. Once they confirm your age they will issue you with a bunch of Age attestations. At this point you don't even know where you will use these, so that info literally cannot be sent to the provider. The attestations are a JWT-like envelope with a payload conceptually equivalent to `{"nonce": "LARGE_RANDOM_HEX_STRING", "age_over_18":true}`, signed with the provider's public key. (The actual implementation is more complex).
2. This is stored in a local app, which will guarantee each attestation only gets used once (to avoid linking user across relying sites). There is no special authentication of the app in the protocol with the replying site, so you can write your own. The Commission provides an open source reference app. There is a standard protocol for communicating with verification providers, however it is not mandatory, so using the reference app might not support all verification providers, but should support a variety.
3. When you want to visit some site needing age verification, and you already have a verified account, you just sign in, otherwise, that site will use a standardized protocol to request proof from the app. The app will provide just the attestation token. The relying site does not get any info about your identity, other than the attestation token. Plus of course, the relying party must accept any age verification provider approved by the commission, not just its preferred one. The EC's solution also supports the app providing the relying site a Zero-Knowledge Proof of having such a token, which makes it possible for the relying site to learn the user's identity even if colluding with the age verification provider.
Try what exactly? Its illegal to stream movies for free, but there are hundreds if not thousands of illegal streaming sites. How would porn access fair any better at being regulated away?
If you're using a Samsung device then you can use Screen Curtain within Samsung's Good Guardians application on the Galaxy Store, which allows you to play media with the screen turned off.
Triggers most of the wrong people. You know, those that aren't even mentioned by someone him in this case but are still offended like they're being tortured. THat sort.
Kotlin, the Android language, isn't owned by Google. it's from Jetbrains. Picking Kotlin is one of a few great decisions Google has done for Android IMO.
They actually are not. Take a look at say the two most popular languages to come out of Google being Go and Dart… none of those communities ever really feel hard done by, the tooling is great, the documentation is amazing, it runs everywhere, it’s fast, it’s easy to work with, has excellent cross language interop and they are just generally well supported.
I think you’re just going on vibes here but it’s kind of bullshit when you think about it for more than a moment.
People that have been around Dart long enough absolutely felt hard done by. That project burned so much community good will on the way to finally getting slight traction with Flutter.
I’m actively a part of that community for the past 5 years and I have zero idea what you’re talking about. It’s one of the most loved languages out there when you look at surveys of its users and for good reason.
Half a decade is more than enough time for me to be able to say with a really high degree of confidence and authority that I’m positive that the situation with Google and Dart is in fact not at all like the situation with Apple and Swift as the OP was implying.
Also the Android and iOS development experiences are vastly different. Android is much more pleasant to work with. Android Studio exists but you don’t need to use it, unlike XCode. I’m very happy writing Android apps using vim and adb.
I develop for both platforms and don’t agree at all. The Android dev experience has a lot of potential to be good, but it’s dragged down by the unmitigated messes that are Gradle and ProGuard, both of which regularly cause more pain for me than their iOS counterparts (Swift Package Manager and clang’s code stripper).
It’s also only been relatively recently that Google has decided it’s ok to be opinionated and provide happy paths for devs to follow in their UI library with Compose. Android Framework was/is notorious for having 5 ways to accomplish any given task and none being “right” or the only one capable of doing what you need being deprecated.
And then there’s Kotlin, which is so close to being a great language but dies on weird hills ideologically (e.g. please just give me “if let” syntax, “.let {}” is ugly and automatic unwrapping fails just enough to not be useful).
Freedom of editor is nice but doesn’t make up for the rest, at least for me.
> it’s dragged down by the unmitigated messes that are Gradle and ProGuard
its crazy looking back though, when android studio first came out there was a big hope it would be better than ant but idk personally i also hate gradle with a passion...
> “if let” syntax, “.let {}”
probably guard let would be even better since it avoids indenting on the happy path but jmo
W shadow drop.