W10… Nothing.
W11, some bullshit popover sidebar thing that takes up actually (Literally? Factually?) 50% of my desktop that tells me about the NASDAQ, the weather, some “local” roadworks in the next city over (when my street has roadworks blocking some significant traffic lights in the literal capital of my country), some recommendations for games, a shopping ad, and some bullshit news headlines that I don’t care about.
Basically “professional software” that isn’t tech related.
There are fantastic alternatives that are (nearly) transparent for individual users.
There are BETTER alternatives for some software.
But working in a team/company that doesn’t prioritise Linux accessibility is painful. And it’s pain that people aren’t paid to deal with to complete their actual workload.
MS has corporate by the balls.
As a hobby developer, I feel like I’m just gluing libraries together to get what I want.
Server hardware does.
I think dell Rx30 are only just getting to EOL, and it was released in 2015.
Although, buying an Rx30 before 5 years ago would be in the 10s of thousands.
Refurbished Rx40 and Rx50 are somewhat affordable.
I keep trying to find Arch BTW, but the download page doesn’t list it
Which applies to EU countries.
Not sure if apple is going to do separate builds for separate regions
If you want remote access to your home services behind a cgnat, the best way is with a VPS. This gives you a static public IP that your services connect to, and that you can connect to when out and about.
If you don’t want the traffic decrypted on the VPS, then tunnel the VPN back to your homelab.
As the VPN already is encrypted, there is no point in re-encrypting it between the vps and homelab.
Rathole https://github.com/rapiz1/rathole is one of the easiest I have found for this.
Or you can do things with ssh tunnels.
For VPN, wireguard is very good
Worth reading the article, but for the TL:drs and comment readers:
- A patent attorney has narrowed down the list of potential candidates that could be central to Nintendo’s lawsuit against Palworld developer Pocketpair to 28 patents.
- Out of those, one particular intellectual property describing creature-capture mechanics was labeled as a “killer patent” that would be difficult not to infringe when making a game with monster-taming elements.
- The said property is part of a recently approved patent family consisting of three more patents, all of which were approved mere weeks before Nintendo and The Pokemon Company sued Pocketpair.
You can set a static IP on the router, disable it’s DHCP, and have pihole manage DHCP with the routers static IP as the gateway
Like I said, impressive work.
Converting science to shaders is an art.
I guess your coding standards follows scientific standards.
And I guess it depends on your audience.
I guess the perspective is that science/maths formulae are meant to be manipulated. So writing out descriptive names is only done at the most basic levels of understanding. Most of the workings are done on paper/boards, or manually. Extra letters are not efficient.
Whereas programming is meant to be understood and adapted. So self-describing code is key! Most workings are done within an IDE with autocomplete. Extra letters don’t matter.
If you are targeting the science community with this, a paragraph about adapting science to programming will be important.
Scientists will find your article and go “well yeh, that’s K2”. But explaining why these aren’t named as such will hopefully help them to produce useful code in the future.
The fun of code that spans disciplines!
Edit;
Om a side note, I am terrible at coding standards when I’m working with a new paradigm.
First is “make it work”, after which it’s pretty much done.
Never mind consistent naming conventions and all that.
The fact you wrote up an article on it is amazing!
Good work!
Interesting.
I love creative applications of shaders. They are very powerful.
In my opinion only, but willing to discuss.
And I’ll preface this by saying if I tried to publish a scientific paper and my formulas used a bunch of made up symbols that are not standardised, I imagine it would get a lot of corrections on peer review.
So, from a programming perspective, don’t use abbreviations.
Basically working on naming.
I can read that TAU is the diffusion rate due to a comment. Then I dig further into the code as I am trying to figure something out and I encounter tau. Now I have to remember that tau is explained by a comment, instead of the name of the variable. Why not call it diffusionRate then have a comment indicating this is TAU.
A science person will be able to find the comment indicating where it is initialised and be able to adjust it without having to know programming. A programming person will be able to understand what it does without having to know science things.
Programming is essentially writing code to be read.
It’s written once and read many times.
Similar with the K variables.
K is reactionRate.
K1 is reactionKillRate.
K2 is reactionFeedRate.
Scientists know what these are. But I would only expect to see variables like this in some bizarre nested loop, and I would consider it a code smell.
The inboundFlow “line” has a lot going on with little explanation (except in comments). The calculation is already happening and going into memory. Why not name that memory with variables?
Things like adjacentFlow and diagonalFlow to essentially name those respective lines.
Could even have adjacentFlowWeight and diagonalFlowWeight for some of those “magic numbers”.
Comments shouldn’t explain what is happening, but why it’s happening.
The code already explains what is happening.
So a comment indicating what the overall formula is, how that relates to the used variables, then the variables essentially explain what each part of it is.
If a line is getting too complicated to be easily understood, then parting it out into further variables (or even function call, tho not applicable here) will help.
I would put in an editted example, however I’m on mobile and I know I will mess up the formatting.
A final style note, however I’m not certain on this.
I presume 1. and 1.0 are identical representing the float value of 1.0?
In which case, standardise to 1.0
There are instances of 2.0 and 2.
While both are functionally identical, something like (1.0, 1.0, 1.0) is going to be easier to spot that these are floats, as well as spotting typos/commas - when compared to (1., 1., 1.,).
IMO, at least
Sounds like a long-awaited race condition finally coalescing.
The boot splash screen would expect the drivers to be ready, and will hang/timeout if it isn’t ready when it tries to render the splash screen
I can say I’ve never glorified suicide. When I’ve been suicidal, suicide is literally the only logical solution my brain can arrive at. It’s completely irrational in hindsight, but it makes so much sense at the time.
I don’t think I have ever not-watched something due to content warnings alone. But it has alerted me that there may be issues, so it doesn’t surprise me when it comes up.
It’s from 2015, so its probably what you are doing anyway
A technical reason is because he has been a president before
I have 3nm ~in my pants~
I would say the more regular expiration and renewal of an LE cert is better.
It’s an ongoing check instead of an annual check.
At the homelab scale, proxmox is great.
Create a VM, install docker and use docker compose for various services.
Create additional VMs when you feel the need. You might never feel the need, and that’s fine. Or you might want a VM per service for isolation purposes.
Have proxmox take regular snapshots of the VMs.
Every now and then, copy those backups onto an external USB harddrive.
Take snapshots before, during and after tinkering so you have checkpoints to restore to. Copy the latest snapshot onto an external USB drive once you are happy with the tinkering.
Create a private git repository (on GitHub or whatever), and use it to store your docker-compose files, related config files, and little readmes describing how to get that compose file to work.
Proxmox solves a lot of headaches. Docker solves a lot of headaches. Both are widely used, so plenty of examples and documentation about them.
That’s all you really need to do.
At some point, you will run into an issue or limitation. Then you have to solve for that problem, update your VMs, compose files, config files, readmes and git repo.
Until you hit those limitations, what’s the point in over engineering it? It’s just going to over complicate things. I’m guilty of this.
Automating any of the above will become apparent when tinkering stops being fun.
The best thing to do to learn all these services is to comb the documentation, read GitHub issues, browse the source a bit.
Back when Blockchain was first a huge hype bubble, there were companies that added “Blockchain” to their name, or announced a pivot into Blockchain tech, and watched their stock value soar by a few hundred percent (with market value being many times their revenue).
I had googled a list of news articles, until I found this:
https://www.sciencedirect.com/science/article/abs/pii/S0165176519301703
A noteworthy example: https://www.cnbc.com/2017/12/21/long-island-iced-tea-micro-cap-adds-blockchain-to-name-and-stock-soars.html
Anyway.
That’s the bubble.
Over-valuation. People taking advantage of the hype. People jumping on any opportunity to “not be left out” or to “get in early”.
AI has uses.
Everyone is throwing things at the wall to seeing what sticks. Not much of it will.
Marketing are capitalising on the hype.