[flagged]
FreeCORE TrueNAS Core – Continued
31–40 of 106 posts
Re: FreeCORE TrueNAS Core – Continued
#32If you need your hand held to file share, that's why Windows Server still exists and is the gold standard for SMB.
Re: FreeCORE TrueNAS Core – Continued
#33Why does anyone bother with these ephemeral meme distros when you can accomplish the same with vanilla FreeBSD/Illumos/Linux using standard commands and documentation? If you need your hand held to file share, that's why Windows Server still exists and is the gold standard for SMB.
Re: FreeCORE TrueNAS Core – Continued
#34Worth noting that TrueNAS recently stopped publishing their build scripts, intentionally making it harder to build their open source code.[0] [0] https://forums.truenas.com/t/clearing-the-air-on-build-scrip...
It's like those SOHO router vendors that release incomprehensible tarballs of their GPL components; lotsa luck building it.
If I'm paying for closed-source ZFS, I'll go with the real thing and buy a Solaris license.
Re: FreeCORE TrueNAS Core – Continued
#35Earlier quoted context omitted.
Torvalds is mostly merging code in the kernel, not writing modules. He claims he's a manager now: https://www.zdnet.com/article/open-source-summit-linus-torva... But he's very pro-ai, though, and is vibe closing other projects like https://www.phoronix.com/news/Linus-Torvalds-Vide-Coding Linux is definitely going to speed up as it starts to get vibe coded. In a few years, I bet that it's all going to be built with ag…
Imagine calling Linus a vibe coder... go look up the definition and then re-evaluate your statement.
And why do you act like it's an insult? For most problems, reading and writing code by hand is dead. For the remainder, it will be soon.
Re: FreeCORE TrueNAS Core – Continued
#36Earlier quoted context omitted.
Why is it not enough to give you all of their code for free? Why do they also have obligations and expectations beyond that? The entitlement never ends! > At work the trend is only adopt open source on a paid plan, adopting or relying on open source otherwise is just waiting for the rug to be pulled. "Won't do free labour for our commercial enterprise to profit off of forever" is a rug pull now? It's incredible that…
They do not give all of the code. If you have an object, and don't have everything needed to reproduce the object, then you have not been given the source to the object. And with BSD licenced code this is their right. And it's my and anyone else's right to observe all of this and criticize it.
Re: FreeCORE TrueNAS Core – Continued
#37Earlier quoted context omitted.
This is disappointing, time to migrate from yet another was-open-source-now-only-technically-open-source software. At work the trend is only adopt open source on a paid plan, adopting or relying on open source otherwise is just waiting for the rug to be pulled. Essentially treat open source as closed source. How did we end up with this state of affairs?
Why is it not enough to give you all of their code for free? Why do they also have obligations and expectations beyond that? The entitlement never ends! > At work the trend is only adopt open source on a paid plan, adopting or relying on open source otherwise is just waiting for the rug to be pulled. "Won't do free labour for our commercial enterprise to profit off of forever" is a rug pull now? It's incredible that…
They're allowed to stop publishing new work whenever they want to. That's part of the free, open-source software game, wherein: We're all free to provide as much as we wish, and also free to consume as much as we want. Nobody necessarily owes anyone else anything and it's really very beautiful in these ways. This is enabled in large part due to the very low cost of distributing copies of intangible software (which can be very close to zero).
But when money gets involved, then things become different. Contracts can be had. Support requirements can be determined. If a contract requires 5 years of support, then it can be reasonably expected for support to continue for at least 5 years.
It's OK to want that, and to never use software that doesn't involve money. It's also OK for an author/company/org to not want that, and to never agree to those terms.
These are different goals, but one party doing it one way doesn't detract from another party doing it some other way. It's all OK.
Re: FreeCORE TrueNAS Core – Continued
#38Earlier quoted context omitted.
Imagine calling Linus a vibe coder... go look up the definition and then re-evaluate your statement.
He calls himself a vibe coder. I gave you the link. Who am I to call him a liar? And why do you act like it's an insult? For most problems, reading and writing code by hand is dead. For the remainder, it will be soon.
> "Also note that the python visualizer tool has been basically written by vibe-coding"
Re: FreeCORE TrueNAS Core – Continued
#39Earlier quoted context omitted.
He calls himself a vibe coder. I gave you the link. Who am I to call him a liar? And why do you act like it's an insult? For most problems, reading and writing code by hand is dead. For the remainder, it will be soon.
Linus said that this particular project was vibe coded, not that he was a vibe coder or that he's going to vibe-code everything he does from now on. > "Also note that the python visualizer tool has been basically written by vibe-coding"
He'll keep ramping up his vibe coding, because he can see it's the future.
Re: FreeCORE TrueNAS Core – Continued
#40Worth noting that TrueNAS recently stopped publishing their build scripts, intentionally making it harder to build their open source code.[0] [0] https://forums.truenas.com/t/clearing-the-air-on-build-scrip...
Doesn't this violate the whole spirit of the GPL? He's shocked that the usual suspects are ripping off GPL code. Tale as old as time. It's like those SOHO router vendors that release incomprehensible tarballs of their GPL components; lotsa luck building it. If I'm paying for closed-source ZFS, I'll go with the real thing and buy a Solaris license.