The IPv6 range is barely even used.
Yet.
Also I imagine that there will be a secondary market for IPv6 at some point.
Like there already is one for IPv4 addresses?
I stand by my point:
No-one will ever need a /48 range.
Somewhere between Linux woes, gaming, open source, 3D printing, recreational coding, and occasional ranting.
🇬🇧 / 🇩🇪
The IPv6 range is barely even used.
Yet.
Also I imagine that there will be a secondary market for IPv6 at some point.
Like there already is one for IPv4 addresses?
I stand by my point:
No-one will ever need a /48 range.
The ranges will become larger over time because “we have it”, and companies will get thousands of sections with figuratively unlimited IP addresses in them each.
With this huge ranges we’ll have the same problem with IPv6 in a few years that we already have with IPv4.
They not only force their user to buy their crap, they also intentionally and maliciously frame the AGPL in a certain way.
I am sure fans will find a way to make it happen.
I am pretty sure they will.
Spicy Pillow!
I did not, but of course you can. Either by using an adapter (maybe a printable one?), or – if it is an SSD – by just placing the drive there and hld it in place with one screw.
If there already is a drive installed you want to removed and there is no spare cover, you can also print one.
(You can of course buy the parts instead of printing them. Those adapters and covers are fully standardized and widely available.)
Digital for things you consume. Physical for things you love.
I wish you wouldn’t use GitHub but an open source forge, though.
There will always be this one asshole of a coworker who happily name-dropping you in a conference call with the project owner.
Why are people still accepting this?
Write an ungodly large amount of code-comments - up to a point where you add 20 lines of explanations to a 6 lines long function where two lines are variables assignments.
Source code is for humans to read. The compiler ignores the comments.
Okay, bye!
Yep! The functionality for performing arithmetic expressions this way is called “arithmetic expansion”.
2.6.4 Arithmetic Expansion
Arithmetic expansion provides a mechanism for evaluating an arithmetic expression and substituting its value. The format for arithmetic expansion shall be as follows:
$((expression))
The expression shall be treated as if it were in double-quotes, except that a double-quote inside the expression is not treated specially. The shell shall expand all tokens in the expression for parameter expansion, command substitution, and quote removal.
Next, the shell shall treat this as an arithmetic expression and substitute the value of the expression. […]
https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html#tag_19_06_04
That is a posixly correct method to do arithmetic expressions.
I gave up Bash scripting. I explicitly do “shell scripting” now, where “shell” is implied to be a POSIX compliant shell of any type.
Always has been like that.
Not one single corporation is your friend or wants to be. All they want is your money. No exceptions.
To me, this is the worst issue here.
Even large Projects suggest things that are basically
curl | sh
– without even mentioning anything about how this could be problematic.New user are “trained” doing this.
Every project suggesting it should be not only opposed but actively fought against until they change this bullshit.