I'm a technical kinda guy, doing technical kinda stuff.
@aussie.zone
I'm a technical kinda guy, doing technical kinda stuff.
It's not brilliant, it's something a software engineer should have mentioned in the first 5 minutes of the initial design meeting. It very likely was.
So what you need to understand is that mashing Bing and local results together was a deliberate design decision. Whether to artificially inflate Bing search numbers , or to get that sweet cash from sponsored results, who knows?
The CPU in an average consumer PC can do tens of billions of instructions per second now. 10,000,000,000+ instructions per second. And then it can also offload some work to other devices. Here, graphics card, deal with updating this display at 144Hz. Hey network card, take this buffer and squirt it out the ethernet port at a 1 gigabit line speed for me.
And even with all that help, it still takes for-fucking-ever to get shit done. What the fuck are all those instructions doing‽
There is a lot of "woo datacentres bad" in this article and very little actual substance.
A 4 million dollar data centre is tiny. It's not gonna have AI in it and draw gigawatts. My work has an off site redundant data centre that's essentially three shipping containers, and it cost them ten million bucks, and it just keeps a hot copy of the business data synced from a similar-sized data centre down the road.
So this very well could just be space for actual "legitimate" storage and compute for semi local businesses that want a backup far enough away so that when one burns down the other one is ok.
I had a system with an Athon 700 cpu around 2005 and somehow it was a ripping machine.
Using MythTV's built in encoder it could rip a standard feature length DVD to about 800MB in about 45 minutes, so I've got plenty of 2000's DVDs from the local video store on file still.
A few years earlier I was putting bulk Looney Tunes cartoons onto VCD for my children, pretty much wore our DVD player out with those discs haha.
Broadcom's tactic here is to dump the little fish, keep the whales. Then rake in that revenue for very little effort in support and development until budget proposals showing better alternatives are written, enterprise capital expenditure cycles around to the next refresh, and the whales finally go elsewhere.
And despite having silicon ear plugs at the last two
Are they "music" earplugs that attempt to have a flat attenuation across the whole audio spectrum? High frequency sound is the most easily attenuated by earplugs so if you use "normal" earplugs that just aim for max attenuation you might find drum'n'bass overpowering everything else.
While I agree that having a charging point at home is not mandatory, it's much much friendlier,
Even a normal outlet can handle slow charging an EV if you drive less than 100km a day.
Typical EV usage : 18kWh per 100km
Typical "granny" charger : 1800 watts (240v,7 amps)
10 hours at 1800 watts = 18kWh = 100km.
Get home at 6pm, plug in car, car is charged at 4am , leave for work at 7am. Enough spare time there to shift to charging outside peak evening usage at 9pm instead.
If you've got a toy project that you want "AI" to give you a hand with, do it now.
Pretty soon all these companies are going to have to pay for all that investment in compute resources they've been busily soaking up over the last few years, and then they're going to have to pay back their investors, and then they're going to have to try and make a profit
This is the golden time for cheap commercial AI. Already the noose is starting to tighten, and it will never again be as cheap as it is now.
Yes, it's trending in that direction, and I've been experimenting with pretty small models on my PC as I don't really have the hardware to go large. If you've got the coding chops to set it up, it's definitely something to keep an eye on.
There's actually scope for someone to set up / sell local compute hardware+software packages, similar to all those coin miners. Give the end user a way to update models, or push models out to them or something, it seems it would be a good middle ground between manually typing code like a peasant and total corporate AI apocalypse.
I don't see that at all. Perhaps you are just projecting your own issues onto Lemmy at large. I think you need to have a good hard look at yourself and your internal biases and then come back and apologise to all of us.
Conclusion: just replace the CMOS battery on a yearly basis during planned system downtime.
This appears to be more the angle of the person being fed an endless stream of hate on social media and thus becoming radicalised.
What causes them to be fed an endless stream of hate? Algorithms. Who provides those algorithms? Social media companies. Why do they do this? To maintain engagement with their sites so they can make money via advertising.
And so here we are, with sites that see you viewed 65 percent of a stream showing an angry mob, therefore you would like to see more angry mobs in your feed. Is it any wonder that shit like this happens?
Considering that some extra trackers were just added in this company's first release, it doesn't seem like it's going to be great.
Ok there's a whole lot of wtf going on here.
AI codebots in the cloud doing your code for you, cool, I guess.
So you need to watch them? And presumably intervene if necessary? Ok.
So then:
They decided that they'd stream a video of the AI codebots doing their thing.
At 40Mbps per stream.
For "enterprise use".
Where presumably they want lots of users.
And then they didn't know about locked down enterprise internet and had to engineer a fallback to jpeg for when things aren't great for them. Newsflash - with streaming video peaking at 40Mbs per user, things will never be great for your product in the real world.
How, in any way, does this scale to anything approaching success? Their back end now has to have the compute power to encode and serve up gigabits of streaming video for anything more than ~50 concurrent users, let alone the compute usage of the actual "useful" bit , the AI codebots.
For say, 5 users out of a site of 200, IT departments will now see hundreds of megabits of streaming traffic - and if they're proactive, they will choke those endpoints to a crawl so that their pathetic uplink has a chance to serve the other 195 users.
All of this for a system that is fundamentally working on maybe 5kB of visible unicode text at any particular moment.
thanks for using Leebra!
go to feed...