Something I’ve always found funny about the “AI will replace programmers soon” is that this means AI’s can create AI’s and isn’t this basically the end of the economy?
Every office worker is out of a job just like that and labourers only have as long as it takes to sort out the robot bodies then everyone is out of a job.
You thought the great recession was bad? You ain’t seen nothing!
The performance is just a “nice to have”.
Python package management, especially at scale is infuriating. At work we use python microservices in docker containers and it infuriates me trying to update the one our team is responsible for.
I always like to rant that python 3rd party package management tools are a mistake. We should’ve gone for an “as simple as possible” setup instead of all this.
So I’m sceptical of UV on principle since it’s yet another 3rd party package manager but if it can do all of this and not be a nightmare I’ll be ok with it.
Man I just realised there’s a Gemini button! I never actually open the app, I use shortcuts from notifications! Good on google letting users opt out of something basically no one wants!
The AOSP is a huge success and phones are really only the tip of the iceberg, android runs everywhere and is basically responsible for the mainstream adoption of “smart” devices.
It’s a small OS that runs on basically anything and you can stick it on most computers regardless of how strange the hardware setup is.
Is it perfect? No, as a project android is basically maintained by Google alone and Google obviously doesn’t think it’s perfect, or fuschia wouldn’t exist.
I’m not sure this is a fair comparison, since this is only coming to RCS and not SMS my (completely unsubstantiated) guess would be that this is a message protocol issue.
On the other hand Signal is an encrypted internet messaging service and editing internet messages has been easy for everyone not named twitter for years.
deleted by creator
It looks like it’s 3x faster than the previous cpython wasm compilation. Recall that most of the performance improvements in python have been done in the last ~2 releases.
My distro is debian based so it’s still on 3.10 which I would guess this new wasm implementation is much closer to in performance.
Compiling to wasm also means that you can distribute a binary rather than needing people to have python installed.
What mantra? I think this maintainer is doing the right thing here by trying to understand why this fix works.
You should always attempt to address the root cause of an issue instead of slapping band aid patches onto everything.
To me it looks like the maintainer is trying to find out what exactly is wrong. “this doesn’t happen in our C implementation” implies that there’s something wrong with the rust code specifically.
I guess that’s meant to be 2025 since the graph is projected? Pretty funky screw up though.
In the article it’s said that the JiT has similar performance to the latest stable interpreter but that it’s also very unoptimised. So I would assume it’s inferior to the pypy implementation right now.
FYI, this is from 2015 and was deprecated around rust v1.0 release. It’s not a current issue.
As far as I was aware Go didn’t have enums and this
const()
Pattern is just a weird thing people do because it behaves like an enum?
I’m not sure if the rules are different with macros, I’ve never written one but this lint is generally caused because you set a var to a value and then overwrite that value before you use it. e.g.
let mut a = 1; a = 2; println!(“{}”, a);
This will throw the same warning because 1 is never used, this could’ve just been:
let a = 2; println!(“{}”, a);
So first I’d double check that I NEED last at all. Maybe try:
cargo clippy
See if it can tell you how to fix it.
If that doesn’t work, it’s sometimes necessary to skip certain lints. E.g. if you make a library, most of the code will be flagged as dead code because it isn’t used and you can use an #[allow(dead_code)] to stop the linter warning. You might be able to use #[allow(this_linting_rule)].
Hope something here helps.
It’s already been said a couple times but if your more experienced team members are saying, “that’s a really weird task” the issue is probably the task not you.
Having daily meetings with a senior because you’re having a lot of trouble progressing isn’t necessarily a bad thing. Everyone has jobs that are absolute ordeals and sometimes it’s better to break them down even further and just go one step at a time.
Also, are you involved in your team sprint planning? Who says “this ticket is a 1 day job” that should be your teammates, or at least a subset of them? Why did they decide this was an easy task? What did they, or you, miss in the execution?
In my experience this does happen on occasion, it absolutely shouldn’t be happening all the time though.
Generally when this starts to happen my team lead puts his foot down and says, no more changes until you sign off on what we have and we’ve released the MVP. After all, if the core functionality is done, then the MVP is done and we don’t need to keep sitting on it.
The title is a bit misleading, the summary on the article makes it clear that YouTube kids functionality is being rolled into the main app rather than being its own thing.
In that case, this is also a yes.
My phone app(also google phone app) is only 91mb’s, Google Pixel 6, everything up to date.