If you plan on doing it on a regular basis, you might want to try latex. This is going to be hard on the first one or two poster but on the long run it can save a lot of time…
The basic edition is free, and has all the snap to alignments you’re looking for. The pro version ($100) lets you save as an SVG, PNG, or PDF, so printing what you make shouldn’t be an issue. It’s a lot more powerful piece of software than I expected it to be.
I agree with OP, but the whole confrontation could’ve been avoided in the first place if all dependencies were spelled out to the letter in the form of a flake.nix with the latest accompanying flake.lock file.
It’s a frontend JavaScript UI library. I can’t control what other dependencies people install alongside my library, or even whether they follow my library’s dependency list.
Yes, and I have a package.json that lists dependencies and the versions I test with. You can force a different version though. I don’t think that’s what happened here. I’m guessing it’s a version of some dependency that should work, because it was released as a minor version within the range I specified, but doesn’t actually work.
It could also be an issue with the build system/bundler, which I can’t really control either.
Don’t be the guy who ignores reports that your software doesn’t work with new dependency versions just because you can’t be arsed to test with anything else even if the report looks like a legitimate problem.
That was less directed at you and more at the idea that just pinning versions solves the issue which is unfortunately very frequent among proponents of things like vendoring, nix, Docker containers and similar tools that allow a project to stay on an old version for potentially years. Sorry if that came across that way.
As someone who is out of the loop a lot, what is it about Docker that you hate? What do you use instead?
It took me weeks to wrap my head around it, but now I enjoy being able to spin something up without too much work. At work we have the whole CICD thing with Docker and K8, but I am pretty far removed from what they have to do in the run files.
What other kinds of workflows do people use these days?
I just watched this, it was a very good video, experienced a lot of the same things he did/does, thx. Was really interesting learning about the history of some these “alienated loner with god-complex” that was cultivated in early tech. Also good stuff about how the purpose for a given space shapes the discussion and interactions.
A lot of us understand the problem: that silicon-valley, in pursuit of profits and engagement, has wrecked peoples brains with traumatizing ragebait for years, and how stressful it makes all of our lives. We have to do everything we can to make these spaces the opposite: enjoyable, fun, and at the same time not addictive.
There is always a risk using libraries from others. If you install something without knowing what you are doing and without considering the risks, you should not be installing it.
You are literally sending 99% of the new Linux users back to Windows haha. C’ mon its not that hard, look at what custom ROM developers do. They put a big disclaimer warning of the risks of installing the software. You won’t find a single user blaming the devs for a bricked phone, and there are lot of them. The one who has to consider the risks and warn about them is the dev, just because (s)he is the one who knows the software better and not all users are developers and they usually don’t know what are the risks.
You can install shit in Windows too, it is exactly the same case when grandma installs too many toolbars in Internet Explorer 6. No one is warning you there that you might be installing malware.
What I mean is that there are already curated repositories for each distro that can be accessed easily by the package manager. If you go outside of your package manager and repos, gloves are off, you better know what you are doing.
Regarding custom ROMs, since you brought it up and being a custom ROM enthusiast, there are still a lot of complaints, nastiness and pressure from the users similar to this. Installing a ROM has definitely a higher knowledge barrier and that makes you aware of the risks, also you will brick your phone before you are able to install a ROM… if you don’t know what you are doing.
Finally, the developer here in this very lemmy post mentions that the OP of that bug report was working with them in order to solve the issue. The one on the screenshot was just a random dude unnecessarily being rude. Free software is usually delivered as is with no warranties, specifically small projects and libraries.
Being offensive and trying to be offensive are not mutually inclusive. And I wasn’t intending that as a personal rebuke or anything. Just commenting that, in the context of profanity censors, that is a word usually better left unsaid anyhow. Sorry if it came off as a comment on you specifically.
It depends on if the first guy is complaining about having to reinstall this specific software, or if the software borked his entire system to the point that he has to reinstall his entire OS. Because that happened to me once. But in the first scenario he is being a dick, and in the second one not so much.
I disagree, in neither scenario the open source dev owes him anything. You get to use and modify the software for free, but the flip side is you are entitled to nothing.
I can’t say I’ve spoken directly to a dev in a situation like that, thankfully, but if that opinion were dominant, FOSS wouldn’t be a thing. Destroying your data or OS is kind of a no-no, whether you pay for the software or not. Obviously, you can’t sue the FOSS dev, but come on, it’d be amazingly shitty if they didn’t even try to help if there’s any evidence it’s their fault.
Honestly, no. It’s your job to vet the software you run. If it’s open source, you had every chance to make sure it wasn’t going to irreversibly break your system ahead of time.
Alternatively, you could pay money for a solution from a reputable company with support.
??? You quoted my comment with ‘reputable’ in it. You put a level of trust in anything you use. Reputable companies are unlikely to fuck your shit up with bad software. It happens - not trying to say it doesn’t - but again, you have to trust somewhere.
You’re implying that to even install the simplest of programs, I’d need to read and understannd many thousands of lines of code, starting with the FOSS project itself and then spidering out to every dependency. This speaks nothing of the fact that it may be written in multiple languages, some of which I am not familiar with, and even if I am, code can be written in ways that’s almost impossible to understand. This might take a week for a 200 line project.
Reminds me of when my employer said they were going to stop using open source software until a team had vetted it completely. Lol, once they talked to engineers that idea died immediately.
Legal obligations that I grasped at age 9 don’t really interest me to talk about. It’s pretty obvious I understand them. What I was trying to talk about was what reasonable people should do. But apparently that’s offensive to many ITT as most responses are condescending af
You’re right to an extent, but there is nuance. No end user goes through the Debian repositories and checking the source code for each package by hand. You would be well within your rights to be annoyed if a rm -rf / got added into a script in the repos somehow. A level of trust somewhere is unavoidable for things to work smoothly.
Of course the difference in level of responsibility between core repos and random code pulled of github is vast.
I can see how you got there, but I’m actually not saying you need to understand any programming languages at all. If the code is out there, and the product is worthwhile, the community can and will vet it.
Like I responded to the other guy, you put a level of trust in anything you use. You can pay for a product and expect polish and support, or you can go the open source route, the DIY hobbyist route, and expect to have to do more yourself. You might have to do research on a product before you trust it. This isn’t a radical concept to me. If I was putting together an RC car, I would do research on the motor to make sure it was unlikely to fail catastrophically.
That’s absolutely a ridiculous stance. Yes, you can personally go through everything, but there’s also searching around to find out what other people say about it, actually look through the issues people have raised. Some of it applies to proprietary software as well, find out what other people say about the software. You don’t need to do everything yourself, but you do have to take responsibility for trying to make sure it will work as you hope it will.
Right? And it seems like no one is interested in understanding my point, most only seem interested in defending developers of FOSS. I understand there is no legal obligation from FOSS devs… That is irrelevant.
I love FOSS. It’s one of the best products of humanity. I am not attacking devs at all…
My point was only that while devs don’t owe anyone anything legally, if the rare edge case happens where their code is destructive by accident, it would be a dick move to ignore complaints about it. I guess because it didn’t spell it all out like this, I “deserved” all the downvotes (on since-deleted comments) and condescending remarks?
Yes I know that if I use Firefox I can’t sue them if somehow they wipe my OS. Yes I know that would probably never happen, it’s extremely unlikely to happen. But if it did, FF owes us at least a response. And I means owes in the sense that it’s the right thing to do, not “if you don’t do it I can sue you”.
You are entitled to the truth. If the dev knows their software could have very damaging effects then that should be front and center on the software page.
Usually it is? But ultimately it’s still your own responsibility. You did not pay the dev, the dev does not ask you to pay them, ergo the dev owes you diddly squad.
Let’s be decent with each other, I don’t think my expectations are outrageous. I consider decent to make sure that the person that will use your software is aware of the dangers. And the best person to know those dangers is usually the dev.
In this case, in trying to resolve the issue, he deleted his node_modules directory. So he’s talking about having to reinstall everything by typing npm install and waiting for it to finish.
No. It’s provided without warranty nor guarantee that it’ll work or even leave your system intact. That’s the core of most opensource licenses. Dev owes nobody nothing.
I didn’t say anyone owed anyone anything. I was saying one level of frustration was understandable, one was not. Anyhow, my case happened twenty years ago when creative commons barely existed.
No, not sue me for lemmy comments. AI is trained with lots of data. The world wide web is full of publicly accessible data like our comments. However, not all publicly accessible data may be used without a license. Examples thereof are news paper articles, videos, still pictures, etc. Normally, if you want to use those commercially, consent has to be given by the license holder and a in some cases a fee has to be paid.
Microsoft Copilot is an AI model to help people write code. However, it was trained mostly on opensource code (code made publicly available) which was very often licensed. And it is done so in such a manner that commercial use is allowed with the obligation to make that commercial code publicly available too. Microsoft does not make the code for Copilot publicly accessible and uses code licensed in many, many other ways - and it does so without asking for consent.
This is often a double standard as companies that hide their code fight very hard to keep it secret and/or pursue those in court who do not get a license to use it. However, they will happily use licensed consent to their benefit without consent nor potential payment.
With some clever tricks, AIs have been duped into revealing their training data (often licensed, sometimes very private e.g addresses, birthday, health information, etc.). Lawsuits have ensued (against the AI owners like Microsoft) and are currently active with a pending verdict. Until the verdicts come, I add the license link to my comments. Who knows, maybe it will have an impact, maybe not.
Hopefully I could explain the situation in an understandable manner for you.
The funny thing is that since it’s an actual word the spell checker might not be of any use to see that it might not be the word you’re actually wanting to use. And with the amount of people using “payed” instead of “paid” the dictionaries will probably include “payed” as an alternative way to conjugate “to pay” in the currency sense.
Me approaching Foss developer with bug: Pardon me, if you could grace this lowly worm with but a moment of your attention; I with me a bug report, and I believe I have found the section of code responsible. This inadequate being lacks the technical expertise to fix it and would be eternally indebted if you would turn your monumental skills upon its trifling problems. It would please me immensely if my paltry efforts were of some assistance.
You’ve clearly never worked with any psychopaths or narcissists. Often, pointed (though importantly, carefully offline and undocumented) cruelty is one of the only ways to effectively punch back and make people like that stop trying to fuck with you, because many people like that only really respond to threat dynamics. It’s not terribly common, and it’s not fun to do, but it definitely is warranted once in a blue moon.
Thanks. Send a complete log of every software on your system, two videos of the bugs in action, and a detailed analysis of what you’ve had for breakfast.
It is, until it isn’t. I’ve seen devs delete or abandon their projects because of too mush abuse. Nobody likes being yelled at. (Unless that’s your kink. I won’t judge.)
opensource
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.