1,707 karma · joined April 1, 2008
Stepping back for a momement, it's clear that permissioned data is driven by real world use-cases (Bluesky needs DMs, Tangled needs private repos, etc). However, I think the synergies with the existing atproto needs to be pretty significant to warrant developing yet another encrypted space spec. We already have various double ratchet protocols, Matrix is having a huge boom. From the point of view of an app developer, does everything need to be handled by atproto, or could we accept that atproto is just for the public stuff?
Another consequence of US NatSec being gradually privatized is that once your income stream derives mostly from government spending, it becomes an imperative to influence politics to secure that stream. Yet some of these companies will remain vulnerable to shifting political winds.
It’s pretty simple, actually. Once such a dominant market position is achieved, you can get away with almost anything, whether with customers or employees. This is true of all the BigTech companies.
I would actually strengthen this to: «The core issue with Rust is that Rust still hasn’t stabilized _»
Yes, drastically. This means I'll have to wear Zuck's glasses I think, because the AI currently doesn't know what was discussed at the coffee machine or what management is planning to do with new features. It's like a speed typing goblin living in an isolated basement, always out of the loop.
My non-technical friends are essentially using ChatGPT as a search engine. They like the interface, but in the end it's used to find information. I personally just still use a search engine, and I almost always go to straight to Wikipedia, where I think the real value is. Wikipedia has added much more value to the world than AI, but you don't see it reflected in stock market valuations.
My conclusion is that the technology is currently very overhyped, but I'm also excited for where the general AI space may go in the medium term. For chat bots (including voice) in particular, I think it could already offer some very clear improvements.
Productivity has a specific meaning in economics, i.e. labor productivity (GDP per hours worked). What I think you are referring to here is output, i.e. GDP.
You can learn more about this here and see the latest country data: https://data.oecd.org/lprdty/gdp-per-hour-worked.htm
As with all things Bazel, it's great when it works, but it has a steep learning curve that could be hard to justify in many situations. You need at least one person on the team who is willing to really spend time on it.
You mean like a democracy?
I don't charge at home, but do most of my charging in the parking garage at work. This is not a fast charger (~2kW), but is wholly sufficient because I just plug it in in the morning. Alternatively, you could charge at home and not having access to any other charging would also be fine. The home charger doesn't even need to be good, because you can just leave it in overnight and even for a slow charge this will fill up aroun d 200km. The only time I actually use a "supercharger" location is for road trips.
The two most common qualms I hear from prospective EV buyers is range anxiety and time to charge. None of these are real issues for me. A full battery anyway lasts for around 400km, which is either 2 weeks of driving to work for me, or ~4 hours of roadtrip driving. After 4 hours of driving on the highway, I have no problems waiting 20min at a supercharger while I get food. Usually, the charger is actually too fast for me in this case.
Errors are too fundamental to be this hard.
This is an underrated point. This is the case for programmers in finance as well, and requires a hefty salary premium to put up with.