[-] doodoo_wizard@lemmy.ml 35 points 4 weeks ago

The other reply is a good answer, but also dropping a video with no context or explanation is a hallmark of content spammers and growth hackers.

Even if looking like a crappy kind of poster isn’t enough to dissuade someone from just dropping a link and fucking off, providing some context and input to how and what the link will do and what it means as a post in the particular community is a lot better behavior and starts a conversation as opposed to doing nothing.

[-] doodoo_wizard@lemmy.ml 31 points 1 month ago

The mit license allows someone (some company) to modify the open source codebase and sell the result without making their modifications public.

It allows the software equivalent of the enclosure of the commons.

If there was a particularly large or significant and widespread codebase —like for example the coreutils— that was used everywhere and mit licensed, a company could make their own slightly different coreutils without publicizing the differences and use their position in the market to enclose the commons of knowledge about the use of that software. Such a situation would lead to a fractured feature ecosystem and confusion around best practices. In that environment, the biggest and most popular software distributor would benefit because their product would be most common and therefore the best target to design around.

I know there’s a lot of “coulds” and “woulds” in that sentence, but that’s exactly what happened in the 80s and 90s with the ostensibly open source Unix codebase and the reason why the gpl was invented.

[-] doodoo_wizard@lemmy.ml 57 points 1 month ago

~~Rust based~~ MIT licensed coreutils

[-] doodoo_wizard@lemmy.ml 33 points 1 month ago

Could that happen? No. A massive amount of android development comes from employees paid by google to do it. What amount of resources should be siphoned away from linux/gnu stuff to support android developers? None.

Is it possible though? No. Android is a proprietary binary blob core (idr if kernel is the right term) with a bunch of open source stuff wrapped around it. For gnu, that part would have to be rewritten and that’s too big a job to take on.

Should it happen? Again, no. There are already plenty of alternatives to google branded android. Just use those.

Even if you were to wave a wand and make the android custodians according to your will, play services, the thing google is restricting, is still googles thing.

[-] doodoo_wizard@lemmy.ml 43 points 1 month ago

Every euro country or agency that has done or announced this has simply used it to extract concessions from Microsoft and either stayed with or switched back to windows.

[-] doodoo_wizard@lemmy.ml 21 points 1 month ago

Yeah I guess if you’re constantly slamming your penis in the car door than having a button that turns back time would be one approach.

[-] doodoo_wizard@lemmy.ml 61 points 1 month ago

As usual the real damage of a source leak isn’t other companies cloning and selling your flagship product, which numerous well established legal frameworks exist to counteract, but everyone realizing how bone crushingly stupid you and all the people you’re paying millions to write the product clearly are.

[-] doodoo_wizard@lemmy.ml 20 points 3 months ago* (last edited 3 months ago)

Fair warning, if you apply enough scrutiny to any big distribution you’ll find tons of stuff like this.

Theres some awesome schizo timecube esque website that documents Debian (my chosen distro) mess in great detail. I’ll edit in the url if I can find it.

E: found it: Debian History Harassment & Abuse culture evolution

If you can’t be a truther about something you’ll lie for anything I guess

[-] doodoo_wizard@lemmy.ml 26 points 3 months ago

Yeah it’s fine.

[-] doodoo_wizard@lemmy.ml 24 points 4 months ago

Like the other person, I’m disgusted by this. Aside from an educational case, where a person can use a simplified version to establish context and use it to learn how to read the original (which seems dubious), what’s an argument for this?

[-] doodoo_wizard@lemmy.ml 36 points 5 months ago

Reseat the stick you installed and run memtest 86.

It’s more likely that you have a badly installed stick or a faulty stick than consumer memory controllers in the last 20 years care about the installed memory being the same.

[-] doodoo_wizard@lemmy.ml 23 points 5 months ago* (last edited 5 months ago)

You’re getting bad advice.

If you don’t expect to actually be shuffling packets back and forth or doing any kind of quality of service or vpn or really anything then the pi will be the better choice just barely because of its super low power consumption at idle. In that situation you would be at idle enough to actually justify using the pi. It would suck in the same way that using a pi for stuff usually sucks but you could justify it maybe.

If you plan to have a bunch of hosted stuff, a seedbox, qos, manage vpn connections and especially upgrade your lan to 1gb + later on down the line, the mini pc will actually be more efficient per cycle. In that circumstance you’d be at idle less, and the mini pcs more powerful processor, wider bus and expandability would make it less of a bottleneck presently and down the road.

Risc CPUs like the arm in the raspberry pi are really good at not doing anything, or doing a really small subset of things (it’s in the name!), but x86 is great at doing some stuff and being able to do a wide variety of stuff with its big instruction set. If you raise an eyebrow at my claim, consider that before gpus were the main way to do math in a data center it was x86. If the people who literally count every fraction of a watt of power consumption as billable time think it’s most efficient it probably is!

With ~08+ CPUs ability to turn cores and functions off at the clock tree and communicate back and forth with the os to orchestrate and coordinate it, there’s not as much daylight between the power usage of a pi and a mini pcs as some of these comments might make you think.

The long and the short of it is that you’ll most likely have a better time using the mini pc than the pi and claims that it’ll bankrupt you with power bills are greatly exaggerated.

In terms of privacy, I’d go for the mini pc. All your packages are most likely going to be open source, but the x86 stuff gets more scrutiny and isn’t as “magic blobby” as the arm world is.

Source: I have used over twenty different pi variants including knockoffs, wrote for microcontrollers before they were called sbcs, host a bunch of services on x86 which are monitored for their power usage using a power distribution controller by my lovely wife who keeps an eagle eye on the bills and I literally registered an account because people were telling you the wrong thing on the internet.

If you wanna verify that for yourself, get a cheap plug em in power meter and try both units running the package you choose under some artificial load like managing qos between a device streaming 4k and one torrenting 50 different Linux isos.

view more: next ›

doodoo_wizard

joined 5 months ago