no you didn’t Mr. Simpson, no one can
Oliver Lowe
- 0 Posts
- 37 Comments
Joined 2 years ago
Cake day: June 13th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
well there was probably awareness of ideas of sacrifice, punishment, right/wrong. Old ideas…
12·1 year agoAM radio paywall? Where?
I suppose there’s positive, then there’s “totally changed how I work”. It’s a big call. Maybe a real-world example would make it sound more believable: “before ChatGPT, I would have to sift through stacks of outdated VB6 documentation on $task. This took up most of the day. Yesterday I used a LLM to get a basic implementation of $task then I tidied it up and installed it within an hour.”
10·1 year agoBYD employ about 570,000 people and by some measures are the largest carmaker in the world. I’d never heard of them either until a couple years ago. They’ve definitely got the cash to put into PR like this. Past couple years Australia started importing their electric cars. https://en.wikipedia.org/wiki/BYD_Company
Ah come on, we all know as software people we can never stop the spreadsheets from being the real data interchange format ;)
Yes that’s true. I guess what I wanted to point out is that GitLab has dependencies like Postgres, Redis, Ruby (with Rails), Vue.js… whereas Forgejo can use just SQLite and jQuery.
Something not mentioned yet: Forgejo, the software running Codeberg, has a smaller feature set and narrower scope than GitLab (“GitLab is the most comprehensive AI-powered DevSecOps Platform” from their website).
Forgejo is much easier to administrate for smaller groups. For example compare the dependencies mentioned in the Forgejo installation documentation and the Gitlab installation documentation.
how can a writer be so ignorant.
They probably know exactly what they’re doing. Singling out Japan makes for a “better” headline to a mostly North American audience.
It’s also a bit of a clever headline. Compare the original headline and this one: “All major automakers continue to produce sports cars”. Both headlines could technically be true.
But the original headline lets you get away with stirring up some emotion e.g. “Japan alone is keeping the sportscar industry afloat, European, American manufacturers don’t care, sportscars are dying”. Life, death: strong words! It’s misleading and shitty journalism.
I wonder if their compositors would be laggy and bloated with features, too?
We can never know exactly. For me I always think about the (incidental) complexity of these huge apps like Instagram.
Somebody mentioned the phone overheating when watching Reels - those short videos. Here’s a made-up example (but I’ve written some software for video streaming services)…
Those videos are pretty short, and some people skip the clip even after less than 1 second. Instagram want that next video to be playing instantly (gotta get that dopamine hit ASAP!). A strategy you could take is have the app load the next, say, 5 possible videos in the background before you’ve even seen them. When the user swipes, that video is already playing. To make this even faster we could execute some recommendation decisions on-device rather than on some servers (over a relatively much slower 4G connection).
With all this complexity comes greater chance of some unexpected behaviour. Instead of loading 5 videos, maybe we accidentally load 100 and never clean up the old ones. Maybe after an OS update we need to change the way we mark a task as low priority.
Cool insight - thanks! All points even more to bad planning by the Instagram team as you said originally.
I guess I wouldn’t be particularly surprised. Apple put shitloads of R&D into power-efficiency. Can’t imagine the culture at Instagram/Meta is like that.
I can imagine it’s a collection of bugs where it’s sorta the OS’ problem but sorta the application’s problem. It probably reached a stalemate. Nobody really wanted to spend the extra engineering effort; maybe it would all have to be undone then rewritten again to get something out in time.
Thanks. I see what you mean. When I first started reading about the topic someone brought up low-background steel: https://en.wikipedia.org/wiki/Low-background_steel Grim but relevant topic!
the more degenerate they become over time.
To clarify, by “they” do you mean the language models?
and log files eating up storage space was a common culprit.
Another classic symptom of poorly maintained software. Constant announcements of trivial nonsense, like
[INFO]: Sum(1, 1) - got result 2!filling up disks.I don’t know if the systems you’re talking about are like this, but it wouldn’t surprise me!
of course!